Re: draft-manning-bgpattrib-type-00.txt as Informational RFC
Tony Bates <tbates@cisco.com> Fri, 30 August 1996 23:25 UTC
Received: from ietf.org by ietf.org id aa18317; 30 Aug 96 19:25 EDT
Received: from cnri by ietf.org id aa18313; 30 Aug 96 19:25 EDT
Received: from merit.edu by CNRI.Reston.VA.US id aa15227; 30 Aug 96 19:25 EDT
Received: (from daemon@localhost) by merit.edu (8.7.5/merit-2.0) id SAA07739
for idr-outgoing; Fri, 30 Aug 1996 18:54:56 -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 SAA07734 for <bgp@merit.edu>;
Fri, 30 Aug 1996 18:54:53 -0400 (EDT)
Received: by interlock.ans.net id AA27728
(InterLock SMTP Gateway 3.0 for bgp@ans.net);
Fri, 30 Aug 1996 18:54:51 -0400
Received: by interlock.ans.net (Internal Mail Agent-1);
Fri, 30 Aug 1996 18:54:51 -0400
Message-Id: <199608302254.PAA13135@trix.cisco.com>
To: Yakov Rekhter <yakov@cisco.com>
Cc: jhalpern@newbridge.com, bgp@ans.net
Subject: Re: draft-manning-bgpattrib-type-00.txt as Informational RFC
In-Reply-To: Your message of Thu, 29 Aug 1996 09:33:52 PDT.
<199608291637.JAA20995@hubbub.cisco.com>
Sender: ietf-archive-request@ietf.org
From: Tony Bates <tbates@cisco.com>
X-Phone: +1 408 527 2470
Date: Fri, 30 Aug 1996 15:54:48 -0700
X-Orig-Sender: owner-idr@merit.edu
Precedence: bulk
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