Hi Dino, I’m referring to this exchange [1] between Alvaro and you, regarding the use of ITR-RLOCs from the Map-Request as the addresses to use to send the Map-Notifies to.
The summary is that since Map-Requests include the “ITR-RLOC” fields, we are using those, instead of the source address of the Map-Request, to send the Map-Notifies. This is for both Map-Notifies used to ack subscription as well as for Map-Notifies sent as publication (the Map-Server keeps track of the last ITR-RLOCs received for a subscriber). Hope it makes sense :) Alberto [1] https://mailarchive.ietf.org/arch/msg/lisp/hN4tpuZl2nm86UVTqqmH24q0Tx8/ From: Dino Farinacci <[email protected]> Date: Sunday, November6 2022 at 2:39 PM To: Alberto Rodriguez-Natal (natal) <[email protected]> Cc: Alvaro Retana <[email protected]>, [email protected] <[email protected]>, Luigi Iannone <[email protected]>, [email protected] <[email protected]>, Vina Ermagan <[email protected]>, Stefano Secci <[email protected]>, Fabio Maino (fmaino) <[email protected]>, Sharon Barkai <[email protected]>, Albert Cabellos <[email protected]>, Johnson Leong <[email protected]>, JACQUENET Christian INNOV/NET <[email protected]>, [email protected] <[email protected]> Subject: Re: AD Review of draft-ietf-lisp-pubsub-09 > [AR] As mentioned in the Alvaro/Dino discussion, regular Map-Notifies as per > 9301 are sent to the source IP address of the Map-Register that triggered > them. Since PubSub extends LISP to specify that Map-Notifies can also be > triggered by Map-Requests, we need to specify where these > Map-Request-triggered Map-Notifies are sent to. This isn't making sense to me. Are you talking about a Map-Notify as an ack to the Map-Register or an unsolicited Map-Notify and if the latter, the notification is going to the source address of the LAST subscription request. And if another Map-Request came later with the N-bit set again, with a new/different source IP address, the map-server must cache the last address (and later send Map-Notify to this new address). Agree? Dino
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
