| draft-ietf-lisp-rfc6830bis-19.txt | draft-ietf-lisp-rfc6830bis-20.txt | |||
|---|---|---|---|---|
| Network Working Group D. Farinacci | Network Working Group D. Farinacci | |||
| Internet-Draft V. Fuller | Internet-Draft V. Fuller | |||
| Obsoletes: 6830 (if approved) D. Meyer | Obsoletes: 6830 (if approved) D. Meyer | |||
| Intended status: Standards Track D. Lewis | Intended status: Standards Track D. Lewis | |||
| Expires: March 26, 2019 Cisco Systems | Expires: March 30, 2019 Cisco Systems | |||
| A. Cabellos (Ed.) | A. Cabellos (Ed.) | |||
| UPC/BarcelonaTech | UPC/BarcelonaTech | |||
| September 22, 2018 | September 26, 2018 | |||
| The Locator/ID Separation Protocol (LISP) | The Locator/ID Separation Protocol (LISP) | |||
| draft-ietf-lisp-rfc6830bis-19 | draft-ietf-lisp-rfc6830bis-20 | |||
| Abstract | Abstract | |||
| This document describes the Data-Plane protocol for the Locator/ID | This document describes the Data-Plane protocol for the Locator/ID | |||
| Separation Protocol (LISP). LISP defines two namespaces, End-point | Separation Protocol (LISP). LISP defines two namespaces, End-point | |||
| Identifiers (EIDs) that identify end-hosts and Routing Locators | Identifiers (EIDs) that identify end-hosts and Routing Locators | |||
| (RLOCs) that identify network attachment points. With this, LISP | (RLOCs) that identify network attachment points. With this, LISP | |||
| effectively separates control from data, and allows routers to create | effectively separates control from data, and allows routers to create | |||
| overlay networks. LISP-capable routers exchange encapsulated packets | overlay networks. LISP-capable routers exchange encapsulated packets | |||
| according to EID-to-RLOC mappings stored in a local Map-Cache. | according to EID-to-RLOC mappings stored in a local Map-Cache. | |||
| skipping to change at page 1, line 46 ¶ | skipping to change at page 1, line 46 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| 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." | |||
| This Internet-Draft will expire on March 26, 2019. | This Internet-Draft will expire on March 30, 2019. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2018 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 | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://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 | |||
| skipping to change at page 3, line 7 ¶ | skipping to change at page 3, line 7 ¶ | |||
| 17. Network Management Considerations . . . . . . . . . . . . . . 33 | 17. Network Management Considerations . . . . . . . . . . . . . . 33 | |||
| 18. Changes since RFC 6830 . . . . . . . . . . . . . . . . . . . 33 | 18. Changes since RFC 6830 . . . . . . . . . . . . . . . . . . . 33 | |||
| 19. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 | 19. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 | |||
| 19.1. LISP UDP Port Numbers . . . . . . . . . . . . . . . . . 34 | 19.1. LISP UDP Port Numbers . . . . . . . . . . . . . . . . . 34 | |||
| 20. References . . . . . . . . . . . . . . . . . . . . . . . . . 34 | 20. References . . . . . . . . . . . . . . . . . . . . . . . . . 34 | |||
| 20.1. Normative References . . . . . . . . . . . . . . . . . . 34 | 20.1. Normative References . . . . . . . . . . . . . . . . . . 34 | |||
| 20.2. Informative References . . . . . . . . . . . . . . . . . 35 | 20.2. Informative References . . . . . . . . . . . . . . . . . 35 | |||
| Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 39 | Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 39 | |||
| Appendix B. Document Change Log . . . . . . . . . . . . . . . . 39 | Appendix B. Document Change Log . . . . . . . . . . . . . . . . 39 | |||
| B.1. Changes to draft-ietf-lisp-rfc6830bis-19 . . . . . . . . 40 | B.1. Changes to draft-ietf-lisp-rfc6830bis-20 . . . . . . . . 40 | |||
| B.2. Changes to draft-ietf-lisp-rfc6830bis-18 . . . . . . . . 40 | B.2. Changes to draft-ietf-lisp-rfc6830bis-19 . . . . . . . . 40 | |||
| B.3. Changes to draft-ietf-lisp-rfc6830bis-17 . . . . . . . . 40 | B.3. Changes to draft-ietf-lisp-rfc6830bis-18 . . . . . . . . 40 | |||
| B.4. Changes to draft-ietf-lisp-rfc6830bis-16 . . . . . . . . 40 | B.4. Changes to draft-ietf-lisp-rfc6830bis-17 . . . . . . . . 40 | |||
| B.5. Changes to draft-ietf-lisp-rfc6830bis-15 . . . . . . . . 40 | B.5. Changes to draft-ietf-lisp-rfc6830bis-16 . . . . . . . . 40 | |||
| B.6. Changes to draft-ietf-lisp-rfc6830bis-14 . . . . . . . . 40 | B.6. Changes to draft-ietf-lisp-rfc6830bis-15 . . . . . . . . 40 | |||
| B.7. Changes to draft-ietf-lisp-rfc6830bis-13 . . . . . . . . 41 | B.7. Changes to draft-ietf-lisp-rfc6830bis-14 . . . . . . . . 41 | |||
| B.8. Changes to draft-ietf-lisp-rfc6830bis-12 . . . . . . . . 41 | B.8. Changes to draft-ietf-lisp-rfc6830bis-13 . . . . . . . . 41 | |||
| B.9. Changes to draft-ietf-lisp-rfc6830bis-11 . . . . . . . . 41 | B.9. Changes to draft-ietf-lisp-rfc6830bis-12 . . . . . . . . 41 | |||
| B.10. Changes to draft-ietf-lisp-rfc6830bis-10 . . . . . . . . 41 | B.10. Changes to draft-ietf-lisp-rfc6830bis-11 . . . . . . . . 41 | |||
| B.11. Changes to draft-ietf-lisp-rfc6830bis-09 . . . . . . . . 41 | B.11. Changes to draft-ietf-lisp-rfc6830bis-10 . . . . . . . . 41 | |||
| B.12. Changes to draft-ietf-lisp-rfc6830bis-08 . . . . . . . . 42 | B.12. Changes to draft-ietf-lisp-rfc6830bis-09 . . . . . . . . 42 | |||
| B.13. Changes to draft-ietf-lisp-rfc6830bis-07 . . . . . . . . 42 | B.13. Changes to draft-ietf-lisp-rfc6830bis-08 . . . . . . . . 42 | |||
| B.14. Changes to draft-ietf-lisp-rfc6830bis-06 . . . . . . . . 42 | B.14. Changes to draft-ietf-lisp-rfc6830bis-07 . . . . . . . . 42 | |||
| B.15. Changes to draft-ietf-lisp-rfc6830bis-05 . . . . . . . . 43 | B.15. Changes to draft-ietf-lisp-rfc6830bis-06 . . . . . . . . 42 | |||
| B.16. Changes to draft-ietf-lisp-rfc6830bis-04 . . . . . . . . 43 | B.16. Changes to draft-ietf-lisp-rfc6830bis-05 . . . . . . . . 43 | |||
| B.17. Changes to draft-ietf-lisp-rfc6830bis-03 . . . . . . . . 43 | B.17. Changes to draft-ietf-lisp-rfc6830bis-04 . . . . . . . . 43 | |||
| B.18. Changes to draft-ietf-lisp-rfc6830bis-02 . . . . . . . . 43 | B.18. Changes to draft-ietf-lisp-rfc6830bis-03 . . . . . . . . 43 | |||
| B.19. Changes to draft-ietf-lisp-rfc6830bis-01 . . . . . . . . 43 | B.19. Changes to draft-ietf-lisp-rfc6830bis-02 . . . . . . . . 43 | |||
| B.20. Changes to draft-ietf-lisp-rfc6830bis-00 . . . . . . . . 44 | B.20. Changes to draft-ietf-lisp-rfc6830bis-01 . . . . . . . . 43 | |||
| B.21. Changes to draft-ietf-lisp-rfc6830bis-00 . . . . . . . . 44 | ||||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44 | |||
| 1. Introduction | 1. Introduction | |||
| This document describes the Locator/Identifier Separation Protocol | This document describes the Locator/Identifier Separation Protocol | |||
| (LISP). LISP is an encapsulation protocol built around the | (LISP). LISP is an encapsulation protocol built around the | |||
| fundamental idea of separating the topological location of a network | fundamental idea of separating the topological location of a network | |||
| attachment point from the node's identity [CHIAPPA]. As a result | attachment point from the node's identity [CHIAPPA]. As a result | |||
| LISP creates two namespaces: Endpoint Identifiers (EIDs), that are | LISP creates two namespaces: Endpoint Identifiers (EIDs), that are | |||
| used to identify end-hosts (e.g., nodes or Virtual Machines) and | used to identify end-hosts (e.g., nodes or Virtual Machines) and | |||
| skipping to change at page 18, line 49 ¶ | skipping to change at page 18, line 49 ¶ | |||
| the case of IPv6) SHOULD be copied from the inner-header 'Time to | the case of IPv6) SHOULD be copied from the inner-header 'Time to | |||
| Live' field. | Live' field. | |||
| o The outer-header 'Differentiated Services Code Point' (DSCP) field | o The outer-header 'Differentiated Services Code Point' (DSCP) field | |||
| (or the 'Traffic Class' field, in the case of IPv6) SHOULD be | (or the 'Traffic Class' field, in the case of IPv6) SHOULD be | |||
| copied from the inner-header DSCP field ('Traffic Class' field, in | copied from the inner-header DSCP field ('Traffic Class' field, in | |||
| the case of IPv6) to the outer-header. | the case of IPv6) to the outer-header. | |||
| o The 'Explicit Congestion Notification' (ECN) field (bits 6 and 7 | o The 'Explicit Congestion Notification' (ECN) field (bits 6 and 7 | |||
| of the IPv6 'Traffic Class' field) requires special treatment in | of the IPv6 'Traffic Class' field) requires special treatment in | |||
| order to avoid discarding indications of congestion [RFC3168]. | order to avoid discarding indications of congestion [RFC6040]. | |||
| ITR encapsulation MUST copy the 2-bit 'ECN' field from the inner | ITR encapsulation MUST copy the 2-bit 'ECN' field from the inner | |||
| header to the outer header. Re-encapsulation MUST copy the 2-bit | header to the outer header. Re-encapsulation MUST copy the 2-bit | |||
| 'ECN' field from the stripped outer header to the new outer | 'ECN' field from the stripped outer header to the new outer | |||
| header. | header. | |||
| When doing ETR/PETR decapsulation: | When doing ETR/PETR decapsulation: | |||
| o The inner-header 'Time to Live' field (or 'Hop Limit' field, in | o The inner-header 'Time to Live' field (or 'Hop Limit' field, in | |||
| the case of IPv6) SHOULD be copied from the outer-header 'Time to | the case of IPv6) SHOULD be copied from the outer-header 'Time to | |||
| Live' field, when the Time to Live value of the outer header is | Live' field, when the Time to Live value of the outer header is | |||
| skipping to change at page 34, line 47 ¶ | skipping to change at page 34, line 47 ¶ | |||
| Requirement Levels", BCP 14, RFC 2119, | Requirement Levels", BCP 14, RFC 2119, | |||
| DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
| <https://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
| [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, | [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, | |||
| "Definition of the Differentiated Services Field (DS | "Definition of the Differentiated Services Field (DS | |||
| Field) in the IPv4 and IPv6 Headers", RFC 2474, | Field) in the IPv4 and IPv6 Headers", RFC 2474, | |||
| DOI 10.17487/RFC2474, December 1998, | DOI 10.17487/RFC2474, December 1998, | |||
| <https://www.rfc-editor.org/info/rfc2474>. | <https://www.rfc-editor.org/info/rfc2474>. | |||
| [RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition | ||||
| of Explicit Congestion Notification (ECN) to IP", | ||||
| RFC 3168, DOI 10.17487/RFC3168, September 2001, | ||||
| <https://www.rfc-editor.org/info/rfc3168>. | ||||
| [RFC6040] Briscoe, B., "Tunnelling of Explicit Congestion | [RFC6040] Briscoe, B., "Tunnelling of Explicit Congestion | |||
| Notification", RFC 6040, DOI 10.17487/RFC6040, November | Notification", RFC 6040, DOI 10.17487/RFC6040, November | |||
| 2010, <https://www.rfc-editor.org/info/rfc6040>. | 2010, <https://www.rfc-editor.org/info/rfc6040>. | |||
| [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for | [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for | |||
| Writing an IANA Considerations Section in RFCs", BCP 26, | Writing an IANA Considerations Section in RFCs", BCP 26, | |||
| RFC 8126, DOI 10.17487/RFC8126, June 2017, | RFC 8126, DOI 10.17487/RFC8126, June 2017, | |||
| <https://www.rfc-editor.org/info/rfc8126>. | <https://www.rfc-editor.org/info/rfc8126>. | |||
| [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | |||
| skipping to change at page 40, line 5 ¶ | skipping to change at page 40, line 5 ¶ | |||
| The LISP working group would like to give a special thanks to Jari | The LISP working group would like to give a special thanks to Jari | |||
| Arkko, the Internet Area AD at the time that the set of LISP | Arkko, the Internet Area AD at the time that the set of LISP | |||
| documents were being prepared for IESG last call, and for his | documents were being prepared for IESG last call, and for his | |||
| meticulous reviews and detailed commentaries on the 7 working group | meticulous reviews and detailed commentaries on the 7 working group | |||
| last call documents progressing toward standards-track RFCs. | last call documents progressing toward standards-track RFCs. | |||
| Appendix B. Document Change Log | Appendix B. Document Change Log | |||
| [RFC Editor: Please delete this section on publication as RFC.] | [RFC Editor: Please delete this section on publication as RFC.] | |||
| B.1. Changes to draft-ietf-lisp-rfc6830bis-19 | B.1. Changes to draft-ietf-lisp-rfc6830bis-20 | |||
| o Posted late-September 2018. | ||||
| o Fix old reference to RFC3168, changed to RFC6040. | ||||
| B.2. Changes to draft-ietf-lisp-rfc6830bis-19 | ||||
| o Posted late-September 2018. | o Posted late-September 2018. | |||
| o More editorial changes. | o More editorial changes. | |||
| B.2. Changes to draft-ietf-lisp-rfc6830bis-18 | B.3. Changes to draft-ietf-lisp-rfc6830bis-18 | |||
| o Posted mid-September 2018. | o Posted mid-September 2018. | |||
| o Changes to reflect comments from Secdir review (Mirja). | o Changes to reflect comments from Secdir review (Mirja). | |||
| B.3. Changes to draft-ietf-lisp-rfc6830bis-17 | B.4. Changes to draft-ietf-lisp-rfc6830bis-17 | |||
| o Posted September 2018. | o Posted September 2018. | |||
| o Indicate in the "Changes since RFC 6830" section why the document | o Indicate in the "Changes since RFC 6830" section why the document | |||
| has been shortened in length. | has been shortened in length. | |||
| o Make reference to RFC 8085 about UDP congestion control. | o Make reference to RFC 8085 about UDP congestion control. | |||
| o More editorial changes from multiple IESG reviews. | o More editorial changes from multiple IESG reviews. | |||
| B.4. Changes to draft-ietf-lisp-rfc6830bis-16 | B.5. Changes to draft-ietf-lisp-rfc6830bis-16 | |||
| o Posted late August 2018. | o Posted late August 2018. | |||
| o Distinguish the message type names between ICMP for IPv4 and ICMP | o Distinguish the message type names between ICMP for IPv4 and ICMP | |||
| for IPv6 for handling MTU issues. | for IPv6 for handling MTU issues. | |||
| B.5. Changes to draft-ietf-lisp-rfc6830bis-15 | B.6. Changes to draft-ietf-lisp-rfc6830bis-15 | |||
| o Posted August 2018. | o Posted August 2018. | |||
| o Final editorial changes before RFC submission for Proposed | o Final editorial changes before RFC submission for Proposed | |||
| Standard. | Standard. | |||
| o Added section "Changes since RFC 6830" so implementers are | o Added section "Changes since RFC 6830" so implementers are | |||
| informed of any changes since the last RFC publication. | informed of any changes since the last RFC publication. | |||
| B.6. Changes to draft-ietf-lisp-rfc6830bis-14 | B.7. Changes to draft-ietf-lisp-rfc6830bis-14 | |||
| o Posted July 2018 IETF week. | o Posted July 2018 IETF week. | |||
| o Put obsolete of RFC 6830 in Intro section in addition to abstract. | o Put obsolete of RFC 6830 in Intro section in addition to abstract. | |||
| B.7. Changes to draft-ietf-lisp-rfc6830bis-13 | B.8. Changes to draft-ietf-lisp-rfc6830bis-13 | |||
| o Posted March IETF Week 2018. | o Posted March IETF Week 2018. | |||
| o Clarified that a new nonce is required per RLOC. | o Clarified that a new nonce is required per RLOC. | |||
| o Removed 'Clock Sweep' section. This text must be placed in a new | o Removed 'Clock Sweep' section. This text must be placed in a new | |||
| OAM document. | OAM document. | |||
| o Some references changed from normative to informative | o Some references changed from normative to informative | |||
| B.8. Changes to draft-ietf-lisp-rfc6830bis-12 | B.9. Changes to draft-ietf-lisp-rfc6830bis-12 | |||
| o Posted July 2018. | o Posted July 2018. | |||
| o Fixed Luigi editorial comments to ready draft for RFC status. | o Fixed Luigi editorial comments to ready draft for RFC status. | |||
| B.9. Changes to draft-ietf-lisp-rfc6830bis-11 | B.10. Changes to draft-ietf-lisp-rfc6830bis-11 | |||
| o Posted March 2018. | o Posted March 2018. | |||
| o Removed sections 16, 17 and 18 (Mobility, Deployment and | o Removed sections 16, 17 and 18 (Mobility, Deployment and | |||
| Traceroute considerations). This text must be placed in a new OAM | Traceroute considerations). This text must be placed in a new OAM | |||
| document. | document. | |||
| B.10. Changes to draft-ietf-lisp-rfc6830bis-10 | B.11. Changes to draft-ietf-lisp-rfc6830bis-10 | |||
| o Posted March 2018. | o Posted March 2018. | |||
| o Updated section 'Router Locator Selection' stating that the Data- | o Updated section 'Router Locator Selection' stating that the Data- | |||
| Plane MUST follow what's stored in the Map-Cache (priorities and | Plane MUST follow what's stored in the Map-Cache (priorities and | |||
| weights). | weights). | |||
| o Section 'Routing Locator Reachability': Removed bullet point 2 | o Section 'Routing Locator Reachability': Removed bullet point 2 | |||
| (ICMP Network/Host Unreachable),3 (hints from BGP),4 (ICMP Port | (ICMP Network/Host Unreachable),3 (hints from BGP),4 (ICMP Port | |||
| Unreachable),5 (receive a Map-Reply as a response) and RLOC | Unreachable),5 (receive a Map-Reply as a response) and RLOC | |||
| probing | probing | |||
| o Removed 'Solicit-Map Request'. | o Removed 'Solicit-Map Request'. | |||
| B.11. Changes to draft-ietf-lisp-rfc6830bis-09 | B.12. Changes to draft-ietf-lisp-rfc6830bis-09 | |||
| o Posted January 2018. | o Posted January 2018. | |||
| o Add more details in section 5.3 about DSCP processing during | o Add more details in section 5.3 about DSCP processing during | |||
| encapsulation and decapsulation. | encapsulation and decapsulation. | |||
| o Added clarity to definitions in the Definition of Terms section | o Added clarity to definitions in the Definition of Terms section | |||
| from various commenters. | from various commenters. | |||
| o Removed PA and PI definitions from Definition of Terms section. | o Removed PA and PI definitions from Definition of Terms section. | |||
| o More editorial changes. | o More editorial changes. | |||
| o Removed 4342 from IANA section and move to RFC6833 IANA section. | o Removed 4342 from IANA section and move to RFC6833 IANA section. | |||
| B.12. Changes to draft-ietf-lisp-rfc6830bis-08 | B.13. Changes to draft-ietf-lisp-rfc6830bis-08 | |||
| o Posted January 2018. | o Posted January 2018. | |||
| o Remove references to research work for any protocol mechanisms. | o Remove references to research work for any protocol mechanisms. | |||
| o Document scanned to make sure it is RFC 2119 compliant. | o Document scanned to make sure it is RFC 2119 compliant. | |||
| o Made changes to reflect comments from document WG shepherd Luigi | o Made changes to reflect comments from document WG shepherd Luigi | |||
| Iannone. | Iannone. | |||
| o Ran IDNITs on the document. | o Ran IDNITs on the document. | |||
| B.13. Changes to draft-ietf-lisp-rfc6830bis-07 | B.14. Changes to draft-ietf-lisp-rfc6830bis-07 | |||
| o Posted November 2017. | o Posted November 2017. | |||
| o Rephrase how Instance-IDs are used and don't refer to [RFC1918] | o Rephrase how Instance-IDs are used and don't refer to [RFC1918] | |||
| addresses. | addresses. | |||
| B.14. Changes to draft-ietf-lisp-rfc6830bis-06 | B.15. Changes to draft-ietf-lisp-rfc6830bis-06 | |||
| o Posted October 2017. | o Posted October 2017. | |||
| o Put RTR definition before it is used. | o Put RTR definition before it is used. | |||
| o Rename references that are now working group drafts. | o Rename references that are now working group drafts. | |||
| o Remove "EIDs MUST NOT be used as used by a host to refer to other | o Remove "EIDs MUST NOT be used as used by a host to refer to other | |||
| hosts. Note that EID blocks MAY LISP RLOCs". | hosts. Note that EID blocks MAY LISP RLOCs". | |||
| skipping to change at page 43, line 9 ¶ | skipping to change at page 43, line 15 ¶ | |||
| o ETRs may, rather than will, be the ones to send Map-Replies. | o ETRs may, rather than will, be the ones to send Map-Replies. | |||
| o Recommend, rather than mandate, max encapsulation headers to 2. | o Recommend, rather than mandate, max encapsulation headers to 2. | |||
| o Reference VPN draft when introducing Instance-ID. | o Reference VPN draft when introducing Instance-ID. | |||
| o Indicate that SMRs can be sent when ITR/ETR are in the same node. | o Indicate that SMRs can be sent when ITR/ETR are in the same node. | |||
| o Clarify when private addresses can be used. | o Clarify when private addresses can be used. | |||
| B.15. Changes to draft-ietf-lisp-rfc6830bis-05 | B.16. Changes to draft-ietf-lisp-rfc6830bis-05 | |||
| o Posted August 2017. | o Posted August 2017. | |||
| o Make it clear that a Re-encapsulating Tunnel Router is an RTR. | o Make it clear that a Re-encapsulating Tunnel Router is an RTR. | |||
| B.16. Changes to draft-ietf-lisp-rfc6830bis-04 | B.17. Changes to draft-ietf-lisp-rfc6830bis-04 | |||
| o Posted July 2017. | o Posted July 2017. | |||
| o Changed reference of IPv6 RFC2460 to RFC8200. | o Changed reference of IPv6 RFC2460 to RFC8200. | |||
| o Indicate that the applicability statement for UDP zero checksums | o Indicate that the applicability statement for UDP zero checksums | |||
| over IPv6 adheres to RFC6936. | over IPv6 adheres to RFC6936. | |||
| B.17. Changes to draft-ietf-lisp-rfc6830bis-03 | B.18. Changes to draft-ietf-lisp-rfc6830bis-03 | |||
| o Posted May 2017. | o Posted May 2017. | |||
| o Move the control-plane related codepoints in the IANA | o Move the control-plane related codepoints in the IANA | |||
| Considerations section to RFC6833bis. | Considerations section to RFC6833bis. | |||
| B.18. Changes to draft-ietf-lisp-rfc6830bis-02 | B.19. Changes to draft-ietf-lisp-rfc6830bis-02 | |||
| o Posted April 2017. | o Posted April 2017. | |||
| o Reflect some editorial comments from Damien Sausez. | o Reflect some editorial comments from Damien Sausez. | |||
| B.19. Changes to draft-ietf-lisp-rfc6830bis-01 | B.20. Changes to draft-ietf-lisp-rfc6830bis-01 | |||
| o Posted March 2017. | o Posted March 2017. | |||
| o Include references to new RFCs published. | o Include references to new RFCs published. | |||
| o Change references from RFC6833 to RFC6833bis. | o Change references from RFC6833 to RFC6833bis. | |||
| o Clarified LCAF text in the IANA section. | o Clarified LCAF text in the IANA section. | |||
| o Remove references to "experimental". | o Remove references to "experimental". | |||
| B.20. Changes to draft-ietf-lisp-rfc6830bis-00 | B.21. Changes to draft-ietf-lisp-rfc6830bis-00 | |||
| o Posted December 2016. | o Posted December 2016. | |||
| o Created working group document from draft-farinacci-lisp | o Created working group document from draft-farinacci-lisp | |||
| -rfc6830-00 individual submission. No other changes made. | -rfc6830-00 individual submission. No other changes made. | |||
| Authors' Addresses | Authors' Addresses | |||
| Dino Farinacci | Dino Farinacci | |||
| Cisco Systems | Cisco Systems | |||
| End of changes. 27 change blocks. | ||||
| 50 lines changed or deleted | 52 lines changed or added | |||
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||