An Encoding Parameter for HTTP Basic Authentication
draft-reschke-basicauth-enc-05

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-03-11
Replaced by draft-ietf-httpauth-basicauth-update, rfc7617, draft-ietf-httpauth-basicauth-enc
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         J. Reschke
Internet-Draft                                                greenbytes
Updates: 2617 (if approved)                               March 11, 2012
Intended status: Standards Track
Expires: September 12, 2012

          An Encoding Parameter for HTTP Basic Authentication
                     draft-reschke-basicauth-enc-05

Abstract

   The "Basic" authentication scheme defined in RFC 2617 does not
   properly define how to treat non-ASCII characters.  This has lead to
   a situation where user agent implementations disagree, and servers
   make different assumptions based on the locales they are running in.
   There is little interoperability for the non-ASCII characters in the
   ISO-8859-1 character set, and even less interoperability for any
   characters beyond that.

   This document defines a backwards-compatible extension to "Basic",
   specifying the server's character encoding expectation, using a new
   authentication scheme parameter.

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

   Distribution of this document is unlimited.  Although this is not a
   work item of the HTTPbis Working Group, comments should be sent to
   the Hypertext Transfer Protocol (HTTP) mailing list at
   ietf-http-wg@w3.org [1], which may be joined by sending a message
   with subject "subscribe" to ietf-http-wg-request@w3.org [2].

   Discussions of the HTTPbis Working Group are archived at
   <http://lists.w3.org/Archives/Public/ietf-http-wg/>.

   XML versions, latest edits and the issues list for this document are
   available from
   <http://greenbytes.de/tech/webdav/#draft-reschke-basicauth-enc>.

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 http://datatracker.ietf.org/drafts/current/.

Reschke                Expires September 12, 2012               [Page 1]
Internet-Draft        Basic Auth Encoding Parameter           March 2012

   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 September 12, 2012.

Copyright Notice

   Copyright (c) 2012 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
   (http://trustee.ietf.org/license-info) 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.

Reschke                Expires September 12, 2012               [Page 2]
Internet-Draft        Basic Auth Encoding Parameter           March 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Notational Conventions . . . . . . . . . . . . . . . . . . . .  4
   3.  The 'accept-charset' auth-param  . . . . . . . . . . . . . . .  4
   4.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  5
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  5
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  5
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     8.1.  Normative References . . . . . . . . . . . . . . . . . . .  6
     8.2.  Informative References . . . . . . . . . . . . . . . . . .  7
   Appendix A.  Deployment Considerations . . . . . . . . . . . . . .  7
     A.1.  User Agents  . . . . . . . . . . . . . . . . . . . . . . .  7
       A.1.1.  Alternative approach . . . . . . . . . . . . . . . . .  7
     A.2.  Origin Servers . . . . . . . . . . . . . . . . . . . . . .  8
   Appendix B.  FAQ (to be removed by RFC Editor before
                publication)  . . . . . . . . . . . . . . . . . . . .  8
     B.1.  Why not simply switch the default encoding to UTF-8? . . .  8
     B.2.  What about Digest? . . . . . . . . . . . . . . . . . . . .  8
     B.3.  Will existing UAs ignore the parameter?  . . . . . . . . .  8
   Appendix C.  Change Log (to be removed by RFC Editor before
Show full document text