An Encoding Parameter for HTTP Basic Authentication
draft-ietf-httpauth-basicauth-enc-02

The information below is for an old version of the document
Document Type Active Internet-Draft (httpauth WG)
Last updated 2014-02-04
Replaces draft-reschke-basicauth-enc
Replaced by draft-ietf-httpauth-basicauth-update, rfc7617
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
HTTPAuth Working Group                                        J. Reschke
Internet-Draft                                                greenbytes
Updates: 2617 (if approved)                             February 4, 2014
Intended status: Experimental
Expires: August 8, 2014

          An Encoding Parameter for HTTP Basic Authentication
                  draft-ietf-httpauth-basicauth-enc-02

Abstract

   The "Basic" authentication scheme defined in RFC 2617 does not
   properly define how to treat non-ASCII characters.  This has led 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 repertoire, and even less interoperability for
   any characters beyond that.

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

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

   Discussion of this draft takes place on the HTTPAuth working group
   mailing list (http-auth@ietf.org), which is archived at <http://
   www.ietf.org/mail-archive/web/http-auth/current/maillist.html>.

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

   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

   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

Reschke                  Expires August 8, 2014                 [Page 1]
Internet-Draft        Basic Auth Encoding Parameter        February 2014

   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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 August 8, 2014.

Copyright Notice

   Copyright (c) 2014 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 August 8, 2014                 [Page 2]
Internet-Draft        Basic Auth Encoding Parameter        February 2014

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Notational Conventions . . . . . . . . . . . . . . . . . . . .  4
   3.  The 'charset' auth-param . . . . . . . . . . . . . . . . . . .  4
   4.  Example  . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  5
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  5
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  6
   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 . . . . . . . . . . . . . . . . .  8
     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?  . . . . . . . . .  9
   Appendix C.  Change Log (to be removed by RFC Editor before
                publication)  . . . . . . . . . . . . . . . . . . . .  9
Show full document text