Re: [mpls] [PWE3] ELI as a reserved label

Curtis Villamizar <curtis@occnc.com> Tue, 03 August 2010 00:03 UTC

Return-Path: <curtis@occnc.com>
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 64D703A69D1; Mon, 2 Aug 2010 17:03:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.421
X-Spam-Level:
X-Spam-Status: No, score=-2.421 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599]
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 UYpTlJoBGcv7; Mon, 2 Aug 2010 17:03:24 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by core3.amsl.com (Postfix) with ESMTP id 483FB3A6969; Mon, 2 Aug 2010 17:03:24 -0700 (PDT)
Received: from harbor.orleans.occnc.com (harbor.orleans.occnc.com [173.9.106.135]) by harbor.orleans.occnc.com (8.13.6/8.13.6) with ESMTP id o7303ek1005853; Mon, 2 Aug 2010 20:03:40 -0400 (EDT) (envelope-from curtis@harbor.orleans.occnc.com)
Message-Id: <201008030003.o7303ek1005853@harbor.orleans.occnc.com>
To: Greg Mirsky <gregimirsky@gmail.com>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Mon, 02 Aug 2010 09:12:40 PDT." <AANLkTi=WNbHxa-k+DE34DD4fKudMcgQbvcVuNno8GU0m@mail.gmail.com>
Date: Mon, 02 Aug 2010 20:03:40 -0400
Sender: curtis@occnc.com
Cc: mpls@ietf.org, pwe3@ietf.org
Subject: Re: [mpls] [PWE3] ELI as a reserved label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
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, 03 Aug 2010 00:03:25 -0000

In message <AANLkTi=WNbHxa-k+DE34DD4fKudMcgQbvcVuNno8GU0m@mail.gmail.com>
Greg Mirsky writes:
>
>
> Dear Curtis,
>
> interestingly, I was thinking of possible implications of EL and
> multipath in FRR Facility backup network.
>
> You wrote:
>
>   BTW - There are some implications for facilities FRR.  On the
>   facilities backup path there is no per LSP PATH or RESV message to
>   look at to see what value of ELI is being used.  If the facilities
>   backup path is over multipath (ie: LAG, bundle, or RSVP ECMP), then
>   the value of ELI will not be known.  This might force detour style
>   FRR or use of GMPLS path protection (or segement which is more
>   detour-like).  A fixed ELI would help here too (allowing bypass
>   FRR).
>
> If the protected link is LAG or Link bundle, then I think it is more
> likly that LSPs will get squeezed as BW shrinks. Thus it might be not
> a local protection but restoration that will be playing in.  Another
> scenario, a singleton link protected by a path that has LAG or Link
> Bundle in it. I think that it would be up to local policy of the
> particular PLR to signal use of EL on the bypass tunnel regardless of
> whether EL been used on any of protected LSPs.
>
> Regards,
> Greg


Greg,

I would imagine that in networks where LAG (or link bundle or ECMP) is
important, EL would be enabled anywhere that it could be supported
except in outer tiers where capacity was small enough that single
links only were needed.

Curtis