Re: [mpls] [Need clarification] LDP Multi-Topology Extensions RFC 7307
Quintin zhao <quintin.zhao@huawei.com> Fri, 28 August 2015 16:48 UTC
Return-Path: <quintin.zhao@huawei.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E899B1A1A06; Fri, 28 Aug 2015 09:48:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 OYuLrxZGPAVe; Fri, 28 Aug 2015 09:48:14 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A93A1A0056; Fri, 28 Aug 2015 09:48:06 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BWW44128; Fri, 28 Aug 2015 16:48:04 +0000 (GMT)
Received: from SJCEML702-CHM.china.huawei.com (10.218.25.35) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 28 Aug 2015 17:48:02 +0100
Received: from SJCEML701-CHM.china.huawei.com ([169.254.3.222]) by SJCEML702-CHM.china.huawei.com ([169.254.4.111]) with mapi id 14.03.0235.001; Fri, 28 Aug 2015 09:47:52 -0700
From: Quintin zhao <quintin.zhao@huawei.com>
To: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>, "skraza@cisco.com" <skraza@cisco.com>, "czhou@cisco.com" <czhou@cisco.com>, "lufang@microsoft.com" <lufang@microsoft.com>, "lilianyuan@chinamobile.com" <lilianyuan@chinamobile.com>, "daniel@olddog.co.uk" <daniel@olddog.co.uk>
Thread-Topic: [Need clarification] LDP Multi-Topology Extensions RFC 7307
Thread-Index: AdDhWsyBkUk3t6ieQEC++4CcKOQKAQAUjkNA
Date: Fri, 28 Aug 2015 16:47:52 +0000
Message-ID: <11208E03C9803E4CB4C3D898F153D6C0390B3C74@SJCEML701-CHM.china.huawei.com>
References: <327562D94EA7BF428CD805F338C31EF06C0473F7@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <327562D94EA7BF428CD805F338C31EF06C0473F7@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.156.10]
Content-Type: multipart/alternative; boundary="_000_11208E03C9803E4CB4C3D898F153D6C0390B3C74SJCEML701CHMchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/arYU0mote01n-dVBVU5ke3IPn8U>
Cc: "mpls@ietf.org" <mpls@ietf.org>, Fangsheng <fangsheng@huawei.com>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, Rajeshmv <rajeshmv@huawei.com>, "Wunan (Eric)" <eric.wu@huawei.com>
Subject: Re: [mpls] [Need clarification] LDP Multi-Topology Extensions RFC 7307
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Aug 2015 16:48:17 -0000
Anil, >From RFC 5036, section 3.4.3<https://tools.ietf.org/html/rfc5036#section-3.4.3> for the Address List TLV, it specifies the addresses included in the Address List TLV as below: Addresses A list of addresses from the specified Address Family. The encoding of the individual addresses depends on the Address Family. So the new addresses associated with the new address family (MT IPv4 and MT Ipv6 defined in RFC7307) can be used in the Address List TLV. I agree with you that It should be clearer if this is explained explicitly similar to FEC TLV in RFC7307. Regards, Quintin From: Anil Kumar S N (VRP Network BL) Sent: 2015年8月28日 2:29 To: Quintin zhao; skraza@cisco.com; czhou@cisco.com; lufang@microsoft.com; lilianyuan@chinamobile.com; daniel@olddog.co.uk Cc: mpls-chairs@ietf.org; mpls@ietf.org; Wunan (Eric); Lizhenbin; Rajeshmv; Dhruv Dhody; Fangsheng Subject: [Need clarification] LDP Multi-Topology Extensions RFC 7307 Hi All, I need clarification on the LDP MT behavior. LDP extension for Multi-Topology explains following : 1. New Address Families: MT IP 2. LDP FEC Elements with MT IP AF 3. LDP MT Capability Advertisement As per LDP Specification RFC 5036, Address Family filed is carried in FEC TLV and Address List TLV. Nothing about Address List TLV is mentioned in LDP Multi-Topology Extensions RFC 7307, Can we use “New Address Families: MT IP” in Address List TLV or not ? (when a interface is bound to Non-default MT) I feel this can be explained more specifically similar to FEC TLV in LDP Multi-Topology Extensions RFC 7307. Appreciate if authors or community members can help to clarify. Thanks & Regards Anil S N “Be liberal in what you accept, and conservative in what you send” - Jon Postel
- [mpls] [Need clarification] LDP Multi-Topology Ex… Anil Kumar S N (VRP Network BL)
- Re: [mpls] [Need clarification] LDP Multi-Topolog… Quintin zhao