draft-ietf-lisp-rfc6830bis-13.txt   draft-ietf-lisp-rfc6830bis-14.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: January 16, 2019 Cisco Systems Expires: January 18, 2019 Cisco Systems
A. Cabellos (Ed.) A. Cabellos (Ed.)
UPC/BarcelonaTech UPC/BarcelonaTech
July 15, 2018 July 17, 2018
The Locator/ID Separation Protocol (LISP) The Locator/ID Separation Protocol (LISP)
draft-ietf-lisp-rfc6830bis-13 draft-ietf-lisp-rfc6830bis-14
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 January 16, 2019. This Internet-Draft will expire on January 18, 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 5 skipping to change at page 3, line 5
15. Router Performance Considerations . . . . . . . . . . . . . . 30 15. Router Performance Considerations . . . . . . . . . . . . . . 30
16. Security Considerations . . . . . . . . . . . . . . . . . . . 31 16. Security Considerations . . . . . . . . . . . . . . . . . . . 31
17. Network Management Considerations . . . . . . . . . . . . . . 32 17. Network Management Considerations . . . . . . . . . . . . . . 32
18. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 18. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32
18.1. LISP UDP Port Numbers . . . . . . . . . . . . . . . . . 32 18.1. LISP UDP Port Numbers . . . . . . . . . . . . . . . . . 32
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 32
19.1. Normative References . . . . . . . . . . . . . . . . . . 32 19.1. Normative References . . . . . . . . . . . . . . . . . . 32
19.2. Informative References . . . . . . . . . . . . . . . . . 33 19.2. Informative References . . . . . . . . . . . . . . . . . 33
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 37 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 37
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 37 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 37
B.1. Changes to draft-ietf-lisp-rfc6830bis-13 . . . . . . . . 38 B.1. Changes to draft-ietf-lisp-rfc6830bis-14 . . . . . . . . 38
B.2. Changes to draft-ietf-lisp-rfc6830bis-12 . . . . . . . . 38 B.2. Changes to draft-ietf-lisp-rfc6830bis-13 . . . . . . . . 38
B.3. Changes to draft-ietf-lisp-rfc6830bis-11 . . . . . . . . 38 B.3. Changes to draft-ietf-lisp-rfc6830bis-12 . . . . . . . . 38
B.4. Changes to draft-ietf-lisp-rfc6830bis-10 . . . . . . . . 38 B.4. Changes to draft-ietf-lisp-rfc6830bis-11 . . . . . . . . 38
B.5. Changes to draft-ietf-lisp-rfc6830bis-09 . . . . . . . . 38 B.5. Changes to draft-ietf-lisp-rfc6830bis-10 . . . . . . . . 38
B.6. Changes to draft-ietf-lisp-rfc6830bis-08 . . . . . . . . 39 B.6. Changes to draft-ietf-lisp-rfc6830bis-09 . . . . . . . . 39
B.7. Changes to draft-ietf-lisp-rfc6830bis-07 . . . . . . . . 39 B.7. Changes to draft-ietf-lisp-rfc6830bis-08 . . . . . . . . 39
B.8. Changes to draft-ietf-lisp-rfc6830bis-06 . . . . . . . . 39 B.8. Changes to draft-ietf-lisp-rfc6830bis-07 . . . . . . . . 39
B.9. Changes to draft-ietf-lisp-rfc6830bis-05 . . . . . . . . 40 B.9. Changes to draft-ietf-lisp-rfc6830bis-06 . . . . . . . . 39
B.10. Changes to draft-ietf-lisp-rfc6830bis-04 . . . . . . . . 40 B.10. Changes to draft-ietf-lisp-rfc6830bis-05 . . . . . . . . 40
B.11. Changes to draft-ietf-lisp-rfc6830bis-03 . . . . . . . . 40 B.11. Changes to draft-ietf-lisp-rfc6830bis-04 . . . . . . . . 40
B.12. Changes to draft-ietf-lisp-rfc6830bis-02 . . . . . . . . 40 B.12. Changes to draft-ietf-lisp-rfc6830bis-03 . . . . . . . . 40
B.13. Changes to draft-ietf-lisp-rfc6830bis-01 . . . . . . . . 40 B.13. Changes to draft-ietf-lisp-rfc6830bis-02 . . . . . . . . 40
B.14. Changes to draft-ietf-lisp-rfc6830bis-00 . . . . . . . . 41 B.14. Changes to draft-ietf-lisp-rfc6830bis-01 . . . . . . . . 40
B.15. Changes to draft-ietf-lisp-rfc6830bis-00 . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 41 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 41
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 4, line 16 skipping to change at page 4, line 16
IAB-sponsored Routing and Addressing Workshop held in Amsterdam in IAB-sponsored Routing and Addressing Workshop held in Amsterdam in
October 2006 (see [RFC4984]). October 2006 (see [RFC4984]).
This document specifies the LISP Data-Plane encapsulation and other This document specifies the LISP Data-Plane encapsulation and other
LISP forwarding node functionality while [I-D.ietf-lisp-rfc6833bis] LISP forwarding node functionality while [I-D.ietf-lisp-rfc6833bis]
specifies the LISP control plane. LISP deployment guidelines can be specifies the LISP control plane. LISP deployment guidelines can be
found in [RFC7215] and [RFC6835] describes considerations for network found in [RFC7215] and [RFC6835] describes considerations for network
operational management. Finally, [I-D.ietf-lisp-introduction] operational management. Finally, [I-D.ietf-lisp-introduction]
describes the LISP architecture. describes the LISP architecture.
This document obsoletes RFC 6830.
2. Requirements Notation 2. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Definition of Terms 3. Definition of Terms
Address Family Identifier (AFI): AFI is a term used to describe an Address Family Identifier (AFI): AFI is a term used to describe an
address encoding in a packet. An address family that pertains to address encoding in a packet. An address family that pertains to
skipping to change at page 38, line 5 skipping to change at page 38, 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-13 B.1. Changes to draft-ietf-lisp-rfc6830bis-14
o Posted July 2018 IETF week.
o Put obsolete of RFC 6830 in Intro section in addition to abstract.
B.2. Changes to draft-ietf-lisp-rfc6830bis-13
o Posted July 2018.
o Fixed Luigi editorial comments to ready draft for RFC status.
B.3. Changes to draft-ietf-lisp-rfc6830bis-12
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.2. Changes to draft-ietf-lisp-rfc6830bis-12 B.4. Changes to draft-ietf-lisp-rfc6830bis-11
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 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.4. Changes to draft-ietf-lisp-rfc6830bis-10 B.5. 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.5. Changes to draft-ietf-lisp-rfc6830bis-09 B.6. 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.6. Changes to draft-ietf-lisp-rfc6830bis-08 B.7. 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.7. Changes to draft-ietf-lisp-rfc6830bis-07 B.8. 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.8. Changes to draft-ietf-lisp-rfc6830bis-06 B.9. 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 40, line 9 skipping to change at page 40, 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 addreses can be used. o Clarify when private addreses can be used.
B.9. Changes to draft-ietf-lisp-rfc6830bis-05 B.10. Changes to draft-ietf-lisp-rfc6830bis-05
o Posted August 2017. o Posted August 2017.
o Make it clear that a Reencapsulating Tunnel Router is an RTR. o Make it clear that a Reencapsulating Tunnel Router is an RTR.
B.10. Changes to draft-ietf-lisp-rfc6830bis-04 B.11. 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.11. Changes to draft-ietf-lisp-rfc6830bis-03 B.12. 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.12. Changes to draft-ietf-lisp-rfc6830bis-02 B.13. 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.13. Changes to draft-ietf-lisp-rfc6830bis-01 B.14. 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.14. Changes to draft-ietf-lisp-rfc6830bis-00 B.15. 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. 19 change blocks. 
37 lines changed or deleted 46 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/