[Lsr] LSR IETF 113 Slot Requests

2022-02-24 Thread Yingzhen Qu
Hi, The draft agenda for IETF 113 has been posted: https://datatracker.ietf.org/meeting/113/agenda/ LSR is scheduled to meet on Thursday afternoon session II, 14:30-16:30 UTC, March 24. Please send slot requests to lsr-cha...@ietf.org

Re: [Lsr] WG Adoption Call for draft-wang-lsr-stub-link-attributes-02

2022-02-24 Thread Acee Lindem (acee)
Hi Chris, I'm currently a co-author and provided input on the encoding and moving the encoding from the base LSAs/TLVs to the TE LSAs/TLVs given that the intended use is, in fact, traffic engineering. However, I do not support WG adoption unless the utility of advertising these external

Re: [Lsr] Update to OSPF Terminology (draft-fox-lsr-ospf-terminology)

2022-02-24 Thread tom petch
From: Lsr on behalf of Christian Hopps Sent: 24 February 2022 14:02 Alvaro Retana writes: > On February 23, 2022 at 8:35:03 PM, Christian Hopps wrote: > > > Chris: > > Hi! > > >> I support these changes, and thanks for taking this up. > > :-) > > >> I guess it makes sense to not go full-in

Re: [Lsr] Update to OSPF Terminology (draft-fox-lsr-ospf-terminology)

2022-02-24 Thread Christian Hopps
Alvaro Retana writes: On February 23, 2022 at 8:35:03 PM, Christian Hopps wrote: Chris: Hi! I support these changes, and thanks for taking this up. :-) I guess it makes sense to not go full-in and re-spin the base docs if there literally are no other changes (although one wonders

Re: [Lsr] Update to OSPF Terminology (draft-fox-lsr-ospf-terminology)

2022-02-24 Thread Acee Lindem (acee)
Agree with Alvaro... There is nothing that says we can't do this document now and still redo the base documents with updated terminology and Errata incorporated. The latter is likely to be a multi-year process while hopefully the former can be done in a year given the right focus. Thanks, Acee

Re: [Lsr] Update to OSPF Terminology (draft-fox-lsr-ospf-terminology)

2022-02-24 Thread Alvaro Retana
On February 23, 2022 at 8:35:03 PM, Christian Hopps wrote: Chris: Hi! > I support these changes, and thanks for taking this up. :-) > I guess it makes sense to not go full-in and re-spin the base docs if there > literally are no other changes (although one wonders if it will actually >