DCCP Extensions for Multipath Operation with Multiple Addresses
draft-amend-tsvwg-multipath-dccp-03

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf 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)
Transport Area Working Group                                    M. Amend
Internet-Draft                                              E. Bogenfeld
Intended status: Experimental                           Deutsche Telekom
Expires: May 7, 2020                                        A. Brunstrom
                                                              A. Kassler
                                                     Karlstad University
                                                            V. Rakocevic
                                               City University of London
                                                       November 04, 2019

    DCCP Extensions for Multipath Operation with Multiple Addresses
                  draft-amend-tsvwg-multipath-dccp-03

Abstract

   DCCP communication is currently restricted to a single path per
   connection, yet multiple paths often exist between peers.  The
   simultaneous use of these multiple paths for a DCCP session could
   improve resource usage within the network and, thus, improve user
   experience through higher throughput and improved resilience to
   network failure.

   Multipath DCCP provides the ability to simultaneously use multiple
   paths between peers.  This document presents a set of extensions to
   traditional DCCP to support multipath operation.  The protocol offers
   the same type of service to applications as DCCP and it provides the
   components necessary to establish and use multiple DCCP flows across
   potentially disjoint paths.

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 May 7, 2020.

Amend, et al.              Expires May 7, 2020                  [Page 1]
Internet-Draft               Multipath DCCP                November 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Multipath DCCP in the Networking Stack  . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  MP-DCCP Concept . . . . . . . . . . . . . . . . . . . . .   3
     1.4.  Differences from Multipath TCP  . . . . . . . . . . . . .   4
     1.5.  Requirements Language . . . . . . . . . . . . . . . . . .   7
   2.  Operation Overview  . . . . . . . . . . . . . . . . . . . . .   7
   3.  MP-DCCP Protocol  . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Multipath Capable Feature . . . . . . . . . . . . . . . .   8
     3.2.  Multipath Option  . . . . . . . . . . . . . . . . . . . .   9
       3.2.1.  MP_CONFIRM  . . . . . . . . . . . . . . . . . . . . .   9
       3.2.2.  MP_JOIN . . . . . . . . . . . . . . . . . . . . . . .   9
       3.2.3.  MP_FAST_CLOSE . . . . . . . . . . . . . . . . . . . .  10
       3.2.4.  MP_KEY  . . . . . . . . . . . . . . . . . . . . . . .  10
       3.2.5.  MP_SEQ  . . . . . . . . . . . . . . . . . . . . . . .  11
       3.2.6.  MP_HMAC . . . . . . . . . . . . . . . . . . . . . . .  11
       3.2.7.  MP_RTT  . . . . . . . . . . . . . . . . . . . . . . .  11
       3.2.8.  MP_ADDADDR  . . . . . . . . . . . . . . . . . . . . .  12
       3.2.9.  MP_REMOVEADDR . . . . . . . . . . . . . . . . . . . .  12
       3.2.10. MP_PRIO . . . . . . . . . . . . . . . . . . . . . . .  12
     3.3.  MP-DCCP Handshaking Procedure . . . . . . . . . . . . . .  12
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   5.  Interactions with Middleboxes . . . . . . . . . . . . . . . .  13
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  13
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   8.  Informative References  . . . . . . . . . . . . . . . . . . .  14
Show full document text