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

Zhuangshunwan <zhuangshunwan@huawei.com> Sun, 09 October 2022 07:54 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 69B95C14F6E5 for <idr@ietfa.amsl.com>; Sun, 9 Oct 2022 00:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 WKCSa8mAHo36 for <idr@ietfa.amsl.com>; Sun, 9 Oct 2022 00:54:56 -0700 (PDT)
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 9D3B8C14F693 for <idr@ietf.org>; Sun, 9 Oct 2022 00:54:55 -0700 (PDT)
Received: from fraeml741-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4MlZ7X539Nz6801v for <idr@ietf.org>; Sun, 9 Oct 2022 15:54:16 +0800 (CST)
Received: from kwepemi100002.china.huawei.com (7.221.188.188) by fraeml741-chm.china.huawei.com (10.206.15.222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Sun, 9 Oct 2022 09:54:51 +0200
Received: from kwepemi500002.china.huawei.com (7.221.188.171) by kwepemi100002.china.huawei.com (7.221.188.188) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Sun, 9 Oct 2022 15:54:49 +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.2375.031; Sun, 9 Oct 2022 15:54:49 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: Susan Hares <shares@ndzh.com>, "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+WVLsPJAKyg+QAAAmo/wABOmPL4ANHyAiAAWQiV5ABt5h8kA==
Date: Sun, 09 Oct 2022 07:54:49 +0000
Message-ID: <f2de9288f897477cb0567aea5a48b91d@huawei.com>
References: <BYAPR08MB487272B6440945C76FACC0D8B36A9@BYAPR08MB4872.namprd08.prod.outlook.com> <CAKEJeo4kkR+g3jht0xPewoit+2fUJ2n=iup-BybpEGStRs5qWA@mail.gmail.com> <dab72d72097842f2b4785fb9b90ae607@huawei.com> <BN7PR08MB48687474B33C55CC305837A1B37E9@BN7PR08MB4868.namprd08.prod.outlook.com> <5344e8f77dbf4a60b72934279ee8c57c@huawei.com> <BYAPR08MB4872121D7C21BBC408F4B2EDB3569@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB4872121D7C21BBC408F4B2EDB3569@BYAPR08MB4872.namprd08.prod.outlook.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_f2de9288f897477cb0567aea5a48b91dhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/n9WxT6fSW8hXcTuMvpGeNzgn75s>
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: Sun, 09 Oct 2022 07:54:58 -0000

Hi Sue,

Thanks for your kind reminder, the draft-ietf-idr-ts-flowspec-srv6-policy has been submitted:

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

To be updated in the next version:
Thanks to Nat Kao for the following comments, we will add SR-MPLS use-cases:
# Nat:
# 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/

#

Best Regards,
Shunwan

From: Susan Hares [mailto:shares@ndzh.com]
Sent: Friday, September 30, 2022 9:51 PM
To: Zhuangshunwan <zhuangshunwan@huawei.com>; idr@ietf.org
Subject: RE: [Idr] draft-jiang-idr-ts-flowspec-srv6-policy-07.txt - (8/17/2022 to 8/31/2022

Shunwan:

This draft has been adopted.  Please submit the draft-ietf-idr-ts-flowspec-srv6-policy-00.txt.

Cheerily, Sue

From: Zhuangshunwan <zhuangshunwan@huawei.com<mailto:zhuangshunwan@huawei.com>>
Sent: Friday, September 23, 2022 7:54 AM
To: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>; idr@ietf.org<mailto:idr@ietf.org>
Subject: RE: [Idr] draft-jiang-idr-ts-flowspec-srv6-policy-07.txt - (8/17/2022 to 8/31/2022


Hi Sue,

draft-jiang-idr-ts-flowspec-srv6-policy-07.txt will expire on September 24, 2022.
Should we update it to the version 08 now, or should we wait until the call adoption results are announced and then update the draft?

Best Regards,
Shunwan
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Wednesday, September 7, 2022 3:09 AM
To: idr@ietf.org<mailto:idr@ietf.org>
Subject: Re: [Idr] draft-jiang-idr-ts-flowspec-srv6-policy-07.txt - (8/17/2022 to 8/31/2022

This Adoption call for draft-jian-idr-ts-flowspec-srv6-policy-07.txt is closed.
The IDR chairs will announced the results on 9/10/2022.

Cheerily, Sue

From: Zhuangshunwan <zhuangshunwan@huawei.com<mailto:zhuangshunwan@huawei.com>>
Sent: Wednesday, August 31, 2022 9:06 AM
To: Nat Kao <pyxislx@gmail.com<mailto:pyxislx@gmail.com>>; Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Cc: idr@ietf.org<mailto:idr@ietf.org>
Subject: RE: [Idr] draft-jiang-idr-ts-flowspec-srv6-policy-07.txt - (8/17/2022 to 8/31/2022


Hi Nat,

Thanks for your support and suggestion!

Regarding the suggestion of “the same mechanism can also be applied to policies with SR-MPLS SID-lists.”, the corresponding use cases will certainly be added in future version.

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<mailto:shares@ndzh.com>>
Cc: idr@ietf.org<mailto: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