draft-ietf-lisp-rfc6830bis-25.txt   draft-ietf-lisp-rfc6830bis-26.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: April 24, 2019 Cisco Systems Expires: May 8, 2019 Cisco Systems
A. Cabellos (Ed.) A. Cabellos (Ed.)
UPC/BarcelonaTech UPC/BarcelonaTech
October 21, 2018 November 4, 2018
The Locator/ID Separation Protocol (LISP) The Locator/ID Separation Protocol (LISP)
draft-ietf-lisp-rfc6830bis-25 draft-ietf-lisp-rfc6830bis-26
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 April 24, 2019. This Internet-Draft will expire on May 8, 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
16. Security Considerations . . . . . . . . . . . . . . . . . . . 32 16. Security Considerations . . . . . . . . . . . . . . . . . . . 32
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 . . . . . . . . . . . . . . . . . . . . . 34 19. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
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 . . . . . . . . . . . . . . . . 40 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 40
B.1. Changes to draft-ietf-lisp-rfc6830bis-24 . . . . . . . . 40 B.1. Changes to draft-ietf-lisp-rfc6830bis-26 . . . . . . . . 40
B.2. Changes to draft-ietf-lisp-rfc6830bis-24 . . . . . . . . 40 B.2. Changes to draft-ietf-lisp-rfc6830bis-25 . . . . . . . . 40
B.3. Changes to draft-ietf-lisp-rfc6830bis-23 . . . . . . . . 40 B.3. Changes to draft-ietf-lisp-rfc6830bis-24 . . . . . . . . 40
B.4. Changes to draft-ietf-lisp-rfc6830bis-22 . . . . . . . . 40 B.4. Changes to draft-ietf-lisp-rfc6830bis-23 . . . . . . . . 40
B.5. Changes to draft-ietf-lisp-rfc6830bis-21 . . . . . . . . 40 B.5. Changes to draft-ietf-lisp-rfc6830bis-22 . . . . . . . . 40
B.6. Changes to draft-ietf-lisp-rfc6830bis-20 . . . . . . . . 40 B.6. Changes to draft-ietf-lisp-rfc6830bis-21 . . . . . . . . 40
B.7. Changes to draft-ietf-lisp-rfc6830bis-19 . . . . . . . . 41 B.7. Changes to draft-ietf-lisp-rfc6830bis-20 . . . . . . . . 41
B.8. Changes to draft-ietf-lisp-rfc6830bis-18 . . . . . . . . 41 B.8. Changes to draft-ietf-lisp-rfc6830bis-19 . . . . . . . . 41
B.9. Changes to draft-ietf-lisp-rfc6830bis-17 . . . . . . . . 41 B.9. Changes to draft-ietf-lisp-rfc6830bis-18 . . . . . . . . 41
B.10. Changes to draft-ietf-lisp-rfc6830bis-16 . . . . . . . . 41 B.10. Changes to draft-ietf-lisp-rfc6830bis-17 . . . . . . . . 41
B.11. Changes to draft-ietf-lisp-rfc6830bis-15 . . . . . . . . 41 B.11. Changes to draft-ietf-lisp-rfc6830bis-16 . . . . . . . . 41
B.12. Changes to draft-ietf-lisp-rfc6830bis-14 . . . . . . . . 41 B.12. Changes to draft-ietf-lisp-rfc6830bis-15 . . . . . . . . 41
B.13. Changes to draft-ietf-lisp-rfc6830bis-13 . . . . . . . . 42 B.13. Changes to draft-ietf-lisp-rfc6830bis-14 . . . . . . . . 42
B.14. Changes to draft-ietf-lisp-rfc6830bis-12 . . . . . . . . 42 B.14. Changes to draft-ietf-lisp-rfc6830bis-13 . . . . . . . . 42
B.15. Changes to draft-ietf-lisp-rfc6830bis-11 . . . . . . . . 42 B.15. Changes to draft-ietf-lisp-rfc6830bis-12 . . . . . . . . 42
B.16. Changes to draft-ietf-lisp-rfc6830bis-10 . . . . . . . . 42 B.16. Changes to draft-ietf-lisp-rfc6830bis-11 . . . . . . . . 42
B.17. Changes to draft-ietf-lisp-rfc6830bis-09 . . . . . . . . 42 B.17. Changes to draft-ietf-lisp-rfc6830bis-10 . . . . . . . . 42
B.18. Changes to draft-ietf-lisp-rfc6830bis-08 . . . . . . . . 43 B.18. Changes to draft-ietf-lisp-rfc6830bis-09 . . . . . . . . 43
B.19. Changes to draft-ietf-lisp-rfc6830bis-07 . . . . . . . . 43 B.19. Changes to draft-ietf-lisp-rfc6830bis-08 . . . . . . . . 43
B.20. Changes to draft-ietf-lisp-rfc6830bis-06 . . . . . . . . 43 B.20. Changes to draft-ietf-lisp-rfc6830bis-07 . . . . . . . . 43
B.21. Changes to draft-ietf-lisp-rfc6830bis-05 . . . . . . . . 44 B.21. Changes to draft-ietf-lisp-rfc6830bis-06 . . . . . . . . 43
B.22. Changes to draft-ietf-lisp-rfc6830bis-04 . . . . . . . . 44 B.22. Changes to draft-ietf-lisp-rfc6830bis-05 . . . . . . . . 44
B.23. Changes to draft-ietf-lisp-rfc6830bis-03 . . . . . . . . 44 B.23. Changes to draft-ietf-lisp-rfc6830bis-04 . . . . . . . . 44
B.24. Changes to draft-ietf-lisp-rfc6830bis-02 . . . . . . . . 44 B.24. Changes to draft-ietf-lisp-rfc6830bis-03 . . . . . . . . 44
B.25. Changes to draft-ietf-lisp-rfc6830bis-01 . . . . . . . . 44 B.25. Changes to draft-ietf-lisp-rfc6830bis-02 . . . . . . . . 44
B.26. Changes to draft-ietf-lisp-rfc6830bis-00 . . . . . . . . 45 B.26. Changes to draft-ietf-lisp-rfc6830bis-01 . . . . . . . . 44
B.27. Changes to draft-ietf-lisp-rfc6830bis-00 . . . . . . . . 45
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45
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 17, line 45 skipping to change at page 17, line 45
are transmitted as zero and ignored on receipt. The format of the are transmitted as zero and ignored on receipt. The format of the
LISP header would look like this: LISP header would look like this:
x x x x 1 x x x x x x x 1 x x x
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|N|L|E|V|I|R|K|K| Nonce/Map-Version | |N|L|E|V|I|R|K|K| Nonce/Map-Version |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Instance ID | LSBs | | Instance ID | LSBs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
R: The R-bit is a Reserved bit for future use. It MUST be set to 0 R: The R-bit is a Reserved and unassigned bit for future use. It
on transmit and MUST be ignored on receipt. MUST be set to 0 on transmit and MUST be ignored on receipt.
KK: The KK-bits are a 2-bit field used when encapsulated packets are KK: The KK-bits are a 2-bit field used when encapsulated packets are
encrypted. The field is set to 00 when the packet is not encrypted. The field is set to 00 when the packet is not
encrypted. See [RFC8061] for further information. encrypted. See [RFC8061] for further information.
LISP Nonce: The LISP 'Nonce' field is a 24-bit value that is LISP Nonce: The LISP 'Nonce' field is a 24-bit value that is
randomly generated by an ITR when the N-bit is set to 1. Nonce randomly generated by an ITR when the N-bit is set to 1. Nonce
generation algorithms are an implementation matter but are generation algorithms are an implementation matter but are
required to generate different nonces when sending to different required to generate different nonces when sending to different
RLOCs. However, the same nonce can be used for a period of time RLOCs. However, the same nonce can be used for a period of time
skipping to change at page 34, line 5 skipping to change at page 34, line 5
o It is no longer mandated that a maximum number of 2 LISP headers o It is no longer mandated that a maximum number of 2 LISP headers
be prepended to a packet. If there is a application need for more be prepended to a packet. If there is a application need for more
than 2 LISP headers, an implementation can support more. However, than 2 LISP headers, an implementation can support more. However,
it is RECOMMENDED that a maximum of two LISP headers can be it is RECOMMENDED that a maximum of two LISP headers can be
prepended to a packet. prepended to a packet.
o The 3 reserved flag bits in the LISP header have been allocated o The 3 reserved flag bits in the LISP header have been allocated
for [RFC8061]. The low-order 2 bits of the 3-bit field (now named for [RFC8061]. The low-order 2 bits of the 3-bit field (now named
the KK bits) are used as a key identifier. The 1 remaining bit is the KK bits) are used as a key identifier. The 1 remaining bit is
still documented as reserved. still documented as reserved and unassigned.
o Data-Plane gleaning for creating map-cache entries has been made o Data-Plane gleaning for creating map-cache entries has been made
optional. Any ITR implementations that depend on or assume the optional. Any ITR implementations that depend on or assume the
remote ETR is gleaning should not do so. This does not create any remote ETR is gleaning should not do so. This does not create any
interoperability problems since the control-plane map-cache interoperability problems since the control-plane map-cache
population procedures are unilateral and are the typical method population procedures are unilateral and are the typical method
for map-cache population. for map-cache population.
o The bulk of the changes to this document which reduces its length o The bulk of the changes to this document which reduces its length
are due to moving the LISP control-plane messaging and procedures are due to moving the LISP control-plane messaging and procedures
skipping to change at page 34, line 44 skipping to change at page 34, line 44
20.1. Normative References 20.1. Normative References
[I-D.ietf-lisp-6834bis] [I-D.ietf-lisp-6834bis]
Iannone, L., Saucez, D., and O. Bonaventure, "Locator/ID Iannone, L., Saucez, D., and O. Bonaventure, "Locator/ID
Separation Protocol (LISP) Map-Versioning", draft-ietf- Separation Protocol (LISP) Map-Versioning", draft-ietf-
lisp-6834bis-02 (work in progress), September 2018. lisp-6834bis-02 (work in progress), September 2018.
[I-D.ietf-lisp-rfc6833bis] [I-D.ietf-lisp-rfc6833bis]
Fuller, V., Farinacci, D., and A. Cabellos-Aparicio, Fuller, V., Farinacci, D., and A. Cabellos-Aparicio,
"Locator/ID Separation Protocol (LISP) Control-Plane", "Locator/ID Separation Protocol (LISP) Control-Plane",
draft-ietf-lisp-rfc6833bis-18 (work in progress), October draft-ietf-lisp-rfc6833bis-19 (work in progress), October
2018. 2018.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
DOI 10.17487/RFC0768, August 1980, DOI 10.17487/RFC0768, August 1980,
<https://www.rfc-editor.org/info/rfc768>. <https://www.rfc-editor.org/info/rfc768>.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
DOI 10.17487/RFC0791, September 1981, DOI 10.17487/RFC0791, September 1981,
<https://www.rfc-editor.org/info/rfc791>. <https://www.rfc-editor.org/info/rfc791>.
skipping to change at page 40, line 12 skipping to change at page 40, line 12
Kaduk, Eric Rescorla, Alvaro Retana, Alexey Melnikov, Alissa Cooper, Kaduk, Eric Rescorla, Alvaro Retana, Alexey Melnikov, Alissa Cooper,
Suresh Krishnan, Alberto Rodriguez-Natal, Vina Ermagen, Mohamed Suresh Krishnan, Alberto Rodriguez-Natal, Vina Ermagen, Mohamed
Boucadair, Brian Trammell, Sabrina Tanamal, and John Drake. The Boucadair, Brian Trammell, Sabrina Tanamal, and John Drake. The
contributions they offered greatly added to the security, scale, and contributions they offered greatly added to the security, scale, and
robustness of the LISP architecture and protocols. robustness of the LISP architecture and protocols.
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-24 B.1. Changes to draft-ietf-lisp-rfc6830bis-26
o Posted late October 2018.
o Changed description about "reserved" bits to state "reserved and
unassigned".
B.2. Changes to draft-ietf-lisp-rfc6830bis-25
o Posted mid October 2018. o Posted mid October 2018.
o Added more to the Security Considerations section with discussion o Added more to the Security Considerations section with discussion
about echo-nonce attacks. about echo-nonce attacks.
B.2. Changes to draft-ietf-lisp-rfc6830bis-24 B.3. Changes to draft-ietf-lisp-rfc6830bis-24
o Posted mid October 2018. o Posted mid October 2018.
o Final editorial changes for Eric and Ben. o Final editorial changes for Eric and Ben.
B.3. Changes to draft-ietf-lisp-rfc6830bis-23 B.4. Changes to draft-ietf-lisp-rfc6830bis-23
o Posted early October 2018. o Posted early October 2018.
o Added an applicability statement in section 1 to address security o Added an applicability statement in section 1 to address security
concerns from Telechat. concerns from Telechat.
B.4. Changes to draft-ietf-lisp-rfc6830bis-22 B.5. Changes to draft-ietf-lisp-rfc6830bis-22
o Posted early October 2018. o Posted early October 2018.
o Changes to reflect comments post Telechat. o Changes to reflect comments post Telechat.
B.5. Changes to draft-ietf-lisp-rfc6830bis-21 B.6. Changes to draft-ietf-lisp-rfc6830bis-21
o Posted late-September 2018. o Posted late-September 2018.
o Changes to reflect comments from Sep 27th Telechat. o Changes to reflect comments from Sep 27th Telechat.
B.6. Changes to draft-ietf-lisp-rfc6830bis-20 B.7. Changes to draft-ietf-lisp-rfc6830bis-20
o Posted late-September 2018. o Posted late-September 2018.
o Fix old reference to RFC3168, changed to RFC6040. o Fix old reference to RFC3168, changed to RFC6040.
B.7. Changes to draft-ietf-lisp-rfc6830bis-19 B.8. 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.8. Changes to draft-ietf-lisp-rfc6830bis-18 B.9. 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.9. Changes to draft-ietf-lisp-rfc6830bis-17 B.10. 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.10. Changes to draft-ietf-lisp-rfc6830bis-16 B.11. 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.11. Changes to draft-ietf-lisp-rfc6830bis-15 B.12. 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.12. Changes to draft-ietf-lisp-rfc6830bis-14 B.13. 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.13. Changes to draft-ietf-lisp-rfc6830bis-13 B.14. 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.14. Changes to draft-ietf-lisp-rfc6830bis-12 B.15. 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.15. Changes to draft-ietf-lisp-rfc6830bis-11 B.16. 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.16. Changes to draft-ietf-lisp-rfc6830bis-10 B.17. 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.17. Changes to draft-ietf-lisp-rfc6830bis-09 B.18. 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.18. Changes to draft-ietf-lisp-rfc6830bis-08 B.19. 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.19. Changes to draft-ietf-lisp-rfc6830bis-07 B.20. 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.20. Changes to draft-ietf-lisp-rfc6830bis-06 B.21. 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 44, line 9 skipping to change at page 44, 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.21. Changes to draft-ietf-lisp-rfc6830bis-05 B.22. 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.22. Changes to draft-ietf-lisp-rfc6830bis-04 B.23. 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.23. Changes to draft-ietf-lisp-rfc6830bis-03 B.24. 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.24. Changes to draft-ietf-lisp-rfc6830bis-02 B.25. 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.25. Changes to draft-ietf-lisp-rfc6830bis-01 B.26. 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.26. Changes to draft-ietf-lisp-rfc6830bis-00 B.27. 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. 34 change blocks. 
60 lines changed or deleted 68 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/