draft-ietf-tsvwg-tunnel-congestion-feedback-01.txt   draft-ietf-tsvwg-tunnel-congestion-feedback-02.txt 
Internet Engineering Task Force X. Wei Internet Engineering Task Force X. Wei
INTERNET-DRAFT Huawei Technologies INTERNET-DRAFT Huawei Technologies
Intended Status: Informational L.Zhu Intended Status: Informational L.Zhu
Expires: June 2, 2016 Huawei Technologies Expires: January 9, 2017 Huawei Technologies
L.Deng L.Deng
China Mobile China Mobile
November 30, 2015 July 8, 2016
Tunnel Congestion Feedback Tunnel Congestion Feedback
draft-ietf-tsvwg-tunnel-congestion-feedback-01 draft-ietf-tsvwg-tunnel-congestion-feedback-02
Abstract Abstract
This document describes a mechanism to calculate congestion of a This document describes a mechanism to calculate congestion of a
tunnel segment based on RFC6040 recommendations, and a feedback tunnel segment based on RFC6040 recommendations, and a feedback
protocol by which to send the measured congestion of the tunnel from protocol by which to send the measured congestion of the tunnel from
egress to ingress . A basic model for measuring tunnel congestion egress to ingress . A basic model for measuring tunnel congestion
and feedback is described, and a protocol for carrying the feedback and feedback is described, and a protocol for carrying the feedback
data is outlined. data is outlined.
skipping to change at page 2, line 7 skipping to change at page 2, line 7
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Copyright and License Notice Copyright and License Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 41 skipping to change at page 2, line 41
5.1.2 ect0-nectPacketTotalCount . . . . . . . . . . . . . . . 9 5.1.2 ect0-nectPacketTotalCount . . . . . . . . . . . . . . . 9
5.1.3 ect1-nectPacketTotalCount . . . . . . . . . . . . . . . 10 5.1.3 ect1-nectPacketTotalCount . . . . . . . . . . . . . . . 10
5.1.4 ce-nectPacketTotalCount . . . . . . . . . . . . . . . . 10 5.1.4 ce-nectPacketTotalCount . . . . . . . . . . . . . . . . 10
5.1.5 ce-ect0PacketTotalCount . . . . . . . . . . . . . . . . 10 5.1.5 ce-ect0PacketTotalCount . . . . . . . . . . . . . . . . 10
5.1.6 ce-ect1PacketTotalCount . . . . . . . . . . . . . . . . 11 5.1.6 ce-ect1PacketTotalCount . . . . . . . . . . . . . . . . 11
5.1.7 ect0-ect0PacketTotalCount . . . . . . . . . . . . . . . 11 5.1.7 ect0-ect0PacketTotalCount . . . . . . . . . . . . . . . 11
5.1.8 ect1-ect1PacketTotalCount . . . . . . . . . . . . . . . 11 5.1.8 ect1-ect1PacketTotalCount . . . . . . . . . . . . . . . 11
6. Congestion Management . . . . . . . . . . . . . . . . . . . . . 12 6. Congestion Management . . . . . . . . . . . . . . . . . . . . . 12
7. Security . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 7. Security . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 12 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 12
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1 Normative References . . . . . . . . . . . . . . . . . . . 13 9.1 Normative References . . . . . . . . . . . . . . . . . . . 14
9.2 Informative References . . . . . . . . . . . . . . . . . . 13 9.2 Informative References . . . . . . . . . . . . . . . . . . 15
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
In IP network, persistent congestion (or named congestion collapse) In IP network, persistent congestion (or named congestion collapse)
lowers transport throughput, leading to waste of network resource. lowers transport throughput, leading to waste of network resource.
Appropriate congestion control mechanisms are therefore critical to Appropriate congestion control mechanisms are therefore critical to
prevent the network from falling into the persistent congestion prevent the network from falling into the persistent congestion
state. Currently, transport protocols such as TCP[RFC793], state. Currently, transport protocols such as TCP[RFC793],
SCTP[RFC4960], DCCP[RFC4340], have their built-in congestion control SCTP[RFC4960], DCCP[RFC4340], have their built-in congestion control
mechanisms, and even for certain single transport protocol like TCP mechanisms, and even for certain single transport protocol like TCP
skipping to change at page 5, line 14 skipping to change at page 5, line 14
+-------------------+ +-------------------+
|+---------+ +--+ | |+---------+ +--+ |
feedback ||Collector|---|DP| | feedback ||Collector|---|DP| |
+---->|+---------+ +--+ |######### +---->|+---------+ +--+ |#########
| | | # | | | #
| | Controller | # | | Controller | #
| +-------------------+ # | +-------------------+ #
| # | #
| # | #
+--------------+ +------V------+ +--------------+ +------V------+
| +--------+ | | | | +--------+ | | |
| |Exporter| | | | | |Exporter| | | |
| +---|----+ | | | | +---|----+ | | |
| +--|--+ | | | | +--|--+ | | |
| |Meter| | | | | |Meter| | | |
| +-----+ | | | | +-----+ | | |
| | | +--+ | | | | +--+ |
| | | |AP| | | | | |AP| |
| | | +--+ | | | | +--+ |
|Egress | | Ingress | |Egress | | Ingress |
+--------------+ +-------------+ +--------------+ +-------------+
skipping to change at page 5, line 40 skipping to change at page 5, line 40
named "controller". Here, after Exporter function on egress has named "controller". Here, after Exporter function on egress has
collected network congestion level information, it feeds back the collected network congestion level information, it feeds back the
information to the collector of a controller instead of the ingress. information to the collector of a controller instead of the ingress.
Then the controller makes congestion management decision and sends Then the controller makes congestion management decision and sends
the decision to the ingress to implement. the decision to the ingress to implement.
4. Congestion Level Measurement 4. Congestion Level Measurement
This section describes how to measure congestion level in a tunnel. This section describes how to measure congestion level in a tunnel.
There may be different approaches to packet loss detection for There could be different approaches of packet loss detection for
different tunneling protocol scenarios. For instance, if there is a different tunneling protocol scenarios. For instance, if there is a
sequence field in the tunneling protocol header, it will be easy for sequence field in the tunneling protocol header, it will be easy for
egress to detect packet loss through the gaps in sequence number egress to detect packet loss through the gaps in sequence number
space. Another approach is to compare the number of packets entering space. Another approach is to compare the number of packets entering
ingress and the number of packets arriving at egress over the same ingress and the number of packets arriving at egress over the same
span of packets. This document will focus on the latter one which is span of packets. This document will focus on the latter one which is
a more general approach. a more general approach.
If the routers support Explicit Congestion Notification (ECN), after If the routers support Explicit Congestion Notification (ECN), after
router's queue length is over a predefined threshold, the routers router's queue length is over a predefined threshold, the routers
skipping to change at page 9, line 31 skipping to change at page 9, line 31
# Meter on egress measures congestion level information according to # Meter on egress measures congestion level information according to
template record, the template record can be preconfigured or use the template record, the template record can be preconfigured or use the
template record from ingress, the content of template record should template record from ingress, the content of template record should
be the same as template record of ingress. be the same as template record of ingress.
# Exporter of egress sends measurement record together with the # Exporter of egress sends measurement record together with the
measurement record of ingress to Controller or back to the ingress. measurement record of ingress to Controller or back to the ingress.
5.1 IPFIX Extentions 5.1 IPFIX Extentions
This sub-section defines a list of new IPFIX Information Elements
according to RFC7013 [RFC7013].
5.1.1 ce-cePacketTotalCount 5.1.1 ce-cePacketTotalCount
Description: The total number of incoming packets with CE|CE ECN Description: The total number of incoming packets with CE|CE ECN
marking combination for this Flow at the Observation Point since the marking combination for this Flow at the Observation Point since the
Metering Process (re-)initialization for this Observation Point. Metering Process (re-)initialization for this Observation Point.
Abstract Data Type: unsigned64 Abstract Data Type: unsigned64
Data Type Semantics: totalCounter Data Type Semantics: totalCounter
skipping to change at page 12, line 49 skipping to change at page 12, line 51
7. Security 7. Security
This document describes the tunnel congestion calculation and This document describes the tunnel congestion calculation and
feedback. For feeding back congestion, security mechanisms of IPFIX feedback. For feeding back congestion, security mechanisms of IPFIX
are expected to be sufficient. No additional security concerns are are expected to be sufficient. No additional security concerns are
expected. expected.
8. IANA Considerations 8. IANA Considerations
This document defines a set of new IPFIX Information Elements (IE). This document defines a set of new IPFIX Information Elements
New registry for these IE identifiers is needed. (IE),which need to be registered at IANA IPFIX Information Element
Registry.
TBD1~TBD8. ElementID: TBD1
Name:ce-cePacketTotalCount
Data Type: unsigned64
Data Type Semantics: totalCounter
Status: current
Description:The total number of incoming packets with CE|CE ECN
marking combination for this Flow at the Observation Point since the
Metering Process (re-)initialization for this Observation Point.
Units: packets
ElementID: TBD2
Name:ect0-nectPacketTotalCount
Data Type: unsigned64
Data Type Semantics: totalCounter
Status: current
Description:The total number of incoming packets with ECT(0)|N-ECT
ECN marking combination for this Flow at the Observation Point since
the Metering Process (re-)initialization for this Observation Point.
Units: packets
ElementID: TBD3
Name: ect1-nectPacketTotalCount
Data Type: unsigned64
Data Type Semantics: totalCounter
Status: current
Description:The total number of incoming packets with ECT(1)|N-ECT
ECN marking combination for this Flow at the Observation Point since
the Metering Process (re-)initialization for this Observation Point.
Units: packets
ElementID: TBD4
Name:ce-nectPacketTotalCount
Data Type: unsigned64
Data Type Semantics: totalCounter
Status: current
Description:The total number of incoming packets with CE|N-ECT ECN
marking combination for this Flow at the Observation Point since the
Metering Process (re-)initialization for this Observation Point.
Units: packets
ElementID: TBD5
Name:ce-ect0PacketTotalCount
Data Type: unsigned64
Data Type Semantics: totalCounter
Status: current
Description:The total number of incoming packets with CE|ECT(0) ECN
marking combination for this Flow at the Observation Point since the
Metering Process (re-)initialization for this Observation Point.
Units: packets
ElementID: TBD6
Name:ce-ect1PacketTotalCount
Data Type: unsigned64
Data Type Semantics: totalCounter
Status: current
Description:The total number of incoming packets with CE|ECT(1) ECN
marking combination for this Flow at the Observation Point since the
Metering Process (re-)initialization for this Observation Point.
Units: packets
ElementID: TBD7
Name:ect0-ect0PacketTotalCount
Data Type: unsigned64
Data Type Semantics: totalCounter
Status: current
Description:The total number of incoming packets with ECT(0)|ECT(0)
ECN marking combination for this Flow at the Observation Point since
the Metering Process (re-)initialization for this Observation Point.
Units: packets
ElementID: TBD8
Name:ect1-ect1PacketTotalCount
Data Type: unsigned64
Data Type Semantics: totalCounter
Status: current
Description:The total number of incoming packets with
ECT(1)|ECT(1)ECN marking combination for this Flow at the Observation
Point since the Metering Process (re-)initialization for this
Observation Point.
Units: packets
[TO BE REMOVED: This registration should take place at the following
location: http://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-
information-elements]
9. References 9. References
9.1 Normative References 9.1 Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997, Requirement Levels", BCP 14, RFC 2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition [RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition
skipping to change at page 13, line 41 skipping to change at page 15, line 33
[RFC6040] Briscoe, B., "Tunnelling of Explicit Congestion [RFC6040] Briscoe, B., "Tunnelling of Explicit Congestion
Notification", RFC 6040, November 2010, <http://www.rfc- Notification", RFC 6040, November 2010, <http://www.rfc-
editor.org/info/rfc6040>. editor.org/info/rfc6040>.
[RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken, [RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken,
"Specification of the IP Flow Information Export (IPFIX) "Specification of the IP Flow Information Export (IPFIX)
Protocol for the Exchange of Flow Information", STD 77, Protocol for the Exchange of Flow Information", STD 77,
RFC 7011, September 2013, <http://www.rfc- RFC 7011, September 2013, <http://www.rfc-
editor.org/info/rfc7011>. editor.org/info/rfc7011>.
9.2 Informative References [RFC7013] Trammell, B. and B. Claise, "Guidelines for Authors and
Reviewers of IP Flow Information Export (IPFIX)
Information Elements", BCP 184, RFC 7013, September 2013,
<http://www.rfc-editor.org/info/rfc7013>.
[CONEX] Matt Mathis, Bob Briscoe. "Congestion Exposure (ConEx) [CONEX] Matt Mathis, Bob Briscoe. "Congestion Exposure (ConEx)
Concepts, Abstract Mechanism and Requirements", draft- Concepts, Abstract Mechanism and Requirements", RFC7713,
ietf-conex-abstract-mech-13, October 24, 2014 December 2015
9.2 Informative References
[CB] G. Fairhurst. "Network Transport Circuit Breakers", draft-ietf- [CB] G. Fairhurst. "Network Transport Circuit Breakers", draft-ietf-
tsvwg-circuit-breaker-01, April 02, 2015 tsvwg-circuit-breaker-01, April 02, 2015
[CP] Bob Briscoe, Murari Sridharan. "Network Performance Isolation [CP] Bob Briscoe, Murari Sridharan. "Network Performance Isolation
in Data Centres using Congestion Policing", draft-briscoe- in Data Centres using Congestion Policing", draft-briscoe-
conex-data-centre-02, February 14, 2014 conex-data-centre-02, February 14, 2014
10. Acknowledgements 10. Acknowledgements
Thanks Bob Briscoe for his insightful suggestions on the basic Thanks Bob Briscoe for his insightful suggestions on the basic
mechanisms of congestion information collection and many other useful mechanisms of congestion information collection and many other useful
comments. Thanks David Black for his useful technical suggestions. comments. Thanks David Black for his useful technical suggestions.
Also, thanks Anthony Chan and John Kaippallimalil for their careful Also, thanks Anthony Chan and John Kaippallimalil for their careful
reviews. reviews.
Authors' Addresses Authors' Addresses
Xinpeng Wei Xinpeng Wei
Beiqing Rd. Z-park No.156, Haidian District, Beiqing Rd. Z-park No.156, Haidian District,
 End of changes. 13 change blocks. 
18 lines changed or deleted 109 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/