Re: [mpls] MPLS-RT review of draft-kompella-mpls-larp

Lucy yong <> Tue, 14 July 2015 14:45 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id A111E1ACE3A for <>; Tue, 14 Jul 2015 07:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.211
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id FxMG5t-MtOSW for <>; Tue, 14 Jul 2015 07:45:16 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 91D0C1ACE0F for <>; Tue, 14 Jul 2015 07:45:15 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id BVD92609; Tue, 14 Jul 2015 14:45:14 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Tue, 14 Jul 2015 15:45:13 +0100
Received: from ([]) by dfweml704-chm ([]) with mapi id 14.03.0235.001; Tue, 14 Jul 2015 07:45:08 -0700
From: Lucy yong <>
To: "Aissaoui, Mustapha (Mustapha)" <>, Loa Andersson <>, "Kamran Raza (skraza)" <>, Sriganesh Kini <>, "" <>, "" <>
Thread-Topic: MPLS-RT review of draft-kompella-mpls-larp
Thread-Index: AQHQs1BokGTTQa71gESl0maU1nDJwZ3GMyUAgBTcKbA=
Date: Tue, 14 Jul 2015 14:45:07 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D571B807B@dfweml701-chm>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Cc: "" <>
Subject: Re: [mpls] MPLS-RT review of draft-kompella-mpls-larp
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 14 Jul 2015 14:45:18 -0000

Hi All,

I reviewed draft-kompella-mpls-larp as the member of MPLS Review Team and have the following comments:

is the document coherent?

Yes. It specifies LARP protocol to advertise label binding for IP host address, which extends MPLS to Hosts. Definitely MPLS related.

is it useful (i.e., is it likely to be actually useful in operational networks)?

Technically speaking, this protocol can be implemented. I am not a (DC) operator so not sure if the operator wants to deploy this protocol in DC or between access nodes and first hop MPLS-enabled device. The protocol may help automation at mpls edge. One question: beside label binding to host address, what other MPLS benefits will hosts gain compared to current architecture? For example, if MPLS OAM features can be extended to hosts, i.e. end-to-end?

is the document technically sound? 
Yes, LARP is used between host and MPLS network to convey label binding to IP host address. The draft provides a solution in control plane and data plane to achieve this purpose.

is the document ready to be considered for WG adoption?
Not yet.  IMO: LARP protocol should work in a practical environment where hosts and an MPLS device are connected via an intermediate bridge (IEEE.1Q). Current draft only considers the case that host directly connects to MPLS device. In addition, it is necessary to address some items listed in section 4 ahead, which helps validate the feasibility in operational environment. For examples, 1) client and service in sync; 4) if there are many servers, which one to pick? 


> -----Original Message-----
> From: Loa Andersson []
> Sent: Tuesday, June 30, 2015 12:18 PM
> To: Lucy yong; Kamran Raza (skraza); Sriganesh Kini; Aissaoui, 
> Mustapha (Mustapha);; 
> Subject: MPLS-RT review of draft-kompella-mpls-larp
> Lucy, Kamran, Sri and Mustapha;
> You have be selected as MPLS-RT reviewers for draft-kompella-mpls-larp.
> 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 14, 2015? Please respond in a timely fashion.
> Thanks, Loa
> (as MPLS WG chair)
> --
> Loa Andersson                        email:
> Senior MPLS Expert                
> Huawei Technologies (consultant)     phone: +46 739 81 21 64