Re: [Lsr] Working Group Last Call for "OSPFv3 Extensions for SRv6" - draft-ietf-lsr-ospfv3-srv6-extensions-06.txt (Corrected Address)

2022-08-17 Thread Ketan Talaulikar
Hi Yingzhen, Thanks for your review and please check inline below for responses. The changes as discussed below will be reflected in the upcoming update of the draft. On Wed, Aug 17, 2022 at 5:22 AM Yingzhen Qu wrote: > I support progressing this draft. > > I have the following minor

Re: [Lsr] Working Group Last Call for "OSPFv3 Extensions for SRv6" - draft-ietf-lsr-ospfv3-srv6-extensions-06.txt (Corrected Address)

2022-08-17 Thread Ketan Talaulikar
Hello Acee/All, There has not been any further comment/feedback on the point that Dirk brought up in the thread below: https://mailarchive.ietf.org/arch/msg/lsr/_4HcJEsteNQxjxuot1uLdoXeH6s/ I want to point out that not just the LA-flag, but also the P-flag is required for propagation of the SRv6

Re: [Lsr] Working Group Last Call for "OSPFv3 Extensions for SRv6" - draft-ietf-lsr-ospfv3-srv6-extensions-06.txt (Corrected Address)

2022-08-17 Thread Acee Lindem (acee)
Hi Ketan, From: Ketan Talaulikar Date: Wednesday, August 17, 2022 at 11:04 AM To: Acee Lindem Cc: lsr , "draft-ietf-lsr-ospfv3-srv6-extensi...@ietf.org" , "Goethals, Dirk (Nokia - BE/Antwerp)" Subject: Re: [Lsr] Working Group Last Call for "OSPFv3 Extensions for SRv6" -

Re: [Lsr] Working Group Last Call for "OSPFv3 Extensions for SRv6" - draft-ietf-lsr-ospfv3-srv6-extensions-06.txt (Corrected Address)

2022-08-17 Thread Acee Lindem (acee)
Hi Yingzhen, From: Yingzhen Qu Date: Tuesday, August 16, 2022 at 7:52 PM To: Acee Lindem Cc: lsr , "draft-ietf-lsr-ospfv3-srv6-extensi...@ietf.org" Subject: Re: [Lsr] Working Group Last Call for "OSPFv3 Extensions for SRv6" - draft-ietf-lsr-ospfv3-srv6-extensions-06.txt (Corrected Address)

Re: [Lsr] Working Group Last Call for "OSPFv3 Extensions for SRv6" - draft-ietf-lsr-ospfv3-srv6-extensions-06.txt (Corrected Address)

2022-08-17 Thread Ketan Talaulikar
Hi Acee, Please check inline below. On Wed, Aug 17, 2022 at 8:06 PM Acee Lindem (acee) wrote: > Hi Ketan, > > > > *From: *Lsr on behalf of Ketan Talaulikar < > ketant.i...@gmail.com> > *Date: *Wednesday, August 17, 2022 at 9:48 AM > *To: *Acee Lindem > *Cc: *lsr ,

Re: [Lsr] Working Group Last Call for "OSPFv3 Extensions for SRv6" - draft-ietf-lsr-ospfv3-srv6-extensions-06.txt (Corrected Address)

2022-08-17 Thread Acee Lindem (acee)
Hi Ketan, From: Lsr on behalf of Ketan Talaulikar Date: Wednesday, August 17, 2022 at 9:48 AM To: Acee Lindem Cc: lsr , "draft-ietf-lsr-ospfv3-srv6-extensi...@ietf.org" , "Goethals, Dirk (Nokia - BE/Antwerp)" Subject: Re: [Lsr] Working Group Last Call for "OSPFv3 Extensions for SRv6" -

Re: [Lsr] Working Group Last Call for "OSPFv3 Extensions for SRv6" - draft-ietf-lsr-ospfv3-srv6-extensions-06.txt (Corrected Address)

2022-08-17 Thread Acee Lindem (acee)
Hi Ketan, From: Ketan Talaulikar Date: Wednesday, August 17, 2022 at 11:35 AM To: Acee Lindem Cc: lsr , "draft-ietf-lsr-ospfv3-srv6-extensi...@ietf.org" , "Goethals, Dirk (Nokia - BE/Antwerp)" Subject: Re: [Lsr] Working Group Last Call for "OSPFv3 Extensions for SRv6" -

Re: [Lsr] Working Group Last Call for "OSPFv3 Extensions for SRv6" - draft-ietf-lsr-ospfv3-srv6-extensions-06.txt (Corrected Address)

2022-08-17 Thread Ketan Talaulikar
Hi Acee, The routing for anycast is transparent but there are features and use cases where the knowledge of Anycast is required or helpful. I don't have all the draft pointers, but there have been presentations in SPRING and RTGWG WGs on redundancy and protection features that leverage anycast.

[Lsr] Yangdoctors last call review of draft-ietf-isis-sr-yang-13

2022-08-17 Thread Jan Lindblad via Datatracker
Reviewer: Jan Lindblad Review result: Ready with Issues This is the YANG Doctor last call review of draft-ietf-isis-sr-yang-13. I think this module is written in a nice, straight forward way. There are a few things that have to be fixed before this can be published, however, so I will call it

[Lsr] AD review of draft-ietf-lsr-isis-rfc5316bis-02

2022-08-17 Thread John Scudder
Hi Authors, Thanks for your patience as this clean and easy-to-review document sat in my queue for too long. :-( Here’s my review. I’ve supplied my comments in the form of an edited copy of the draft. Minor editorial suggestions (including at least two reversions to the language of the base

[Lsr] Datatracker State Update Notice:

2022-08-17 Thread IETF Secretariat
IESG state changed: New State: AD Evaluation (The previous state was Publication Requested) Datatracker URL: https://datatracker.ietf.org/doc/draft-ietf-lsr-pce-discovery-security-support/ ___ Lsr mailing list Lsr@ietf.org

[Lsr] Datatracker State Update Notice:

2022-08-17 Thread IETF Secretariat
IESG state changed: New State: AD Evaluation::Revised I-D Needed (The previous state was AD Evaluation) See review sent to WG mailing list. Datatracker URL: https://datatracker.ietf.org/doc/draft-ietf-lsr-pce-discovery-security-support/ ___ Lsr

Re: [Lsr] Comments ondraft-gong-lsr-exclusive-link-for-flex-algo

2022-08-17 Thread Les Ginsberg (ginsberg)
Liyan – For IS-IS there is no need for a new mechanism to exclude a link from algo 0 SPF. On that we at least seem to agree. Changing Algo 0 SPF in order to accommodate a new requirement you have for flex-algo is simply wrong – which is why I still think your draft is not needed. What then

Re: [Lsr] AD review of draft-ietf-lsr-isis-rfc5316bis-02

2022-08-17 Thread Les Ginsberg (ginsberg)
John – Thanx for the thoughtful review. I accept all of your editorial changes except as noted below. Responses inline. From: Lsr On Behalf Of John Scudder Sent: Wednesday, August 17, 2022 12:02 PM To: draft-ietf-lsr-isis-rfc5316...@ietf.org; lsr@ietf.org Subject: [Lsr] AD review of

Re: [Lsr] Comments ondraft-gong-lsr-exclusive-link-for-flex-algo

2022-08-17 Thread 龚立艳
Hi All, According to the comments, we have updated the draft to clarify these two solutions. SolutionA, The maximum link metric, which is backward compatible but may not work in OSPF, since the links with maximum link metric are not always treated as unreachable by OSPF routers. Besides,