Fwd: New Version Notification for draft-rtgwg-bgp-pic-00.txt
Ahmed Bashandy <bashandy@cisco.com> Thu, 01 November 2012 18:21 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 529B321F8FF6 for <rtgwg@ietfa.amsl.com>; Thu, 1 Nov 2012 11:21:07 -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 a7hbAZ8wO+JV for <rtgwg@ietfa.amsl.com>; Thu, 1 Nov 2012 11:21:06 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 38FE221F8F85 for <rtgwg@ietf.org>; Thu, 1 Nov 2012 11:21:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7832; q=dns/txt; s=iport; t=1351794066; x=1353003666; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=eeSqTWDF61Ax970QoPfIIgFd8YYqFNBrviWpU3o5FAk=; b=bEexOuyd6ZMD1E8E3SWjxvY2AzXhlHRij77rivZAfxF1XE+BIPqXc7uq lOZ42Ni8uzRoO7TQgCIdT1lXFR8Oix+tZ61n4TUGzWZE602oTHOQdGU/5 z2UE8mLI/qsjWmdqIq6DU0cC0+p//8H/QQRn08rN6/lTY92qL+ihmwq2X U=;
X-Files: signature.asc : 248
X-IronPort-AV: E=Sophos; i="4.80,695,1344211200"; d="asc'?scan'208,217"; a="137634897"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-1.cisco.com with ESMTP; 01 Nov 2012 18:21:06 +0000
Received: from [10.82.210.28] (rtp-vpn4-540.cisco.com [10.82.210.28]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id qA1IL3MF014079; Thu, 1 Nov 2012 18:21:04 GMT
Message-ID: <5092BD8B.3070605@cisco.com>
Date: Thu, 01 Nov 2012 20:20:59 +0200
From: Ahmed Bashandy <bashandy@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Fwd: New Version Notification for draft-rtgwg-bgp-pic-00.txt
References: <20121001140839.25089.92354.idtracker@ietfa.amsl.com>
In-Reply-To: <20121001140839.25089.92354.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.5
X-Forwarded-Message-Id: <20121001140839.25089.92354.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="------------enig523FBD60525868C33F92F3B5"
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: Thu, 01 Nov 2012 18:21:08 -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 The basic idea relies on constructing the forwarding chains such that the BGP pathlists are shared among the maximum possible number of BGP prefixes. At the same time, BGP pathlists act as dependents on IGP prefixes in a hierarchy that allows modifying IGP without impacting BGP. The draft will be presented in the RTGWG meeting next week All comments and suggestions are most welcomed Thanks Ahmed -------- Original Message -------- Subject: New Version Notification for draft-rtgwg-bgp-pic-00.txt Date: Mon, 1 Oct 2012 07:08:39 -0700 From: <internet-drafts@ietf.org> To: <bashandy@cisco.com> CC: <pmohapat@cisco.com>, <cfilsfil@cisco.com> A new version of I-D, draft-rtgwg-bgp-pic-00.txt has been successfully submitted by Ahmed Bashandy and posted to the IETF repository. Filename: draft-rtgwg-bgp-pic Revision: 00 Title: Abstract Creation date: 2012-09-28 WG ID: Individual Submission Number of pages: 19 URL: http://www.ietf.org/internet-drafts/draft-rtgwg-bgp-pic-00.txt Status: http://datatracker.ietf.org/doc/draft-rtgwg-bgp-pic Htmlized: http://tools.ietf.org/html/draft-rtgwg-bgp-pic-00 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 Secretariat
- Fwd: New Version Notification for draft-rtgwg-bgp… Ahmed Bashandy