--- 1/draft-ietf-lisp-rfc6830bis-35.txt 2020-11-18 13:14:12.193414949 -0800 +++ 2/draft-ietf-lisp-rfc6830bis-36.txt 2020-11-18 13:14:12.297417574 -0800 @@ -1,25 +1,25 @@ Network Working Group D. Farinacci Internet-Draft lispers.net Obsoletes: 6830 (if approved) V. Fuller Intended status: Standards Track vaf.net Internet Consulting -Expires: March 13, 2021 D. Meyer +Expires: May 22, 2021 D. Meyer 1-4-5.net D. Lewis Cisco Systems A. Cabellos (Ed.) UPC/BarcelonaTech - September 9, 2020 + November 18, 2020 The Locator/ID Separation Protocol (LISP) - draft-ietf-lisp-rfc6830bis-35 + draft-ietf-lisp-rfc6830bis-36 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. @@ -38,21 +38,21 @@ 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 March 13, 2021. + This Internet-Draft will expire on May 22, 2021. Copyright Notice Copyright (c) 2020 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 @@ -1042,21 +1042,23 @@ router to uniquely identify the address space. The value is copied to the 'Instance ID' field of the LISP header, and the I-bit is set to 1. When an ETR decapsulates a packet, the Instance ID from the LISP header is used as a table identifier to locate the forwarding table to use for the inner destination EID lookup. For example, an 802.1Q VLAN tag or VPN identifier could be used as a 24-bit Instance ID. See [I-D.ietf-lisp-vpn] for LISP VPN use-case - details. + details. Please note that the Instance ID is not protected, an on- + path attacker can modify the tags and for instance, allow + communicatons between logically isolated VLANs. Participants within a LISP deployment must agree on the meaning of Instance ID values. The source and destination EIDs MUST belong to the same Instance ID. Instance ID SHOULD NOT be used with overlapping IPv6 EID addresses. 9. Routing Locator Selection The Map-Cache contains the state used by ITRs and PITRs to @@ -1627,27 +1629,27 @@ lisp-data 4341 udp LISP Data Packets 20. References 20.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-06 (work in progress), February 2020. + lisp-6834bis-07 (work in progress), October 2020. [I-D.ietf-lisp-rfc6833bis] Farinacci, D., Maino, F., Fuller, V., and A. Cabellos- Aparicio, "Locator/ID Separation Protocol (LISP) Control- - Plane", draft-ietf-lisp-rfc6833bis-28 (work in progress), - July 2020. + Plane", draft-ietf-lisp-rfc6833bis-29 (work in progress), + September 2020. [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, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate