Re: [Idr] draft-jiang-idr-ts-flowspec-srv6-policy-07.txt - (8/17/2022 to 8/31/2022

[Zhuangshunwan <[e-mail]>]

Hi Linda,

Thanks for your review and support!

Please find the reply to your questions inline with [Shunwan].

Best Regards,
Shunwan

From: Idr [mailto:[e-mail]] On Behalf Of Linda Dunbar
Sent: Wednesday, August 31, 2022 12:56 AM
To: [e-mail]; Susan Hares <[e-mail]>
Subject: Re: [Idr] draft-jiang-idr-ts-flowspec-srv6-policy-07.txt - (8/17/2022 to 8/31/2022

I have read the draft and support the WG Adoption.

Question:
Will you add an example showing  the Flowspec filter rules for directing a flow to an SRv6 Policy?
[Shunwan]  Do you want an examples similar to that on page 5 of draft-dmc-idr-flowspec-tn-aware-mobility-02 ? If yes, we will provide an example later.

Will you consider the encoding style of https://datatracker.ietf.org/doc/draft-dmc-idr-flowspec-tn-aware-mobility/  to direct a flow to an SRv6 policy?
[Shunwan] What we understand is that you're referring to the style of Section 5 of draft-dmc-idr-flowspec-tn-aware-mobility-02. Is it right£¿
If yes, our answer is no. Basic idea of draft-jiang-idr-ts-flowspec-srv6-policy-07 is: Flowspec NLRI + Redirect IP Action + Policy Color + PrefixSID (Optional);  Using Nexthop from Redirect IP Action and Policy Color to associate with the SRv6 Policy (C, N).  This solution reuses various existing protocol components and does not require new protocol extensions. In addition, this solution is the same as the SR Policy framework in which service routes use (C, N) to associate with SR Policy.


NITS:
¡¤         Abstract section: ¡°aslo¡± -> ¡°also¡±
¡¤         ¡°information¡± -> ¡°information¡±
¡¤         Page 3: ¡°The color is a 32-bit numerical value that associates the SRv6 Policy¡± -> ¡°The color is a 32-bit numerical value that associates with  the SRv6 Policy¡±
[Shunwan] Ack, will update them in next revision.  Thank you again for your careful review!

Inserted below are the Answers to the questions of the WG adoption:

Linda Dunbar
From: Idr [mailto:[e-mail]] On Behalf Of Susan Hares
Sent: Wednesday, August 17, 2022 10:59 PM
To: [e-mail]<mailto:[e-mail]>
Subject: [Idr] draft-jiang-idr-ts-flowspec-srv6-policy-07.txt - (8/17/2022 to 8/31/2022

This begins a 2 week WG adoption call for draft-jiang-idr-ts-flowspec-srv6-policy-07.txt
https://datatracker.ietf.org/doc/draft-jiang-idr-ts-flowspec-srv6-policy/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-jiang-idr-ts-flowspec-srv6-policy%2F&data=05%7C01%7Clinda.dunbar%40futurewei.com%7Ce1ba2985b66548c9682008da8a872957%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637974610403821442%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fUXe%2F5uPNSvV9SwqBpEzJMVqiQPjR2gwdzgjqZwJ%2BeI%3D&reserved=0>

During your discussion of this draft, please consider:

1) Do you agree with extending 8955 and 8956 to carry the
action bit [C] found for IPv4 and IPv6 found
draft-ietf-idr-flowspec-redirect-ip-02.txt

Figure 1 : Local Administrator

0                   1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          Reserved           |C|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

C = 0 ¨C redirect original flow
C = 1 ¨C redirect copy of original flow

This bit augments the Redirect to IP action in RFC8955
And RFC8956.

[Linda] Yes.


2) Do you agree with this document use of this feature
in addition to  draft-ietf-idr-flowspec-path-redirect
https://datatracker.ietf.org/doc/draft-ietf-idr-flowspec-path-redirect/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-idr-flowspec-path-redirect%2F&data=05%7C01%7Clinda.dunbar%40futurewei.com%7Ce1ba2985b66548c9682008da8a872957%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637974610403977680%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ASIB1ofqKL4jOhY7ALIVDI12ceAEDAC9NWAc55WoFj8%3D&reserved=0>

[Linda] Yes

See the following thread for a discussion of this in March:
 https://mailarchive.ietf.org/arch/msg/idr/HENTMEoiMJGmcMuVz7LTYclCSdw/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fidr%2FHENTMEoiMJGmcMuVz7LTYclCSdw%2F&data=05%7C01%7Clinda.dunbar%40futurewei.com%7Ce1ba2985b66548c9682008da8a872957%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637974610403977680%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oKo4Mfh2TiwFHtUC4Wx3Ov2QuLSAjn0xunvSaFPRrfs%3D&reserved=0>

3) Will this work help deployment of SRv6 networks?

[Linda] Yes

We¡¯ll discuss this draft at the IDR interim on 8/29/2022.

Cheerily, Susan Hares