Subject: [Idr] Fwd: New Version Notification for draft-bashandy-idr-bgp-repair-label-00

From: Ahmed Bashandy <[email-masked]>
Date: Mon, 28 Feb 2011 22:32:49 +0200

Hi,

This is a draft that proposes rerouting traffic, without waiting for BGP to re-converge, to another PE in a BGP-free core when a PE detects that the NH is no longer reachable. Because traffic coming from the core is redirected back to the core, we propose using a specially advertised label to make sure that the traffic does not get re-routed multiple times into the core, thus avoiding loops.

All comments are highly appreciated

Ahmed

-------- Original Message --------
Subject: 	New Version Notification for draft-bashandy-idr-bgp-repair-label-00
Date: 	Mon, 28 Feb 2011 08:49:59 -0800 (PST)
From: 	IETF I-D Submission Tool <[email-masked]>
To: 	[email-masked]
CC: 	[email-masked]

A new version of I-D, draft-bashandy-idr-bgp-repair-label-00.txt has been successfully submitted by Ahmed Bashandy and posted to the IETF repository.

Filename:	 draft-bashandy-idr-bgp-repair-label
Revision:	 00
Title:		 Scalable, Loop-Free BGP FRR using Repair Label
Creation_date:	 2011-02-28
WG ID:		 Independent Submission
Number_of_pages: 14

Abstract:
Consider a BGP free core scenario. Suppose the provider edge BGP
speaker PE1, PE2,..., PEn know about a prefix P/p via the external
routers CE1, CE2,..., CEm.  If the PE router PEi loses connectivity to
the primary path, whether it is another PE router or a CE router, it
desirable to immediately restore traffic by rerouting packets arriving
to PEi and destined to the prefix P/p to one of the other PE routers
that advertised P/p, say PEj, until BGP re-converges. However if the
loss of connectivity of PEi to the primary path also resulted in the
loss of connectivity between PEj and CEj, rerouting a packet without
before the control plane converges may result in a loop. In this
document, we propose using a repair label for traffic restoration
while avoiding loops. We propose advertising the ''repair'' label
through BGP.

The IETF Secretariat.