Lossless and overhead free DCCP - UDP header conversion (U-DCCP)
draft-amend-tsvwg-dccp-udp-header-conversion-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)
|
Transport Area Working Group M. Amend
Internet-Draft Deutsche Telekom
Intended status: Experimental A. Brunstrom
Expires: September 12, 2019 A. Kassler
Karlstad University
V. Rakocevic
City University of London
March 11, 2019
Lossless and overhead free DCCP - UDP header conversion (U-DCCP)
draft-amend-tsvwg-dccp-udp-header-conversion-00
Abstract
The Datagram Congestion Control protocol (DCCP) is a non-widely
deployed transport protocol in the Internet. The reason for that is
a typical chicken-egg problem. Even if there would be a use for
application developer to rely on DCCP, middle-boxes like firewalls
and NATs will prevent DCCP end-to-end since they lack support for
DCCP. However, as long as the protocol penetration of DCCP will not
increase, middle-boxes will not handle DCCP properly. To overcome
this challenge NAT/NATP traversal and UDP encapsulation for DCCP is
already defined. However the first requires special middle-box
support and the latter introduces overhead. The proposal of a
multipath extension for DCCP further stresses the question of
efficient middle-box passing as its main goal is to be applied over
the Internet, traversing numerous uncontrolled middle-boxes. This
document introduces a new approach, disguising DCCP during
transmission as UDP without requiring middle-box modification nor
introducing any overhead.
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.
Amend, et al. Expires September 12, 2019 [Page 1]
Internet-Draft DCCP - UDP header conversion March 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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. U-DCCP . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. The DCCP Generic header . . . . . . . . . . . . . . . . . 4
3.3. UDP header . . . . . . . . . . . . . . . . . . . . . . . 5
3.4. U-DCCP conversion considerations . . . . . . . . . . . . 6
3.5. U-DCCP header . . . . . . . . . . . . . . . . . . . . . . 6
3.6. Implementation . . . . . . . . . . . . . . . . . . . . . 7
3.7. Pseudo-code DCCP to U-DCCP conversion . . . . . . . . . . 7
3.8. Pseudo-code U-DCCP to DCCP restoration . . . . . . . . . 8
3.9. U-DCCP negotiation (required????) . . . . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
8. Informative References . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
The Datagram Congestion Control Protocol (DCCP) [RFC4340] is a
transport-layer protocol that provides upper layers with the ability
to use non-reliable congestion-controlled flows. The current
specification for DCCP [RFC4340] specifies a direct native
encapsulation in IPv4 or IPv6 packets.
Show full document text