Requirements for a MASQUE Protocol to Proxy IP Traffic
draft-cms-masque-ip-proxy-reqs-01

Document Type Active Internet-Draft (individual)
Last updated 2020-08-06
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                                  A. Chernyakhovsky
Internet-Draft                                                 D. McCall
Intended status: Informational                               D. Schinazi
Expires: 8 February 2021                                      Google LLC
                                                           7 August 2020

         Requirements for a MASQUE Protocol to Proxy IP Traffic
                   draft-cms-masque-ip-proxy-reqs-01

Abstract

   There is interest among MASQUE working group participants in
   designing a protocol that can proxy IP traffic over HTTP.  This
   document describes the set of requirements for such a protocol.

   Discussion of this work is encouraged to happen on the MASQUE IETF
   mailing list masque@ietf.org or on the GitHub repository which
   contains the draft: https://github.com/DavidSchinazi/masque-drafts.

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 8 February 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Chernyakhovsky, et al.   Expires 8 February 2021                [Page 1]
Internet-Draft          IP Proxying Requirements             August 2020

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Conventions . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Consumer VPN  . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Point to Point Connectivity . . . . . . . . . . . . . . .   4
     2.3.  Point to Network Connectivity . . . . . . . . . . . . . .   4
     2.4.  Network to Network Connectivity . . . . . . . . . . . . .   4
   3.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  IP Session Establishment  . . . . . . . . . . . . . . . .   5
     3.2.  Proxying of IP packets  . . . . . . . . . . . . . . . . .   5
     3.3.  Maximum Transmission Unit . . . . . . . . . . . . . . . .   5
     3.4.  IP Assignment . . . . . . . . . . . . . . . . . . . . . .   5
     3.5.  Route Negotiation . . . . . . . . . . . . . . . . . . . .   5
     3.6.  Identity  . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.7.  Transport Security  . . . . . . . . . . . . . . . . . . .   6
     3.8.  Authentication  . . . . . . . . . . . . . . . . . . . . .   6
     3.9.  Reliable Transmission of IP Packets . . . . . . . . . . .   6
     3.10. Flow Control  . . . . . . . . . . . . . . . . . . . . . .   6
     3.11. Indistinguishability  . . . . . . . . . . . . . . . . . .   6
     3.12. Support HTTP/2 and HTTP/3 . . . . . . . . . . . . . . . .   7
     3.13. Multiplexing  . . . . . . . . . . . . . . . . . . . . . .   7
     3.14. Load balancing  . . . . . . . . . . . . . . . . . . . . .   7
     3.15. Extensibility . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Non-requirements  . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Addressing Architecture . . . . . . . . . . . . . . . . .   8
     4.2.  Translation . . . . . . . . . . . . . . . . . . . . . . .   8
     4.3.  IP Packet Extraction  . . . . . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   8
   References  . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     Normative References  . . . . . . . . . . . . . . . . . . . . .   9
     Informative References  . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10
Show full document text