IPv6 Destination Option for Congestion Exposure (ConEx)
RFC 7837
|
| Document |
Type |
|
RFC - Experimental
(May 2016; No errata)
|
|
Last updated |
|
2016-05-13
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Dirk Kutscher
|
|
Shepherd write-up |
|
Show
(last changed 2015-05-08)
|
| IESG |
IESG state |
|
RFC 7837 (Experimental)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Martin Stiemerling
|
|
Send notices to |
|
(None)
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
No IANA Actions
|
Internet Engineering Task Force (IETF) S. Krishnan
Request for Comments: 7837 Ericsson
Category: Experimental M. Kuehlewind
ISSN: 2070-1721 ETH Zurich
B. Briscoe
Simula Research Laboratory
C. Ralli
Telefonica
May 2016
IPv6 Destination Option for Congestion Exposure (ConEx)
Abstract
Congestion Exposure (ConEx) is a mechanism by which senders inform
the network about the congestion encountered by packets earlier in
the same flow. This document specifies an IPv6 destination option
that is capable of carrying ConEx markings in IPv6 datagrams.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for examination, experimental implementation, and
evaluation.
This document defines an Experimental Protocol for the Internet
community. 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). Not
all documents approved by the IESG are a candidate for any level of
Internet Standard; see 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/rfc7837.
Krishnan, et al. Experimental [Page 1]
RFC 7837 ConEx Destination Option May 2016
Copyright Notice
Copyright (c) 2016 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 Used in This Document . . . . . . . . . . . . . . 3
3. Requirements for the Coding of ConEx in IPv6 . . . . . . . . 4
4. ConEx Destination Option (CDO) . . . . . . . . . . . . . . . 5
5. Implementation in the Fast Path of ConEx-Aware Routers . . . 8
6. Tunnel Processing . . . . . . . . . . . . . . . . . . . . . . 8
7. Compatibility with Use of IPsec . . . . . . . . . . . . . . . 9
8. Mitigating Flooding Attacks by Using Preferential Drop . . . 9
9. Security Considerations . . . . . . . . . . . . . . . . . . . 11
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
11.1. Normative References . . . . . . . . . . . . . . . . . . 11
11.2. Informative References . . . . . . . . . . . . . . . . . 12
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
Krishnan, et al. Experimental [Page 2]
RFC 7837 ConEx Destination Option May 2016
1. Introduction
Congestion Exposure (ConEx) [RFC7713] is a mechanism by which senders
inform the network about the congestion encountered by packets
earlier in the same flow. This document specifies an IPv6
destination option [RFC2460] that can be used for performing ConEx
markings in IPv6 datagrams.
This document specifies the ConEx wire protocol in IPv6. The ConEx
information can be used by any network element on the path to, for
example, do traffic management or egress policing. Additionally,
this information will potentially be used by an audit function that
checks the integrity of the sender's signaling. Further, each
transport protocol that supports ConEx signaling will need to
precisely specify when the transport sets ConEx markings (e.g., the
behavior for TCP is specified in [RFC7786]).
This document specifies ConEx for IPv6 only. Due to space
limitations in the IPv4 header and the risk of options that might be
stripped by a middlebox in IPv4, the primary goal of the working
Show full document text