QUIC Address Extension
draft-pauly-quic-address-extension-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-11
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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                                                   C. Wood
Intended status: Standards Track                              E. Kinnear
Expires: September 12, 2019                                   Apple Inc.
                                                          March 11, 2019

                         QUIC Address Extension
                 draft-pauly-quic-address-extension-00

Abstract

   This document defines an extension to the QUIC transport protocol
   that adds support for requesting and receiving the public network
   address of an endpoint from its peer.

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 September 12, 2019.

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

Pauly, et al.          Expires September 12, 2019               [Page 1]
Internet-Draft           QUIC Address Extension               March 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Connection Lifetime Optimizations . . . . . . . . . . . .   3
     2.2.  Privacy Stance Enhancements . . . . . . . . . . . . . . .   3
   3.  Transport Parameter . . . . . . . . . . . . . . . . . . . . .   3
   4.  Address Request and Response Frame Types  . . . . . . . . . .   3
   5.  Address Frame Usage . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The QUIC Transport Protocol [I-D.ietf-quic-transport] provides a
   secure, multiplexed connection for transmitting reliable streams of
   application data.  Connections are associated with unique Connection
   Identifiers (CIDs) that facilitate migration for clients that are
   mobile or have multiple network associations.  CIDs also help
   connections survive Network Address Translator (NAT) port re-
   bindings, provided that the client behind the NAT sends a new packet
   with a known CID before the server drops the connection.

   There is currently no explicit signal an endpoint can use to detect
   the presence of NATs.  This problematic as it can encourage endpoints
   to aggressively send packets to keep NAT bindings alive.

   This document describes an extension to QUIC that enables peers to
   request their public address and port from peers.  This can be used
   to detect NATs and to help guide CID rotation policies.

1.1.  Requirements Language

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

2.  Motivation

   There are several cases in which an endpoint might wish to know its
   public network address.

Pauly, et al.          Expires September 12, 2019               [Page 2]
Internet-Draft           QUIC Address Extension               March 2019

2.1.  Connection Lifetime Optimizations

   Knowing whether or not an endpoint is behind a NAT can help guide
   connection keepalive mechanisms.  For example, peers that are not
   behind NATs might not need to send frequent keepalive packets (such
   as packets containing PING frames) to prevent NAT bindings
Show full document text