draft-ietf-lisp-pubsub-07.txt   draft-ietf-lisp-pubsub-08.txt 
LISP Working Group A. Rodriguez-Natal LISP Working Group A. Rodriguez-Natal
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Experimental V. Ermagan Intended status: Experimental V. Ermagan
Expires: July 12, 2021 Google Expires: August 6, 2021 Google
A. Cabellos A. Cabellos
UPC/BarcelonaTech UPC/BarcelonaTech
S. Barkai S. Barkai
Nexar Nexar
M. Boucadair M. Boucadair
Orange Orange
January 8, 2021 February 2, 2021
Publish/Subscribe Functionality for LISP Publish/Subscribe Functionality for LISP
draft-ietf-lisp-pubsub-07 draft-ietf-lisp-pubsub-08
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 38 skipping to change at page 1, line 38
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 July 12, 2021. This Internet-Draft will expire on August 6, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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
skipping to change at page 7, line 5 skipping to change at page 7, line 5
[I-D.ietf-lisp-rfc6833bis]. The xTR processes the Map-Reply as [I-D.ietf-lisp-rfc6833bis]. The xTR processes the Map-Reply as
specified in Section 8.1 of [I-D.ietf-lisp-rfc6833bis]. specified in Section 8.1 of [I-D.ietf-lisp-rfc6833bis].
If an xTR-ID is successfully added to the list of subscribers for an If an xTR-ID is successfully added to the list of subscribers for an
EID-Record, the Map-Server MUST extract the nonce and ITR-RLOCs EID-Record, the Map-Server MUST extract the nonce and ITR-RLOCs
present in the Map-Request, and store the association between the present in the Map-Request, and store the association between the
EID-Record, xTR-ID, ITR-RLOCs and nonce. Any already present state EID-Record, xTR-ID, ITR-RLOCs and nonce. Any already present state
regarding ITR-RLOCs and/or nonce for the same xTR-ID MUST be regarding ITR-RLOCs and/or nonce for the same xTR-ID MUST be
overwritten. overwritten.
If the Map-Request only has one ITR-RLOC with AFI = 0 (i.e., Unknown The following specifies the procedure to remove a subscription. If
the Map-Request only has one ITR-RLOC with AFI = 0 (i.e., Unknown
Address), the Map-Server MUST remove the subscription state for that Address), the Map-Server MUST remove the subscription state for that
xTR-ID. In this case, the Map-Server MUST send the Map-Notify to the xTR-ID. In this case, the Map-Server MUST send the Map-Notify to the
source RLOC of the Map-Request. When the TTL for the EID-record source RLOC of the Map-Request. When the TTL for the EID-record
expires, the EID-prefix is removed from the Map-Server's subscription expires, the EID-prefix is removed from the Map-Server's subscription
cache. On EID-Record removal, the Map-Server notifies the cache. On EID-Record removal, the Map-Server notifies the
subscribers via a Map-Notify with TTL equal 0. subscribers via a Map-Notify with TTL equal 0.
6. Mapping Notification Publish Procedures 6. Mapping Notification Publish Procedures
The publish procedure is implemented via Map-Notify messages that the The publish procedure is implemented via Map-Notify messages that the
skipping to change at page 11, line 40 skipping to change at page 11, line 40
11. Normative References 11. 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-30 (work in progress), Plane", draft-ietf-lisp-rfc6833bis-30 (work in progress),
November 2020. November 2020.
[I-D.ietf-lisp-sec] [I-D.ietf-lisp-sec]
Maino, F., Ermagan, V., Cabellos-Aparicio, A., and D. Maino, F., Ermagan, V., Cabellos-Aparicio, A., and D.
Saucez, "LISP-Security (LISP-SEC)", draft-ietf-lisp-sec-21 Saucez, "LISP-Security (LISP-SEC)", draft-ietf-lisp-sec-22
(work in progress), July 2020. (work in progress), January 2021.
[RFC1982] Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1982, [RFC1982] Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1982,
DOI 10.17487/RFC1982, August 1996, DOI 10.17487/RFC1982, August 1996,
<https://www.rfc-editor.org/info/rfc1982>. <https://www.rfc-editor.org/info/rfc1982>.
[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>.
 End of changes. 6 change blocks. 
7 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/