Re: [Idr] WG adoption call - draft-li-idr-flowspec-srv6-05,txt
Aijun Wang <wangaijun@tsinghua.org.cn> Sat, 07 August 2021 00:42 UTC
Return-Path: <wangaijun@tsinghua.org.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 11DD83A2145; Fri, 6 Aug 2021 17:42:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.438
X-Spam-Level: *
X-Spam-Status: No, score=1.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_SBL_CSS=3.335, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Ii2yKddgkNdU; Fri, 6 Aug 2021 17:42:03 -0700 (PDT)
Received: from mail-m17638.qiye.163.com (mail-m17638.qiye.163.com [59.111.176.38]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10FEC3A2141; Fri, 6 Aug 2021 17:42:02 -0700 (PDT)
Received: from smtpclient.apple (unknown [109.166.36.204]) by mail-m17638.qiye.163.com (Hmail) with ESMTPA id AFA391C0130; Sat, 7 Aug 2021 08:41:58 +0800 (CST)
Content-Type: multipart/alternative; boundary="Apple-Mail-56BA4584-B4FA-4716-BBCF-5C38E510C2DF"
Content-Transfer-Encoding: 7bit
From: Aijun Wang <wangaijun@tsinghua.org.cn>
Mime-Version: 1.0 (1.0)
Date: Sat, 07 Aug 2021 08:41:55 +0800
Message-Id: <26C6F1BE-2A89-43C0-8367-C23A67DCF132@tsinghua.org.cn>
References: <BY3PR13MB50443EE4693E3AEDB3B44D91F2F39@BY3PR13MB5044.namprd13.prod.outlook.com>
Cc: Aijun Wang <wangaj3@chinatelecom.cn>, draft-li-idr-flowspec-srv6@ietf.org, idr <idr@ietf.org>
In-Reply-To: <BY3PR13MB50443EE4693E3AEDB3B44D91F2F39@BY3PR13MB5044.namprd13.prod.outlook.com>
To: Huaimo Chen <huaimo.chen@futurewei.com>
X-Mailer: iPhone Mail (18F72)
X-HM-Spam-Status: e1kfGhgUHx5ZQUtXWQgPGg8OCBgUHx5ZQUlOS1dZCBgUCR5ZQVlLVUtZV1 kWDxoPAgseWUFZKDYvK1lXWShZQUpMS0tKN1dZLVlBSVdZDwkaFQgSH1lBWUJIH0NWT0pLTh1DSE pJGEMYVRMBExYaEhckFA4PWVdZFhoPEhUdFFlBWU9LSFVKSktITk9VS1kG
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6Okk6Vgw5Qj9JNSsSDTJPLCs5 FBlPCSxVSlVKTUlDSUJNQkpCT0xMVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlKS0JVSk1NVUhNVUlLT1lXWQgBWUFKS0JPTDcG
X-HM-Tid: 0a7b1e0f36c6d993kuwsafa391c0130
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/NmvDuQXb5ZXYUvkPKmoY1rbPuu4>
Subject: Re: [Idr] WG adoption call - draft-li-idr-flowspec-srv6-05,txt
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: Sat, 07 Aug 2021 00:42:09 -0000
Hi, Huaimo: Thanks for your answer. I support its adoption. Aijun Wang China Telecom > On Aug 7, 2021, at 00:49, Huaimo Chen <huaimo.chen@futurewei.com> wrote: > > > Hi Aijun, > > Thank you very much for your comments and suggestions. > My responses are inline below with [HC]. > > Is it more general to define one new “field type”, for example, “100” to represent to match “SID’s LOC:FUNC:ARGS” in component type “TBD2”, also the whole SID, then there is no necessary to define component type “TBD1”? > [HC]: You are right. A new “field type” can be defined to match “SID’s LOC:FUNC:ARGS” in component type “TBD2”. This will eliminate component type “TBD1”. We will update the draft accordingly. > > And, it’s encoding follows Flowspec b1, how can it be developed as part of v2 drafts? Should the encoding be changed to follow the v2 specification? > [HC]: It seems that BGP Flow Specification v2 is encapsulated in a different NLRI which encapsulates previous flow specification v1 information. > > Best Regards, > Huaimo > From: wangaj3@chinatelecom.cn <wangaj3@chinatelecom.cn> on behalf of Aijun Wang <wangaj3@chinatelecom.cn> > Sent: Friday, August 6, 2021 12:22 PM > To: draft-li-idr-flowspec-srv6@ietf.org <draft-li-idr-flowspec-srv6@ietf.org> > Cc: idr <idr@ietf.org> > Subject: WG adoption call - draft-li-idr-flowspec-srv6-05,txt > > Hi, Authors: > > Is it more general to define one new “field type”, for example, “100” to represent to match “SID’s LOC:FUNC:ARGS” in component type “TBD2”, also the whole SID, then there is no necessary to define component type “TBD1”? > > > > And, it’s encoding follows Flowspec b1, how can it be developed as part of v2 drafts? Should the encoding be changed to follow the v2 specification? > > Aijun Wang > China Telecom > > > > > > > From: Susan Hares <shares@ndzh.com> > > Sent: Friday, July 23, 2021 12:57 PM > > To: idr@ietf.org <idr@ietf.org>; draft-li-idr-flowspec-srv6@ietf.org <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 > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr