Re: [Lsr] WG Adoption Call for draft-li-lsr-ospfv3-srv6-extensions

For the third concern, I think it is better to list the considerations behind the format design of the TLVs to help readers understand them better. For the specification behavior you mention, this doc SHOULD specify it explicitly.
By the way, what a router should do when it receives END.X SID containing algorithm that is different from the one carried in the convering locator?

Best Regards,
Zhenqiang Li

li_zhenqiang@hotmail.com

From: Ketan Talaulikar (ketant)
Date: 2020-01-30 16:44
To: li_zhenqiang@hotmail.com; Christian Hopps; lsr
CC: draft-li-lsr-ospfv3-srv6-extensions; lsr-ads; Christian Hopps; Acee Lindem (acee)
Subject: RE: RE: [Lsr] WG Adoption Call for draft-li-lsr-ospfv3-srv6-extensions
Please check inline again.

From: li_zhenqiang@hotmail.com <li_zhenqiang@hotmail.com> 
Sent: 30 January 2020 13:46
To: Ketan Talaulikar (ketant) <ketant@cisco.com>; Christian Hopps <chopps@chopps.org>; lsr <lsr@ietf.org>
Cc: draft-li-lsr-ospfv3-srv6-extensions <draft-li-lsr-ospfv3-srv6-extensions@ietf.org>; lsr-ads <lsr-ads@ietf.org>; Christian Hopps <chopps@chopps.org>; Acee Lindem (acee) <acee@cisco.com>
Subject: Re: RE: [Lsr] WG Adoption Call for draft-li-lsr-ospfv3-srv6-extensions

Thank you KT for your quick response. Please see my reply begins with [ZQ].

Best Regards,
Zhenqiang Li

li_zhenqiang@hotmail.com

From: Ketan Talaulikar (ketant)
Date: 2020-01-30 13:42
To: li_zhenqiang@hotmail.com; Christian Hopps; lsr
CC: draft-li-lsr-ospfv3-srv6-extensions; lsr-ads; Christian Hopps; Acee Lindem (acee)
Subject: RE: [Lsr] WG Adoption Call for draft-li-lsr-ospfv3-srv6-extensions
Hello Zhenqiang Li,

Thanks for your review and comments. Please check inline below.

From: li_zhenqiang@hotmail.com <li_zhenqiang@hotmail.com> 
Sent: 30 January 2020 08:46
To: Christian Hopps <chopps@chopps.org>; lsr <lsr@ietf.org>
Cc: draft-li-lsr-ospfv3-srv6-extensions <draft-li-lsr-ospfv3-srv6-extensions@ietf.org>; lsr-ads <lsr-ads@ietf.org>; Christian Hopps <chopps@chopps.org>; Acee Lindem (acee) <acee@cisco.com>
Subject: Re: [Lsr] WG Adoption Call for draft-li-lsr-ospfv3-srv6-extensions

support the adoption with the following comments.

1. What does SRH stack mean in section 4.2? AS specified in RFC8200 and draft-ietf-6man-segment-routing-header, only one SRH can be presented in one IPv6 header.

[KT] Thanks for catching this error and will fix as below:

OLD: The Maximum End Pop MSD Type specifies the maximum number of SIDs in
   the top SRH in an SRH stack to which the router can apply Penultimate
   Segment Pop (PSP) or Ultimate Segment Pop (USP)

NEW: The Maximum End Pop MSD Type specifies the maximum number of SIDs in   the SRH for which the router can apply Penultimate   Segment Pop (PSP) or Ultimate Segment Pop (USP)

[ZQ] Fine.

2. The abbreviations used in this draft should be listed in a seperated section or point out where they are defined.
[KT] We’ve followed the convention of expanding on first use as also providing reference where necessary. Please do let know if we’ve missed doing so anywhere.

[ZQ] Some examples: SPF computation in secction 5,  TBD in section 2.
[KT] Will expand SPF and some other such on first use :-). The TBD (to be decided) is for use until the code point are allocated by IANA.

3. Algorithm field is defined for End.x SID to carry the algorithm the end.x sid associates. But no algorithm field is defined for End SID in section 7. May I know the reason?
[KT] The SRv6 Locator TLV that is the parent of the SRv6 End SID Sub-TLV carries the algorithm and hence there is no need to repeat in the Sub-TLV. This is not the case for SRv6 End.X SID Sub-TLV and hence it has the algorithm field.

[ZQ] Make sense but still a little bit weird. Since any SID belongs to a locator, or it is not routable, the algorithm field in the end.x sid is not needed, end.x sid associates the algorithm carried in the corresponding locator tlv.
[KT] Having an algorithm field advertised with the End.X SID makes it easier for implementation to find the algorithm specific End.X SID without making the longest prefix match on all locators advertised by the node to find the algorithm to which the SID belongs. It also makes it possible to verify that the algorithm associated with the End.X SID matches that of the covering Locator when the link advertisement with End.X SID is received. 

Thanks,
Ketan

Thanks,
Ketan

Best Regards,
Zhenqiang Li

li_zhenqiang@hotmail.com

From: Christian Hopps
Date: 2020-01-24 04:24
To: lsr
CC: draft-li-lsr-ospfv3-srv6-extensions; lsr-ads; Christian Hopps; Acee Lindem \(acee\)
Subject: [Lsr] WG Adoption Call for draft-li-lsr-ospfv3-srv6-extensions
Hi LSR WG and Draft Authors,

The authors originally requested adoption back @ 105; however, some comments were received and new version was produced. Moving forward...

This begins a 2 week WG adoption poll for the following draft:

  https://datatracker.ietf.org/doc/draft-li-lsr-ospfv3-srv6-extensions/
Please indicate your support or objection by Feb 6, 2020.

Authors, please respond indicating whether you are aware of any IPR that applies to this draft.

Thanks,
Chris & Acee.
_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr