[IPP] Fwd: [http-auth] RFC 7617 on The 'Basic' HTTP Authentication Scheme
Michael Sweet
msweet at apple.com
Thu Oct 1 13:08:53 UTC 2015
> Begin forwarded message:
>
> From: rfc-editor at rfc-editor.org
> Date: September 30, 2015 at 7:39:35 PM EDT
> To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
> Cc: drafts-update-ref at iana.org, http-auth at ietf.org, rfc-editor at rfc-editor.org
> Subject: [http-auth] RFC 7617 on The 'Basic' HTTP Authentication Scheme
>
> A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 7617
>
> Title: The 'Basic' HTTP Authentication Scheme
> Author: J. Reschke
> Status: Standards Track
> Stream: IETF
> Date: September 2015
> Mailbox: julian.reschke at greenbytes.de
> Pages: 15
> Characters: 30163
> Obsoletes: RFC 2617
>
> I-D Tag: draft-ietf-httpauth-basicauth-update-07.txt
>
> URL: https://www.rfc-editor.org/info/rfc7617
>
> DOI: http://dx.doi.org/10.17487/RFC7617
>
> This document defines the "Basic" Hypertext Transfer Protocol (HTTP)
> authentication scheme, which transmits credentials as user-id/
> password pairs, encoded using Base64.
>
> This document is a product of the Hypertext Transfer Protocol Authentication Working Group of the IETF.
>
> This is now a Proposed Standard.
>
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and suggestions
> for improvements. Please refer to the current edition of the Official
> Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
> standardization state and status of this protocol. Distribution of this
> memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
> https://www.ietf.org/mailman/listinfo/ietf-announce
> https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/rfc.html
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> Association Management Solutions, LLC
>
>
> _______________________________________________
> http-auth mailing list
> http-auth at ietf.org
> https://www.ietf.org/mailman/listinfo/http-auth
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
More information about the ipp
mailing list