Quality-of-Service Option for Proxy Mobile IPv6
RFC 7222
|
| Document |
Type |
|
RFC - Proposed Standard
(May 2014; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Basavaraj Patil
|
|
Shepherd write-up |
|
Show
(last changed 2014-02-21)
|
| IESG |
IESG state |
|
RFC 7222 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Brian Haberman
|
|
Send notices to |
|
(None)
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
RFC-Ed-Ack
|
Internet Engineering Task Force (IETF) M. Liebsch
Request for Comments: 7222 NEC
Category: Standards Track P. Seite
ISSN: 2070-1721 Orange
H. Yokota
KDDI Lab
J. Korhonen
Broadcom Communications
S. Gundavelli
Cisco
May 2014
Quality-of-Service Option for Proxy Mobile IPv6
Abstract
This specification defines a new mobility option, the Quality-of-
Service (QoS) option, for Proxy Mobile IPv6. This option can be used
by the local mobility anchor and the mobile access gateway for
negotiating Quality-of-Service parameters for a mobile node's IP
flows. The negotiated QoS parameters can be used for QoS policing
and marking of packets to enforce QoS differentiation on the path
between the local mobility anchor and the mobile access gateway.
Furthermore, making QoS parameters available on the mobile access
gateway enables mapping of these parameters to QoS rules that are
specific to the access technology and allows those rules to be
enforced on the access network using access-technology-specific
approaches.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7222.
Liebsch, et al. Standards Track [Page 1]
RFC 7222 QoS Support for Proxy Mobile IPv6 May 2014
Copyright Notice
Copyright (c) 2014 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 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. Conventions and Terminology .....................................4
2.1. Conventions ................................................4
2.2. Terminology ................................................5
3. Overview of QoS Support in Proxy Mobile IPv6 ....................7
3.1. Quality-of-Service Option -- Usage Examples ................9
3.2. Quality-of-Service Attributes -- Usage Examples ...........11
4. Protocol Messaging Extensions ..................................12
4.1. Quality-of-Service Option .................................12
4.2. Quality-of-Service Attributes .............................14
4.2.1. Per-Mobile-Node Aggregate Maximum Downlink
Bit Rate ...........................................16
4.2.2. Per-Mobile-Node Aggregate Maximum Uplink Bit Rate ..17
4.2.3. Per-Mobility-Session Aggregate Maximum
Downlink Bit Rate ..................................18
4.2.4. Per-Mobility-Session Aggregate Maximum
Uplink Bit Rate ....................................20
4.2.5. Allocation and Retention Priority ..................22
4.2.6. Aggregate Maximum Downlink Bit Rate ................23
4.2.7. Aggregate Maximum Uplink Bit Rate ..................25
4.2.8. Guaranteed Downlink Bit Rate .......................26
4.2.9. Guaranteed Uplink Bit Rate .........................27
4.2.10. QoS Traffic Selector ..............................28
4.2.11. QoS Vendor-Specific Attribute .....................29
4.3. New Status Code for Proxy Binding Acknowledgement .........30
4.4. New Notification Reason for Update Notification Message ...30
4.5. New Status Code for Update Notification
Show full document text