[GROW] New Version Notification for draft-raszuk-diverse-bgp-path-dist-00

Robert Raszuk <raszuk@cisco.com> Sun, 05 July 2009 13:34 UTC

Return-Path: <raszuk@cisco.com>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10D4C3A6907 for <grow@core3.amsl.com>; Sun, 5 Jul 2009 06:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.511
X-Spam-Level:
X-Spam-Status: No, score=-6.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MbhdHIsfjLxY for <grow@core3.amsl.com>; Sun, 5 Jul 2009 06:34:46 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 1E8603A6B08 for <grow@ietf.org>; Sun, 5 Jul 2009 06:34:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,351,1243814400"; d="scan'208";a="337827518"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 05 Jul 2009 13:35:11 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n65DZBXq002912 for <grow@ietf.org>; Sun, 5 Jul 2009 06:35:11 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n65DZB8k029034 for <grow@ietf.org>; Sun, 5 Jul 2009 13:35:11 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 5 Jul 2009 06:35:10 -0700
Received: from [10.21.78.138] ([10.21.78.138]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 5 Jul 2009 06:35:10 -0700
Message-ID: <4A50AC0B.9060607@cisco.com>
Date: Sun, 05 Jul 2009 06:35:07 -0700
From: Robert Raszuk <raszuk@cisco.com>
Organization: Cisco Systems
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: "grow@ietf.org" <grow@ietf.org>
Content-Type: text/plain; charset="ISO-8859-2"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Jul 2009 13:35:10.0885 (UTC) FILETIME=[6B3BC550:01C9FD75]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1231; t=1246800911; x=1247664911; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=raszuk@cisco.com; z=From:=20Robert=20Raszuk=20<raszuk@cisco.com> |Subject:=20New=20Version=20Notification=20for=20=20draft-r aszuk-diverse-bgp-path-dist-00 |Sender:=20; bh=9t1bxA8SA6YR4PhodqoPQPxnIAxC3zA/OgmEIaPBYy0=; b=vUoDsKQZNn4BIIz+I+PqhuR43DHA/ejsG/IIx89Z85cV6bUobhWQBHlD6D ZkYeMSlmN4K95xskNBmVoBGkjdQgQWz/lYP1FLIEkf1nezJH5XfnKII8ifKp DArw8lOxh0;
Authentication-Results: sj-dkim-3; header.From=raszuk@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
Subject: [GROW] New Version Notification for draft-raszuk-diverse-bgp-path-dist-00
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raszuk@cisco.com
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Jul 2009 13:34:47 -0000

A new version of I-D, draft-raszuk-diverse-bgp-path-dist-00.txt has been 
successfuly submitted and posted to the IETF repository.

Filename:	 draft-raszuk-diverse-bgp-path-dist
Revision:	 00
Title:		 Distribution of diverse BGP paths.
Creation_date:	 2009-07-05
WG ID:		 Independent Submission
Number_of_pages: 20

http://www.ietf.org/internet-drafts/draft-raszuk-diverse-bgp-path-dist-00.txt

Abstract:
The BGP4 protocol specifies the selection and propagation of a single
best path for each prefix.  As defined today BGP has no mechanisms to
distribute paths other then best path between it's speakers.  This
behaviour results in number of disadvantages for new applications and
services.

This document presents an alternative mechanism for solving the
problem based on the concept of parallel route reflector planes.  It
also compares existing solutions and proposed ideas that enable
distribution of more paths than just the best path.

This proposal does not specify any changes to the BGP protocol
definition.  It does not require upgrades to provider edge or core
routers nor does it need network wide upgrades.  The authors believe
that the GROW WG would be the best place for this work.