[Idr] 回复: WG adoption call - draft-li-idr-flowspec-srv6-05,txt

zhuyq8@chinatelecom.cn Mon, 26 July 2021 00:18 UTC

Return-Path: <zhuyq8@chinatelecom.cn>
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 854C13A1030 for <idr@ietfa.amsl.com>; Sun, 25 Jul 2021 17:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZxnwgaj4O1m for <idr@ietfa.amsl.com>; Sun, 25 Jul 2021 17:18:00 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.220]) by ietfa.amsl.com (Postfix) with ESMTP id EA1AA3A1028 for <idr@ietf.org>; Sun, 25 Jul 2021 17:17:59 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.48:43408.1537662877
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-120.88.10.46 (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id 0B3EB280088; Mon, 26 Jul 2021 08:17:56 +0800 (CST)
X-189-SAVE-TO-SEND: 44031110@chinatelecom.cn
Received: from ([172.18.0.48]) by app0024 with ESMTP id 221c150478324a4e83c86912e693b02c for idr@ietf.org; Mon Jul 26 08:17:56 2021
X-Transaction-ID: 221c150478324a4e83c86912e693b02c
X-filter-score:
X-Real-From: zhuyq8@chinatelecom.cn
X-Receive-IP: 172.18.0.48
X-MEDUSA-Status: 0
Sender: zhuyq8@chinatelecom.cn
From: <zhuyq8@chinatelecom.cn>
To: <idr@ietf.org>
Cc: "'Susan Hares'" <shares@ndzh.com>
References: <022201d77fe3$eb9ba9b0$c2d2fd10$@ndzh.com>, <BY3PR13MB5044F3B20B8109A08ACC6951F2E69@BY3PR13MB5044.namprd13.prod.outlook.com>, <BY3PR13MB5044F30052DAA67E76167B05F2E69@BY3PR13MB5044.namprd13.prod.outlook.com> <7544e0dc94404a14bb0c8061a63b5ca9>
In-Reply-To: <7544e0dc94404a14bb0c8061a63b5ca9>
Date: Mon, 26 Jul 2021 08:17:52 +0800
Message-ID: <00b801d781b3$addf2350$099d69f0$@chinatelecom.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B9_01D781F6.BC0633E0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHSMA+SzG3WNAYeCjdPMBqg8QJxWwG7XqGlAooZyIkBqFoN8qsvlo8g
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/yodgKMdn2kVYElGgY9B5JtqJRSY>
Subject: [Idr] =?gb2312?b?u9i4tDogV0cgYWRvcHRpb24gY2FsbCAgLSAgIGRyYWZ0?= =?gb2312?b?LWxpLWlkci1mbG93c3BlYy1zcnY2LTA1LHR4dA==?=
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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, 26 Jul 2021 00:18:05 -0000

We have deployed BGP-FS and SRv6 in our backbone network. It’s very useful
to extend BGP Flow Specification for SRv6 packets filtering.

I support this draft as a co-author. 

B.R.

Yongqing Zhu

From: Susan Hares <shares@ndzh.com <mailto:shares@ndzh.com> >
Sent: Friday, July 23, 2021 12:57 PM
To: idr@ietf.org <mailto:idr@ietf.org>  <idr@ietf.org <mailto:idr@ietf.org>
>; draft-li-idr-flowspec-srv6@ietf.org
<mailto:draft-li-idr-flowspec-srv6@ietf.org>
<draft-li-idr-flowspec-srv6@ietf.org
<mailto:draft-li-idr-flowspec-srv6@ietf.org> >
Subject: WG adoption call - draft-li-idr-flowspec-srv6-05,txt 

 

This begins a 2 week WG adoption call for draft-li-idr-flowspec-srv6-05.txt.

 

I am missing 3 IPR statements (Zhenbin Li , Lei Li , and Lei Liu).  

These authors should send in their IPR statements in response to this call. 

 

This draft is targeted for the V2 version of flow specification.  

Flow specification v2 draft will be discussed at an interim on 9/13/2021. 

 

If it is adopted, it will be developed as part of the v2 set of drafts. 

 

Please consider if: 

 

1) if this draft is useful for networks, 

2) if you wish to adopt this draft prior to adopting flow specification v2. 

 

Cheerily, Susan Hares