draft-ietf-lisp-rfc6830bis-22.txt   draft-ietf-lisp-rfc6830bis-23.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 4, 2019 Cisco Systems Expires: April 6, 2019 Cisco Systems
A. Cabellos (Ed.) A. Cabellos (Ed.)
UPC/BarcelonaTech UPC/BarcelonaTech
October 1, 2018 October 3, 2018
The Locator/ID Separation Protocol (LISP) The Locator/ID Separation Protocol (LISP)
draft-ietf-lisp-rfc6830bis-22 draft-ietf-lisp-rfc6830bis-23
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 4, 2019. This Internet-Draft will expire on April 6, 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
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Scope of Applicability . . . . . . . . . . . . . . . . . 4
2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 4 2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 4
3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4 3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 5
4. Basic Overview . . . . . . . . . . . . . . . . . . . . . . . 9 4. Basic Overview . . . . . . . . . . . . . . . . . . . . . . . 9
4.1. Packet Flow Sequence . . . . . . . . . . . . . . . . . . 11 4.1. Packet Flow Sequence . . . . . . . . . . . . . . . . . . 11
5. LISP Encapsulation Details . . . . . . . . . . . . . . . . . 12 5. LISP Encapsulation Details . . . . . . . . . . . . . . . . . 13
5.1. LISP IPv4-in-IPv4 Header Format . . . . . . . . . . . . . 13 5.1. LISP IPv4-in-IPv4 Header Format . . . . . . . . . . . . . 13
5.2. LISP IPv6-in-IPv6 Header Format . . . . . . . . . . . . . 14 5.2. LISP IPv6-in-IPv6 Header Format . . . . . . . . . . . . . 14
5.3. Tunnel Header Field Descriptions . . . . . . . . . . . . 15 5.3. Tunnel Header Field Descriptions . . . . . . . . . . . . 15
6. LISP EID-to-RLOC Map-Cache . . . . . . . . . . . . . . . . . 20 6. LISP EID-to-RLOC Map-Cache . . . . . . . . . . . . . . . . . 20
7. Dealing with Large Encapsulated Packets . . . . . . . . . . . 20 7. Dealing with Large Encapsulated Packets . . . . . . . . . . . 20
7.1. A Stateless Solution to MTU Handling . . . . . . . . . . 21 7.1. A Stateless Solution to MTU Handling . . . . . . . . . . 21
7.2. A Stateful Solution to MTU Handling . . . . . . . . . . . 22 7.2. A Stateful Solution to MTU Handling . . . . . . . . . . . 22
8. Using Virtualization and Segmentation with LISP . . . . . . . 22 8. Using Virtualization and Segmentation with LISP . . . . . . . 22
9. Routing Locator Selection . . . . . . . . . . . . . . . . . . 23 9. Routing Locator Selection . . . . . . . . . . . . . . . . . . 23
10. Routing Locator Reachability . . . . . . . . . . . . . . . . 25 10. Routing Locator Reachability . . . . . . . . . . . . . . . . 25
skipping to change at page 3, line 4 skipping to change at page 3, line 5
14. Multicast Considerations . . . . . . . . . . . . . . . . . . 31 14. Multicast Considerations . . . . . . . . . . . . . . . . . . 31
15. Router Performance Considerations . . . . . . . . . . . . . . 31 15. Router Performance Considerations . . . . . . . . . . . . . . 31
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 . . . . . . . . . . . . . . . . 39 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 39
B.1. Changes to draft-ietf-lisp-rfc6830bis-22 . . . . . . . . 40 B.1. Changes to draft-ietf-lisp-rfc6830bis-22 . . . . . . . . 40
B.2. Changes to draft-ietf-lisp-rfc6830bis-21 . . . . . . . . 40 B.2. Changes to draft-ietf-lisp-rfc6830bis-22 . . . . . . . . 40
B.3. Changes to draft-ietf-lisp-rfc6830bis-20 . . . . . . . . 40 B.3. Changes to draft-ietf-lisp-rfc6830bis-21 . . . . . . . . 40
B.4. Changes to draft-ietf-lisp-rfc6830bis-19 . . . . . . . . 40 B.4. Changes to draft-ietf-lisp-rfc6830bis-20 . . . . . . . . 40
B.5. Changes to draft-ietf-lisp-rfc6830bis-18 . . . . . . . . 40 B.5. Changes to draft-ietf-lisp-rfc6830bis-19 . . . . . . . . 40
B.6. Changes to draft-ietf-lisp-rfc6830bis-17 . . . . . . . . 40 B.6. Changes to draft-ietf-lisp-rfc6830bis-18 . . . . . . . . 40
B.7. Changes to draft-ietf-lisp-rfc6830bis-16 . . . . . . . . 40 B.7. Changes to draft-ietf-lisp-rfc6830bis-17 . . . . . . . . 40
B.8. Changes to draft-ietf-lisp-rfc6830bis-15 . . . . . . . . 41 B.8. Changes to draft-ietf-lisp-rfc6830bis-16 . . . . . . . . 41
B.9. Changes to draft-ietf-lisp-rfc6830bis-14 . . . . . . . . 41 B.9. Changes to draft-ietf-lisp-rfc6830bis-15 . . . . . . . . 41
B.10. Changes to draft-ietf-lisp-rfc6830bis-13 . . . . . . . . 41 B.10. Changes to draft-ietf-lisp-rfc6830bis-14 . . . . . . . . 41
B.11. Changes to draft-ietf-lisp-rfc6830bis-12 . . . . . . . . 41 B.11. Changes to draft-ietf-lisp-rfc6830bis-13 . . . . . . . . 41
B.12. Changes to draft-ietf-lisp-rfc6830bis-11 . . . . . . . . 41 B.12. Changes to draft-ietf-lisp-rfc6830bis-12 . . . . . . . . 41
B.13. Changes to draft-ietf-lisp-rfc6830bis-10 . . . . . . . . 41 B.13. Changes to draft-ietf-lisp-rfc6830bis-11 . . . . . . . . 41
B.14. Changes to draft-ietf-lisp-rfc6830bis-09 . . . . . . . . 42 B.14. Changes to draft-ietf-lisp-rfc6830bis-10 . . . . . . . . 42
B.15. Changes to draft-ietf-lisp-rfc6830bis-08 . . . . . . . . 42 B.15. Changes to draft-ietf-lisp-rfc6830bis-09 . . . . . . . . 42
B.16. Changes to draft-ietf-lisp-rfc6830bis-07 . . . . . . . . 42 B.16. Changes to draft-ietf-lisp-rfc6830bis-08 . . . . . . . . 42
B.17. Changes to draft-ietf-lisp-rfc6830bis-06 . . . . . . . . 42 B.17. Changes to draft-ietf-lisp-rfc6830bis-07 . . . . . . . . 43
B.18. Changes to draft-ietf-lisp-rfc6830bis-05 . . . . . . . . 43 B.18. Changes to draft-ietf-lisp-rfc6830bis-06 . . . . . . . . 43
B.19. Changes to draft-ietf-lisp-rfc6830bis-04 . . . . . . . . 43 B.19. Changes to draft-ietf-lisp-rfc6830bis-05 . . . . . . . . 43
B.20. Changes to draft-ietf-lisp-rfc6830bis-03 . . . . . . . . 43 B.20. Changes to draft-ietf-lisp-rfc6830bis-04 . . . . . . . . 43
B.21. Changes to draft-ietf-lisp-rfc6830bis-02 . . . . . . . . 43 B.21. Changes to draft-ietf-lisp-rfc6830bis-03 . . . . . . . . 44
B.22. Changes to draft-ietf-lisp-rfc6830bis-01 . . . . . . . . 44 B.22. Changes to draft-ietf-lisp-rfc6830bis-02 . . . . . . . . 44
B.23. Changes to draft-ietf-lisp-rfc6830bis-00 . . . . . . . . 44 B.23. Changes to draft-ietf-lisp-rfc6830bis-01 . . . . . . . . 44
B.24. 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 4, line 25 skipping to change at page 4, line 27
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. This document obsoletes RFC 6830.
1.1. Scope of Applicability
LISP was originally developed to address the Internet-wide route
scaling problem [RFC4984]. While there are a number of approaches of
interest for that problem, as LISP as been developed and refined, a
large number of other LISP uses have been found and are being used.
As such, the design and development of LISP has changed so as to
focus on these use cases. The common property of these uses is a
large set of cooperating entities seeking to communicate over the
public Internet or other large underlay IP infrastructures, while
keeping the addressing and topology of the cooperating entities
separate from the underlay and Internet topology, routing, and
addressing.
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", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
3. Definition of Terms 3. Definition of Terms
skipping to change at page 5, line 31 skipping to change at page 5, line 49
general, an ETR receives LISP-encapsulated IP packets from the general, an ETR receives LISP-encapsulated IP packets from the
Internet on one side and sends decapsulated IP packets to site Internet on one side and sends decapsulated IP packets to site
end-systems on the other side. ETR functionality does not have to end-systems on the other side. ETR functionality does not have to
be limited to a router device. A server host can be the endpoint be limited to a router device. A server host can be the endpoint
of a LISP tunnel as well. of a LISP tunnel as well.
EID-to-RLOC Database: The EID-to-RLOC Database is a global EID-to-RLOC Database: The EID-to-RLOC Database is a global
distributed database that contains all known EID-Prefix-to-RLOC distributed database that contains all known EID-Prefix-to-RLOC
mappings. Each potential ETR typically contains a small piece of mappings. Each potential ETR typically contains a small piece of
the database: the EID-to-RLOC mappings for the EID-Prefixes the database: the EID-to-RLOC mappings for the EID-Prefixes
"behind" the router. These map to one of the router's own "behind" the router. These map to one of the router's own IP
globally visible IP addresses. Note that there MAY be transient addresses that are routable on the underlay. Note that there MAY
conditions when the EID-Prefix for the site and Locator-Set for be transient conditions when the EID-Prefix for the site and
each EID-Prefix may not be the same on all ETRs. This has no Locator-Set for each EID-Prefix may not be the same on all ETRs.
negative implications, since a partial set of Locators can be
used. This has no negative implications, since a partial set of Locators
can be used.
EID-to-RLOC Map-Cache: The EID-to-RLOC Map-Cache is generally EID-to-RLOC Map-Cache: The EID-to-RLOC Map-Cache is generally
short-lived, on-demand table in an ITR that stores, tracks, and is short-lived, on-demand table in an ITR that stores, tracks, and is
responsible for timing out and otherwise validating EID-to-RLOC responsible for timing out and otherwise validating EID-to-RLOC
mappings. This cache is distinct from the full "database" of EID- mappings. This cache is distinct from the full "database" of EID-
to-RLOC mappings; it is dynamic, local to the ITR(s), and to-RLOC mappings; it is dynamic, local to the ITR(s), and
relatively small, while the database is distributed, relatively relatively small, while the database is distributed, relatively
static, and much more global in scope. static, and much more global in scope to LISP nodes.
EID-Prefix: An EID-Prefix is a power-of-two block of EIDs that are EID-Prefix: An EID-Prefix is a power-of-two block of EIDs that are
allocated to a site by an address allocation authority. EID- allocated to a site by an address allocation authority. EID-
Prefixes are associated with a set of RLOC addresses. EID-Prefix Prefixes are associated with a set of RLOC addresses. EID-Prefix
allocations can be broken up into smaller blocks when an RLOC set allocations can be broken up into smaller blocks when an RLOC set
is to be associated with the larger EID-Prefix block. is to be associated with the larger EID-Prefix block.
End-System: An end-system is an IPv4 or IPv6 device that originates End-System: An end-system is an IPv4 or IPv6 device that originates
packets with a single IPv4 or IPv6 header. The end-system packets with a single IPv4 or IPv6 header. The end-system
supplies an EID value for the destination address field of the IP supplies an EID value for the destination address field of the IP
header when communicating globally (i.e., outside of its routing header when communicating outside of its routing domain. An end-
domain). An end-system can be a host computer, a switch or router system can be a host computer, a switch or router device, or any
device, or any network appliance. network appliance.
Endpoint ID (EID): An EID is a 32-bit (for IPv4) or 128-bit (for Endpoint ID (EID): An EID is a 32-bit (for IPv4) or 128-bit (for
IPv6) value used in the source and destination address fields of IPv6) value used in the source and destination address fields of
the first (most inner) LISP header of a packet. The host obtains the first (most inner) LISP header of a packet. The host obtains
a destination EID the same way it obtains a destination address a destination EID the same way it obtains a destination address
today, for example, through a Domain Name System (DNS) [RFC1034] today, for example, through a Domain Name System (DNS) [RFC1034]
lookup or Session Initiation Protocol (SIP) [RFC3261] exchange. lookup or Session Initiation Protocol (SIP) [RFC3261] exchange.
The source EID is obtained via existing mechanisms used to set a The source EID is obtained via existing mechanisms used to set a
host's "local" IP address. An EID used on the public Internet host's "local" IP address. An EID used on the public Internet
MUST have the same properties as any other IP address used in that MUST have the same properties as any other IP address used in that
manner; this means, among other things, that it MUST be globally manner; this means, among other things, that it MUST be globally
unique. An EID is allocated to a host from an EID-Prefix block unique. An EID is allocated to a host from an EID-Prefix block
associated with the site where the host is located. An EID can be associated with the site where the host is located. An EID can be
used by a host to refer to other hosts. Note that EID blocks MAY used by a host to refer to other hosts. Note that EID blocks MAY
be assigned in a hierarchical manner, independent of the network be assigned in a hierarchical manner, independent of the network
topology, to facilitate scaling of the mapping database. In topology, to facilitate scaling of the mapping database. In
addition, an EID block assigned to a site MAY have site-local addition, an EID block assigned to a site MAY have site-local
structure (subnetting) for routing within the site; this structure structure (subnetting) for routing within the site; this structure
is not visible to the global routing system. In theory, the bit is not visible to the underlay routing system. In theory, the bit
string that represents an EID for one device can represent an RLOC string that represents an EID for one device can represent an RLOC
for a different device. When used in discussions with other for a different device. When used in discussions with other
Locator/ID separation proposals, a LISP EID will be called an Locator/ID separation proposals, a LISP EID will be called an
"LEID". Throughout this document, any references to "EID" refer "LEID". Throughout this document, any references to "EID" refer
to an LEID. to an LEID.
Ingress Tunnel Router (ITR): An ITR is a router that resides in a Ingress Tunnel Router (ITR): An ITR is a router that resides in a
LISP site. Packets sent by sources inside of the LISP site to LISP site. Packets sent by sources inside of the LISP site to
destinations outside of the site are candidates for encapsulation destinations outside of the site are candidates for encapsulation
by the ITR. The ITR treats the IP destination address as an EID by the ITR. The ITR treats the IP destination address as an EID
skipping to change at page 31, line 32 skipping to change at page 31, line 32
The outer IP header (the destination Routing Locator address), The outer IP header (the destination Routing Locator address),
prepended by a LISP router, can use the same group address as the prepended by a LISP router, can use the same group address as the
destination Routing Locator, use a multicast or unicast Routing destination Routing Locator, use a multicast or unicast Routing
Locator obtained from a Mapping System lookup, or use other means to Locator obtained from a Mapping System lookup, or use other means to
determine the group address mapping. determine the group address mapping.
With respect to the source Routing Locator address, the ITR prepends With respect to the source Routing Locator address, the ITR prepends
its own IP address as the source address of the outer IP header. 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. Just like it would if the destination EID was a unicast address.
This source Routing Locator address, like any other Routing Locator This source Routing Locator address, like any other Routing Locator
address, MUST be globally routable. address, MUST be routable on the underlay.
There are two approaches for LISP-Multicast, one that uses native There are two approaches for LISP-Multicast, one that uses native
multicast routing in the underlay with no support from the Mapping multicast routing in the underlay with no support from the Mapping
System and the other that uses only unicast routing in the underlay System and the other that uses only unicast routing in the underlay
with support from the Mapping System. See [RFC6831] and [RFC8378], with support from the Mapping System. See [RFC6831] and [RFC8378],
respectively, for details. Details for LISP-Multicast and respectively, for details. Details for LISP-Multicast and
interworking with non-LISP sites are described in [RFC6831] and interworking with non-LISP sites are described in [RFC6831] and
[RFC6832]. [RFC6832].
15. Router Performance Considerations 15. Router Performance Considerations
skipping to change at page 40, line 9 skipping to change at page 40, line 9
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-22 B.1. Changes to draft-ietf-lisp-rfc6830bis-22
o Posted early October 2018. o Posted early October 2018.
o Added an applicability statement in section 1 to address security
concerns from Telechat.
B.2. Changes to draft-ietf-lisp-rfc6830bis-22
o Posted early October 2018.
o Changes to reflect comments post Telechat. o Changes to reflect comments post Telechat.
B.2. Changes to draft-ietf-lisp-rfc6830bis-21 B.3. 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.3. Changes to draft-ietf-lisp-rfc6830bis-20 B.4. 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.4. Changes to draft-ietf-lisp-rfc6830bis-19 B.5. 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.5. Changes to draft-ietf-lisp-rfc6830bis-18 B.6. 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.6. Changes to draft-ietf-lisp-rfc6830bis-17 B.7. 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.7. Changes to draft-ietf-lisp-rfc6830bis-16 B.8. 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.8. Changes to draft-ietf-lisp-rfc6830bis-15 B.9. 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.9. Changes to draft-ietf-lisp-rfc6830bis-14 B.10. 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.10. Changes to draft-ietf-lisp-rfc6830bis-13 B.11. 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.11. Changes to draft-ietf-lisp-rfc6830bis-12 B.12. 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.12. Changes to draft-ietf-lisp-rfc6830bis-11 B.13. 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.13. Changes to draft-ietf-lisp-rfc6830bis-10 B.14. 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.14. Changes to draft-ietf-lisp-rfc6830bis-09 B.15. 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.15. Changes to draft-ietf-lisp-rfc6830bis-08 B.16. 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.16. Changes to draft-ietf-lisp-rfc6830bis-07 B.17. 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.17. Changes to draft-ietf-lisp-rfc6830bis-06 B.18. 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 22 skipping to change at page 43, line 35
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.18. Changes to draft-ietf-lisp-rfc6830bis-05 B.19. 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.19. Changes to draft-ietf-lisp-rfc6830bis-04 B.20. 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.20. Changes to draft-ietf-lisp-rfc6830bis-03 B.21. 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.21. Changes to draft-ietf-lisp-rfc6830bis-02 B.22. 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.22. Changes to draft-ietf-lisp-rfc6830bis-01 B.23. 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.23. Changes to draft-ietf-lisp-rfc6830bis-00 B.24. 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. 38 change blocks. 
63 lines changed or deleted 86 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/