RFC 5701 on IPv6 Address Specific BGP Extended Community Attribute
rfc-editor@rfc-editor.org Tue, 24 November 2009 00:35 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 712353A6AFF; Mon, 23 Nov 2009 16:35:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.13
X-Spam-Level:
X-Spam-Status: No, score=-17.13 tagged_above=-999 required=5 tests=[AWL=-0.131, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
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 L8Uu3+pG6SxG; Mon, 23 Nov 2009 16:35:54 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id AC5983A6AE6; Mon, 23 Nov 2009 16:35:54 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 4E61E372B7E; Mon, 23 Nov 2009 16:30:41 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5701 on IPv6 Address Specific BGP Extended Community Attribute
From: rfc-editor@rfc-editor.org
Message-Id: <20091124003041.4E61E372B7E@bosco.isi.edu>
Date: Mon, 23 Nov 2009 16:30:41 -0800
Cc: l3vpn@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Nov 2009 00:35:55 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 5701
Title: IPv6 Address Specific BGP Extended
Community Attribute
Author: Y. Rekhter
Status: Standards Track
Date: November 2009
Mailbox: yakov@juniper.net
Pages: 5
Characters: 9626
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-l3vpn-v6-ext-communities-02.txt
URL: http://www.rfc-editor.org/rfc/rfc5701.txt
Current specifications of BGP Extended Communities (RFC 4360)
support the IPv4 Address Specific Extended Community, but do not
support an IPv6 Address Specific Extended Community. The lack of an IPv6 Address Specific Extended Community may be a problem when an application
uses the IPv4 Address Specific Extended Community, and one wants to use
this application in a pure IPv6 environment. This document defines
a new BGP attribute, the IPv6 Address Specific Extended Community, that
addresses this problem. The IPv6 Address Specific Extended Community
is similar to the IPv4 Address Specific Extended Community, except
that it carries an IPv6 address rather than an IPv4 address. [STANDARDS
TRACK]
This document is a product of the Layer 3 Virtual Private Networks Working Group of the IETF.
This is now a Proposed Standard Protocol.
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 Internet
Official Protocol Standards (STD 1) 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
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
USC/Information Sciences Institute