Re: [Idr] WG adoption call - draft-li-idr-flowspec-srv6-05, txt - Extended to 8/27/2021 -

Hi Sue,

I support adoption for SRv6 SID under the Flowspec V2. Some comments -

- Expand SRv6, SID, on first use
- Use the updated Requirements Language as per RFC 8174
- s/using a new type of Segment Routing Header (SRH)/using a new type of
IPv6 extension header called Segment Routing Header (SRH)/
- :: in "LOC:FUNCT:ARGS::" is incorrect as per RFC8986 (and the RFC uses
ARG instead of ARGS)
- This text -- "These match capabilities of the features are only permitted
to match when there is an accompanying SRH." conflicts with RFC 8754 [
https://datatracker.ietf.org/doc/html/rfc8754#section-4.1] which allows
SRv6 SID in the DA without SRH.
- Section 5, there is no "Flow Spec IPv6 Component Types", RFC8956 asks to
use the existing "Flow Spec Component Types" registry with IPv4 Name and
IPv6 Name. Also, avoid suggesting the value 15 (best to ask for early
allocation post-adoption).

Thanks!
Dhruv

On Thu, Aug 19, 2021 at 7:04 PM Susan Hares <shares@ndzh.com> wrote:

> The WG Adoption call for draft-li-idr-flowspec-srv6 is extended to
> 8/27/2021.
>
>
>
> The draft has been revised to indicate a dependence on flow specification
> v2 encoding.   Does this provide enough linkage?
>
>
>
> Cheers, Susan Hares
>
>
>
> *From:* Susan Hares [mailto:shares@ndzh.com]
> *Sent:* Friday, July 23, 2021 12:58 PM
> *To:* idr@ietf.org; draft-li-idr-flowspec-srv6@ietf.org
> *Subject:* WG adoption call - draft-li-idr-flowspec-srv6-05,txt
>
>
>
> This begins a 2 week WG adoption call for
> draft-li-idr-flowspec-srv6-05.txt.
>
>
>
> I am missing 3 IPR statements (Zhenbin Li , Lei Li , and Lei Liu).
>
> These authors should send in their IPR statements in response to this
> call.
>
>
>
> This draft is targeted for the V2 version of flow specification.
>
> Flow specification v2 draft will be discussed at an interim on 9/13/2021.
>
>
>
> If it is adopted, it will be developed as part of the v2 set of drafts.
>
>
>
> Please consider if:
>
>
>
> 1) if this draft is useful for networks,
>
> 2) if you wish to adopt this draft prior to adopting flow specification
> v2.
>
>
>
> Cheerily, Susan Hares
>
>
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>