draft-ietf-lisp-pubsub-04.txt   draft-ietf-lisp-pubsub-05.txt 
LISP Working Group A. Rodriguez-Natal LISP Working Group A. Rodriguez-Natal
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Experimental V. Ermagan Intended status: Experimental V. Ermagan
Expires: March 14, 2020 Google Expires: September 19, 2020 Google
J. Leong J. Leong
F. Maino F. Maino
Cisco Systems Cisco Systems
A. Cabellos-Aparicio A. Cabellos-Aparicio
Technical University of Catalonia Technical University of Catalonia
S. Barkai S. Barkai
Nexar Inc. Nexar Inc.
D. Farinacci D. Farinacci
lispers.net lispers.net
M. Boucadair M. Boucadair
C. Jacquenet C. Jacquenet
skipping to change at page 1, line 21 skipping to change at page 1, line 22
Technical University of Catalonia Technical University of Catalonia
S. Barkai S. Barkai
Nexar Inc. Nexar Inc.
D. Farinacci D. Farinacci
lispers.net lispers.net
M. Boucadair M. Boucadair
C. Jacquenet C. Jacquenet
Orange Orange
S. Secci S. Secci
Cnam Cnam
September 11, 2019 March 18, 2020
Publish/Subscribe Functionality for LISP Publish/Subscribe Functionality for LISP
draft-ietf-lisp-pubsub-04 draft-ietf-lisp-pubsub-05
Abstract Abstract
This document specifies an extension to the use of Map-Request to This document specifies an extension to the use of Map-Request to
enable Publish/Subscribe (PubSub) operation for LISP. enable Publish/Subscribe (PubSub) operation for LISP.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 46 skipping to change at page 1, line 47
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 March 14, 2020. This Internet-Draft will expire on September 19, 2020.
Copyright Notice 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. 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
skipping to change at page 7, line 5 skipping to change at page 7, line 5
Upon receipt of the Map-Request, the Map-Server processes it as Upon receipt of the Map-Request, the Map-Server processes it as
described in [I-D.ietf-lisp-rfc6833bis]. Furthermore, upon described in [I-D.ietf-lisp-rfc6833bis]. Furthermore, upon
processing, for each EID-Record that has the N-bit set to 1, the Map- 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 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 list of xTR that have requested to be subscribed to that mapping
record. record.
If the xTR-ID is added to the list, the Map-Server MUST send a Map- 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 Notify message back to the xTR to acknowledge the successful
subscription. The Map-Server MUST follow the specification in subscription. The Map-Server MUST follow the specification in
Section 6.1.7 of [I-D.ietf-lisp-rfc6833bis] to build the Map-Notify [I-D.ietf-lisp-rfc6833bis] to build the Map-Notify with the following
with the following considerations: considerations:
(1) The Map-Server MUST use the nonce from the Map-Request as the (1) The Map-Server MUST use the nonce from the Map-Request as the
nonce for the Map-Notify. nonce for the Map-Notify.
(2) The Map-Server MUST use its security association with the xTR (2) The Map-Server MUST use its security association with the xTR
(see Section 3) to compute the authentication data of the Map- (see Section 3) to compute the authentication data of the Map-
Notify. Notify.
(3) The Map-Server MUST send the Map-Notify to one of the ITR-RLOCs (3) The Map-Server MUST send the Map-Notify to one of the ITR-RLOCs
received in the Map-Request. received in the Map-Request.
skipping to change at page 10, line 30 skipping to change at page 10, line 30
| | | | Bit | | | | | Bit |
+----------+---------------+-------------+--------------------------+ +----------+---------------+-------------+--------------------------+
Table 1: Additions to the LISP Map-Request Header Bits Sub-Registry Table 1: Additions to the LISP Map-Request Header Bits Sub-Registry
10. Normative References 10. Normative References
[I-D.ietf-lisp-rfc6833bis] [I-D.ietf-lisp-rfc6833bis]
Farinacci, D., Maino, F., Fuller, V., and A. Cabellos- Farinacci, D., Maino, F., Fuller, V., and A. Cabellos-
Aparicio, "Locator/ID Separation Protocol (LISP) Control- Aparicio, "Locator/ID Separation Protocol (LISP) Control-
Plane", draft-ietf-lisp-rfc6833bis-25 (work in progress), Plane", draft-ietf-lisp-rfc6833bis-27 (work in progress),
June 2019. January 2020.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
skipping to change at page 11, line 11 skipping to change at page 11, line 11
USA USA
Email: natal@cisco.com Email: natal@cisco.com
Vina Ermagan Vina Ermagan
Google Google
USA USA
Email: ermagan@gmail.com Email: ermagan@gmail.com
Johnson Leong Johnson Leong
Cisco Systems
170 Tasman Drive
San Jose, CA
USA
Email: joleong@cisco.com Email: johnsonleong@gmail.com
Fabio Maino Fabio Maino
Cisco Systems Cisco Systems
170 Tasman Drive 170 Tasman Drive
San Jose, CA San Jose, CA
USA USA
Email: fmaino@cisco.com Email: fmaino@cisco.com
Albert Cabellos-Aparicio Albert Cabellos-Aparicio
 End of changes. 10 change blocks. 
14 lines changed or deleted 11 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/