Fwd: I-D Action: draft-rtgwg-bgp-pic-00.txt
Ahmed Bashandy <bashandy@cisco.com> Mon, 01 October 2012 14:51 UTC
Return-Path: <bashandy@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 71F7C1F0D02 for <rtgwg@ietfa.amsl.com>; Mon, 1 Oct 2012 07:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.283
X-Spam-Level:
X-Spam-Status: No, score=-10.283 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IMR6xYPymkg9 for <rtgwg@ietfa.amsl.com>; Mon, 1 Oct 2012 07:51:24 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 728471F0CCD for <rtgwg@ietf.org>; Mon, 1 Oct 2012 07:51:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7866; q=dns/txt; s=iport; t=1349103082; x=1350312682; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=1CI8QFwzlJpCwl5mu8FCEMNzIkWedvu8x0+Uahc9H00=; b=ACBJPMETgeoI+XiCI+gKJu85kGlingw8DAmYqOihEfvreZMwU4yKHEa3 oc638GFHhuYsG8/C6miaNexEHV9V8u72ODYKHir0avODsDnb12RDKcayD 4JSS8+8s2INbHVZs18WgBYF7P3ZNFkipNSUq9UCrUeiuhKoDEGexikaol g=;
X-Files: signature.asc : 248
X-IronPort-AV: E=Sophos; i="4.80,517,1344211200"; d="asc'?scan'208,217"; a="127084242"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-2.cisco.com with ESMTP; 01 Oct 2012 14:51:11 +0000
Received: from [10.82.233.208] (rtp-vpn5-463.cisco.com [10.82.233.208]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id q91Ep88b013866; Mon, 1 Oct 2012 14:51:09 GMT
Message-ID: <5069ADDB.1040404@cisco.com>
Date: Mon, 01 Oct 2012 16:51:07 +0200
From: Ahmed Bashandy <bashandy@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Fwd: I-D Action: draft-rtgwg-bgp-pic-00.txt
References: <20121001140838.25089.41031.idtracker@ietfa.amsl.com>
In-Reply-To: <20121001140838.25089.41031.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.4
X-Forwarded-Message-Id: <20121001140838.25089.41031.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="------------enig0A17B76FB11CF608234B1BBF"
Cc: "Pradosh Mohapatra (pmohapat)" <pmohapat@cisco.com>
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: Mon, 01 Oct 2012 14:51:25 -0000
Hi, This draft provides an overview of BGP prefix independent convergence and how it is possible to achieve sub-second and, for certain local failures, sub-50msec convergence using hierarchical and shared FIB chain design All comments and suggestions are most welcomed Thanks Ahmed -------- Original Message -------- Subject: I-D Action: draft-rtgwg-bgp-pic-00.txt Date: Mon, 1 Oct 2012 07:08:38 -0700 From: <internet-drafts@ietf.org> Reply-To: <internet-drafts@ietf.org> To: <i-d-announce@ietf.org> A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Abstract Author(s) : Ahmed Bashandy Clarence Filsfils Prodosh Mohapatra Filename : draft-rtgwg-bgp-pic-00.txt Pages : 19 Date : 2012-10-01 Abstract: In the network comprising thousands of iBGP peers exchanging millions of routes, many routes are reachable via more than one path. Given the large scaling targets, it is desirable to restore traffic after failure in a time period that does not depend on the number of BGP prefixes. In this document we proposed a technique by which traffic can be re-routed to ECMP or pre-calculated backup paths in a timeframe that does not depend on the number of BGP prefixes. The objective is achieved through organizing the forwarding chains in a hierarchical manner and sharing forwarding elements among the maximum possible number of routes. The proposed technique achieves prefix independent convergence while ensuring incremental deployment, complete transparency and automation, and zero management and provisioning effort The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-rtgwg-bgp-pic There's also a htmlized version available at: http://tools.ietf.org/html/draft-rtgwg-bgp-pic-00 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
- Fwd: I-D Action: draft-rtgwg-bgp-pic-00.txt Ahmed Bashandy
- Fwd: I-D Action: draft-rtgwg-bgp-pic-00.txt Ahmed Bashandy
- RE: I-D Action: draft-rtgwg-bgp-pic-00.txt bruno.decraene