| < draft-ietf-tsvwg-tunnel-congestion-feedback-06.txt | draft-ietf-tsvwg-tunnel-congestion-feedback-07.txt > | |||
|---|---|---|---|---|
| Internet Engineering Task Force X. Wei | Internet Engineering Task Force X. Wei | |||
| INTERNET-DRAFT Huawei Technologies | INTERNET-DRAFT Y. Li | |||
| Intended Status: Informational L.Zhu | Intended Status: Informational Huawei Technologies | |||
| Expires: June 7, 2018 Huawei Technologies | Expires: November 7, 2019 S. Boutros | |||
| L.Deng | VMware | |||
| L. Geng | ||||
| China Mobile | China Mobile | |||
| December 4, 2017 | May 6, 2019 | |||
| Tunnel Congestion Feedback | Tunnel Congestion Feedback | |||
| draft-ietf-tsvwg-tunnel-congestion-feedback-06 | draft-ietf-tsvwg-tunnel-congestion-feedback-07 | |||
| Abstract | Abstract | |||
| This document describes a method to measure congestion on a tunnel | This document describes a method to measure congestion on a tunnel | |||
| segment based on recommendations from RFC 6040, "Tunneling of | segment based on recommendations from RFC 6040, "Tunneling of | |||
| Explicit Congestion Notification", and to use IPFIX to communicate | Explicit Congestion Notification", and to use IPFIX to communicate | |||
| the congestion measurements from the tunnel's egress to a controller | the congestion measurements from the tunnel's egress to a controller | |||
| which can respond by modifying the traffic control policies at the | which can respond by modifying the traffic control policies at the | |||
| tunnel's ingress. | tunnel's ingress. | |||
| skipping to change at page 2, line 4 ¶ | skipping to change at page 2, line 6 ¶ | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| 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) 2017 IETF Trust and the persons identified as the | ||||
| Copyright (c) 2019 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 17, line 25 ¶ | skipping to change at page 17, line 25 ¶ | |||
| [TO BE REMOVED: This registration should take place at the following | [TO BE REMOVED: This registration should take place at the following | |||
| location: http://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix- | location: http://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix- | |||
| information-elements] | 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>. | ||||
| [RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition | [RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition | |||
| of Explicit Congestion Notification (ECN) to IP", | of Explicit Congestion Notification (ECN) to IP", | |||
| RFC 3168, September 2001, <http://www.rfc- | RFC 3168, September 2001. | |||
| editor.org/info/rfc3168>. | ||||
| [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. | [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. | |||
| Jacobson, "RTP: A Transport Protocol for Real-Time | Jacobson, "RTP: A Transport Protocol for Real-Time | |||
| Applications", STD 64, RFC 3550, July 2003, | Applications", STD 64, RFC 3550, July 2003. | |||
| <http://www.rfc-editor.org/info/rfc3550>. | ||||
| [RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P. | [RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P. | |||
| Conrad, "Stream Control Transmission Protocol (SCTP) | Conrad, "Stream Control Transmission Protocol (SCTP) | |||
| Partial Reliability Extension", RFC 3758, May 2004, | Partial Reliability Extension", RFC 3758, May 2004. | |||
| <http://www.rfc-editor.org/info/rfc3758>. | ||||
| [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram | [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram | |||
| Congestion Control Protocol (DCCP)", RFC 4340, March 2006, | Congestion Control Protocol (DCCP)", RFC 4340, March 2006. | |||
| <http://www.rfc-editor.org/info/rfc4340>. | ||||
| [RFC4960] Stewart, R., Ed., "Stream Control Transmission Protocol", | [RFC4960] Stewart, R., Ed., "Stream Control Transmission Protocol", | |||
| RFC 4960, September 2007, <http://www.rfc- | RFC 4960, September 2007. | |||
| editor.org/info/rfc4960>. | ||||
| [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. | |||
| editor.org/info/rfc6040>. | ||||
| [RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken, | ||||
| "Specification of the IP Flow Information Export (IPFIX) | ||||
| Protocol for the Exchange of Flow Information", STD 77, | ||||
| RFC 7011, September 2013, <http://www.rfc- | ||||
| editor.org/info/rfc7011>. | ||||
| [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", RFC7713, | Concepts, Abstract Mechanism and Requirements", RFC7713, | |||
| December 2015 | December 2015 | |||
| 9.2 Informative References | 9.2 Informative References | |||
| [RFC8084] G. Fairhurst. "Network Transport Circuit Breakers", draft- | [RFC8084] G. Fairhurst. "Network Transport Circuit Breakers", draft- | |||
| ietf-tsvwg-circuit-breaker-01, April 02, 2015 | ietf-tsvwg-circuit-breaker-01, April 02, 2015 | |||
| 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, Jake Holland, John Kaippallimalil and | Also, thanks Lei Zhu, Lingli Deng, Anthony Chan, Jake Holland, John | |||
| Vincent Roca for their careful reviews. | Kaippallimalil and Vincent Roca for their careful 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, | |||
| Beijing, 100095, P. R. China | Beijing, 100095, P. R. China | |||
| E-mail: weixinpeng@huawei.com | EMail: weixinpeng@huawei.com | |||
| Zhu Lei | Yizhou Li | |||
| Beiqing Rd. Z-park No.156, Haidian District, | Huawei Technologies | |||
| Beijing, 100095, P. R. China | 101 Software Avenue, | |||
| E-mail:lei.zhu@huawei.com | Nanjing 210012 | |||
| Lingli Deng | China | |||
| Beijing, 100095, P. R. China | ||||
| E-mail: denglingli@gmail.com | Phone: +86-25-56624584 | |||
| EMail: liyizhou@huawei.com | ||||
| Sami Boutros | ||||
| VMware, Inc. | ||||
| EMail: boutross@vmware.com | ||||
| Liang Geng | ||||
| China Mobile | ||||
| EMail: gengliang@chinamobile.com | ||||
| End of changes. 14 change blocks. | ||||
| 35 lines changed or deleted | 19 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||