Re: [Bier] Comments on draft-venaas-bier-mtud-02
Xiejingrong <xiejingrong@huawei.com> Sat, 27 October 2018 07:53 UTC
Return-Path: <xiejingrong@huawei.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66168128D68 for <bier@ietfa.amsl.com>; Sat, 27 Oct 2018 00:53:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 UlFvG6BjgNqO for <bier@ietfa.amsl.com>; Sat, 27 Oct 2018 00:53:49 -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 3A8E312785F for <bier@ietf.org>; Sat, 27 Oct 2018 00:53:49 -0700 (PDT)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 365234885F0C7 for <bier@ietf.org>; Sat, 27 Oct 2018 08:53:44 +0100 (IST)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sat, 27 Oct 2018 08:53:45 +0100
Received: from NKGEML514-MBX.china.huawei.com ([fe80::40a8:f0d:c0f3:2ca5]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0415.000; Sat, 27 Oct 2018 15:53:31 +0800
From: Xiejingrong <xiejingrong@huawei.com>
To: "bier@ietf.org" <bier@ietf.org>
Thread-Topic: Comments on draft-venaas-bier-mtud-02
Thread-Index: AdRtwGXGNcOwoKfCRqiI/Tp3ykPNqQACaWJw
Date: Sat, 27 Oct 2018 07:53:31 +0000
Message-ID: <16253F7987E4F346823E305D08F9115A99B2849B@nkgeml514-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.217.214]
Content-Type: multipart/alternative; boundary="_000_16253F7987E4F346823E305D08F9115A99B2849Bnkgeml514mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/PMYmNRBf2mkX3MzVMtj_Ji3dFZI>
Subject: Re: [Bier] Comments on draft-venaas-bier-mtud-02
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Oct 2018 07:53:51 -0000
s/RFC8279/RFC8296 From: Xiejingrong Sent: Saturday, October 27, 2018 2:53 PM To: bier@ietf.org Subject: Comments on draft-venaas-bier-mtud-02 Hi, I read out the 3 building blocks in this draft, and I think they are helpful for BIER deployment. 1. A bottom value configured or defaut to make the MTU at least no worse than static configured. 2. A simple/big-grain discovery of per-subdomain MTU by simple per-subdomain TLV for BIER specific usage. 3. A Warning of mis-configuration for administrators to avoid silent error. Some comments are: 1. I think one of the real usage of this mechanism are useful for BFIR (to leverage the possible bigger MTU discovered). To quote of the 'requirement' defined in RFC8279 as a use-case may be useful. Each BFIR is expected to know the Maximum Transmission Unit (MTU) of the BIER domain. This may be known by provisioning, or by some other method outside the scope of this document. 2. I think the document is not mean to leverage the bigger MTU (than the default for example) outside of the BIER-domain. For example, to notice the user-side link to use bigger packets. There are some words in abstract. And again similar to above, list of the un-intended use-case (that is esay to be confused) may be helpful too.
- [Bier] Comments on draft-venaas-bier-mtud-02 Xiejingrong
- Re: [Bier] Comments on draft-venaas-bier-mtud-02 Xiejingrong