BGP Communities to Proposed Standard
Yakov Rekhter <yakov@cisco.com> Fri, 12 April 1996 15:35 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15919; 12 Apr 96 11:35 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa15914; 12 Apr 96 11:35 EDT
Received: from p-o.ans.net by CNRI.Reston.VA.US id aa08998; 12 Apr 96 11:35 EDT
Received: (from majordom@localhost) by p-o.ans.net (8.7.5/8.7.3) id PAA37085 for bgp-outgoing; Fri, 12 Apr 1996 15:19:32 GMT
X-Authentication-Warning: p-o.ans.net: majordom set sender to bgp-owner using -f
Message-Id: <199604121519.IAA16633@hubbub.cisco.com>
To: bgp@ans.net
Subject: BGP Communities to Proposed Standard
Date: Fri, 12 Apr 1996 08:19:23 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Yakov Rekhter <yakov@cisco.com>
X-Orig-Sender: bgp-owner@ans.net
Precedence: bulk
Reply-To: bgp@ans.net
Folks, At the last WG meeting we discussed BGP Communities attribute and agreed to ask the IESG to publish it as a Proposed Standard. There are two independent implementations of this attribute (BayNetworks and Cisco). This is the WG last call on this document. If there will be no objections within 2 weeks (4/26/96), I'll send a note to the IESG asking the IESG to advance the Internet Draft to a Proposed Standard. Yakov. ------- Forwarded Message Return-Path: ietf-announce-request@IETF.CNRI.Reston.VA.US Received: from beasley.cisco.com (beasley.cisco.com [171.69.2.135]) by puli.cisco.com (8.6.8+c/8.6.5) with ESMTP id GAA03071; Thu, 11 Apr 1996 06:17:52 -0700 Received: from IETF.cnri.reston.VA.US (ietf.cnri.reston.va.us [132.151.1.35]) by beasley.cisco.com (8.6.12/CISCO.GATE.1.1) with SMTP id GAA00896; Thu, 11 Apr 1996 06:17:00 -0700 Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13384; 11 Apr 96 9:11 EDT Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa13314; 11 Apr 96 9:09 EDT Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce:; Cc: bgp@ans.net Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US From: Internet-Drafts@CNRI.Reston.VA.US Reply-To: Internet-Drafts@CNRI.Reston.VA.US Subject: I-D ACTION:draft-ietf-idr-communities-00.txt Date: Thu, 11 Apr 96 09:09:52 -0400 X-Orig-Sender: cclark@CNRI.Reston.VA.US Message-Id: <9604110909.aa13314@IETF.CNRI.Reston.VA.US> - --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing Working Group of the IETF. Title : BGP communities attribute Author(s) : R. Chandra, P. Traina, T. Li Filename : draft-ietf-idr-communities-00.txt Pages : 5 Date : 04/10/1996 Border Gateway Protocol [1] is an inter-autonomous system routing protocol designed for TCP/IP internets. This document describes an extension to BGP which may be used to pass additional information to both neighboring and remote BGP peers. The intention of the proposed technique is to aid in policy administration and reduce the management complexity of maintaining the Internet. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-idr-communities-00.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-idr-communities-00.txt Internet-Drafts directories are located at: o Africa Address: ftp.is.co.za (196.4.160.8) o Europe Address: nic.nordu.net (192.36.148.17) Address: ftp.nis.garr.it (193.205.245.10) o Pacific Rim Address: munnari.oz.au (128.250.1.21) o US East Coast Address: ds.internic.net (198.49.45.10) o US West Coast Address: ftp.isi.edu (128.9.0.32) Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-idr-communities-00.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e., documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. For questions, please mail to Internet-Drafts@cnri.reston.va.us. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. - --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" - --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19960410143533.I-D@CNRI.Reston.VA.US> ENCODING mime FILE /internet-drafts/draft-ietf-idr-communities-00.txt - --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-communities-00.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19960410143533.I-D@CNRI.Reston.VA.US> - --OtherAccess-- - --NextPart-- ------- End of Forwarded Message
- BGP Communities to Proposed Standard Yakov Rekhter
- Re: BGP Communities to Proposed Standard Tony Bates
- Re: BGP Communities to Proposed Standard Sean Doran
- Re: BGP Communities to Proposed Standard Tony Bates
- Re: BGP Communities to Proposed Standard Yakov Rekhter
- Re: BGP Communities to Proposed Standard Sean Doran
- Re: BGP Communities to Proposed Standard Dorian Kim
- BGP Communities to Proposed Standard Yakov Rekhter