Hi Acee,
On 04/03/2025 18:58, Acee Lindem wrote:
Speaking as WG member:
I support adoption. However, it seems this draft could have been combined with
the draft defining the flex-algo constraints for the reverse metric. I guess
more RFCs equals better CVs 😎
not really :)
I guess you meant
Hi WG,
I support this adoption.
Thanks,
Allen
-- Forwarded message --
From: Acee Lindem
To: lsr
Cc: "draft-glctgp-lsr-l2-bundle-member-remote...@ietf.org" <
draft-glctgp-lsr-l2-bundle-member-remote...@ietf.org>
Bcc:
Date: Sun, 2 Mar 2025 13:56:42 +
Subject: WG Adoption Poll
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)
> wrote:
>
> Acee -
> IEEE Std 802.1AB-2016 Figure 8-11 has exactly what we need.
> I
Hi Acee，WG，
I support adoption.
Best Regards,
Ran
-- Forwarded message --From: Acee Lindem
To: lsr Cc:
"draft-glctgp-lsr-l2-bundle-member-remote...@ietf.org"
Bcc: Date: Sun, 2 Mar
2025 13:56:42 +Subject: WG Adoption Poll for "Advertisement of Remote
Interface Identifi
Hello Acee,
Good to hear from you. I've copied Scott Mansfield who worked on the LLDP YANG
in case he has a different perspective.
The Management Address TLV was designed with a bit of flexibility to allow you
to advertise a management address used to reach a higher level entity for
vario
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)
> wrote:
>
> Acee -
> IEEE Std 802.1AB-2016 Figure 8-11 has exactly what we need.
>
Hi Acee, WG,
I support this draft as it enhances the IGP Flexible Algorithm by introducing
an SPF algorithm based on reverse link metrics, which is useful for use cases
such as multicast.
Best Regards,
Ran
Original
From: AceeLindem
To: lsr ;
Cc: draft-ppsenak-lsr-igp-reverse-spf-a
Hi Paul,
That's what I thought - that the management address was not necessarily
associated with the local L2 interface.
The Port ID TLV also doesn't include the local ifIndex so it appears that there
is currently no way to learn this in LLDP - correct?
Thanks,
Acee
> On Mar 5, 2025, at 1:3
Great. Thanks for the explanation! Looks good to me.
---
Mike Ounsworth
From: Acee Lindem
Sent: Tuesday, March 4, 2025 5:14 PM
To: Mike Ounsworth
Cc: sec...@ietf.org; draft-ietf-lsr-ospf-prefix-extended-flags@ietf.org;
last-call ; lsr
Subject: [EXTERNAL] Re: Secdir last call revie
