Re: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label

Shane Amante <shane@castlepoint.net> Tue, 27 July 2010 16:22 UTC

Return-Path: <shane@castlepoint.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A43F93A6A40 for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 09:22:05 -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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3SVsx9BKO9Lz for <mpls@core3.amsl.com>; Tue, 27 Jul 2010 09:22:04 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id EB7A73A6880 for <mpls@ietf.org>; Tue, 27 Jul 2010 09:22:03 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 239A036817C; Tue, 27 Jul 2010 10:22:26 -0600 (MDT)
Received: from host2.tcb.net (64.78.235.218 [64.78.235.218]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Tue, 27 Jul 2010 10:22:24 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.235.218; client-port=58566; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/alternative; boundary="Apple-Mail-25--854653069"
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <03ba01cb2d9d$518de440$c7728182@china.huawei.com>
Date: Tue, 27 Jul 2010 18:22:21 +0200
Message-Id: <854FD998-DD00-48F1-9682-589EBE89F27A@castlepoint.net>
References: <02ac01cb2d87$a1c83ac0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED6E7@EMBX01-HQ.jnpr.net> <034201cb2d8f$25cd0ec0$c7728182@china.huawei.com> <5E893DB832F57341992548CDBB3331639844EED714@EMBX01-HQ.jnpr.net> <03ba01cb2d9d$518de440$c7728182@china.huawei.com>
To: Yong Lucy <lucyyong@huawei.com>
X-Mailer: Apple Mail (2.1081)
Cc: mpls@ietf.org
Subject: Re: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 27 Jul 2010 16:22:05 -0000

Lucy,

On Jul 27, 2010, at 17:06 GMT+02:00, Yong Lucy wrote:
> Hi John,
> I don’t get it. If egress LSR asks ingress LSR to place ELI on the stack, the ingress can insert a unique ELI label on the stack followed by entropy label. When packet arrives to egress LSR, the LSR will find ELI on the stack. Why is it important for egress LSP to allocate a value for ELI instead of using standardized value?

I think John already answered this question, but I'll give it a try, as well.  It's really a design choice on the part of the co-authors, in an attempt to avoid asking the MPLS WG to allocate a reserved label from the very scarce reserved label space.  I would note that there are only 8 reserved MPLS label values that are currently unassigned:
http://www.iana.org/assignments/mpls-label-values/mpls-label-values.xhtml

So, if we believe it's "sound engineering" to use an ELI instead of a reserved label -- certainly a judgement call -- then, I believe, we should NOT request a reserved label in order that future applications that have a legitimate use (or, said differently, may not be able to function properly without a reserved label value) have an ability to acquire one.

-shane



> Regards,
> Lucy
>  
> From: John E Drake [mailto:jdrake@juniper.net] 
> Sent: Tuesday, July 27, 2010 8:31 AM
> To: Yong Lucy; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
> Subject: RE: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
>  
> Lucy,
>  
> Yes it does.  That is the whole point.  That is how the egress knows whether the ingress has placed an entropy label in the stack.  (That is why we termed it the ‘Entropy Label Indicator’.)
>  
> Thanks,
>  
> John
>  
> From: Yong Lucy [mailto:lucyyong@huawei.com] 
> Sent: Tuesday, July 27, 2010 6:25 AM
> To: John E Drake; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
> Subject: RE: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
>  
> What is the benefit for such control? Egress LSR does not use this value.
> Lucy
>  
> From: John E Drake [mailto:jdrake@juniper.net] 
> Sent: Tuesday, July 27, 2010 8:10 AM
> To: Yong Lucy; Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
> Subject: RE: [mpls] entropy label indicator label indraft-kompella-mpls-entropy-label
>  
> Lucy, we discussed this and decided it was better to have the egress control the values of the ELI it advertises.  Plus, getting a reserved value would be difficult
>  
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Yong Lucy
> Sent: Tuesday, July 27, 2010 5:31 AM
> To: Kireeti Kompella; 'Shane Amante'; mpls@ietf.org
> Subject: [mpls] entropy label indicator label in draft-kompella-mpls-entropy-label
>  
> Hi Kireeti and Shane,
>  
> Could we consider use one of reserved label for ELI purpose? This will make implementation much easy, i.e. not need to keep the state for each ELI label. The approach can be used in general for RSVP-TE and BGP as well.
>  
> Regards,
> Lucy
>  
>  
>