Client Authentication over New TLS Connection
draft-thomson-httpbis-cant-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-05-08
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)
HTTPBIS                                                       M. Thomson
Internet-Draft                                                   Mozilla
Intended status: Standards Track                             May 8, 2014
Expires: November 9, 2014

             Client Authentication over New TLS Connection
                     draft-thomson-httpbis-cant-00

Abstract

   This document defines an HTTP authentication scheme that can be added
   to an error response to indicate to a client that a successful
   response will only be provided over a new TLS connection, and only if
   the client has provided a certificate on that connection.

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/.

   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 November 9, 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.

Thomson                 Expires November 9, 2014                [Page 1]
Internet-Draft                    CANT                          May 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions and Terminology . . . . . . . . . . . . . . .   2
   2.  Client Certificate Challenge  . . . . . . . . . . . . . . . .   2
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informational References  . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   Client authentication in HTTP sometimes relies on certificate-based
   authentication of clients in Transport Layer Security (TLS)
   [RFC5246].  Some uses of client authentication rely on TLS
   renegotiation, triggering renegotiation in response to a request for
   a particular resource.

   HTTP/2 [I-D.ietf-httpbis-http2] forbids the use of renegotiation,
   except for at the very beginning of a connection.  This makes
   addressing some client authentication use cases difficult.

   This document defines a new authentication scheme,
   "ClientCertificate", for use in HTTP authentication challenges
   [I-D.ietf-httpbis-p7-auth].  In combination with the 401
   (Unauthorized) status code, this indicates that the resource requires
   client authentication at the TLS layer in order to access it.

1.1.  Conventions and Terminology

   At times, this document falls back on shorthands for establishing
   interoperability requirements on implementations: the capitalized
   words "MUST", "SHOULD" and "MAY".  These terms are defined in
   [RFC2119].

2.  Client Certificate Challenge

   A new authentication scheme ([I-D.ietf-httpbis-p7-auth]) for the
   "WWW-Authenticate" and "Proxy-Authenticate" header fields is defined
   with the name "ClientCertificate".

   A challenge with this authentication scheme does not define any
   parameters except "realm".  The "realm" can be used to select an
   appropriate certificate, or if a certificate is already in use, to
   indicate the need for a different certificate.  Other challenge

Thomson                 Expires November 9, 2014                [Page 2]
Internet-Draft                    CANT                          May 2014

   parameters MAY be used to provide a client with information it can
   use to select an appropriate certificate.  Unknown parameters MUST be
   ignored.

   This challenge cannot be satisfied by constructing an Authorization
   header field [I-D.ietf-httpbis-p7-auth], it can only be satisfied by
   making the request on a TLS connection where an appropriate
Show full document text