Hey Paul, 

Is the interface number associated with the LLDP Management Address TLV always 
the local ifIndex of the Layer-2 link? 

Hope All is Well,
Acee

> On Mar 4, 2025, at 2:01 PM, Les Ginsberg (ginsberg) <ginsb...@cisco.com> 
> wrote:
> 
> Acee -
>  IEEE Std 802.1AB-2016 Figure 8-11 has exactly what we need.
> In particular:
>  8.5.9.5 interface numbering subtype
> The interface numbering subtype field shall contain an integer value 
> indicating the numbering method used
> for defining the interface number. The following three values are currently 
> defined:
> 1) Unknown
> 2) ifIndex
> 3) system port number
>  And
>  8.5.9.6 interface number
> The interface number field shall contain the assigned number within the 
> system that identifies the specific
> interface associated with this management address.
>     Les
>   > -----Original Message-----
> > From: Acee Lindem <acee.i...@gmail.com>
> > Sent: Tuesday, March 4, 2025 9:56 AM
> > To: Acee Lindem <acee.i...@gmail.com>
> > Cc: lsr <lsr@ietf.org>; draft-glctgp-lsr-l2-bundle-member-remote...@ietf.org
> > Subject: Re: WG Adoption Poll for "Advertisement of Remote Interface
> > Identifiers for Layer 2 Bundle Members" -draft-glctgp-lsr-l2-bundle-member-
> > remote-id-02
> > > 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

Reply via email to