Re: Remote LFA

Clarence Filsfils <cfilsfil@cisco.com> Tue, 11 October 2011 16:35 UTC

Return-Path: <cfilsfil@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77BCE21F8E34 for <rtgwg@ietfa.amsl.com>; Tue, 11 Oct 2011 09:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level:
X-Spam-Status: No, score=-10.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cONeb71uCMyY for <rtgwg@ietfa.amsl.com>; Tue, 11 Oct 2011 09:35:21 -0700 (PDT)
Received: from av-tac-sj.cisco.com (firebird.cisco.com [171.68.227.73]) by ietfa.amsl.com (Postfix) with ESMTP id 077EC21F8E28 for <rtgwg@ietf.org>; Tue, 11 Oct 2011 09:35:21 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from bonfire.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-sj.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p9BGZKfw028067 for <rtgwg@ietf.org>; Tue, 11 Oct 2011 09:35:20 -0700 (PDT)
Received: from [10.55.57.5] (ams-cfilsfil-8914.cisco.com [10.55.57.5]) by bonfire.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p9BGZICR021780; Tue, 11 Oct 2011 09:35:18 -0700 (PDT)
Message-ID: <4E947045.909@cisco.com>
Date: Tue, 11 Oct 2011 18:35:17 +0200
From: Clarence Filsfils <cfilsfil@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Gábor Sándor Enyedi <gabor.sandor.enyedi@ericsson.com>
Subject: Re: Remote LFA
References: <4E946A07.80403@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E20EA2EF9C6@ESESSCMS0359.eemea.ericsson.se>
In-Reply-To: <EFAB865EBEFB734CA1FABD543B2E0E2E20EA2EF9C6@ESESSCMS0359.eemea.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "imc.shand@googlemail.com" <imc.shand@googlemail.com>, "Stewart Bryant (stbryant)" <stbryant@cisco.com>, "So, Ning" <ning.so@verizonbusiness.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Oct 2011 16:35:21 -0000

Gabor,

It is independent. See the draft:

"
6.  Historical Note

    The basic concepts behind Remote LFA were invented in 2002 and were
    later included in draft-bryant-ipfrr-tunnels, submitted in 2004.

    draft-bryant-ipfrr-tunnels targetted a 100% protection coverage and
    hence included additional mechanims on top of the Remote LFA concept.
    The addition of these mechanisms made the proposal very complex and
    computationally intensive and it was therefore not pursued as a
    working group item.

    As explained in [I-D.filsfils-rtgwg-lfa-applicability], the purpose
    of the LFA FRR technology is not to provide coverage at any cost.  A
    solution for this already exists with MPLS TE FRR.  MPLS TE FRR is a
    mature technology which is able to provide protection in any topology
    thanks to the explicit routing capability of MPLS TE.

    The purpose of LFA FRR technology is to provide for a simple FRR
    solution when such a solution is possible.  The first step along this
    simplicity approach was "local" LFA [RFC5286].  We propose "Remote
    LFA" as a natural second step.  The following section motivates its
    benefits in terms of simplicity, incremental deployment and
    significant coverage increase.
"

Cheers,
Clarence