HTTP Header Fields for Proxied SVCB Metadata
draft-proxied-svcb-headers-00

Document Type Active Internet-Draft (individual)
Author Tommy Pauly 
Last updated 2021-02-19
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) 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                                           T. Pauly
Internet-Draft                                               Apple, Inc.
Intended status: Standards Track                        19 February 2021
Expires: 23 August 2021

              HTTP Header Fields for Proxied SVCB Metadata
                     draft-proxied-svcb-headers-00

Abstract

   This document defines HTTP header fields for the passing Service
   Binding (SVCB) DNS metadata in HTTP responses.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Source for this draft and an issue tracker can be found at
   https://github.com/tfpauly/privacy-proxy.

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 23 August 2021.

Copyright Notice

   Copyright (c) 2021 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

Pauly                    Expires 23 August 2021                 [Page 1]
Internet-Draft            Proxied SVCB Headers             February 2021

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements  . . . . . . . . . . . . . . . . . . . . . .   3
   2.  SVCB Request Header Field . . . . . . . . . . . . . . . . . .   3
   3.  SVCB Response Header Fields . . . . . . . . . . . . . . . . .   3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  HTTP Headers  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   CONNECT [RFC7231] and CONNECT-UDP [I-D.ietf-masque-connect-udp] are
   HTTP methods that clients may use to establish TCP or UDP flows to
   target servers.  Once proxy servers establish these flows, proxy
   servers treat allocated flows as opaque byte or datagram streams
   respectively.  Clients specify the target in authority-form
   (Section 5.3 of [RFC7230]), including the name or IP address of the
   server along with a port number.  When using a name instead of an IP
   address, the proxy server locally resolves the name to an IPv4 or
   IPv6 address with A or AAAA queries.  The client does not see these A
   or AAAA answers, as they are only relevant to the proxy in
   establishing a connection to the target.

   In some circumstances, some DNS metadata may be useful to clients.
   This is especially true for information contained in Service Binding
   (SVCB or HTTPS) records [I-D.ietf-dnsop-svcb-https].  These records
   can influence client behavior even when clients are not directly
   interacting with target IP addresses.  The records can be used to
   determine which application-level protocols are supported by an
   endpoint.  These records also can include a TLS Encrypted Client
   Hello [I-D.ietf-tls-esni] configuration, which can be used in
   protecting the end-to-end TLS handshake.

   This document specifies HTTP header fields that proxy servers may use
   to relay information retrieved from SVCB records from proxy servers
   to clients when using CONNECT or CONNECT-UDP.

Pauly                    Expires 23 August 2021                 [Page 2]
Internet-Draft            Proxied SVCB Headers             February 2021

1.1.  Requirements

   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 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

2.  SVCB Request Header Field

   Clients can request SVCB parameters with the Structured Header
Show full document text