One document matched: draft-li-reg-purge-00.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
	  <!ENTITY RFC3563 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3563.xml">
	  <!ENTITY RFC5304 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5304.xml">
	  ]>

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt'?>
<?rfc strict="yes"?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>

<rfc category="info" docName="draft-li-reg-purge-00"
     ipr="trust200902" updates="3563">

  <front>
    <title abbrev="Registry Extension for Purges">
      IS-IS Registry Extension for Purges
    </title>

    <author initials="T" surname="Li" fullname="Tony Li">
      <organization>Cisco Systems, Inc.</organization>
      <address><postal>
	  <street>170 W. Tasman Dr.</street>
	  <city>San Jose</city><region>CA</region>
	  <code>95134</code><country>USA</country> 
	</postal>
	<email>tony.li@tony.li</email>
      </address>
    </author>

    <date month="August" day="13" year="2010"/>
    <area>Routing</area>
    <workgroup>IS-IS Working Group</workgroup>
    <abstract>
      <t>
	IANA maintains the IS-IS TLV Codepoint Registry.  This registry
	documents which TLVs can appear in different types of IS-IS PDUs,
	but does not document which TLVs can be found in zero Remaining
	Lifetime LSP (a.k.a., purges).  This document extends the existing
	registry to record the set of TLVs that are permissible in purges.
      </t>
    </abstract>
  </front>

  <middle>
    <section anchor="intro" title="Introduction">
      <t>
	The IS-IS <xref target='ISO 10589'/> routing protocol maintains a
	link state database of the topology of its routing domain by
	flooding a set of Link State Protocol Data Units (LSPs).  When the
	protocol no longer needs the information stored in an LSP, it uses
	the purge mechanism to cause the Intermediate Systems (ISes) in its
	domain to discard the information contained in the LSP.  The
	process for generating purges can be found in Section 7.3.16.4 of
	<xref target='ISO 10589'/>.  This process retains only the LSP
	header, discarding any TLVs that had been carried within the LSP.
      </t>
      
      <t>
	Subsequent enhancements to IS-IS, such as <xref target='RFC5304'/>,
	amend the process of generating a purge and allow the inclusion of
	certain TLVs in purges. 
      </t>

      <t>
	This document extends the current IS-IS TLV Codepoint Registry,
	defined in <xref target='RFC3563'/>, to record the set of TLVs that
	can be found in purges.  This will serve as an aid to subsequent
	documents, which can then refer to the registry as the definitive
	list of the TLVs allowed in purges.  This will also act as an aid
	to implementors, providing them with an easily accessible
	compendium of allowable TLVs.
      </t>

    </section>

    <section title="IANA Considerations">
      <t>
	This document requests that IANA modify the IS-IS 'TLV Codepoints
	Registry' by adding a column in the registry for 'Purge'.  A 'y' in
	this column indicates that the TLV for this row can be found in a
	purge.  A 'n' in this column indicates that the TLV for this row
	cannot be found in a purge.
      </t>

      <t>
	The 'Purge' column should initially contain a 'y' for TLV type 10
	(Authentication).  All other entries in this column should have an
	'n'.
      </t>
    </section>

    <section anchor="security" title="Security Considerations">
      <t>
	This document introduces no new security issues.
      </t>
    </section>

    <section title="Acknowledgments">
      <t>
	The author would like to thank Les Ginsberg for provoking this
	effort.
      </t>
    </section>

  </middle>

  <back>
    <references title="Informative References">
      <reference anchor="ISO 10589">
	<front>
          <title>
	    Intermediate system to Intermediate system routeing information
	    exchange protocol for use in conjunction with the Protocol for
	    providing the Connectionless-mode Network Service (ISO
	    8473)
	  </title> 
          <author fullname="ISO">
	    <organization >ISO</organization>
	  </author>
	</front>
        <seriesInfo name="ISO/IEC" value="10589:2002"/>
      </reference>

      &RFC3563;
      &RFC5304;
    </references>
  </back>
</rfc>