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

Zhuangshunwan <zhuangshunwan@huawei.com> Mon, 06 March 2023 09:07 UTC

Return-Path: <zhuangshunwan@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F378C151710 for <idr@ietfa.amsl.com>; Mon, 6 Mar 2023 01:07:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.196
X-Spam-Level:
X-Spam-Status: No, score=-4.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jab5U4tpPUvR for <idr@ietfa.amsl.com>; Mon, 6 Mar 2023 01:07:44 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17CCBC1516E3 for <idr@ietf.org>; Mon, 6 Mar 2023 01:07:44 -0800 (PST)
Received: from lhrpeml100002.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4PVXlT1crmz6J6fq for <idr@ietf.org>; Mon, 6 Mar 2023 17:07:17 +0800 (CST)
Received: from kwepemi500004.china.huawei.com (7.221.188.17) by lhrpeml100002.china.huawei.com (7.191.160.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Mon, 6 Mar 2023 09:07:41 +0000
Received: from kwepemi500002.china.huawei.com (7.221.188.171) by kwepemi500004.china.huawei.com (7.221.188.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Mon, 6 Mar 2023 17:07:39 +0800
Received: from kwepemi500002.china.huawei.com ([7.221.188.171]) by kwepemi500002.china.huawei.com ([7.221.188.171]) with mapi id 15.01.2507.021; Mon, 6 Mar 2023 17:07:39 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: Nat Kao <pyxislx@gmail.com>, Susan Hares <shares@ndzh.com>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] draft-jiang-idr-ts-flowspec-srv6-policy-07.txt - (8/17/2022 to 8/31/2022
Thread-Index: AdiySb9LAa1ZOpItTciSP4+WVLsPJAKhwFsAJM3pvfA=
Date: Mon, 06 Mar 2023 09:07:39 +0000
Message-ID: <f6a8ad9c5b5d425fb0fd4b89c19d1d51@huawei.com>
References: <BYAPR08MB487272B6440945C76FACC0D8B36A9@BYAPR08MB4872.namprd08.prod.outlook.com> <CAKEJeo4kkR+g3jht0xPewoit+2fUJ2n=iup-BybpEGStRs5qWA@mail.gmail.com>
In-Reply-To: <CAKEJeo4kkR+g3jht0xPewoit+2fUJ2n=iup-BybpEGStRs5qWA@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.202.95]
Content-Type: multipart/alternative; boundary="_000_f6a8ad9c5b5d425fb0fd4b89c19d1d51huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/uRUbR_LSvd8Z41LdWZChLZvyyW0>
Subject: Re: [Idr] draft-jiang-idr-ts-flowspec-srv6-policy-07.txt - (8/17/2022 to 8/31/2022
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Mar 2023 09:07:45 -0000

Hi Nat and All,



As promised, we have added SR-MPLS use case in draft-ietf-idr-ts-flowspec-srv6-policy.



Special thanks to Nat Kao for suggesting adding SR-MPLS use cases to this document.



The IETF datatracker status page for this Internet-Draft is:

https://datatracker.ietf.org/doc/draft-ietf-idr-ts-flowspec-srv6-policy/



There is also an htmlized version available at:

https://datatracker.ietf.org/doc/html/draft-ietf-idr-ts-flowspec-srv6-policy-02



A diff from the previous version is available at:

https://author-tools.ietf.org/iddiff?url2=draft-ietf-idr-ts-flowspec-srv6-policy-02


Any comments and suggestions are welcome!



Best Regards,

Shunwan


From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Nat Kao
Sent: Wednesday, August 31, 2022 4:30 PM
To: Susan Hares <shares@ndzh.com>
Cc: idr@ietf.org
Subject: Re: [Idr] draft-jiang-idr-ts-flowspec-srv6-policy-07.txt - (8/17/2022 to 8/31/2022

Hi, Susan & WG.

As an operator, I support WG adoption of this draft.
This approach is very useful for on-demand traffic steering with specific/dynamic traffic patterns.

My answers are inline:

On Wed, Aug 17, 2022 at 10:59 PM Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> wrote:
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 – 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/

See the following thread for a discussion of this in March:
 https://mailarchive.ietf.org/arch/msg/idr/HENTMEoiMJGmcMuVz7LTYclCSdw/

Yes, this approach provides a unified way for steering traffic into SR-policies using either SR-MPLS or SRv6 SID-lists.

Note: As discussed before, the same mechanism can also be applied to policies with SR-MPLS SID-lists.
https://mailarchive.ietf.org/arch/msg/idr/q0If1M-UgoeeM16HR-TXCSWRTAQ/


3) Will this work help deployment of SRv6 networks?

Yes.


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

Cheerily, Susan Hares

_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr

Regards,
Nat