[mpls] FW: MPLS-RT review of draft-kompella-mpls-rmr
"Dongjie (Jimmy)" <jie.dong@huawei.com> Wed, 15 July 2015 03:03 UTC
Return-Path: <jie.dong@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 C7C3C1B3108 for <mpls@ietfa.amsl.com>; Tue, 14 Jul 2015 20:03:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 uVhRhtOzImVx for <mpls@ietfa.amsl.com>; Tue, 14 Jul 2015 20:03:40 -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 A7A731B3110 for <mpls@ietf.org>; Tue, 14 Jul 2015 20:03:39 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BYU03866; Wed, 15 Jul 2015 03:03:38 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 15 Jul 2015 04:03:37 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.69]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Wed, 15 Jul 2015 11:03:34 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: MPLS-RT review of draft-kompella-mpls-rmr
Thread-Index: AQHQrpdOD3Qhj21+LUqS6fmvZXsG453aVg3wgAGh3CA=
Date: Wed, 15 Jul 2015 03:03:33 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C9277429D12E@nkgeml512-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.111.97.131]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/4_dBk0-9pxRlx49Dgk4KshjgW24>
Subject: [mpls] FW: MPLS-RT review of draft-kompella-mpls-rmr
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: Wed, 15 Jul 2015 03:03:41 -0000
Forwarding to the MPLS list. > -----Original Message----- > From: Dongjie (Jimmy) > Sent: Tuesday, July 14, 2015 10:30 AM > To: 'Loa Andersson'; stbryant@cisco.com; Sam Aldrin; Eric Gray; > draft-kompella-mpls-rmr@tools.ietf.org; mpls-chairs@tools.ietf.org > Subject: RE: MPLS-RT review of draft-kompella-mpls-rmr > > Hi, > > I’ve been selected to review draft-kompella-mpls-rmr-01 before the WG > adoption call. > > The document is coherent, well written and proposes general solution for > auto-discovery and signaling of MPLS rings. > > Below are my comments to the draft which are non-blocking to WG adoption > call: > > 1.1 Definitions > > In the definition of Ring ID, it says "An RID of 0 means the node is a > "promiscuous" node. Maybe some description of the relationship between the > node and Ring ID could be added here, such as "Every node on a ring is > configured with one or more RIDs". > > 3.2 Ring Links and Directions > > In 1st paragraph, it says "signaling messages and labels across one component > link apply to all components", and multiple lambdas or fibers are given as > example of parallel links. Does this ring lsp mechanism also applies to lambda or > fiber switching LSPs? If so, maybe it is better to make this explicit in the > introduction. > > 3.7 Protection > > The indication which propagates on the ring, does it carry some information of > the failure location? Since when some failure occurs, the switchover of ring > LSPs depends on the failure location, some LSPs may switch from CW to AC, > while for some others switchover is not needed. > > 4. Autodiscovery > > Will the protocol extensions to IGP be part of this document, or as said in the > abstract, "will be described in companion documents"? My personal feeling is > the general mechanism could be specified in this document, while the detailed > IGP extensions are more suitable for an IGP document. > > 4.3 Mastership Phase > > It says the master is determined by "the lowest loopback address of all nodes > with the highest mastership values", if the mastership value of all nodes needs > to be compared, does the mastership value also need to be carried in the IGP > Ring TLVs? > > Section 4.5 Ring Changes and Section 5 Ring Signaling, some text needs to be > added in these two sections. > > Besides, it is better that this document or the companion documents summarize > the changes introduced to the IGP protocols, for example, the timer based > multi-phase information advertisement. > > Best regards, > Jie > > > -----Original Message----- > > From: Loa Andersson [mailto:loa@pi.nu] > > Sent: Thursday, June 25, 2015 12:03 AM > > To: stbryant@cisco.com; Dongjie (Jimmy); Sam Aldrin; Eric Gray; > > draft-kompella-mpls-rmr@tools.ietf.org; mpls-chairs@tools.ietf.org > > Subject: MPLS-RT review of draft-kompella-mpls-rmr > > > > Stewart, Jie, Sam and Eric; > > > > You have be selected as MPLS-RT reviewers for draft-kompella-mpls-rmr-01. > > > > Note to authors: You have been CC'd on this email so that you can know > > that this review is going on. However, please do not review your own > document. > > > > Reviews should comment on whether the document is coherent, is it > > useful (ie, is it likely to be actually useful in operational > > networks), and is the document technically sound? > > > > We are interested in knowing whether the document is ready to be > > considered for WG adoption (ie, it doesn't have to be perfect at this > > point, but should be a good start). > > > > Reviews should be sent to the document authors, WG co-chairs and WG > > secretary, and CC'd to the MPLS WG email list. If necessary, comments > > may be sent privately to only the WG chairs. > > > > If you have technical comments you should try to be explicit about > > what needs to be resolved before adopting it as a working group > > document, and what can wait until the document is a working group > > document and the working group has the revision control. > > > > Are you able to review this draft by July 9, 2015? Please respond in a > > timely fashion. > > > > Thanks, Loa > > (as MPLS WG chair) > > -- > > > > > > Loa Andersson email: loa@mail01.huawei.com > > Senior MPLS Expert loa@pi.nu > > Huawei Technologies (consultant) phone: +46 739 81 21 64
- [mpls] Fwd: Re: MPLS-RT review of draft-kompella-… Stewart Bryant
- [mpls] FW: MPLS-RT review of draft-kompella-mpls-… Dongjie (Jimmy)