RFC 7911 on Advertisement of Multiple Paths in BGP
rfc-editor@rfc-editor.org Mon, 11 July 2016 23:13 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A714812D0AE; Mon, 11 Jul 2016 16:13:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.889
X-Spam-Level:
X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wDHsixVGOcoD; Mon, 11 Jul 2016 16:13:58 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03B5512B02A; Mon, 11 Jul 2016 16:13:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E7E21B80A21; Mon, 11 Jul 2016 16:13:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7911 on Advertisement of Multiple Paths in BGP
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160711231357.E7E21B80A21@rfc-editor.org>
Date: Mon, 11 Jul 2016 16:13:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/I0fbAxu6yogYZbyfx79cLu37HuA>
Cc: drafts-update-ref@iana.org, idr@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jul 2016 23:14:00 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7911
Title: Advertisement of Multiple Paths in BGP
Author: D. Walton, A. Retana,
E. Chen, J. Scudder
Status: Standards Track
Stream: IETF
Date: July 2016
Mailbox: dwalton@cumulusnetworks.com,
aretana@cisco.com,
enkechen@cisco.com,
jgs@juniper.net
Pages: 8
Characters: 17537
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-idr-add-paths-15.txt
URL: https://www.rfc-editor.org/info/rfc7911
DOI: http://dx.doi.org/10.17487/RFC7911
This document defines a BGP extension that allows the advertisement
of multiple paths for the same address prefix without the new paths
implicitly replacing any previous ones. The essence of the extension
is that each path is identified by a Path Identifier in addition to
the address prefix.
This document is a product of the Inter-Domain Routing Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
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