|
RFC 2042 |
| TOC |
|
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
Copyright (C) The Internet Society (1997). All Rights Reserved.
|
RFC 2042 |
| TOC |
1.
Process:
2.
Security Considerations
§
References
§
Author's Address
§
Full Copyright Statement
| TOC |
This document describes the process for creating new BGP attribute type codes. Basic attribute type codes are described in RFC 1771, pages 12 through 15. These, and new attribute type codes that are used in the Internet are registered with the IANA.
The actual process will involve the documentation of such attribute type codes in an RFC. There is no intention of segmenting the code space into public/private or IP/OSI or any other sectioning.
As each attribute type code is in the process of being developed, it will use an octet value of 255, which will be reserved for this use. At the time an attribute type code is assigned a number by the IANA, the documetnation and code base will be updated to reflect the authorized attribute type code value.
IANA maintained values will be published in the periodically updated Assigned Numbers RFC [6]. Requests for assignment of a new attribute type code should be sent to the IANA (IANA@IANA.ORG) with a subject that includes the phrase "BGP Attribute Type".
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
| TOC |
Security issues are not discussed in this memo.
| TOC |
| [1] | Rekhter, Y. and T. Li, "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., "R, BGP Route Reflection An alternative to full mesh IBGP", RFC 1998, June 1996. |
| [4] | Chen, E. and T. Bates, "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. |
| [6] | Reynolds, J. and J. Postel, "Assigned Numbers, ISI", STD 2, RFC 1700, October 1994. |
| TOC |
| Bill Manning | |
| USC/ISI | |
| 4676 Admiralty Way | |
| Marina del Rey | |
| CA. 90292 | |
| Phone: | 01.310.822.1511 |
| EMail: | bmanning@isi.edu |
| TOC |
Copyright (C) The Internet Society (1997). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Funding for the RFC Editor function is currently provided by the Internet Society.