I-D Action: draft-ietf-rtgwg-bgp-pic-07.txt

internet-drafts@ietf.org Mon, 02 April 2018 14:57 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietf.org
Delivered-To: rtgwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 71D18129BBF; Mon, 2 Apr 2018 07:57:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: rtgwg@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-bgp-pic-07.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.77.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152268102542.30983.17270803550493623915@ietfa.amsl.com>
Date: Mon, 02 Apr 2018 07:57:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/53-82XKd_rGC328C5i-Bm9ImduY>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Apr 2018 14:57:06 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Area Working Group WG of the IETF.

        Title           : BGP Prefix Independent Convergence
        Authors         : Ahmed Bashandy
                          Clarence Filsfils
                          Prodosh Mohapatra
	Filename        : draft-ietf-rtgwg-bgp-pic-07.txt
	Pages           : 30
	Date            : 2018-04-02

Abstract:
In the network comprising thousands of iBGP peers exchanging millions
of routes, many routes are reachable via more than one next-hop.
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 an architecture 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 data
structures 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 automation, and zero management and provisioning
effort. It is noteworthy to mention that the benefits of BGP-PIC are
hinged on the existence of more than one path whether as ECMP or
primary-backup.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-bgp-pic/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-rtgwg-bgp-pic-07
https://datatracker.ietf.org/doc/html/draft-ietf-rtgwg-bgp-pic-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-bgp-pic-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/