User-Plane Protocols for Multiple Access Management Service
draft-zhu-intarea-mams-user-protocol-03
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-08-04
|
|
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)
|
INTAREA J. Zhu
Internet Draft Intel
Intended status: Standards Track S. Seo
Expires: February 4, 2017 Korea Telecom
S. Kanugovi
Nokia
S. Peng
Huawei
August 4, 2017
User-Plane Protocols for Multiple Access Management Service
draft-zhu-intarea-mams-user-protocol-03
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), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on February 4, 2017.
Copyright Notice
Copyright (c) 2017 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
(http://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
Zhu Expires February 4, 2018 [Page 1]
Internet-Draft MAMS u-plane protocols August 2017
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.
Abstract
Today, a device can be simultaneously connected to multiple
communication networks based on different technology implementations
and network architectures like WiFi, LTE, and DSL. In such multi-
connectivity scenario, it is desirable to combine multiple access
networks or select the best one to improve quality of experience for
a user and improve overall network utilization and efficiency. This
document presents the u-plane protocols for a multi access
management services (MAMS) framework that can be used to flexibly
select the combination of uplink and downlink access and core
network paths having the optimal performance, and user plane
treatment for improving network utilization and efficiency and
enhanced quality of experience for user applications.
Table of Contents
1. Introduction...................................................3
2. Terminologies..................................................3
3. Conventions used in this document..............................3
4 MAMS User-Plane Protocols......................................4
4.1 MX Adaptation Layer......................................4
4.2 Trailer-based MX Convergence Layer.......................5
4.2.1 Trailer-based MX PDU Format........................5
4.2.2 MX Fragmentation...................................7
4.2.3 MX Concatenation...................................9
4.3 MPTCP-based MX Convergence Layer.........................9
4.4 GRE as MX Convergence Layer.............................10
4.4.1 Transmitter Procedures............................11
4.4.2 Receiver Procedures...............................11
4.5 Co-existence of MX Adaptation and MX Convergence Sublayers
12
5. MX Convergence Control Message................................12
5.1 Keep-Alive Message......................................13
5.2 Probe REQ/ACK Message...................................13
6 Security Considerations.......................................14
7 IANA Considerations...........................................14
8 Contributing Authors..........................................14
9 References....................................................14
9.1 Normative References....................................14
Show full document text