Re: [Lsr] SRLG usage in the IGP Flexible Algorithm draft

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Sun, 03 May 2020 07:46 UTC

Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 584953A16BD; Sun, 3 May 2020 00:46:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.59
X-Spam-Level:
X-Spam-Status: No, score=-1.59 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, PDS_BTC_ID=0.5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecitele.com header.b=BEN2MLqc; dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=eci365.onmicrosoft.com header.b=MKgiABB1
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W4_np73Fs0xC; Sun, 3 May 2020 00:46:30 -0700 (PDT)
Received: from mail1.bemta25.messagelabs.com (mail1.bemta25.messagelabs.com [195.245.230.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BA363A16B6; Sun, 3 May 2020 00:46:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ecitele.com; s=eciselector10072019; t=1588491986; i=@ecitele.com; bh=dxxkSDkM5DKOSgcYBcRwxeCdsElPyPM5q+Z/ZEMcy/0=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=BEN2MLqcr7yAv6YlRmmOjxAVIv7avfWKwUhL/KnQurP9TCoQ+DA5oeJQmDhRe56aK EWG7rKxXydWL21RO6YGdteWsmvBc1B8s6mRMhbUtH/R3bYcD5FbSraRDtirhP0Nb3V 9Kj9qbejsrE1iUBdlC0OJUPC6ufl5i/5cv9EWZzs=
Received: from [100.112.195.143] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-4.bemta.az-a.eu-west-1.aws.symcld.net id 8B/36-46985-1D67EAE5; Sun, 03 May 2020 07:46:25 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA1VTbVBUZRTmvffu7l1knZcF5cRok+vHKLkLS85 4JT+yGYqaobCmZmrUusSVXVoWZncRSH+gSW7sKhikI0LyKbp8mAslH9EUEAJRrJZIBejyFbIQ JhUSDXTvXjX7c+Y553nOc847c16aVObKgmkuzcKZjKxBJfWllFN2p/rq/pq9YdnW5cyxXz4nm IYzdinjbr5FMR0j5yVMfdNRKeOanCeZvqFmkrnimkfP0FF585ckUWVlc0TUjcPXZVFzjVlEDP WmRG+MTUp7W6K78+FVKnn4FJF2a+ymNAMdySOykC+NcDkJ/9z1yMSknQLr6KxUTGoRdFz5yMt QuJqEDwbtEiFR4mICFq7bCDEZRHDZ3U9lITktxdvAWTng7Q/E0whOn5wihYTEnQgqZialgioA Pw3dtc2EgAPxVvDU90tFHAG24g4kYAqvgT7rRZmAFZiFEbtopMS5CD756ZBEIOT8OPd4rtcI4 eUw21XlxSQOgp9HznoxYAxlX/SQIl4Gt4cXJOLzbAh6h3L4yTRPPAF/eWhRsxKunbUhsbwa6s b3iOVocLXaKRFvhO++tclEyRpYaEkXy8kw2u+SiXgd9E1aSVGyAuzTGmEo4HskuKwz9zWPg+O Ym8pBofmPLC1iIyxWDJL53tf7Q+fpESqftyLxBrjYeF++CvJsbpmI10NmQaHs0XoRkjnQ5liT Pl5nSWT1BrU2LEyt1YartVvC1Zs2a9j31KyGS1GncmaLWqthU80ac3riO4Y4jZGzOBF/h3HJX 4XWo7+rpjUt6DGaUC1TXNpZs1e5NDYpLl3HmnVvmVIMnLkFraBpFSjW8Qer9Ddx8VzaPr2Bv+ YHNNB+qkCFTKAV5mQ20ayPF6kuFEnn3C4sIenf5kr5+LujjI+z3thWWF5CKiljkpELDlI4Uvh mLDTrUowPrR/8lWtoZXCAAvn4+Cj9kjlTot7yf34CBdFIFaD4RnDx0xstDzeY4Jcj+OWwvFJY zsL+RwVnEFvgyAszfrER2wt7WrLlzTEd/rub3FztZydDOzMWsl+PkbzfOBGz/9wrpmr9Qby27 ThxYKujMlMauuq5PqW04dXWy+FyR9yXualLDxc8+2JkvW90e/ti2R3/AkPIRmqtTj+r3bC7Na S8+uvW8QtV3Qljqzt2ZZ8vmbs55ljfFTlQseR7gmgr+mNw6YntCUte+zMrqzZBFTF1t/IlT1j pFOzEjHxx27tHG0dKiqw7Xj7YWX4vaE9NZikqOPAkk7rL6eq1j56L+PGU81BTD9bcMIxeiM89 s+l4WuaCrrFB02D37HNGz/cToW/U+di6e0dLf5UM7Cj2DD31Q2JdKvNxp2r4+U8jVZRZx2pDS JOZ/RcGGIP7pgQAAA==
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-5.tower-267.messagelabs.com!1588491982!199753!1
X-Originating-IP: [18.237.140.178]
X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass
X-StarScan-Received:
X-StarScan-Version: 9.50.1; banners=ecitele.com,-,-
X-VirusChecked: Checked
Received: (qmail 12883 invoked from network); 3 May 2020 07:46:24 -0000
Received: from p01c.mail.dlp.protect.symantec.com (HELO mail.ds.dlp.protect.symantec.com) (18.237.140.178) by server-5.tower-267.messagelabs.com with ECDHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 3 May 2020 07:46:24 -0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=j98kJb4ELnMYONWfJ1RG6TZ4XVX18nSVIrizqwMF3Mq3YzoE54D3DINw8soKpPo5DmAOck06kzWhoqztHK+Y6FbfXkwV5p081VvceCFvRH3xFFB540tHJN5OOxbpfzrAF/feqGuXOCrkQCd5qwGgcWvNWypHEBVKSHPzvKTU0IJ1oAVahnC6hITXHfyk/iBKkIHAzyKmNlw7qAPiIasrmcKNmdOee9HpmzG0vgOlModA6pYPh3jROBPkpGx9Q758QF0Y4eg4agzddrBS2g6FsJ/nKVhocMQq2AHEky/VScoE51ypMS5XYZdnPntHUAs1nR9M/nG5kQaIpdg6I1IYDw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Or4JiHeE3un0CNDMtji6gr0SSCmTwYqkbH3B1dSntVQ=; b=UfdyBysN6BECU9IUUrwdq3fWby572DbUXB7kw5X3pN9DV6fVHsXZ+/87tozIDejSaV/KIyxbAB2mXyiy2bri55/2GTGZB7a7EWEagJllT66PZntxcDXeqT9q8M9tWL+UhsNw+Cg1Pxt1F9uXD4BRRWAnqpzc2zBNTX101xICy+vMecTBZLaml/v76Ws7bx5ah5LbaG+NsZ9SLTJF1K6lDTJ0pYzQbyCUVD/DrR85DrbGM5VEvcpJaCALUCY9xqi21nBsK6Q2yMUCr/ZLcAx6+zKuVlN/FVxXvMZnbF3o4gklayOy/sg3rrojOiE7wHQ+SJxqiwt2HPO+fSlxa1BOcg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ecitele.com; dmarc=pass action=none header.from=ecitele.com; dkim=pass header.d=ecitele.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ECI365.onmicrosoft.com; s=selector2-ECI365-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Or4JiHeE3un0CNDMtji6gr0SSCmTwYqkbH3B1dSntVQ=; b=MKgiABB1+7j31y+AV0m2gnDiby4277WHZuK/BG5EgT9OUD3Qc8nPkO3sHDz2XoPKrxtDg87vJ9vK6yzc5OZegI4U+h6qVYZ8AHZcAp8SB2Jqi6kwcqqmpYvMo6G0hTduZQpfVHaqevNGXlMg26nv9wF85Wx7FRnUkLHi3Szjtmc=
Received: from AM0PR0302MB3217.eurprd03.prod.outlook.com (2603:10a6:208:2::12) by AM0PR0302MB3409.eurprd03.prod.outlook.com (2603:10a6:208:11::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2937.22; Sun, 3 May 2020 07:46:20 +0000
Received: from AM0PR0302MB3217.eurprd03.prod.outlook.com ([fe80::a0f0:9917:35:4260]) by AM0PR0302MB3217.eurprd03.prod.outlook.com ([fe80::a0f0:9917:35:4260%3]) with mapi id 15.20.2958.027; Sun, 3 May 2020 07:46:19 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Peter Psenak <ppsenak@cisco.com>, "shraddha@juniper.net" <shraddha@juniper.net>, "cfilsfil@cisco.com" <cfilsfil@cisco.com>, "ketant@cisco.com" <ketant@cisco.com>, "arkadiy.gulko@thomsonreuters.com" <arkadiy.gulko@thomsonreuters.com>
CC: "lsr@ietf.org" <lsr@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, Michael Gorokhovsky <Michael.Gorokhovsky@ecitele.com>, Ron Sdayoor <Ron.Sdayoor@ecitele.com>
Thread-Topic: SRLG usage in the IGP Flexible Algorithm draft
Thread-Index: AdYfAAtyRauA7slnSUiSBLNPZjFKDgAntx2AAF+Zs5A=
Date: Sun, 3 May 2020 07:46:19 +0000
Message-ID: <AM0PR0302MB32171A34910751F32C94D6E89DA90@AM0PR0302MB3217.eurprd03.prod.outlook.com>
References: <AM0PR0302MB3217968E975EDC3B74F091849DAA0@AM0PR0302MB3217.eurprd03.prod.outlook.com> <bf999a11-86cb-000f-4ede-653e7b063313@cisco.com>
In-Reply-To: <bf999a11-86cb-000f-4ede-653e7b063313@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [79.178.58.54]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: cea178e8-a2ee-4530-1e04-08d7ef3611a9
x-ms-traffictypediagnostic: AM0PR0302MB3409:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <AM0PR0302MB340909FA086E4501956643B09DA90@AM0PR0302MB3409.eurprd03.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0392679D18
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR0302MB3217.eurprd03.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(39850400004)(396003)(366004)(346002)(376002)(136003)(2906002)(478600001)(5660300002)(33656002)(76116006)(66446008)(52536014)(64756008)(66556008)(66476007)(66946007)(110136005)(54906003)(86362001)(316002)(107886003)(7696005)(4326008)(26005)(186003)(9686003)(53546011)(6506007)(8936002)(71200400001)(55016002)(8676002); DIR:OUT; SFP:1102;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: K27apqVHeAE1tLiNN+GR6ogze4wvhoVLOiqctgrSzwvTM93LnsaM7Z88wNU7W6Vz694jpXUzOvwNo+K9LcH48qxSIBfV2SLj4WlNqnex7JpXrEe81icwTIDH4SOIlygimeR4CpTFIGklLU/jycRODvVq04DrnY3IHDJdToGpL5THR3jpNYwsfndpkUEAn3n2EIYAekTG92uANK3S0Pwk3/WWxsK62TCj6gwQA52TtCEGlrbgJ/C7F3xYS7GcwHB+78f5NA2nupN+L+q6CE/vvy+hY6X3PziVyULu1nDPP6v648sTfApcydlXNe7tUuq4UhAR0fHQr1seDJMAGdJbrugVSLUcTON1Ok6/z912u4NsIIRgrRx393TeC1uZ3r+y//bJqCce6F6kjlCKBIn/ty5b3xR9IGZbYdFgyz3SAkVlX1880roXkhu6T8cYi/nSXWDa8iclq1pLQl0WXhorS5pgIGeFzCFYEu5QNh4H9ClaNOL5Igd9KdIaBW1L54r/O5E/upBOg7KNNc4oBFIMkQ==
x-ms-exchange-antispam-messagedata: ORGfblSqwlAlES0KlZVHUZktfm86U4D4zsxD3gfLGKA0/+WRUyLomEG7qDx8nNbGpXflfJWE/vKK7wBAa+tsZbKcSbqwFwPW1XyntRkxLKfW2bCILcDh9CmIFo2YYGdfPCHYH+Yl//dT3J+lAivTljJUtSWQsbuURv3K0OqHWEP2Exo6h2wpEn+OBqZFSdoyAee+F3Omx3kv+z9p7r6HjAahVnMWezGqmmspUUQ/I68Yi+0RZ5Pwv6D5EW+uchCtC7y1Xow+oFu0sOxYssjUMVQETpohNjKdRU06YitKdihY6xncEx/0Q8aMOKCrs4DTYX/gmbiu00CVkSDKp5i7xd+ZWGzUVGbUIBqaXcRsOPb9VWB1PHowaEEoNU2+UFiDTnIC7rRKC+/ZCzGF3ZiTQX4KBwYiL/bGuaqH1pXEyx0Ja06TyMBLCZokd1Vr+S4qEWsU0uM4Wg+bnjfjbHPqtxCAP9MdMvkkNJd88T11EtLXY9vsRRghgu9AXoPJNHYO1Y5P3EaLhp4AjPgiOaKrqM5JEBaxU6k8+0pZUY9aSHNvuHUMLSxGlrbf1seprE9RYn4pf8gehjfSdzuyfOJqhpi/UKzHd9U7dDRK1sfyiMo9aPd0WmCNyn2hCfI+iWVUUIxdnwYz78anXqQlswHVy95/K4UcX8t69Kb6drdL9SKfSTmbL90w4gvEZ0Tf4OKu5pUWOX38rS6YJ+QlDBet87wZFPzmVCz8NYH1rLzVnN2ZRIqzIqtuRBZCFe0i4M3FXONv3hRhWdaniU56+Osk4dVTsmJxPsdE9yeR86fIilY=
Content-Type: multipart/alternative; boundary="_000_AM0PR0302MB32171A34910751F32C94D6E89DA90AM0PR0302MB3217_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-Network-Message-Id: cea178e8-a2ee-4530-1e04-08d7ef3611a9
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 May 2020 07:46:19.6634 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: nhDak0oY5jx1ee+rf2yUhuBxaMvysDAKoYtb1mrE+VBVjmw775HwbdGmCAd8NBkR4kdAj/myfOEYSL++uTt2IQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR0302MB3409
X-CFilter-Loop: Reflected
X-DetectorID-Processed: d8d3a2b3-1594-4c39-92fb-b8312fe65a8a
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/ock3US8HK9oEBSWCW9pEgawRCpg>
Subject: Re: [Lsr] SRLG usage in the IGP Flexible Algorithm draft
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 May 2020 07:46:32 -0000

Peter,

Lots of thanks for a prompt response.



My reading of your response is as following:

There are two different ways in which SRLG information can be used with Flexible Algorithms:

1.       In a context of a single Flexible Algorithm, it can be used for computation of backup paths (e.g., as described in the TI-LFA draft). This usage does not require association of any specific SRLG with the given Flexible Algorithm.

2.       In the context of multiple Flexible Algorithms it can be used for creating disjoint sets of paths by pruning the links belonging to a specific SRLG from the topology on which a specific Flexible Algorithm computes its paths. This usage:

a.       Extends the definition of the topology used by a given Flexible Algorithm that can be defined using Admin groups (a.k.a. affinities)

b.       Facilitates usage of already deployed SRLG configurations where such configuration have been in place

c.       Requires explicit association of a given Flexible Algorithm with a specific set of SRLG as defined in the current Flex Algo draft.

The two usages mentioned above are strictly orthogonal.



If the understanding above is correct, it makes to me sense to add the corresponding clarifying text to the draft.



Regards,

Sasha



Office: +972-39266302

Cell:      +972-549266302

Email:   Alexander.Vainshtein@ecitele.com



-----Original Message-----
From: Peter Psenak <ppsenak@cisco.com>
Sent: Friday, May 1, 2020 12:57 PM
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>om>; shraddha@juniper.net; cfilsfil@cisco.com; ketant@cisco.com; arkadiy.gulko@thomsonreuters.com
Cc: lsr@ietf.org; spring@ietf.org; rtgwg@ietf.org; Michael Gorokhovsky <Michael.Gorokhovsky@ecitele.com>om>; Ron Sdayoor <Ron.Sdayoor@ecitele.com>
Subject: Re: SRLG usage in the IGP Flexible Algorithm draft



Alexander,



On 30/04/2020 17:21, Alexander Vainshtein wrote:

> Hi all,

>

> I have a question about the proposed usage of SRLG in the IGP Flexible

> Algorithm <https://clicktime.symantec.com/3Wn8dBNRoEXXTU1kJz6RrsR6H2?u=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-lsr-flex-algo-07> draft.

>

> This usage is defined Section 12 of the draft with the reference to

> the SRLG exclude rule as following:

>

>

>

>        2.  Check if any exclude SRLG rule is part of the

> Flex-Algorithm

>

>        definition.  If such exclude rule exists, check if the link is

>

>        part of any SRLG that is also part of the SRLG exclude rule.

> If

>

>        the link is part of such SRLG, the link MUST be pruned from the

>

>        computation.

>

> This looks effectively undistinguishable from the usage of the exclude

> Admin groups rule as described in the same Section 12 of the draft:

>

>        1.  Check if any exclude rule is part of the Flex-Algorithm

>

>        definition.  If such exclude rule exists, check if any color

> that

>

>        is part of the exclude rule is also set on the link.  If such a

>

>        color is set, the link MUST be pruned from the computation.

>

>  From my POV, with such a definition, there is no need in the

> dedicated “Exclude SRLG” rule as part of the specification of the

> Flexible Algorithm, since such the SRLG Exclude rule can be replaced

> with a matching Exclude All rule  using Admin groups.



there is one very important point. Maintaining the affinities is operationally complex. Some networks have already deployed SRLGs. If SRLG exclude with flex-algo gives people what they want, asking them to deploy affinities would be redundant. That's the main point.



Simple use case:



I have two SRLGs in the network. For some specific traffic I want to send the data via two independent streams. I want to avoid single SRLG failure to affect both streams. I define two flex-algos, each one excluding one SRLG. No need to define extra affinities. This is btw not an academical example, this has been requested by real users.





>

> I also think that such a usage of SRLG does not fit the needs of the

> TI-LFA

> <https://clicktime.symantec.com/3GhKPQ2JAgebW7vLidLjXRx6H2?u=https%3A%

> 2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-rtgwg-segment-routing-ti-lfa-0

> 3> draft that considers an SRLG as a resource that fails when any of

> the links/nodes comprising it fails. E.g., it says in Section 2:

>

>     The Point of Local Repair (PLR), S, needs to find a node Q (a

> repair

>

>     node) that is capable of safely forwarding the traffic to a

>

>     destination D affected by the failure of the protected link L, a

> set

>

>     of links including L (SRLG), or the node F itself.  The PLR also

>

>     needs to find a way to reach Q without being affected by the

>

>     convergence state of the nodes over the paths it wants to use to

>

>     reach Q: the PLR needs a loop-free path to reach Q.



I see no conflict between the LFA draft and flex-algo one. If you do, please be precise where the conflict is.



>

> To me this suggests that SRLGs are only relevant when computing backup

> paths for specific failures, e.g., an LFA for failure of a link hat

> belongs to a specific SRLG must be computed in the topology from which

> all the links belonging to the same SRLG are pruned. This

> understanding matches RFC 4090 that states in Section 6.2 “Procedures

> for Backup Path

> Computation”:



SRLG is a mechanism to express fate share. I see no reason why SRLG could not be used for other than LFA purposes.



thanks,

Peter





>

>        - The backup LSP cannot traverse the downstream node and/or

> link

>

>          whose failure is being protected against.  Note that if the

> PLR

>

>          is the penultimate hop, node protection is not possible, and

>

>          only the downstream link can be avoided. The backup path may

> be

>

>          computed to be SRLG disjoint from the downstream node and/or

>

>          link being avoided.

>

> If SRLGs are only relevant for computation of backup paths, it is not

> clear to me if they should be part of the definition of a specific

> Flexible Algorithm.

>

> What, if anything, did I miss?

>

> Regards, and lots of thanks in advance,

>

> Sasha

>

> Office: +972-39266302

>

> Cell:      +972-549266302

>

> Email:   Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>

>

>

> ______________________________________________________________________

> _____

>

> This e-mail message is intended for the recipient only and contains

> information which is CONFIDENTIAL and which may be proprietary to ECI

> Telecom. If you have received this transmission in error, please

> inform us by e-mail, phone or fax, and then delete the original and

> all copies thereof.

> ______________________________________________________________________

> _____



___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information which is 
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this 
transmission in error, please inform us by e-mail, phone or fax, and then delete the original 
and all copies thereof.
___________________________________________________________________________