--- 1/draft-ietf-lisp-pubsub-04.txt 2020-03-18 18:13:11.110007353 -0700 +++ 2/draft-ietf-lisp-pubsub-05.txt 2020-03-18 18:13:11.138008063 -0700 @@ -1,16 +1,17 @@ LISP Working Group A. Rodriguez-Natal Internet-Draft Cisco Systems Intended status: Experimental V. Ermagan -Expires: March 14, 2020 Google +Expires: September 19, 2020 Google J. Leong + F. Maino Cisco Systems A. Cabellos-Aparicio Technical University of Catalonia S. Barkai Nexar Inc. D. Farinacci lispers.net M. Boucadair C. Jacquenet @@ -10,24 +11,24 @@ Technical University of Catalonia S. Barkai Nexar Inc. D. Farinacci lispers.net M. Boucadair C. Jacquenet Orange S. Secci Cnam - September 11, 2019 + March 18, 2020 Publish/Subscribe Functionality for LISP - draft-ietf-lisp-pubsub-04 + draft-ietf-lisp-pubsub-05 Abstract This document specifies an extension to the use of Map-Request to enable Publish/Subscribe (PubSub) operation for LISP. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. @@ -35,25 +36,25 @@ 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 14, 2020. + This Internet-Draft will expire on September 19, 2020. Copyright Notice - Copyright (c) 2019 IETF Trust and the persons identified as the + 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -243,22 +244,22 @@ Upon receipt of the Map-Request, the Map-Server processes it as described in [I-D.ietf-lisp-rfc6833bis]. Furthermore, upon processing, for each EID-Record that has the N-bit set to 1, the Map- Server proceeds adding the xTR-ID contained in the Map-Request to the list of xTR that have requested to be subscribed to that mapping record. If the xTR-ID is added to the list, the Map-Server MUST send a Map- Notify message back to the xTR to acknowledge the successful subscription. The Map-Server MUST follow the specification in - Section 6.1.7 of [I-D.ietf-lisp-rfc6833bis] to build the Map-Notify - with the following considerations: + [I-D.ietf-lisp-rfc6833bis] to build the Map-Notify with the following + considerations: (1) The Map-Server MUST use the nonce from the Map-Request as the nonce for the Map-Notify. (2) The Map-Server MUST use its security association with the xTR (see Section 3) to compute the authentication data of the Map- Notify. (3) The Map-Server MUST send the Map-Notify to one of the ITR-RLOCs received in the Map-Request. @@ -411,22 +412,22 @@ | | | | Bit | +----------+---------------+-------------+--------------------------+ Table 1: Additions to the LISP Map-Request Header Bits Sub-Registry 10. Normative References [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-25 (work in progress), - June 2019. + Plane", draft-ietf-lisp-rfc6833bis-27 (work in progress), + January 2020. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . @@ -439,26 +440,22 @@ USA Email: natal@cisco.com Vina Ermagan Google USA Email: ermagan@gmail.com Johnson Leong - Cisco Systems - 170 Tasman Drive - San Jose, CA - USA - Email: joleong@cisco.com + Email: johnsonleong@gmail.com Fabio Maino Cisco Systems 170 Tasman Drive San Jose, CA USA Email: fmaino@cisco.com Albert Cabellos-Aparicio