[Idr] 答复: 答复: WG Adoption - draft-li-idr-sr-policy-path-mtu-03.txt - 2 Week WG adoption call (3/30 - 4/13)

Haoweiguo <haoweiguo@huawei.com> Tue, 31 March 2020 08:12 UTC

Return-Path: <haoweiguo@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 315333A1D91 for <idr@ietfa.amsl.com>; Tue, 31 Mar 2020 01:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[HTML_MESSAGE=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 YOnZJod0A14t for <idr@ietfa.amsl.com>; Tue, 31 Mar 2020 01:12:32 -0700 (PDT)
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 D2F7D3A1D9E for <idr@ietf.org>; Tue, 31 Mar 2020 01:12:21 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 1E5FAF124B05F3163FCC for <idr@ietf.org>; Tue, 31 Mar 2020 09:12:19 +0100 (IST)
Received: from nkgeml704-chm.china.huawei.com (10.98.57.158) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.487.0; Tue, 31 Mar 2020 09:12:19 +0100
Received: from nkgeml706-chm.china.huawei.com (10.98.57.153) by nkgeml704-chm.china.huawei.com (10.98.57.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Tue, 31 Mar 2020 16:12:16 +0800
Received: from nkgeml706-chm.china.huawei.com ([10.98.57.153]) by nkgeml706-chm.china.huawei.com ([10.98.57.153]) with mapi id 15.01.1713.004; Tue, 31 Mar 2020 16:12:16 +0800
From: Haoweiguo <haoweiguo@huawei.com>
To: Lizhenbin <lizhenbin@huawei.com>, Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: =?utf-8?B?W0lkcl0g562U5aSNOiAgV0cgQWRvcHRpb24gLSBkcmFmdC1saS1pZHItc3It?= =?utf-8?B?cG9saWN5LXBhdGgtbXR1LTAzLnR4dCAtIDIgV2VlayBXRyBhZG9wdGlvbiBj?= =?utf-8?Q?all_(3/30_-_4/13)?=
Thread-Index: AQHWBy5d8JMZ0Q/8xkWfu4q6vd2kWqhiWZlg
Date: Tue, 31 Mar 2020 08:12:15 +0000
Message-ID: <8ade8339488f4e808829cf304d67f8b4@huawei.com>
References: <01a201d6068f$c1f3aaf0$45db00d0$@ndzh.com> <2020033112223451917676@chinatelecom.cn> <5A5B4DE12C0DAC44AF501CD9A2B01A8D936D25E4@dggemm512-mbx.china.huawei.com>
In-Reply-To: <5A5B4DE12C0DAC44AF501CD9A2B01A8D936D25E4@dggemm512-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.30.193]
Content-Type: multipart/alternative; boundary="_000_8ade8339488f4e808829cf304d67f8b4huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/LlFSzkZEMpCwoXxOn0mDGcvcwhU>
Subject: [Idr] =?utf-8?b?562U5aSNOiAg562U5aSNOiAgV0cgQWRvcHRpb24gLSBkcmFm?= =?utf-8?q?t-li-idr-sr-policy-path-mtu-03=2Etxt_-_2_Week_WG_adoption_call_?= =?utf-8?q?=283/30_-_4/13=29?=
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, 31 Mar 2020 08:12:34 -0000

Hi,
The MTU is an important and sometimes essential attribute for a SR Policy definition, I support the draft adoption for the very useful extension.

Thanks,
weiguo


发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Lizhenbin
发送时间: 31 uNdasa 2020 03:30 PM
收件人: Susan Hares <shares@ndzh.com>om>; idr@ietf.org
主题: [Idr] 答复: WG Adoption - draft-li-idr-sr-policy-path-mtu-03.txt - 2 Week WG adoption call (3/30 - 4/13)

Hi WG,
I support the adoption. It is a useful case and after several rounds of refining the draft is ready for WG adoption.

Best Regards,
Zhenbin (Robin)



From: Susan Hares<mailto:shares@ndzh.com>
Date: 2020-03-30 20:35
To: 'IDR List'<mailto:idr@ietf.org>
Subject: [Idr] WG Adoption - draft-li-idr-sr-policy-path-mtu-03.txt - 2 Week WG adoption call (3/30 - 4/13)
This begins a 2 week WG adoption call for draft-li-idr-sr-policy-path-mtu-03.txt

You can view this draft at:
https://datatracker.ietf.org/doc/draft-li-idr-sr-policy-path-mtu/

This draft distributes path maximum transmission unit for the
SR policy via BGP.

Any discussion regarding on whether one desires
SR Policy should be clearly distinguished from the
Technical discussions on the mechanisms to pass SR policy MTU.

The questions for the people to discuss on this draft are:

1) Is there a need for this mechanism in networks using
        MPLS-SR or SR-V6 and SR policy?

2) Are there any error handling issues besides what is being
     Taken care of in RFC7752bis-03.txt

3) Do you think this draft is ready to be adopted?
     In this category, please list any concerns you have
     regarding adoption.  This category can include
     general concerns about BGP-LS, MPLS-SR,
    SR-V6, and SR-Policy.

Cheers, Sue Hares