[Idr] Fwd: New Version Notification for draft-bashandy-bgp-frr-vector-label-00.txt
Ahmed Bashandy <bashandy@cisco.com> Mon, 09 July 2012 18:29 UTC
Return-Path: <bashandy@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 220C711E8102; Mon, 9 Jul 2012 11:29:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 KfvmittRKzX5; Mon, 9 Jul 2012 11:29:48 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 0A36E11E80D0; Mon, 9 Jul 2012 11:29:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=bashandy@cisco.com; l=8966; q=dns/txt; s=iport; t=1341858613; x=1343068213; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=MKDnFXkbmi02ByGRf9igwLo1MRPv75pc4aU3FSSdQ00=; b=fIAeuVwl2JhJ7/uU59VLHkI9vVXfSPuaDBUvaGwzXI9dVXHxFke1fVLY hlcv+8wehnXvac/E58VhoBRQFC/f1ZuU/EjxTC0nUCq3RZp64xwlwk1WK Qh8RaDrFoKynrksjWm1kEbf/oFT97i3GxOu5LHJiujVsy4bmG8OYcQQtJ s=;
X-Files: signature.asc : 251
X-IronPort-AV: E=Sophos; i="4.77,553,1336348800"; d="asc'?scan'208,217"; a="51465529"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 09 Jul 2012 18:30:13 +0000
Received: from [171.71.139.5] (dhcp-171-71-139-5.cisco.com [171.71.139.5]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q69IUD3g028887; Mon, 9 Jul 2012 18:30:13 GMT
Message-ID: <4FFB2330.4020809@cisco.com>
Date: Mon, 09 Jul 2012 11:30:08 -0700
From: Ahmed Bashandy <bashandy@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "idr@ietf.org List" <idr@ietf.org>, rtgwg@ietf.org
References: <20120708140543.21354.82768.idtracker@ietfa.amsl.com>
In-Reply-To: <20120708140543.21354.82768.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.2
X-Forwarded-Message-Id: <20120708140543.21354.82768.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="------------enigD26DE787B37BEC29F385B464"
Cc: "Maciek Konstantynowicz (mkonstan)" <mkonstan@cisco.com>
Subject: [Idr] Fwd: New Version Notification for draft-bashandy-bgp-frr-vector-label-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 18:29:49 -0000
Hi, The draft proposes a new method for BGP FRR. The approach is very scalable as it does not require injecting any prefixes into the core, no re-advertisement of BGP prefixes, and no state replication. At the same time, it is transparent to the operator in the sense that if it is enabled by default, there is no need for human intervention due to any reason including internal and external topology changes or even when switching from MPLS to IP core and back All comments are most welcomed Thanks Ahmed -------- Original Message -------- Subject: New Version Notification for draft-bashandy-bgp-frr-vector-label-00.txt Date: Sun, 8 Jul 2012 07:05:43 -0700 From: <internet-drafts@ietf.org> To: <bashandy@cisco.com> CC: <naikumar@cisco.com>, <mkonstan@cisco.com> A new version of I-D, draft-bashandy-bgp-frr-vector-label-00.txt has been successfully submitted by Ahmed Bashandy and posted to the IETF repository. Filename: draft-bashandy-bgp-frr-vector-label Revision: 00 Title: BGP FRR Protection against Edge Node Failure Using Vector Labels Creation date: 2012-07-07 WG ID: Individual Submission Number of pages: 32 URL: http://www.ietf.org/internet-drafts/draft-bashandy-bgp-frr-vector-label-00.txt Status: http://datatracker.ietf.org/doc/draft-bashandy-bgp-frr-vector-label Htmlized: http://tools.ietf.org/html/draft-bashandy-bgp-frr-vector-label-00 Abstract: Consider a BGP free core scenario. Suppose the edge BGP speakers PE1, PE2,..., PEn know about a prefix P/m via the external routers CE1, CE2,..., CEm. If the edge router PEi crashes or becomes totally disconnected from the core, it is desirable for a core router "P" carrying traffic to the failed edge router PEi to immediately restore traffic by re-tunneling packets originally tunneled to PEi and destined to the prefix P/m to one of the other edge routers that advertised P/m, say PEj, until BGP re-converges. In doing so, it is highly desirable to keep the core BGP-free while not imposing restrictions on external connectivity or complicating provisioning effort. Thus (1) a core router should not be required to learn any BGP prefix, (2) the size of the forwarding and routing tables in the core routers should be independent of the number of BGP prefixes, (3) re-routing traffic without waiting for re-convergence must not cause loops, (4) provisioning effort should be kept at minimum, and (5) there should be no restrictions on what edge routers advertise what prefixes. For labeled prefixes, (6) the label stack on the packet must allow the repair PEj to correctly forward the packet and (7) there must not be any need to perform more than one label lookup on any edge or core router during steady state The IETF Secretariat
- [Idr] Fwd: New Version Notification for draft-bas… Ahmed Bashandy
- Re: [Idr] Fwd: New Version Notification for draft… Robert Raszuk
- Re: [Idr] Fwd: New Version Notification for draft… Susan Hares
- Re: [Idr] Fwd: New Version Notification for draft… Ahmed Bashandy
- Re: [Idr] Fwd: New Version Notification for draft… Ahmed Bashandy
- Re: [Idr] Fwd: New Version Notification for draft… Robert Raszuk
- Re: [Idr] Fwd: New Version Notification for draft… Ahmed Bashandy
- Re: [Idr] Fwd: New Version Notification for draft… Robert Raszuk
- Re: [Idr] Fwd: New Version Notification for draft… Ahmed Bashandy
- Re: [Idr] Fwd: New Version Notification for draft… Robert Raszuk
- Re: [Idr] Fwd: New Version Notification for draft… Ahmed Bashandy