| < draft-ietf-sfc-nsh-ecn-support-01.txt | draft-ietf-sfc-nsh-ecn-support-02.txt > | |||
|---|---|---|---|---|
| INTERNET-DRAFT Donald Eastlake | INTERNET-DRAFT Donald Eastlake | |||
| Intended status: Proposed Standard Futurewei Technologies | Intended status: Proposed Standard Futurewei Technologies | |||
| Bob Briscoe | Bob Briscoe | |||
| Independent | Independent | |||
| Andrew Malis | Andrew Malis | |||
| Futurewei Technologies | Futurewei Technologies | |||
| Expires: January 6, 2020 July 7, 2019 | Expires: June 31, 2020 January 1, 2020 | |||
| Explicit Congestion Notification (ECN) and Congestion Feedback | Explicit Congestion Notification (ECN) and Congestion Feedback | |||
| Using the Network Service Header (NSH) | Using the Network Service Header (NSH) | |||
| <draft-ietf-sfc-nsh-ecn-support-01.txt> | <draft-ietf-sfc-nsh-ecn-support-02.txt> | |||
| Abstract | Abstract | |||
| Explicit congestion notification (ECN) allows a forwarding element to | Explicit congestion notification (ECN) allows a forwarding element to | |||
| notify downstream devices of the onset of congestion without having | notify downstream devices of the onset of congestion without having | |||
| to drop packets. Coupled with a means to feed back information about | to drop packets. Coupled with a means to feed back information about | |||
| congestion to upstream nodes, this can improve network efficiency | congestion to upstream nodes, this can improve network efficiency | |||
| through better congestion control, frequently without packet drops. | through better congestion control, frequently without packet drops. | |||
| This document specifies ECN and congestion feedback support within a | This document specifies ECN and congestion feedback support within a | |||
| Service Function Chaining (SFC) domain through use of the Network | Service Function Chaining (SFC) domain through use of the Network | |||
| skipping to change at page 2, line 30 ¶ | skipping to change at page 2, line 30 ¶ | |||
| 3.2.1 At NSH Transit Nodes................................12 | 3.2.1 At NSH Transit Nodes................................12 | |||
| 3.2.2 At an SF/Proxy......................................13 | 3.2.2 At an SF/Proxy......................................13 | |||
| 3.2.3 At Other Forwarding Nodes...........................13 | 3.2.3 At Other Forwarding Nodes...........................13 | |||
| 3.3 At Exit/Egress........................................13 | 3.3 At Exit/Egress........................................13 | |||
| 3.4 Conservation of Packets...............................14 | 3.4 Conservation of Packets...............................14 | |||
| 4. Tunnel Congestion Feedback Support.....................15 | 4. Tunnel Congestion Feedback Support.....................15 | |||
| 5. IANA Considerations....................................16 | 5. IANA Considerations....................................16 | |||
| 6. Security Considerations................................17 | 6. Security Considerations................................17 | |||
| 7. Acknowledgements.......................................17 | 7. Acknowledgements.......................................17 | |||
| Normative References......................................18 | Normative References......................................18 | |||
| Informative References....................................19 | Informative References....................................19 | |||
| Authors' Addresses........................................20 | ||||
| INTERNET-DRAFT NSH ECN & Congestion Feedback | INTERNET-DRAFT NSH ECN & Congestion Feedback | |||
| 1. Introduction | 1. Introduction | |||
| Explicit congestion notification (ECN [RFC3168]) allows a forwarding | Explicit congestion notification (ECN [RFC3168]) allows a forwarding | |||
| element to notify downstream devices of the onset of congestion | element to notify downstream devices of the onset of congestion | |||
| without having to drop packets. Coupled with a means to feed back | without having to drop packets. Coupled with a means to feed back | |||
| information about congestion to upstream nodes, this can improve | information about congestion to upstream nodes, this can improve | |||
| network efficiency through better congestion control, frequently | network efficiency through better congestion control, frequently | |||
| without packet drops. This document specifies ECN and congestion | without packet drops. This document specifies ECN and congestion | |||
| skipping to change at page 20, line 11 ¶ | skipping to change at page 20, line 11 ¶ | |||
| Explicit Congestion Notification (ECN) Semantics for Ultra-Low | Explicit Congestion Notification (ECN) Semantics for Ultra-Low | |||
| Queuing Delay (L4S)", draft-ietf-tsvwg-ecn-l4s-id, work in | Queuing Delay (L4S)", draft-ietf-tsvwg-ecn-l4s-id, work in | |||
| progress. | progress. | |||
| INTERNET-DRAFT NSH ECN & Congestion Feedback | INTERNET-DRAFT NSH ECN & Congestion Feedback | |||
| Authors' Addresses | Authors' Addresses | |||
| Donald E. Eastlake, 3rd | Donald E. Eastlake, 3rd | |||
| Futurewei Technologies | Futurewei Technologies | |||
| 1424 Pro Shop Court | 2386 Panoramic Circle | |||
| Davenport, FL 33896 USA | Apopka, FL 32703 USA | |||
| Tel: +1-508-333-2270 | Tel: +1-508-333-2270 | |||
| Email: d3e3e3@gmail.com | Email: d3e3e3@gmail.com | |||
| Bob Briscoe | Bob Briscoe | |||
| Independent | Independent | |||
| UK | UK | |||
| Email: ietf@bobbriscoe.net | Email: ietf@bobbriscoe.net | |||
| URI: http://bobbriscoe.net/ | URI: http://bobbriscoe.net/ | |||
| Andrew G. Malis | Andrew G. Malis | |||
| Futurewei Technologies | Futurewei Technologies | |||
| Email: agmalis@gmail.com | Email: agmalis@gmail.com | |||
| INTERNET-DRAFT NSH ECN & Congestion Feedback | INTERNET-DRAFT NSH ECN & Congestion Feedback | |||
| Copyright and IPR Provisions | Copyright and IPR Provisions | |||
| Copyright (c) 2019 IETF Trust and the persons identified as the | Copyright (c) 2020 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 | |||
| End of changes. 6 change blocks. | ||||
| 8 lines changed or deleted | 5 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/ | ||||