<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>

<!--
     ASCII to XML transformation by Invisible Worlds, Inc.
     http://invisible.net/
     Last transformation: 03-Feb-1999, 02:08:25

     Cannonical version of this document is at:
     http://info.internet.isi.edu/in-notes/rfc/files/rfc2042.txt

     Implementors should verify all content with
     cannonical version.  Failure to do so may result in
     protocol failures.
-->

<rfc number="2042"
     category="info">
<front>
<title abbrev="BGP Atrribute Types">Registering New BGP Attribute Types</title>
<author initials="B." surname="Manning" fullname="Bill Manning">
<organization>USC/ISI</organization>
<address>
<postal>
<street>4676 Admiralty Way</street>
<street>Marina del Rey</street>
<street>CA. 90292</street>
</postal>
<phone>01.310.822.1511</phone>
<email>bmanning@isi.edu</email>
</address>
</author>
<date month="January" year="1997"/>
<keyword>border gateway protocol</keyword>
</front>
<middle>
<section title="Process:">
<t>
   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.
</t>
<t>

   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.
</t>
<t>

   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.
</t>
<t>

   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".
</t>
<t>

   Currently in use attribute type codes are listed below:
</t>
<figure><artwork>
                 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
</artwork></figure>
</section>

<section title="Security Considerations">
<t>
   Security issues are not discussed in this memo.
</t>
</section>
</middle>
<back>
<!-- BEGIN INCLUDE REFERENCES ** DO NOT REMOVE -->
<references>
<reference anchor="_XREF_1">
<front>
<title>A Border Gateway Protocol 4 (BGP-4</title>
<author initials="Y." surname="Rekhter" fullname="Y. Rekhter">
<organization/>
</author>
<author initials="T." surname="Li" fullname="T. Li">
<organization/>
</author>
<date month="March" year="1995"/>
</front>
<seriesInfo>RFC 1771</seriesInfo>
</reference>
<reference anchor="_XREF_2">
<front>
<title>BGP Communities Attribute</title>
<author initials="R." surname="Chandra" fullname="R. Chandra">
<organization/>
</author>
<author initials="P." surname="Traina" fullname="P. Traina">
<organization/>
</author>
<author initials="T." surname="Li" fullname="T. Li">
<organization/>
</author>
<date month="August" year="1996"/>
</front>
<seriesInfo>RFC 1997</seriesInfo>
</reference>
<reference anchor="_XREF_3">
<front>
<title abbrev="R">R, BGP Route Reflection An alternative to full mesh IBGP</title>
<author initials="T." surname="Bates" fullname="T. Bates">
<organization/>
</author>
<date month="June" year="1996"/>
</front>
<seriesInfo>RFC 1998</seriesInfo>
</reference>
<reference anchor="_XREF_4">
<front>
<title abbrev="Destination Preference Attribute for BGP">Destination Preference Attribute for BGP,  Work in progress</title>
<author initials="E." surname="Chen" fullname="E. Chen">
<organization/>
</author>
<author initials="T." surname="Bates" fullname="T. Bates">
<organization/>
</author>
<date month="March" year="1996"/>
</front>
</reference>
<reference anchor="_XREF_5">
<front>
<title abbrev="A BGP/IDRP Route Server alternative to">A BGP/IDRP Route Server alternative to a full mesh routing</title>
<author initials="D." surname="Haskin" fullname="D. Haskin">
<organization/>
</author>
<date month="October" year="1995"/>
</front>
<seriesInfo>RFC 1863</seriesInfo>
</reference>
<reference anchor="_XREF_6">
<front>
<title>Assigned Numbers,  ISI</title>
<author initials="J." surname="Reynolds" fullname="J. Reynolds">
<organization/>
</author>
<author initials="J." surname="Postel" fullname="J. Postel">
<organization/>
</author>
<date month="October" year="1994"/>
</front>
<seriesInfo>STD 2</seriesInfo>
<seriesInfo>RFC 1700</seriesInfo>
</reference>
</references>
<!-- END INCLUDE REFERENCES ** DO NOT REMOVE -->
</back>
</rfc>
