<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
     which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
     There has to be one entity for each item to be referenced. 
     An alternate method (rfc include) is described in the references. -->

<!ENTITY RFC1863 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1863.xml">
<!ENTITY RFC4223 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4223.xml">
<!ENTITY RFC4456 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4456.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs), 
     please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
     (Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="no"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space 
     (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="info" docName="draft-ietf-idr-deprecate-dpa-etal-00" ipr="trust200902">
  <!-- category values: std, bcp, info, exp, and historic
     ipr values: full3667, noModification3667, noDerivatives3667
     you can add the attributes updates="NNNN" and obsoletes="NNNN" 
     they will automatically be output with "(if approved)" -->

  <!-- ***** FRONT MATTER ***** -->

  <front>
    <!-- The abbreviated title is used in the page header - it is only necessary if the 
         full title is longer than 39 characters -->

    <title abbrev="Deprecation of DPA et al">Deprecation of BGP Path Attributes
           DPA, ADVERTISER and RCID_PATH&nbsp;/&nbsp;CLUSTER_ID</title>

    <!-- add 'role="editor"' below for the editors if appropriate -->

    <!-- Another author who claims to be an editor -->

    <author fullname="John Scudder" initials="J."
            surname="Scudder">
      <organization>Juniper Networks</organization>

      <address>
        <postal>
          <street>1194 N. Mathilda Ave</street>

          <!-- Reorder these if your country does things differently -->

          <city>Sunnyvale</city>

          <region>CA</region>

          <code>94089</code>

          <country>USA</country>
        </postal>

        <email>jgs@juniper.net</email>

        <!-- uri and facsimile elements may also be added -->
      </address>
    </author>


    <date year="2012" />

    <!-- If the month and year are both specified and are the current ones, xml2rfc will fill 
         in the current day for you. If only the current year is specified, xml2rfc will fill 
	 in the current day and month for you. If the year is not the current one, it is 
	 necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the 
	 purpose of calculating the expiry date).  With drafts it is normally sufficient to 
	 specify just the year. -->

    <!-- Meta-data Declarations -->

    <area>General</area>

    <workgroup>Internet Engineering Task Force</workgroup>

    <!-- WG name at the upperleft corner of the doc,
         IETF is fine for individual submissions.  
	 If this element is not present, the default is "Network Working Group",
         which is used by the RFC Editor as a nod to the history of the IETF. -->

    <keyword>BGP</keyword>

    <!-- Keywords will be incorporated into HTML output
         files in a meta tag but they have no effect on text or nroff
         output. If you submit your draft to the RFC Editor, the
         keywords will be used for the search engine. -->

    <abstract>
      <t>This document requests IANA to deprecate the BGP path
      attributes DPA, ADVERTISER, and RCID_PATH / CLUSTER_ID, associated 
      with an abandoned Internet Draft and a Historic RFC, respectively.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t>
    As of this writing the BGP Path Attributes registry maintained
    by IANA contains entries for DPA, ADVERTISER, and RCID_PATH / CLUSTER_ID.
    The first of these is associated with <xref target="draft-ietf-idr-bgp-dpa-05"></xref>,
    an Internet Draft that was abandoned in 1996.
    The latter are associated with <xref target="RFC1863"></xref>, an RFC that 
    was reclassified as Historic by <xref target="RFC4223"></xref> in 2005.  Neither of these specifications is
    in use now, nor ever was.
      </t>
      <t>
    Note that the deprecated CLUSTER_ID is distinct from CLUSTER_LIST
    <xref target="RFC4456"></xref>. CLUSTER_LIST is not being deprecated.
      </t>
    </section>
    
    <section title="IANA Considerations">
      <t>
    This document requests IANA to mark the BGP Path Attributes registry
    entries for DPA (Value 11), ADVERTISER (Value 12), and RCID_PATH / 
    CLUSTER_ID (Value 13) as "Deprecated".
      </t>
    </section>
    
    <section title="Security Considerations">
      <t>
    There are no meaningful security consequences arising from this registry
    update.
      </t>
    </section>
  </middle>

  <!--  *****BACK MATTER ***** -->

  <back>
    <!-- References split into informative and normative -->

    <!-- There are 2 ways to insert reference entries from the citation libraries:
     1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
     2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
        (for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")

     Both are cited textually in the same manner: by using xref elements.
     If you use the PI option, xml2rfc will, by default, try to find included files in the same
     directory as the including file. You can also define the XML_LIBRARY environment variable
     with a value containing a set of directories to search.  These can be either in the local
     filing system or remote ones accessed by http (http://domain/dir/... ).-->

    <references title="Informative References">
      &RFC1863;
      &RFC4223;
      &RFC4456;
      <reference anchor="draft-ietf-idr-bgp-dpa-05">
        <!-- the following is the minimum to make xml2rfc happy -->

        <front>
          <title>Destination Preference Attribute for BGP</title>

          <author initials="E." surname="Chen">
            <organization></organization>
          </author>
          <author initials="T." surname="Bates">
            <organization></organization>
          </author>

          <date year="1996" />
        </front>
      </reference>

    </references>
  </back>
</rfc>
