Re: draft-manning-bgpattrib-type-00.txt as Informational RFC
bmanning@isi.edu Fri, 30 August 1996 23:53 UTC
Received: from ietf.org by ietf.org id aa18883; 30 Aug 96 19:53 EDT
Received: from cnri by ietf.org id aa18879; 30 Aug 96 19:53 EDT
Received: from merit.edu by CNRI.Reston.VA.US id aa15485; 30 Aug 96 19:53 EDT
Received: (from daemon@localhost) by merit.edu (8.7.5/merit-2.0) id TAA08142
for idr-outgoing; Fri, 30 Aug 1996 19:26:16 -0400 (EDT)
Received: from interlock.ans.net (interlock.ans.net [147.225.5.5]) by
merit.edu (8.7.5/merit-2.0) with SMTP id TAA08136 for <bgp@merit.edu>;
Fri, 30 Aug 1996 19:26:13 -0400 (EDT)
Sender: ietf-archive-request@ietf.org
From: bmanning@isi.edu
Received: by interlock.ans.net id AA28283
(InterLock SMTP Gateway 3.0 for bgp@ans.net);
Fri, 30 Aug 1996 19:26:12 -0400
Received: by interlock.ans.net (Internal Mail Agent-2);
Fri, 30 Aug 1996 19:26:12 -0400
Posted-Date: Fri, 30 Aug 1996 16:24:35 -0700 (PDT)
Message-Id: <199608302324.AA02454@zed.isi.edu>
Received: by interlock.ans.net (Internal Mail Agent-1);
Fri, 30 Aug 1996 19:26:12 -0400
Subject: Re: draft-manning-bgpattrib-type-00.txt as Informational RFC
To: Tony Bates <tbates@cisco.com>
Date: Fri, 30 Aug 1996 16:24:35 -0700 (PDT)
Cc: yakov@cisco.com, jhalpern@newbridge.com, bgp@ans.net
In-Reply-To: <199608302254.PAA13135@trix.cisco.com> from "Tony Bates" at Aug
30, 96 03:54:48 pm
X-Mailer: ELM [version 2.4 PL25]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Orig-Sender: owner-idr@merit.edu
Precedence: bulk
done and done. any other comment before draft-01? > > > Yakov Rekhter <yakov@cisco.com> writes: > * Joel, > * > * The IDR WG would like to ask the IESG to publish > * draft-manning-bgpattrib-type-00.txt as an Informational RFC. > * > * Yakov. > > Actually....I think it might be useful to at least clarify the doument > with a few references and also use the actual names of the > attributes. This is just an editorial nit but we may as well do it. > Here's the patch for the text. > > --Tony > > *** draft-manning-bgpattrib-type-00.txt Fri Aug 30 12:59:15 1996 > --- draft-manning-bgpattrib-type-00.txt.new Fri Aug 30 15:51:05 1996 > *************** > *** 53,71 **** > Currently in use attribute type codes are listed below: > > > ! 1 origin > ! 2 as path > ! 3 next hop > ! 4 multi exit disc. > ! 5 local preference > ! 6 atomic aggregate > ! 7 aggregator > ! 8 community cisco ID > ! 9 originator cisco ID > ! 10 cluster list cisco ID > ! 11 destination preference MCI ID > ! 12 advertiser Bay ID > ! 13 rcid_path (cluster id) Bay ID > ... > 255 reserved for development > > --- 53,73 ---- > Currently in use attribute type codes are listed below: > > > ! Value Code Reference > ! > ! 1 ORIGIN [1] > ! 2 AS_PATH [1] > ! 3 NEXT_HOP [1] > ! 4 MULTI_EXIT_DISC [1] > ! 5 LOCAL_PREF [1] > ! 6 ATOMIC_AGGREGATE [1] > ! 7 AGGREGATOR [1] > ! 8 COMMUNITY [2] > ! 9 ORIGINATOR_ID [3] > ! 10 CLUSTER_LIST [3] > ! 11 DPA [4] > ! 12 ADVERTISER [5] > ! 13 RCID_PATH / CLUSTER_ID [5] > ... > 255 reserved for development > > *************** > *** 73,78 **** > --- 75,99 ---- > Security considerations of this memo > > None. > + > + > + References > + > + [1] Rekhter, Y., and Li, T., "A Border Gateway Protocol 4 (BGP-4)", > + RFC 1771, March 1995. > + > + [2] Chandra, R., Traina, P., and T. Li, "BGP Communities > + Attribute", RFC 1997, August 1996. > + > + [3] Bates, T., Chandra, R, "BGP Route Reflection An alternative > + to full mesh IBGP", RFC 1998, June 1996. > + > + [4] Chen, E., Bates, T., "Destination Preference Attribute for BGP", > + Work in progress, March 1996. > + > + [5] Haskin, D., "A BGP/IDRP Route Server alternative to a full mesh > + routing", RFC 1863, October 1995. > + > > Authors' Addresses > > > -- --bill