Pascal Thubert (pthubert) <pthub...@cisco.com> wrote: > What if we start like:
Good. > " 3. Overview > This specification extends [RFC8505] and inherits from [RFC8928] to > provide a registration method - called subscription in this case - for > anycast and multicast address. [RFC8505] is agnostic to the routing > protocol in which the address may be redistributed. > In classical networks, [RFC8505] may be used for an ND proxy > operation as specified in [RFC8929], or redistributed in a full- > fledged routing protocol such as EVPN > [I-D.thubert-bess-secure-evpn-mac-signaling] or RIFT > [I-D.ietf-rift-rift]. The device mobility can be gracefully supported > as long has the routers can exchange and make sense of the sequence > counter in the TID field of the EARO. " > Works? _______________________________________________ 6lo mailing list 6lo@ietf.org https://www.ietf.org/mailman/listinfo/6lo