Speaking as WG member: I support adoption.
With respect to acquiring the remote ID, I don't believe that LLDP include the remote ID. There is a port ID but I believe this is an L2 construct. If you're going to reference LLDP, you should add it to the "LLDP IETF Organizationally Specific TLV" as is done for BGP parameters in https://datatracker.ietf.org/doc/draft-acee-idr-lldp-peer-discovery/. Also, you don't mention (via an informational reference) https://datatracker.ietf.org/doc/draft-ietf-lsvr-l3dl/ which does, in fact, advertise the local ifIndex which is commonly used as the interface ID. Thanks, Acee > On Mar 2, 2025, at 8:56 AM, Acee Lindem <acee.i...@gmail.com> wrote: > > LSR WG, > > This starts the Working Group adoption call for > draft-glctgp-lsr-l2-bundle-member-remote-id-02. Please send your > support or objection to this list before March 17th, 2025. > > Thanks, > Acee _______________________________________________ Lsr mailing list -- lsr@ietf.org To unsubscribe send an email to lsr-le...@ietf.org
