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

Greg Mirsky <gregimirsky@gmail.com> Mon, 02 August 2010 16:12 UTC

Return-Path: <gregimirsky@gmail.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 C118B3A6BB8; Mon, 2 Aug 2010 09:12:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.268
X-Spam-Level:
X-Spam-Status: No, score=-2.268 tagged_above=-999 required=5 tests=[AWL=0.330, 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 lDCYv2+xqBHl; Mon, 2 Aug 2010 09:12:13 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 02A6B3A67E6; Mon, 2 Aug 2010 09:12:12 -0700 (PDT)
Received: by vws10 with SMTP id 10so2196057vws.31 for <multiple recipients>; Mon, 02 Aug 2010 09:12:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=c7s4X8Kimavqg8nVtt+IqfXGT33Shj+fiDE3G44i1bI=; b=NIMbNMYuJWUb8xetrs2TnSeGFU/0i2l/E2zuZNV0eStqlDFcwTyoQEVvkRW354ZXcA Crtnv31oxIZtWPJteBDCW0Vqd+gj7L9vaJN5UxYJ4vZmhHSvs8K1QaQi416N54Lyw56w bmmLkhfIykLgdA1Qz8D11+uXriom/BEAjBkXk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=OxVVKdYL8k2Mr8SNX8ec+CoJkeUJ47ZHC+F0B27VRcxQrTHR1FyHUXUoh622/eMEa9 B+Tcjnw1BsJ2F7ICUqN95n9fBEo/4LV5k1RwRSHfN/NctbncMJqu7FXfp4LaGwkOqjDE 5TiLSYZaaOsyvVIwTSEAZOb3uW7c6z/ibn+Xw=
MIME-Version: 1.0
Received: by 10.220.125.4 with SMTP id w4mr4379220vcr.171.1280765560483; Mon, 02 Aug 2010 09:12:40 -0700 (PDT)
Received: by 10.220.86.72 with HTTP; Mon, 2 Aug 2010 09:12:40 -0700 (PDT)
In-Reply-To: <201008021417.o72EHVxJ023448@harbor.orleans.occnc.com>
References: <8B7721F4-8C12-4C88-9036-B19592BE686E@castlepoint.net> <201008021417.o72EHVxJ023448@harbor.orleans.occnc.com>
Date: Mon, 02 Aug 2010 09:12:40 -0700
Message-ID: <AANLkTi=WNbHxa-k+DE34DD4fKudMcgQbvcVuNno8GU0m@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: curtis@occnc.com
Content-Type: multipart/alternative; boundary="001636d3430f45ee9b048cd97802"
Cc: pwe3@ietf.org, mpls@ietf.org
Subject: Re: [mpls] [PWE3] ELI as a reserved 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: Mon, 02 Aug 2010 16:12:15 -0000

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