Re: [Idr] Question on IETF 105 presentation on draft-zhu-idr-bgp-ls-path-mtu
Huzhibo <huzhibo@huawei.com> Tue, 06 August 2019 12:31 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 B89E612016C for <idr@ietfa.amsl.com>; Tue, 6 Aug 2019 05:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 CPK7QHCwUJhX for <idr@ietfa.amsl.com>; Tue, 6 Aug 2019 05:31:14 -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 E981B1200B5 for <idr@ietf.org>; Tue, 6 Aug 2019 05:31:13 -0700 (PDT)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 7D7303B295ED07DB3B80 for <idr@ietf.org>; Tue, 6 Aug 2019 13:31:11 +0100 (IST)
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 6 Aug 2019 13:31:10 +0100
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Tue, 6 Aug 2019 13:31:10 +0100
Received: from DGGEMM406-HUB.china.huawei.com (10.3.20.214) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Tue, 6 Aug 2019 13:31:10 +0100
Received: from DGGEMM529-MBS.china.huawei.com ([169.254.14.250]) by DGGEMM406-HUB.china.huawei.com ([10.3.20.214]) with mapi id 14.03.0439.000; Tue, 6 Aug 2019 20:31:06 +0800
From: Huzhibo <huzhibo@huawei.com>
To: Jeffrey Haas <jhaas@pfrc.org>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] Question on IETF 105 presentation on draft-zhu-idr-bgp-ls-path-mtu
Thread-Index: AQHVQ8C8MGxTAjiKzEGWBiFHdkIDXKbuBLcA
Date: Tue, 06 Aug 2019 12:31:06 +0000
Message-ID: <06CF729DA0D6854E8C1E5121AC3330DFAE8F4A76@dggemm529-mbs.china.huawei.com>
References: <20190726144625.GP28302@pfrc.org>
In-Reply-To: <20190726144625.GP28302@pfrc.org>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.219.232]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Gw9LBZ-s8D0b2lEt2vCScQh6Amg>
Subject: Re: [Idr] Question on IETF 105 presentation on draft-zhu-idr-bgp-ls-path-mtu
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, 06 Aug 2019 12:31:16 -0000
Hi Jeff:
This is my answer to the following two questions.
(For question one)The Minimum MTU of component links can be used for the LAG.And draft-ietf-isis-l2bundles-07 define to advertising L2 Bundle Member Link Attributes,It may also be extended for advertise the L2 Bundle Member Link MTU in BGP_LS if necessary。
(For question two)We extend BGP_LS for MTU to calculate the MTU of the SR Policy Path, In this draft, we carry the MTU of the link through BGP_LS, For PathMtu, I think it may be extended in draft-ietf-idr-te-lsp-distribution-11 If necessary。
ths
Zhibo
-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Jeffrey Haas
Sent: Friday, July 26, 2019 10:46 PM
To: idr@ietf.org
Subject: [Idr] Question on IETF 105 presentation on draft-zhu-idr-bgp-ls-path-mtu
Here are my two questions for clarification:
1. A common problem in networks is Link Aggregate Group (LAG) component links that have MTU mis-matches. Is there a way to use this mechanism to help detect this condition?
2. There is a draft in BFD, draft-ietf-bfd-large-packets, that provides a mechanism to test MTU. Are you aware of this draft? If so, have you considered how you might expose detected path MTU in your feature?
-- Jeff
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr