]> Google LLC

1600 Amphitheatre Parkway Mountain View CA 94043 United States of America dschinazi.ietf@gmail.com

Guardian Project

david@guardianproject.info https://guardianproject.info

Cloudflare Inc.

jonathan.hoyland@gmail.com

Applications and Real-Time HTTPBIS secure tunnels masque http-ng Existing HTTP authentication mechanisms are probeable in the sense that it is possible for an unauthenticated client to probe whether an origin serves resources that require authentication. It is possible for an origin to hide the fact that it requires authentication by not generating Unauthorized status codes, however that only works with non-cryptographic authentication schemes: cryptographic schemes (such as signatures or message authentication codes) require a fresh nonce to be signed, and there is no existing way for the origin to share such a nonce without exposing the fact that it serves resources that require authentication. This document proposes a new non-probeable cryptographic authentication scheme. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the HTTP Working Group mailing list (), which is archived at . Source for this draft and an issue tracker can be found at .

Introduction Existing HTTP authentication mechanisms (see ) are probeable in the sense that it is possible for an unauthenticated client to probe whether an origin serves resources that require authentication. It is possible for an origin to hide the fact that it requires authentication by not generating Unauthorized status codes, however that only works with non-cryptographic authentication schemes: cryptographic schemes (such as signatures or message authentication codes) require a fresh nonce to be signed, and there is no existing way for the origin to share such a nonce without exposing the fact that it serves resources that require authentication. This document proposes a new non-probeable cryptographic authentication scheme. There are scenarios where servers may want to expose the fact that authentication is required for access to specific resources. This is left for future work.

Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. This document uses the following terminology from to specify syntax and parsing: Integer and Byte Sequence.

Computing the Authentication Proof This document only defines the Signature and HMAC authentication schemes for uses of HTTP with TLS . This includes any use of HTTP over TLS as typically used for HTTP/2 , or HTTP/3 where the transport protocol uses TLS as its authentication and key exchange mechanism . The user agent leverages a TLS keying material exporter to generate a nonce which can be signed using the user's key. The keying material exporter uses a label that starts with the characters "EXPORTER-HTTP-Unprompted-Authentication-" (see for the labels and contexts used by each scheme). The TLS keying material exporter is used to generate a 32-byte key which is then used as a nonce.

Header Field Definition The "Unprompted-Authentication" header field allows a user agent to authenticate with an origin server. The authentication is scoped to the HTTP request associated with this header field. The value of the Unprompted-Authentication header field is a credentials object, as defined in . Credentials contain an authentication scheme followed by optional authentication parameters.

Authentication Parameters This specification defines the following authentication parameters, they can be used by the authentication schemes defined in .

The u Parameter The OPTIONAL "u" (user ID) parameter is a byte sequence that specifies the user ID that the user agent wishes to authenticate.

The p Parameter The OPTIONAL "p" (proof) parameter is a byte sequence that specifies the proof that the user agent provides to attest to possessing the credential that matches its user ID.

The s Parameter The OPTIONAL "s" (signature) parameter is an integer that specifies the signature algorithm used to compute the proof transmitted in the "p" directive. Its value is an integer between 0 and 255 inclusive from the IANA "TLS SignatureAlgorithm" registry maintained at <>.

The h Parameter The OPTIONAL "h" (hash) parameter is an integer that specifies the hash algorithm used to compute the proof transmitted in the "p" directive. Its value is an integer between 0 and 255 inclusive from the IANA "TLS HashAlgorithm" registry maintained at <>.

Authentication Schemes This document defines the "Signature" and "HMAC" HTTP authentication schemes.

Signature The "Signature" HTTP Authentication Scheme uses asymmetric cyptography. User agents possess a user ID and a public/private key pair, and origin servers maintain a mapping of authorized user IDs to their associated public keys. When using this scheme, the "u", "p", and "s" parameters are REQUIRED. The TLS keying material export label for this scheme is "EXPORTER-HTTP-Unprompted-Authentication-Signature" and the associated context is empty. The nonce is then signed using the selected asymmetric signature algorithm and transmitted as the proof directive. For example, the user ID "john.doe" authenticating using Ed25519 could produce the following header field (lines are folded to fit):

HMAC The "HMAC" HTTP Authentication Scheme uses symmetric cyptography. User agents possess a user ID and a secret key, and origin servers maintain a mapping of authorized user IDs to their associated secret key. When using this scheme, the "u", "p", and "h" parameters are REQUIRED. The TLS keying material export label for this scheme is "EXPORTER-HTTP-Unprompted-Authentication-HMAC" and the associated context is empty. The nonce is then HMACed using the selected HMAC algorithm and transmitted as the proof directive. For example, the user ID "john.doe" authenticating using HMAC-SHA-512 could produce the following header field (lines are folded to fit):

Other HTTP Authentication Schemes The HTTP Authentication Scheme registry maintained by IANA at <> contains entries not defined in this document. Those entries MAY be used with Unprompted Authentication.

Intermediary Considerations Since the Signature and HMAC HTTP Authentication Schemes leverage TLS keying material exporters, their output cannot be transparently forwarded by HTTP intermediaries. HTTP intermediaries that support this specification will validate the authentication received from the client themselves, then inform the upstream HTTP server of the presence of valid authentication using some other mechanism.

Security Considerations Unprompted Authentication allows a user-agent to authenticate to an origin server while guaranteeing freshness and without the need for the server to transmit a nonce to the user agent. This allows the server to accept authenticated clients without revealing that it supports or expects authentication for some resources. It also allows authentication without the user agent leaking the presence of authentication to observers due to clear-text TLS Client Hello extensions. The authentication proofs described in this document are not bound to individual HTTP requests; if the same user sends an authentication proof on multiple requests they will all be identical. This allows for better compression when sending over the wire, but implies that client implementations that multiplex different security contexts over a single HTTP connection need to ensure that those contexts cannot read each other's header fields. Otherwise, one context would be able to replay the unprompted authentication header field of another. This constraint is met by modern Web browsers. If an attacker were to compromise the browser such that it could access another context's memory, the attacker might also be able to access the corresponding key, so binding authentication to requests would not provide much benefit in practice.

IANA Considerations

Unprompted-Authentication Header Field This document will request IANA to register the following entry in the "HTTP Field Name" registry maintained at <>:

Field Name:

Unprompted-Authentication

Template:

None

Status:

provisional (permanent if this document is approved)

Reference:

This document

Comments:

None

HTTP Authentication Schemes Registry This document, if approved, requests IANA to add two new entries to the "HTTP Authentication Schemes" Registry maintained at <>. Both entries have the Reference set to this document, and the Notes empty. The Authentication Scheme Name of the entries are:

• Signature
• HMAC

TLS Keying Material Exporter Labels This document, if approved, requests IANA to register the following entries in the "TLS Exporter Labels" registry maintained at <>:

• EXPORTER-HTTP-Unprompted-Authentication-Signature
• EXPORTER-HTTP-Unprompted-Authentication-HMAC

Both of these entries are listed with the following qualifiers:

DTLS-OK:

N

Recommended:

Y

Reference:

This document

References Normative References The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes. This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This document describes a set of data types and associated algorithms that are intended to make it easier and safer to define and handle HTTP header and trailer fields, known as "Structured Fields", "Structured Headers", or "Structured Trailers". It is intended for use by specifications of new HTTP fields that wish to use a common syntax that is more restrictive than traditional HTTP field values. This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations. A number of protocols wish to leverage Transport Layer Security (TLS) to perform key establishment but then use some of the keying material for their own purposes. This document describes a general mechanism for allowing that. [STANDARDS-TRACK] Informative References This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version 2 (HTTP/2). HTTP/2 enables a more efficient use of network resources and a reduced latency by introducing field compression and allowing multiple concurrent exchanges on the same connection. This document obsoletes RFCs 7540 and 8740. The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment. This document describes a mapping of HTTP semantics over QUIC. This document also identifies HTTP/2 features that are subsumed by QUIC and describes how HTTP/2 extensions can be ported to HTTP/3. This document describes how Transport Layer Security (TLS) is used to secure QUIC. This document specifies algorithm identifiers and ASN.1 encoding formats for elliptic curve constructs using the curve25519 and curve448 curves. The signature algorithms covered are Ed25519 and Ed448. The key agreement algorithms covered are X25519 and X448. The encoding for public key, private key, and Edwards-curve Digital Signature Algorithm (EdDSA) structures is provided. Federal Information Processing Standard, FIPS

Acknowledgments The authors would like to thank many members of the IETF community, as this document is the fruit of many hallway conversations. Ben Schwartz contributed ideas to this document.