Re: [Idr] IPR Call and WG Adoption for draft-qin-idr-sr-policy-ifit-04.txt (11/1/2020 to 11/16/2020)

Huzhibo <huzhibo@huawei.com> Tue, 03 November 2020 07:10 UTC

Return-Path: <huzhibo@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 101373A14FF for <idr@ietfa.amsl.com>; Mon, 2 Nov 2020 23:10:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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 iunj2RpBWvvN for <idr@ietfa.amsl.com>; Mon, 2 Nov 2020 23:10:18 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 152703A0F35 for <idr@ietf.org>; Mon, 2 Nov 2020 23:10:18 -0800 (PST)
Received: from lhreml740-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id BB4EAB80E75B2F21A91C for <idr@ietf.org>; Tue, 3 Nov 2020 07:10:16 +0000 (GMT)
Received: from dggema718-chm.china.huawei.com (10.3.20.82) by lhreml740-chm.china.huawei.com (10.201.108.190) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1913.5; Tue, 3 Nov 2020 07:10:16 +0000
Received: from dggema769-chm.china.huawei.com (10.1.198.211) by dggema718-chm.china.huawei.com (10.3.20.82) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Tue, 3 Nov 2020 15:10:14 +0800
Received: from dggema769-chm.china.huawei.com ([10.9.128.71]) by dggema769-chm.china.huawei.com ([10.9.128.71]) with mapi id 15.01.1913.007; Tue, 3 Nov 2020 15:10:13 +0800
From: Huzhibo <huzhibo@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] IPR Call and WG Adoption for draft-qin-idr-sr-policy-ifit-04.txt (11/1/2020 to 11/16/2020)
Thread-Index: Adaw2PtgBctpKEXkRb++HOEf6MFzKAA10nCA
Date: Tue, 3 Nov 2020 07:10:13 +0000
Message-ID: <cdb55cee801b45eba9317e1f2c4fafd6@huawei.com>
References: <055301d6b0dc$f84da4a0$e8e8ede0$@ndzh.com>
In-Reply-To: <055301d6b0dc$f84da4a0$e8e8ede0$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.201.204]
Content-Type: multipart/alternative; boundary="_000_cdb55cee801b45eba9317e1f2c4fafd6huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ss-JQ_vm141Qp2Qje9322vvZaNM>
Subject: Re: [Idr] IPR Call and WG Adoption for draft-qin-idr-sr-policy-ifit-04.txt (11/1/2020 to 11/16/2020)
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: Tue, 03 Nov 2020 07:10:20 -0000

Yes,support.

Regards,
Zhibo
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Monday, November 2, 2020 1:57 PM
To: idr@ietf.org
Subject: [Idr] IPR Call and WG Adoption for draft-qin-idr-sr-policy-ifit-04.txt (11/1/2020 to 11/16/2020)

This begins a 2 week WG adoption call for draft-qin-idr-sr-policy-ifit-04.txt (11/2/2020 to 11/16/2020).

The draft can be accessed at:
https://datatracker.ietf.org/doc/draft-zhu-idr-bgp-ls-path-mtu/

The authors should provide IPR statements by 11/5/2020 so the IDR WG can consider the IPR status in their
decision.

This draft adds the IFIT sub-TLV to the BGP Tunnel Encaps attribute for the SR policy tunnel type. This sub-TLV is only valid for SR Policy tunnel types.  Within the IFIT  sub-TLV value field, 5 sub-TLVs may be included (4 for IOAM and 1 for Enhanced Alternate Marking).

The IDR co-chairs thank the authors for their patience.  The WG adoption call for this draft has been delayed by the process of switching shepherds for BGP Tunnel Encaps draft.  Many BESS and IDR drafts currently refer to the BGP tunnel encapsulation drafts.

In your review of this draft, please differentiate between the following:

・         Support/rejection of In-situ Flow Telemetry (IFIT) as a IP routing technology,

・         Support/rejection of alternate marking as a IP routing technology,

・         Support/rejection of adding new sub-TLVS for SR Policy tunnel type of BGP Tunnel Encap Attribute, and

・         Specific issues with the descriptions of these features in the draft.

Cheers, Susan Hares