Network Address Translation Support for QUIC
draft-duke-quic-natsupp-03

Document Type Active Internet-Draft (individual)
Author Martin Duke 
Last updated 2020-07-29
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)
QUIC                                                             M. Duke
Internet-Draft                                         F5 Networks, Inc.
Intended status: Informational                              29 July 2020
Expires: 30 January 2021

              Network Address Translation Support for QUIC
                       draft-duke-quic-natsupp-03

Abstract

   Network Address Translators (NATs) are widely deployed to share
   scarce public IPv4 addresses among multiple end hosts.  They
   overwrite IP addresses and ports in IP packets to do so.  QUIC is a
   protocol on top of UDP that provides transport-like services.  QUIC
   is better-behaved in the presence of NATs than older protocols, and
   existing UDP NATs should operate without incident if unmodified.
   QUIC offers additional features that may tempt NAT implementers as
   potential optimizations.  However, in practice, leveraging these
   features will lead to new connection failure modes and security
   vulnerabilities.

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 30 January 2021.

Copyright Notice

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

Duke                     Expires 30 January 2021                [Page 1]
Internet-Draft              QUIC NAT Support                   July 2020

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  QUIC and NAT Rebinding  . . . . . . . . . . . . . . . . . . .   3
   4.  The Lure of the Connection ID . . . . . . . . . . . . . . . .   4
     4.1.  Resource Conservation . . . . . . . . . . . . . . . . . .   4
     4.2.  "Helping" with routing infrastructure issues  . . . . . .   5
   5.  Filtering behavior  . . . . . . . . . . . . . . . . . . . . .   5
   6.  QUIC Detection  . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   9.  Informative References  . . . . . . . . . . . . . . . . . . .   6
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .   7
   Appendix B.  Change Log . . . . . . . . . . . . . . . . . . . . .   7
     B.1.  since draft-duke-quic-natsupp-02  . . . . . . . . . . . .   7
     B.2.  since draft-duke-quic-natsupp-01  . . . . . . . . . . . .   7
     B.3.  since draft-duke-quic-natsupp-00  . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Network Address Translators (NATs) are a widely deployed means of
   multiplexing multiple private IP addresses over scarce IPv4 public
   address space by replacing those addresses and using ports to
   distinguish those connections.  The new address can also guarantee
   that packets move through a proxy throughout the life of a
   connection, so that the connection can continue with the required
   state at that proxy.

   This document uses the colloquial term NAT to mean NAPT (section 2.2
   of [RFC3022]), which overloads several IP addresses to one IP address
   or to an IP address pool, as commonly deployed in carrier-grade NATs
   or residential NATs.

Duke                     Expires 30 January 2021                [Page 2]
Internet-Draft              QUIC NAT Support                   July 2020

   QUIC [QUIC-TRANSPORT] is a protocol, operating over UDP, that
   provides many transport-like services to the application layer.
   Among these services is the mapping of multiple endpoint IP addresses
   to a single connection through use of a Connection ID (CID).
   Connection IDs are opaque byte fields that are expressed consistently
Show full document text