draft-ietf-httpauth-basicauth-enc-01.txt   draft-ietf-httpauth-basicauth-enc-02.txt 
HTTPAuth Working Group J. Reschke HTTPAuth Working Group J. Reschke
Internet-Draft greenbytes Internet-Draft greenbytes
Updates: 2617 (if approved) June 30, 2013 Updates: 2617 (if approved) February 4, 2014
Intended status: Experimental Intended status: Experimental
Expires: January 1, 2014 Expires: August 8, 2014
An Encoding Parameter for HTTP Basic Authentication An Encoding Parameter for HTTP Basic Authentication
draft-ietf-httpauth-basicauth-enc-01 draft-ietf-httpauth-basicauth-enc-02
Abstract Abstract
The "Basic" authentication scheme defined in RFC 2617 does not The "Basic" authentication scheme defined in RFC 2617 does not
properly define how to treat non-ASCII characters. This has led to a properly define how to treat non-ASCII characters. This has led to a
situation where user agent implementations disagree, and servers make situation where user agent implementations disagree, and servers make
different assumptions based on the locales they are running in. different assumptions based on the locales they are running in.
There is little interoperability for the non-ASCII characters in the There is little interoperability for the non-ASCII characters in the
ISO-8859-1 character repertoire, and even less interoperability for ISO-8859-1 character repertoire, and even less interoperability for
any characters beyond that. any characters beyond that.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Discussion of this draft takes place on the HTTPAuth working group Discussion of this draft takes place on the HTTPAuth working group
mailing list (http-auth@ietf.org), which is archived at <http:// mailing list (http-auth@ietf.org), which is archived at <http://
www.ietf.org/mail-archive/web/http-auth/current/maillist.html>. www.ietf.org/mail-archive/web/http-auth/current/maillist.html>.
XML versions, latest edits and the issues list for this document are XML versions, latest edits and the issues list for this document are
available from available from
<http://greenbytes.de/tech/ <http://greenbytes.de/tech/
webdav/#draft-ietf-httpauth-basicauth-enc>. webdav/#draft-ietf-httpauth-basicauth-enc>.
The changes in this draft are summarized in Appendix C.9. The changes in this draft are summarized in Appendix C.11.
The contents of this document will likely be included into the new
specification of the "Basic" scheme, see
<http://tools.ietf.org/html/draft-ietf-httpauth-basicauth-update>.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 1, 2014. This Internet-Draft will expire on August 8, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 19 skipping to change at page 3, line 19
3. The 'charset' auth-param . . . . . . . . . . . . . . . . . . . 4 3. The 'charset' auth-param . . . . . . . . . . . . . . . . . . . 4
4. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . . 7 8.2. Informative References . . . . . . . . . . . . . . . . . . 7
Appendix A. Deployment Considerations . . . . . . . . . . . . . . 7 Appendix A. Deployment Considerations . . . . . . . . . . . . . . 7
A.1. User Agents . . . . . . . . . . . . . . . . . . . . . . . 7 A.1. User Agents . . . . . . . . . . . . . . . . . . . . . . . 7
A.1.1. Alternative approach . . . . . . . . . . . . . . . . . 7 A.1.1. Alternative approach . . . . . . . . . . . . . . . . . 8
A.2. Origin Servers . . . . . . . . . . . . . . . . . . . . . . 8 A.2. Origin Servers . . . . . . . . . . . . . . . . . . . . . . 8
Appendix B. FAQ (to be removed by RFC Editor before Appendix B. FAQ (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . 8 publication) . . . . . . . . . . . . . . . . . . . . 8
B.1. Why not simply switch the default encoding to UTF-8? . . . 8 B.1. Why not simply switch the default encoding to UTF-8? . . . 8
B.2. What about Digest? . . . . . . . . . . . . . . . . . . . . 8 B.2. What about Digest? . . . . . . . . . . . . . . . . . . . . 8
B.3. Will existing UAs ignore the parameter? . . . . . . . . . 8 B.3. Will existing UAs ignore the parameter? . . . . . . . . . 9
Appendix C. Change Log (to be removed by RFC Editor before Appendix C. Change Log (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . 9 publication) . . . . . . . . . . . . . . . . . . . . 9
C.1. Since draft-reschke-basicauth-enc-00 . . . . . . . . . . . 9 C.1. Since draft-reschke-basicauth-enc-00 . . . . . . . . . . . 9
C.2. Since draft-reschke-basicauth-enc-01 . . . . . . . . . . . 9 C.2. Since draft-reschke-basicauth-enc-01 . . . . . . . . . . . 9
C.3. Since draft-reschke-basicauth-enc-02 . . . . . . . . . . . 9 C.3. Since draft-reschke-basicauth-enc-02 . . . . . . . . . . . 9
C.4. Since draft-reschke-basicauth-enc-03 . . . . . . . . . . . 9 C.4. Since draft-reschke-basicauth-enc-03 . . . . . . . . . . . 9
C.5. Since draft-reschke-basicauth-enc-04 . . . . . . . . . . . 9 C.5. Since draft-reschke-basicauth-enc-04 . . . . . . . . . . . 9
C.6. Since draft-reschke-basicauth-enc-05 . . . . . . . . . . . 9 C.6. Since draft-reschke-basicauth-enc-05 . . . . . . . . . . . 9
C.7. Since draft-reschke-basicauth-enc-06 . . . . . . . . . . . 9 C.7. Since draft-reschke-basicauth-enc-06 . . . . . . . . . . . 9
C.8. Since draft-reschke-basicauth-enc-07 . . . . . . . . . . . 9 C.8. Since draft-reschke-basicauth-enc-07 . . . . . . . . . . . 9
C.9. Since draft-reschke-basicauth-enc-08 . . . . . . . . . . . 9 C.9. Since draft-reschke-basicauth-enc-08 . . . . . . . . . . . 10
C.10. Since draft-ietf-httpauth-basicauth-enc-00 . . . . . . . . 9 C.10. Since draft-ietf-httpauth-basicauth-enc-00 . . . . . . . . 10
Appendix D. Resolved issues (to be removed by RFC Editor C.11. Since draft-ietf-httpauth-basicauth-enc-01 . . . . . . . . 10
before publication) . . . . . . . . . . . . . . . . . 10 Appendix D. Open issues (to be removed by RFC Editor prior to
D.1. terminology . . . . . . . . . . . . . . . . . . . . . . . 10
D.2. parmname2831 . . . . . . . . . . . . . . . . . . . . . . . 10
Appendix E. Open issues (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . 10 publication) . . . . . . . . . . . . . . . . . . . . 10
E.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 D.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
E.2. unorm . . . . . . . . . . . . . . . . . . . . . . . . . . 10 D.2. unorm . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
The "Basic" authentication scheme defined in Section 2 of [RFC2617] The "Basic" authentication scheme defined in Section 2 of [RFC2617]
does not properly define how to treat non-ASCII characters does not properly define how to treat non-ASCII characters
([USASCII]): it uses the Base64 ([RFC4648], Section 4) encoding of ([USASCII]): it uses the Base64 ([RFC4648], Section 4) encoding of
the concatenation of username, separator character, and password the concatenation of username, separator character, and password
without stating which character encoding scheme to use. without stating which character encoding scheme to use.
This has led to a situation where user agent implementations This has led to a situation where user agent implementations
skipping to change at page 7, line 10 skipping to change at page 7, line 10
BCP 166, RFC 6365, September 2011. BCP 166, RFC 6365, September 2011.
[USASCII] American National Standards Institute, [USASCII] American National Standards Institute,
"Coded Character Set -- 7-bit American "Coded Character Set -- 7-bit American
Standard Code for Information Standard Code for Information
Interchange", ANSI X3.4, 1986. Interchange", ANSI X3.4, 1986.
[draft-ietf-httpbis-p7-auth] Fielding, R., Ed. and J. Reschke, Ed., [draft-ietf-httpbis-p7-auth] Fielding, R., Ed. and J. Reschke, Ed.,
"Hypertext Transfer Protocol "Hypertext Transfer Protocol
(HTTP/1.1): Authentication", (HTTP/1.1): Authentication",
draft-ietf-httpbis-p7-auth-22 (work in draft-ietf-httpbis-p7-auth-25 (work in
progress), February 2013. progress), November 2013.
8.2. Informative References 8.2. Informative References
[RFC2831] Leach, P. and C. Newman, "Using Digest [RFC2831] Leach, P. and C. Newman, "Using Digest
Authentication as a SASL Mechanism", Authentication as a SASL Mechanism",
RFC 2831, May 2000. RFC 2831, May 2000.
[RFC4648] Josefsson, S., "The Base16, Base32, and [RFC4648] Josefsson, S., "The Base16, Base32, and
Base64 Data Encodings", RFC 4648, Base64 Data Encodings", RFC 4648,
October 2006. October 2006.
[XHR] Aubourg, J., Song, J., and H. Steen, [XHR] van Kesteren, A., Steen, H., Aubourg,
"XMLHttpRequest", W3C Working Draft WD- J., and J. Song, "XMLHttpRequest Level
XMLHttpRequest-20121206, December 2012, 1", W3C Working Draft WD-
<http://www.w3.org/TR/2012/ XMLHttpRequest-20140130, January 2014,
WD-XMLHttpRequest-20121206/>. <http://www.w3.org/TR/2014/
WD-XMLHttpRequest-20140130/>.
Latest version available at Latest version available at
<http://www.w3.org/TR/XMLHttpRequest/>. <http://www.w3.org/TR/XMLHttpRequest/>.
Appendix A. Deployment Considerations Appendix A. Deployment Considerations
A.1. User Agents A.1. User Agents
User agents not implementing this specification should continue to User agents not implementing this specification should continue to
work as before, ignoring the new parameter. work as before, ignoring the new parameter.
skipping to change at page 10, line 7 skipping to change at page 10, line 17
Made it a draft of the IETF HTTPauth Working Group. Made it a draft of the IETF HTTPauth Working Group.
C.10. Since draft-ietf-httpauth-basicauth-enc-00 C.10. Since draft-ietf-httpauth-basicauth-enc-00
Clarify what encoding step the charset selection applies to. Clarify what encoding step the charset selection applies to.
Use RFC 6365 terminology. Use RFC 6365 terminology.
Rename the parameter to "charset" for consistency with RFC 2831. Rename the parameter to "charset" for consistency with RFC 2831.
Appendix D. Resolved issues (to be removed by RFC Editor before C.11. Since draft-ietf-httpauth-basicauth-enc-01
publication)
Issues that were either rejected or resolved in this version of this
document.
D.1. terminology
Type: edit
julian.reschke@greenbytes.de (2012-02-02): Try to be consistent with
the terminology defined in RFC 6365.
Resolution: Use "character repertoire" and "character encoding
scheme", refer to RFC 6365.
D.2. parmname2831
In Section 3:
Type: change
julian.reschke@greenbytes.de (2012-05-08): RFC 2831 (Digest SASL
Mechanism) defines a *very* similar parameter but calls it "charset".
We may want to be consistent with that.
Resolution: Be consistent with RFC 2831 and use "charset". Update httpbis and XHR references. Add a note about
draft-ietf-httpauth-basicauth-update.
Appendix E. Open issues (to be removed by RFC Editor prior to Appendix D. Open issues (to be removed by RFC Editor prior to
publication) publication)
E.1. edit D.1. edit
Type: edit Type: edit
julian.reschke@greenbytes.de (2010-08-11): Umbrella issue for julian.reschke@greenbytes.de (2010-08-11): Umbrella issue for
editorial fixes/enhancements. editorial fixes/enhancements.
E.2. unorm D.2. unorm
Type: edit Type: edit
julian.reschke@greenbytes.de (2012-02-02): We need a statement about julian.reschke@greenbytes.de (2012-02-02): We need a statement about
unicode normalization forms. unicode normalization forms.
Author's Address Author's Address
Julian F. Reschke Julian F. Reschke
greenbytes GmbH greenbytes GmbH
 End of changes. 17 change blocks. 
53 lines changed or deleted 32 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/