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

[linchangwang <[e-mail]>]

Hi Sue and WG,





I support the adoption of this draft.

This document provides a very simple way to direct IP traffic to SRv6 policies, it follows the SRv6 policy standard exactly.

It will be very helpful for SRv6 networks.



My replies to the questions as below:



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 - redirect original flow

C = 1 - redirect copy of original flow

This bit augments the Redirect to IP action in RFC8955

And RFC8956.





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/



Yes





3) Will this work help deployment of SRv6 networks?



Yes, this draft will be very helpful for SRv6 networks.





Best regards,



Changwang lin



From: Idr <[e-mail]><mailto:&lt;[e-mail]&gt;> 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/



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.



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/



See the following thread for a discussion of this in March:

 https://mailarchive.ietf.org/arch/msg/idr/HENTMEoiMJGmcMuVz7LTYclCSdw/



3) Will this work help deployment of SRv6 networks?



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



Cheerily, Susan Hares

-------------------------------------------------------------------------------------------------------------------------------------
???????????????????,?????????????
?????????????????????(??????????????????
???)?????????????????,??????????????????
??!
This e-mail and its attachments contain confidential information from New H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!