HTTPAuth Working Group J. Reschke
Internet-Draft greenbytes
Updates: 2617 (if approved) September 11, 2013
Intended status: Standards Track
Expires: March 15, 2014

The HTTP Basic Authentication Scheme


[rfc.comment.1: TBD]

Editorial Note (To be removed by RFC Editor before publication)

Discussion of this draft takes place on the HTTPAuth working group mailing list (, which is archived at <>.

XML versions, latest edits and the issues list for this document are available from <>.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress”.

This Internet-Draft will expire on March 15, 2014.

Copyright Notice

Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents ( in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

Issues list

Id Type Status Date Raised By
edit edit open 2013-09-11
 I  edit   (type: edit, status: open) 2013-09-11 Umbrella issue for editorial fixes/enhancements.

1. Introduction

[rfc.comment.2: TBD]

2. Notational Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

3. The 'Basic' Authentication Scheme

[rfc.comment.3: Copy from RFC 2617.]

4. Security Considerations

[rfc.comment.4: Copy rom RFC 2617 and augment.]

5. IANA Considerations

[rfc.comment.5: Register the scheme.]

6. Acknowledgements

[rfc.comment.6: Ack RFC 2617 authors and new contributors from HTTPAuth.]

7. References

7.1 Normative References

[RFC2119] Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels”, BCP 14, RFC 2119, March 1997.
[draft-ietf-httpbis-p7-auth] Fielding, R., Ed. and J. Reschke, Ed., “Hypertext Transfer Protocol (HTTP/1.1): Authentication”, Internet-Draft draft-ietf-httpbis-p7-auth-23 (work in progress), July 2013.

7.2 Informative References

[RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, “HTTP Authentication: Basic and Digest Access Authentication”, RFC 2617, June 1999.

Author's Address

Julian F. Reschkegreenbytes GmbHHafenweg 16Muenster, NW 48155GermanyEmail: julian.reschke@greenbytes.deURI: