RFC 4360 on BGP Extended Communities Attribute
rfc-editor@rfc-editor.org Sat, 04 February 2006 00:24 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5BER-0000cl-TM; Fri, 03 Feb 2006 19:24:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5BEQ-0000bp-3r; Fri, 03 Feb 2006 19:24:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01920; Fri, 3 Feb 2006 19:22:54 -0500 (EST)
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F5BPp-0006LI-Hf; Fri, 03 Feb 2006 19:36:38 -0500
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.8/8.12.8) with ESMTP id k140OV55009686; Fri, 3 Feb 2006 16:24:31 -0800
Received: (from apache@localhost) by nit.isi.edu (8.12.8/8.12.8/Submit) id k140OV5q009685; Fri, 3 Feb 2006 16:24:31 -0800
Date: Fri, 03 Feb 2006 16:24:31 -0800
Message-Id: <200602040024.k140OV5q009685@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="3c3b3ce085c99d862e46b4bcd223ce26"
X-Spam-Score: -13.9 (-------------)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
Cc: idr@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4360 on BGP Extended Communities Attribute
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 4360
Title: BGP Extended Communities Attribute
Author: S. Sangli, D. Tappan,
Y. Rekhter
Status: Standards Track
Date: February 2006
Mailbox: rsrihari@cisco.com,
tappan@cisco.com,
yakov@juniper.net
Pages: 12
Characters: 24145
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-idr-bgp-ext-communities-09.txt
URL: http://www.rfc-editor.org/rfc/rfc4360.txt
This document describes the \"extended community\" BGP-4 attribute. This attribute provides a mechanism for labeling information carried
in BGP-4. These labels can be used to control
the distribution of this information, or for other applications. [STANDARDS TRACK]
This document is a product of the Inter-Domain Routing 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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
A new Request for Comments is now available in online RFC libraries.
RFC 4360
Title: BGP Extended Communities Attribute
Author: S. Sangli, D. Tappan,
Y. Rekhter
Status: Standards Track
Date: February 2006
Mailbox: rsrihari@cisco.com,
tappan@cisco.com,
yakov@juniper.net
Pages: 12
Characters: 24145
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-idr-bgp-ext-communities-09.txt
URL: http://www.rfc-editor.org/rfc/rfc4360.txt
This document describes the \"extended community\" BGP-4 attribute. This attribute provides a mechanism for labeling information carried
in BGP-4. These labels can be used to control
the distribution of this information, or for other applications. [STANDARDS TRACK]
This document is a product of the Inter-Domain Routing 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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce