HTTP Transport Authentication
draft-schinazi-httpbis-transport-auth-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                        D. Schinazi
Internet-Draft                                                Google LLC
Intended status: Experimental                              July 08, 2019
Expires: January 9, 2020

                     HTTP Transport Authentication
                draft-schinazi-httpbis-transport-auth-00

Abstract

   The most common existing authentication mechanisms for HTTP are sent
   with each HTTP request, and authenticate that request instead of the
   underlying HTTP connection, or transport.  While these mechanisms
   work well for existing uses of HTTP, they are not suitable for
   emerging applications that multiplex non-HTTP traffic inside an HTTP
   connection.  This document describes the HTTP Transport
   Authentication Framework, a method of authenticating not only an HTTP
   request, but also its underlying transport.

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 https://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 January 9, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (https://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

Schinazi                 Expires January 9, 2020                [Page 1]
Internet-Draft        HTTP Transport Authentication            July 2019

   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

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions and Definitions . . . . . . . . . . . . . . .   3
   2.  Computing the Authentication Proof  . . . . . . . . . . . . .   3
   3.  Header Field Definition . . . . . . . . . . . . . . . . . . .   4
     3.1.  The u Directive . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  The p Directive . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  The a Directive . . . . . . . . . . . . . . . . . . . . .   4
   4.  Transport Authentication Schemes  . . . . . . . . . . . . . .   4
     4.1.  Signature . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  HMAC  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Proxy Considerations  . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  Transport-Authentication Header Field . . . . . . . . . .   6
     7.2.  Transport Authentication Schemes Registry . . . . . . . .   6
     7.3.  TLS Keying Material Exporter Labels . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
     8.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The most common existing authentication mechanisms for HTTP are sent
   with each HTTP request, and authenticate that request instead of the
   underlying HTTP connection, or transport.  While these mechanisms
   work well for existing uses of HTTP, they are not suitable for
   emerging applications that multiplex non-HTTP traffic inside an HTTP
   connection.  This document describes the HTTP Transport
   Authentication Framework, a method of authenticating not only an HTTP
   request, but also its underlying transport.

   Traditional HTTP semantics specify that HTTP is a stateless protocol
   where each request can be understood in isolation [RFC7230].
   However, the emergence of QUIC [I-D.ietf-quic-transport] as a new
   transport protocol that can carry HTTP [I-D.ietf-quic-http] and the
   existence of QUIC extensions such as the DATAGRAM frame
   [I-D.pauly-quic-datagram] enable new uses of HTTP such as
Show full document text