--- 1/draft-ietf-lisp-rfc6830bis-12.txt 2018-07-15 10:13:11.853799228 -0700 +++ 2/draft-ietf-lisp-rfc6830bis-13.txt 2018-07-15 10:13:11.941801343 -0700 @@ -1,53 +1,55 @@ Network Working Group D. Farinacci Internet-Draft V. Fuller -Intended status: Standards Track D. Meyer -Expires: September 20, 2018 D. Lewis - Cisco Systems +Obsoletes: 6830 (if approved) D. Meyer +Intended status: Standards Track D. Lewis +Expires: January 16, 2019 Cisco Systems A. Cabellos (Ed.) UPC/BarcelonaTech - March 19, 2018 + July 15, 2018 The Locator/ID Separation Protocol (LISP) - draft-ietf-lisp-rfc6830bis-12 + draft-ietf-lisp-rfc6830bis-13 Abstract This document describes the Data-Plane protocol for the Locator/ID Separation Protocol (LISP). LISP defines two namespaces, End-point Identifiers (EIDs) that identify end-hosts and Routing Locators (RLOCs) that identify network attachment points. With this, LISP effectively separates control from data, and allows routers to create overlay networks. LISP-capable routers exchange encapsulated packets according to EID-to-RLOC mappings stored in a local Map-Cache. LISP requires no change to either host protocol stacks or to underlay routers and offers Traffic Engineering, multihoming and mobility, among other features. + This document obsoletes RFC 6830. + Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on September 20, 2018. + This Internet-Draft will expire on January 16, 2019. Copyright Notice Copyright (c) 2018 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 (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -58,23 +60,23 @@ described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 4 3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4 4. Basic Overview . . . . . . . . . . . . . . . . . . . . . . . 8 4.1. Packet Flow Sequence . . . . . . . . . . . . . . . . . . 10 5. LISP Encapsulation Details . . . . . . . . . . . . . . . . . 12 - 5.1. LISP IPv4-in-IPv4 Header Format . . . . . . . . . . . . . 12 + 5.1. LISP IPv4-in-IPv4 Header Format . . . . . . . . . . . . . 13 5.2. LISP IPv6-in-IPv6 Header Format . . . . . . . . . . . . . 13 - 5.3. Tunnel Header Field Descriptions . . . . . . . . . . . . 14 + 5.3. Tunnel Header Field Descriptions . . . . . . . . . . . . 15 6. LISP EID-to-RLOC Map-Cache . . . . . . . . . . . . . . . . . 19 7. Dealing with Large Encapsulated Packets . . . . . . . . . . . 19 7.1. A Stateless Solution to MTU Handling . . . . . . . . . . 20 7.2. A Stateful Solution to MTU Handling . . . . . . . . . . . 21 8. Using Virtualization and Segmentation with LISP . . . . . . . 21 9. Routing Locator Selection . . . . . . . . . . . . . . . . . . 22 10. Routing Locator Reachability . . . . . . . . . . . . . . . . 24 10.1. Echo Nonce Algorithm . . . . . . . . . . . . . . . . . . 25 11. EID Reachability within a LISP Site . . . . . . . . . . . . . 26 12. Routing Locator Hashing . . . . . . . . . . . . . . . . . . . 27 @@ -82,36 +84,37 @@ 13.1. Database Map-Versioning . . . . . . . . . . . . . . . . 29 14. Multicast Considerations . . . . . . . . . . . . . . . . . . 29 15. Router Performance Considerations . . . . . . . . . . . . . . 30 16. Security Considerations . . . . . . . . . . . . . . . . . . . 31 17. Network Management Considerations . . . . . . . . . . . . . . 32 18. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 18.1. LISP UDP Port Numbers . . . . . . . . . . . . . . . . . 32 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 19.1. Normative References . . . . . . . . . . . . . . . . . . 32 19.2. Informative References . . . . . . . . . . . . . . . . . 33 - Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 38 - Appendix B. Document Change Log . . . . . . . . . . . . . . . . 38 - B.1. Changes to draft-ietf-lisp-rfc6830bis-12 . . . . . . . . 39 - B.2. Changes to draft-ietf-lisp-rfc6830bis-11 . . . . . . . . 39 - B.3. Changes to draft-ietf-lisp-rfc6830bis-10 . . . . . . . . 39 - B.4. Changes to draft-ietf-lisp-rfc6830bis-09 . . . . . . . . 39 - B.5. Changes to draft-ietf-lisp-rfc6830bis-08 . . . . . . . . 40 - B.6. Changes to draft-ietf-lisp-rfc6830bis-07 . . . . . . . . 40 - B.7. Changes to draft-ietf-lisp-rfc6830bis-06 . . . . . . . . 40 - B.8. Changes to draft-ietf-lisp-rfc6830bis-05 . . . . . . . . 41 - B.9. Changes to draft-ietf-lisp-rfc6830bis-04 . . . . . . . . 41 - B.10. Changes to draft-ietf-lisp-rfc6830bis-03 . . . . . . . . 41 - B.11. Changes to draft-ietf-lisp-rfc6830bis-02 . . . . . . . . 41 - B.12. Changes to draft-ietf-lisp-rfc6830bis-01 . . . . . . . . 41 - B.13. Changes to draft-ietf-lisp-rfc6830bis-00 . . . . . . . . 41 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42 + Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 37 + Appendix B. Document Change Log . . . . . . . . . . . . . . . . 37 + B.1. Changes to draft-ietf-lisp-rfc6830bis-13 . . . . . . . . 38 + B.2. Changes to draft-ietf-lisp-rfc6830bis-12 . . . . . . . . 38 + B.3. Changes to draft-ietf-lisp-rfc6830bis-11 . . . . . . . . 38 + B.4. Changes to draft-ietf-lisp-rfc6830bis-10 . . . . . . . . 38 + B.5. Changes to draft-ietf-lisp-rfc6830bis-09 . . . . . . . . 38 + B.6. Changes to draft-ietf-lisp-rfc6830bis-08 . . . . . . . . 39 + B.7. Changes to draft-ietf-lisp-rfc6830bis-07 . . . . . . . . 39 + B.8. Changes to draft-ietf-lisp-rfc6830bis-06 . . . . . . . . 39 + B.9. Changes to draft-ietf-lisp-rfc6830bis-05 . . . . . . . . 40 + B.10. Changes to draft-ietf-lisp-rfc6830bis-04 . . . . . . . . 40 + B.11. Changes to draft-ietf-lisp-rfc6830bis-03 . . . . . . . . 40 + B.12. Changes to draft-ietf-lisp-rfc6830bis-02 . . . . . . . . 40 + B.13. Changes to draft-ietf-lisp-rfc6830bis-01 . . . . . . . . 40 + B.14. Changes to draft-ietf-lisp-rfc6830bis-00 . . . . . . . . 41 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 41 1. Introduction This document describes the Locator/Identifier Separation Protocol (LISP). LISP is an encapsulation protocol built around the fundamental idea of separating the topological location of a network attachment point from the node's identity [CHIAPPA]. As a result LISP creates two namespaces: Endpoint Identifiers (EIDs), that are used to identify end-hosts (e.g., nodes or Virtual Machines) and routable Routing Locators (RLOCs), used to identify network @@ -1355,22 +1361,22 @@ values that are greater are considered to be more recent. A value of 0 for the Source Map-Version Number or the Destination Map-Version Number conveys no versioning information, and an ITR does no comparison with previously received Map-Version Numbers. A Map-Version Number can be included in Map-Register messages as well. This is a good way for the Map-Server to assure that all ETRs for a site registering to it will be synchronized according to Map- Version Number. - See [RFC6834] for a more detailed analysis and description of - Database Map-Versioning. + See [I-D.ietf-lisp-6834bis] for a more detailed analysis and + description of Database Map-Versioning. 14. Multicast Considerations A multicast group address, as defined in the original Internet architecture, is an identifier of a grouping of topologically independent receiver host locations. The address encoding itself does not determine the location of the receiver(s). The multicast routing protocol, and the network-based state the protocol creates, determine where the receivers are located. @@ -1387,24 +1393,24 @@ With respect to the source Routing Locator address, the ITR prepends its own IP address as the source address of the outer IP header. Just like it would if the destination EID was a unicast address. This source Routing Locator address, like any other Routing Locator address, MUST be globally routable. There are two approaches for LISP-Multicast, one that uses native multicast routing in the underlay with no support from the Mapping System and the other that uses only unicast routing in the underlay - with support from the Mapping System. See [RFC6831] and - [I-D.ietf-lisp-signal-free-multicast], respectively, for details. - Details for LISP-Multicast and interworking with non-LISP sites are - described in [RFC6831] and [RFC6832]. + with support from the Mapping System. See [RFC6831] and [RFC8378], + respectively, for details. Details for LISP-Multicast and + interworking with non-LISP sites are described in [RFC6831] and + [RFC6832]. 15. Router Performance Considerations LISP is designed to be very "hardware-based forwarding friendly". A few implementation techniques can be used to incrementally implement LISP: o When a tunnel-encapsulated packet is received by an ETR, the outer destination address may not be the address of the router. This makes it challenging for the control plane to get packets from the @@ -1487,24 +1493,29 @@ The IANA registry has allocated UDP port number 4341 for the LISP Data-Plane. IANA has updated the description for UDP port 4341 as follows: lisp-data 4341 udp LISP Data Packets 19. References 19.1. Normative References + [I-D.ietf-lisp-6834bis] + Iannone, L., Saucez, D., and O. Bonaventure, "Locator/ID + Separation Protocol (LISP) Map-Versioning", draft-ietf- + lisp-6834bis-00 (work in progress), July 2018. + [I-D.ietf-lisp-rfc6833bis] Fuller, V., Farinacci, D., and A. Cabellos-Aparicio, "Locator/ID Separation Protocol (LISP) Control-Plane", - draft-ietf-lisp-rfc6833bis-09 (work in progress), March + draft-ietf-lisp-rfc6833bis-10 (work in progress), March 2018. [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, DOI 10.17487/RFC0768, August 1980, . [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, DOI 10.17487/RFC0791, September 1981, . @@ -1526,60 +1537,30 @@ 19.2. Informative References [AFN] IANA, "Address Family Numbers", August 2016, . [CHIAPPA] Chiappa, J., "Endpoints and Endpoint names: A Proposed", 1999, . - [I-D.ietf-lisp-eid-mobility] - Portoles-Comeras, M., Ashtaputre, V., Moreno, V., Maino, - F., and D. Farinacci, "LISP L2/L3 EID Mobility Using a - Unified Control Plane", draft-ietf-lisp-eid-mobility-01 - (work in progress), November 2017. - [I-D.ietf-lisp-introduction] Cabellos-Aparicio, A. and D. Saucez, "An Architectural Introduction to the Locator/ID Separation Protocol (LISP)", draft-ietf-lisp-introduction-13 (work in progress), April 2015. - [I-D.ietf-lisp-mn] - Farinacci, D., Lewis, D., Meyer, D., and C. White, "LISP - Mobile Node", draft-ietf-lisp-mn-01 (work in progress), - October 2017. - - [I-D.ietf-lisp-predictive-rlocs] - Farinacci, D. and P. Pillay-Esnault, "LISP Predictive - RLOCs", draft-ietf-lisp-predictive-rlocs-01 (work in - progress), November 2017. - - [I-D.ietf-lisp-sec] - Maino, F., Ermagan, V., Cabellos-Aparicio, A., and D. - Saucez, "LISP-Security (LISP-SEC)", draft-ietf-lisp-sec-14 - (work in progress), October 2017. - - [I-D.ietf-lisp-signal-free-multicast] - Moreno, V. and D. Farinacci, "Signal-Free LISP Multicast", - draft-ietf-lisp-signal-free-multicast-09 (work in - progress), March 2018. - [I-D.ietf-lisp-vpn] Moreno, V. and D. Farinacci, "LISP Virtual Private - Networks (VPNs)", draft-ietf-lisp-vpn-01 (work in - progress), November 2017. - - [LISA96] Lear, E., Tharp, D., Katinsky, J., and J. Coffin, - "Renumbering: Threat or Menace?", Usenix Tenth System - Administration Conference (LISA 96), October 1996. + Networks (VPNs)", draft-ietf-lisp-vpn-02 (work in + progress), May 2018. [OPENLISP] Iannone, L., Saucez, D., and O. Bonaventure, "OpenLISP Implementation Report", Work in Progress, July 2008. [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, . [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., @@ -1609,64 +1590,36 @@ A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, DOI 10.17487/RFC3261, June 2002, . [RFC4086] Eastlake 3rd, D., Schiller, J., and S. Crocker, "Randomness Requirements for Security", BCP 106, RFC 4086, DOI 10.17487/RFC4086, June 2005, . - [RFC4192] Baker, F., Lear, E., and R. Droms, "Procedures for - Renumbering an IPv6 Network without a Flag Day", RFC 4192, - DOI 10.17487/RFC4192, September 2005, - . - - [RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing - (CIDR): The Internet Address Assignment and Aggregation - Plan", BCP 122, RFC 4632, DOI 10.17487/RFC4632, August - 2006, . - - [RFC4866] Arkko, J., Vogt, C., and W. Haddad, "Enhanced Route - Optimization for Mobile IPv6", RFC 4866, - DOI 10.17487/RFC4866, May 2007, - . - [RFC4984] Meyer, D., Ed., Zhang, L., Ed., and K. Fall, Ed., "Report from the IAB Workshop on Routing and Addressing", RFC 4984, DOI 10.17487/RFC4984, September 2007, . - [RFC5944] Perkins, C., Ed., "IP Mobility Support for IPv4, Revised", - RFC 5944, DOI 10.17487/RFC5944, November 2010, - . - - [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility - Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July - 2011, . - [RFC6831] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, "The Locator/ID Separation Protocol (LISP) for Multicast Environments", RFC 6831, DOI 10.17487/RFC6831, January 2013, . [RFC6832] Lewis, D., Meyer, D., Farinacci, D., and V. Fuller, "Interworking between Locator/ID Separation Protocol (LISP) and Non-LISP Sites", RFC 6832, DOI 10.17487/RFC6832, January 2013, . - [RFC6834] Iannone, L., Saucez, D., and O. Bonaventure, "Locator/ID - Separation Protocol (LISP) Map-Versioning", RFC 6834, - DOI 10.17487/RFC6834, January 2013, - . - [RFC6835] Farinacci, D. and D. Meyer, "The Locator/ID Separation Protocol Internet Groper (LIG)", RFC 6835, DOI 10.17487/RFC6835, January 2013, . [RFC6935] Eubanks, M., Chimento, P., and M. Westerlund, "IPv6 and UDP Checksums for Tunneled Packets", RFC 6935, DOI 10.17487/RFC6935, April 2013, . @@ -1710,20 +1663,25 @@ [RFC8111] Fuller, V., Lewis, D., Ermagan, V., Jain, A., and A. Smirnov, "Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)", RFC 8111, DOI 10.17487/RFC8111, May 2017, . [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 8126, DOI 10.17487/RFC8126, June 2017, . + [RFC8378] Moreno, V. and D. Farinacci, "Signal-Free Locator/ID + Separation Protocol (LISP) Multicast", RFC 8378, + DOI 10.17487/RFC8378, May 2018, + . + Appendix A. Acknowledgments An initial thank you goes to Dave Oran for planting the seeds for the initial ideas for LISP. His consultation continues to provide value to the LISP authors. A special and appreciative thank you goes to Noel Chiappa for providing architectural impetus over the past decades on separation of location and identity, as well as detailed reviews of the LISP architecture and documents, coupled with enthusiasm for making LISP a @@ -1755,91 +1713,97 @@ 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 documents were being prepared for IESG last call, and for his meticulous reviews and detailed commentaries on the 7 working group last call documents progressing toward standards-track RFCs. Appendix B. Document Change Log [RFC Editor: Please delete this section on publication as RFC.] -B.1. Changes to draft-ietf-lisp-rfc6830bis-12 +B.1. Changes to draft-ietf-lisp-rfc6830bis-13 o Posted March IETF Week 2018. o Clarified that a new nonce is required per RLOC. o Removed 'Clock Sweep' section. This text must be placed in a new OAM document. o Some references changed from normative to informative -B.2. Changes to draft-ietf-lisp-rfc6830bis-11 +B.2. Changes to draft-ietf-lisp-rfc6830bis-12 + + o Posted July 2018. + + o Fixed Luigi editorial comments to ready draft for RFC status. + +B.3. Changes to draft-ietf-lisp-rfc6830bis-11 o Posted March 2018. o Removed sections 16, 17 and 18 (Mobility, Deployment and Traceroute considerations). This text must be placed in a new OAM document. -B.3. Changes to draft-ietf-lisp-rfc6830bis-10 +B.4. Changes to draft-ietf-lisp-rfc6830bis-10 o Posted March 2018. o Updated section 'Router Locator Selection' stating that the Data- Plane MUST follow what's stored in the Map-Cache (priorities and weights). o Section 'Routing Locator Reachability': Removed bullet point 2 (ICMP Network/Host Unreachable),3 (hints from BGP),4 (ICMP Port Unreachable),5 (receive a Map-Reply as a response) and RLOC probing o Removed 'Solicit-Map Request'. -B.4. Changes to draft-ietf-lisp-rfc6830bis-09 +B.5. Changes to draft-ietf-lisp-rfc6830bis-09 o Posted January 2018. o Add more details in section 5.3 about DSCP processing during encapsulation and decapsulation. o Added clarity to definitions in the Definition of Terms section from various commenters. o Removed PA and PI definitions from Definition of Terms section. o More editorial changes. o Removed 4342 from IANA section and move to RFC6833 IANA section. -B.5. Changes to draft-ietf-lisp-rfc6830bis-08 +B.6. Changes to draft-ietf-lisp-rfc6830bis-08 o Posted January 2018. o Remove references to research work for any protocol mechanisms. o Document scanned to make sure it is RFC 2119 compliant. o Made changes to reflect comments from document WG shepherd Luigi Iannone. o Ran IDNITs on the document. -B.6. Changes to draft-ietf-lisp-rfc6830bis-07 +B.7. Changes to draft-ietf-lisp-rfc6830bis-07 o Posted November 2017. o Rephrase how Instance-IDs are used and don't refer to [RFC1918] addresses. -B.7. Changes to draft-ietf-lisp-rfc6830bis-06 +B.8. Changes to draft-ietf-lisp-rfc6830bis-06 o Posted October 2017. o Put RTR definition before it is used. 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 hosts. Note that EID blocks MAY LISP RLOCs". @@ -1848,61 +1812,61 @@ o ETRs may, rather than will, be the ones to send Map-Replies. o Recommend, rather than mandate, max encapsulation headers to 2. o Reference VPN draft when introducing Instance-ID. o Indicate that SMRs can be sent when ITR/ETR are in the same node. o Clarify when private addreses can be used. -B.8. Changes to draft-ietf-lisp-rfc6830bis-05 +B.9. Changes to draft-ietf-lisp-rfc6830bis-05 o Posted August 2017. o Make it clear that a Reencapsulating Tunnel Router is an RTR. -B.9. Changes to draft-ietf-lisp-rfc6830bis-04 +B.10. Changes to draft-ietf-lisp-rfc6830bis-04 o Posted July 2017. o Changed reference of IPv6 RFC2460 to RFC8200. o Indicate that the applicability statement for UDP zero checksums over IPv6 adheres to RFC6936. -B.10. Changes to draft-ietf-lisp-rfc6830bis-03 +B.11. Changes to draft-ietf-lisp-rfc6830bis-03 o Posted May 2017. o Move the control-plane related codepoints in the IANA Considerations section to RFC6833bis. -B.11. Changes to draft-ietf-lisp-rfc6830bis-02 +B.12. Changes to draft-ietf-lisp-rfc6830bis-02 o Posted April 2017. o Reflect some editorial comments from Damien Sausez. -B.12. Changes to draft-ietf-lisp-rfc6830bis-01 +B.13. Changes to draft-ietf-lisp-rfc6830bis-01 o Posted March 2017. o Include references to new RFCs published. o Change references from RFC6833 to RFC6833bis. o Clarified LCAF text in the IANA section. o Remove references to "experimental". -B.13. Changes to draft-ietf-lisp-rfc6830bis-00 +B.14. Changes to draft-ietf-lisp-rfc6830bis-00 o Posted December 2016. o Created working group document from draft-farinacci-lisp -rfc6830-00 individual submission. No other changes made. Authors' Addresses Dino Farinacci Cisco Systems