Comment: >
And how does a Map-Resolver verify a Map-Request? There is no security association with it unless it uses draft-ietf-lisp-ecdsa-auth. And what does "an xTR is allowed to use" mean? Based on what, a white-list in the Map-Resolver, which is intractable? And for point (2), how does the Map-Server know which are legit Map-Resolvers? This text is hand-waving with no support text to say how it does it. Dino > On Feb 15, 2023, at 2:47 PM, [email protected] wrote: > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Locator/ID Separation Protocol WG of the > IETF. > > Title : Publish/Subscribe Functionality for the Locator/ID > Separation Protocol (LISP) > Authors : Alberto Rodriguez-Natal > Vina Ermagan > Albert Cabellos > Sharon Barkai > Mohamed Boucadair > Filename : draft-ietf-lisp-pubsub-13.txt > Pages : 21 > Date : 2023-02-15 > > Abstract: > This document specifies an extension to the request/reply based > Locator/ID Separation Protocol (LISP) control plane to enable > Publish/Subscribe (PubSub) operation. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-lisp-pubsub/ > > There is also an htmlized version available at: > https://datatracker.ietf.org/doc/html/draft-ietf-lisp-pubsub-13 > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-lisp-pubsub-13 > > > Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts > > > _______________________________________________ > lisp mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/lisp
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
