[GROW] RFC 6774 on Distribution of Diverse BGP Paths
rfc-editor@rfc-editor.org Tue, 06 November 2012 21:53 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 693FC21F8B65; Tue, 6 Nov 2012 13:53:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level:
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 cSZoPNcrKQ5o; Tue, 6 Nov 2012 13:53:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id EF40521F8B61; Tue, 6 Nov 2012 13:53:43 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 04ED8B1E01F; Tue, 6 Nov 2012 13:47:13 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20121106214713.04ED8B1E01F@rfc-editor.org>
Date: Tue, 06 Nov 2012 13:47:13 -0800
Cc: grow@ietf.org, rfc-editor@rfc-editor.org
Subject: [GROW] RFC 6774 on Distribution of Diverse BGP Paths
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 06 Nov 2012 21:53:45 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6774
Title: Distribution of Diverse BGP Paths
Author: R. Raszuk, Ed.,
R. Fernando, K. Patel,
D. McPherson, K. Kumaki
Status: Informational
Stream: IETF
Date: November 2012
Mailbox: robert@raszuk.net,
rex@cisco.com,
keyupate@cisco.com,
dmcpherson@verisign.com,
ke-kumaki@kddi.com
Pages: 22
Characters: 48316
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-grow-diverse-bgp-path-dist-08.txt
URL: http://www.rfc-editor.org/rfc/rfc6774.txt
The BGP4 protocol specifies the selection and propagation of a single
best path for each prefix. As defined and widely deployed today, BGP
has no mechanisms to distribute alternate paths that are not
considered best path between its speakers. This behavior results in a
number of disadvantages for new applications and services.
The main objective of this document is to observe that by simply
adding a new session between a route reflector and its client, the Nth best
path can be distributed. This document 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 a software upgrade of provider edge (PE)
routers acting as route reflector clients. This document is not an Internet
Standards Track specification; it is published for informational purposes.
This document is a product of the Global Routing Operations Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC