draft-ietf-lisp-rfc6830bis-31.txt   draft-ietf-lisp-rfc6830bis-32.txt 
skipping to change at page 1, line 16 skipping to change at page 1, line 16
Intended status: Standards Track vaf.net Internet Consulting Intended status: Standards Track vaf.net Internet Consulting
Expires: September 6, 2020 D. Meyer Expires: September 6, 2020 D. Meyer
1-4-5.net 1-4-5.net
D. Lewis D. Lewis
Cisco Systems Cisco Systems
A. Cabellos (Ed.) A. Cabellos (Ed.)
UPC/BarcelonaTech UPC/BarcelonaTech
March 5, 2020 March 5, 2020
The Locator/ID Separation Protocol (LISP) The Locator/ID Separation Protocol (LISP)
draft-ietf-lisp-rfc6830bis-31 draft-ietf-lisp-rfc6830bis-32
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 19, line 15 skipping to change at page 19, line 15
misconfiguration. misconfiguration.
Some xTRs and PxTRs performs re-encapsulation operations and need to Some xTRs and PxTRs performs re-encapsulation operations and need to
treat the 'Explicit Congestion Notification' (ECN) in a special way. treat the 'Explicit Congestion Notification' (ECN) in a special way.
Because the re-encapsulation operation is a sequence of two Because the re-encapsulation operation is a sequence of two
operations, namely a decapsulation followed by an encapsulation, the operations, namely a decapsulation followed by an encapsulation, the
ECN bits MUST be treated as described above for these two operations. ECN bits MUST be treated as described above for these two operations.
The LISP dataplane protocol is not backwards compatible with The LISP dataplane protocol is not backwards compatible with
[RFC6830] and does not have explicit support for introducing future [RFC6830] and does not have explicit support for introducing future
protocol changes (e.g. an explicit version field), However, the LISP protocol changes (e.g. an explicit version field). However, the LISP
control plane [I-D.ietf-lisp-rfc6833bis] allows an ETR to register control plane [I-D.ietf-lisp-rfc6833bis] allows an ETR to register
dataplane capabilities by means of new LCAF types [RFC8060]. In this dataplane capabilities by means of new LCAF types [RFC8060]. In this
way an ITR can be made aware of the dataplane capabilities of an ETR, way an ITR can be made aware of the dataplane capabilities of an ETR,
and encapsulate accordingly. The specification of the new LCAF and encapsulate accordingly. The specification of the new LCAF
types, new LCAF mechanisms, and their use, is out of the scope of types, new LCAF mechanisms, and their use, is out of the scope of
this document. this document.
6. LISP EID-to-RLOC Map-Cache 6. LISP EID-to-RLOC Map-Cache
ITRs and PITRs maintain an on-demand cache, referred as LISP EID-to- ITRs and PITRs maintain an on-demand cache, referred as LISP EID-to-
 End of changes. 2 change blocks. 
2 lines changed or deleted 2 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/