IETF Logo Mail Archive

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

Lihao <lihao@h3c.com> Mon, 22 August 2022 03:10 UTC

Return-Path: <lihao@h3c.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 4055BC152576 for <idr@ietfa.amsl.com>; Sun, 21 Aug 2022 20:10:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 RKc7o08T1fMw for <idr@ietfa.amsl.com>; Sun, 21 Aug 2022 20:10:34 -0700 (PDT)
Received: from h3cspam02-ex.h3c.com (smtp.h3c.com [60.191.123.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95240C1522CA for <idr@ietf.org>; Sun, 21 Aug 2022 20:10:33 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 27M39Twr011603; Mon, 22 Aug 2022 11:09:29 +0800 (GMT-8) (envelope-from lihao@h3c.com)
Received: from DAG2EX12-IDC.srv.huawei-3com.com (unknown [10.8.0.76]) by mail.maildlp.com (Postfix) with ESMTP id A4427223C8E5; Mon, 22 Aug 2022 11:09:10 +0800 (CST)
Received: from DAG2EX05-BASE.srv.huawei-3com.com (10.8.0.68) by DAG2EX12-IDC.srv.huawei-3com.com (10.8.0.76) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.17; Mon, 22 Aug 2022 11:09:29 +0800
Received: from DAG2EX05-BASE.srv.huawei-3com.com ([fe80::f963:2fad:283e:6b1c]) by DAG2EX05-BASE.srv.huawei-3com.com ([fe80::f963:2fad:283e:6b1c%2]) with mapi id 15.01.2375.017; Mon, 22 Aug 2022 11:09:29 +0800
From: Lihao <lihao@h3c.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: draft-jiang-idr-ts-flowspec-srv6-policy-07.txt - (8/17/2022 to 8/31/2022
Thread-Index: AdiySb9LAa1ZOpItTciSP4+WVLsPJADh81jw
Date: Mon, 22 Aug 2022 03:09:29 +0000
Message-ID: <78dfd04455b84a76824d3b9cc1294ce7@h3c.com>
References: <BYAPR08MB487272B6440945C76FACC0D8B36A9@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB487272B6440945C76FACC0D8B36A9@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.114.76.35]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_78dfd04455b84a76824d3b9cc1294ce7h3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-MAIL: h3cspam02-ex.h3c.com 27M39Twr011603
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/oCuWk-aXOlAvdt2lH3lUBVqmChs>
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, 22 Aug 2022 03:10:37 -0000

Hi chairs & WG

I support the adoption of this draft.

As an vendor , our router has implemented this feature.

In the recent discussions with provider, we found that the flowspec can be very flexible to conduct on-demand flow streeing, which greatly reduces the deployment workload.

best wishes.



From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Wednesday, August 17, 2022 10:59 PM
To: idr@ietf.org
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 - redirect original flow
C = 1 - 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!

v2.23.0 | Report a Bug | By Email