Separation of Data Path and Data Flow Sublayers in the Transport Layer
draft-asai-tsvwg-transport-review-00
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Hirochika Asai
|
|
Last updated |
|
2020-11-01
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
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 H. Asai
Internet-Draft Preferred Networks
Intended status: Standards Track 2 November 2020
Expires: 6 May 2021
Separation of Data Path and Data Flow Sublayers in the Transport Layer
draft-asai-tsvwg-transport-review-00
Abstract
This document reviews the architectural design of the transport
layer. In particular, this document separates the transport layer
into two sublayers; the data path and the data flow layers. The data
path layer provides functionality on the data path, such as
connection handling, path quality and trajectory monitoring, waypoint
management, and congestion control. The data flow layer provides
additional functionality upon the data path layer, such as flow
control for the receive buffer management, retransmission for
reliable data delivery, and transport layer security. The data path
layer multiplexes multiple data flow layer protocols and provides
data path information to the data flow layer to control data
transmissions, such as prioritization and inverse multiplexing for
multipath protocols.
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 6 May 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Asai Expires 6 May 2021 [Page 1]
Internet-Draft Data Path and Data Flow Layers November 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
2. Transport Layer Functionality Review . . . . . . . . . . . . 3
2.1. Conventional Layering . . . . . . . . . . . . . . . . . . 3
2.2. Data Path-aware Networking . . . . . . . . . . . . . . . 4
2.3. Resource Management: Flow Control and Congestion
Control . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4. Multipath Protocols . . . . . . . . . . . . . . . . . . . 6
2.5. Reliable Data Communication . . . . . . . . . . . . . . . 6
2.6. Security . . . . . . . . . . . . . . . . . . . . . . . . 7
2.7. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Specifications of Data Path Layer and Data Flow Layer . . . . 8
3.1. Data Path Layer . . . . . . . . . . . . . . . . . . . . . 8
3.1.1. In-band trajectory monitoring . . . . . . . . . . . . 8
3.1.2. Waypoint management . . . . . . . . . . . . . . . . . 9
3.1.3. Bidirectional connection establishment . . . . . . . 9
3.1.4. Data path quality (congestion) monitoring and
congestion control . . . . . . . . . . . . . . . . . 10
3.1.5. Data flow multiplexing . . . . . . . . . . . . . . . 10
3.1.6. Packet Duplication . . . . . . . . . . . . . . . . . 10
3.2. Data Flow Layer . . . . . . . . . . . . . . . . . . . . . 10
3.2.1. Retransmission for reliable data communication . . . 11
3.2.2. Flow control for receive-buffer management . . . . . 11
3.2.3. Flow prioritization . . . . . . . . . . . . . . . . . 11
3.2.4. End-to-end security . . . . . . . . . . . . . . . . . 11
3.2.5. Inverse multiplexing for multipath protocols . . . . 11
4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1. Multipath Transport Protocols . . . . . . . . . . . . . . 12
4.2. Congestion Control Acceleration . . . . . . . . . . . . . 13
4.3. In-Network Computing . . . . . . . . . . . . . . . . . . 14
4.4. Flow Arbitration . . . . . . . . . . . . . . . . . . . . 15
5. Implementation Considerations . . . . . . . . . . . . . . . . 16
Show full document text