<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629xslt\rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC5226 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">
<!ENTITY RFC4601 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4601.xml">
<!ENTITY RFC5384 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5384.xml">
<!ENTITY RFC3692 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3692.xml">





]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="no"?>
<?rfc compact="yes"?>
<rfc category="std" docName="draft-atwood-pim-reserve-exp-00"
     ipr="trust200811">
  <front>
    <title abbrev="IANA Allocation of Experimental Code Points">IANA Allocation of Experimental Code Points for PIM Join Attribute and PIM Encoded-Source Address</title>


<author fullname="William Atwood" initials="W." surname="Atwood">
			<organization>Concordia University/CSE</organization>
			<address>
				<postal>
					<street>1455 de Maisonneuve Blvd, West</street>
					<city>Montreal</city>
					<region>QC</region>
					<code>H3G 1M8</code>
					<country>Canada</country>
				</postal>
				<phone>+1(514)848-2424 ext3046</phone>
				<email>william.atwood@concordia.ca</email>
				<uri>http://users.encs.concordia.ca/~bill</uri>
			</address>
		</author>
    <author fullname="Stig Venaas" initials="S." surname="Venaas">
      <organization>Cisco</organization>
			<address>
				<postal>
					<street>170 West Tasman Drive</street>
					<city>San Jose</city>
					<region>CA</region>
					<code>95134</code>
					<country>USA</country>
				</postal>
				<email>stig@cisco.com</email>
			</address>
	</author>	
    <date day="03" month="March" year="2014" />

    <area>Routing</area>

    <workgroup>PIM</workgroup>

    <abstract>
      <t>This memo asks the IANA to allocate experimental code points to the PIM Join Attribute Types register and the Encoded-Source Address Encoding Type Field register. </t>
    </abstract>
  </front>

  <middle>
    <section anchor="Introl" title="Introduction">
      <t>To make it possible to experiment with protocol extensions safely, <xref target="RFC3692"></xref> recommends that "protocol documents should consider reserving a small set of protocol
   numbers for experimentation."</t>
   <t>Two IANA registries related to Protocol Independent Multicast (PIM) do not reserve any numbers for experimentation.</t>
   <t>This document requests the IANA to reserve two numbers for the Registry "PIM Join Attribute Types" and four numbers for the "Encoded-Source Address Encoding Type Field".</t>

     

		<section title="Terminology">
			<t>The key words "MUST", "MUST NOT", "REQUIRED",
      "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
      "OPTIONAL" in this document are to be interpreted as described in <xref target="RFC2119">RFC 2119</xref>.</t>
		</section>
	</section>	
      <section anchor="Background" title="Background" >
      <t>In the Protocol Independent Multicast (PIM) Parameters [URL] Protocol Registry, two sub-registries have no allocation for either Private or Experimental use.  They are "Encoded-Source Address Encoding Type Field", for which the current definitions are given in <xref target="RFC4601"></xref> and <xref target="RFC5384"></xref>, and "PIM Join Attribute Types", for which the current definitions are given in <xref target="RFC5384"></xref>.</t>
      <t>For the Encoded-Source Address Encoding Type Field, two values area assigned, and the remainder (2-255) are unassigned.</t>
      <t>For the PIM Join Attribute Types, four values are assigned, and the remainder (4-63) are unassigned.</t>
      <t>The remaining sub-registries all have values assigned for Private Use, for Experimental Use, or for extension of the type space.</t>
      <t>The registrations proposed in this document are of type Experimental <xref target="RFC5226"></xref>, because the expected usage of these reservations would not likely be confined to a single site.</t>
      </section>
      <section title="Security Considerations">
      <t>This document only assigns values in two IANA registries.  The security implications of the use of these values must be considered by those who make use of them.</t>      
      </section>
      <section title="IANA Considerations">
      <t>The requests in this document are for two registries that are part of the "Protocol Independent Multicast (PIM) Parameters" Registry.</t>
      <t>This document requests the IANA to reserve four values in the "Encoded-Source Address Encoding Type Field" registry:
      </t>
      <t>
				<figure>
					<preamble></preamble>
					<artwork><![CDATA[
 Type          Name                      Reference
 ----          ----                      ---------
 251-255       Reserved (Experimental)   [RFC4601][RFC5384][this doc]
 ]]></artwork>
					<postamble></postamble>
				</figure>
			</t>
			<t>This document requests the IANA to reserve two values in the "PIM Join Attribute Types" registry:
      </t>
      <t>
				<figure>
					<preamble></preamble>
					<artwork><![CDATA[
 Type          Name                      Reference
 ----          ----                      ---------
 64-65         Reserved (Experimental)   [RFC5384][this doc]
 ]]></artwork>
					<postamble></postamble>
				</figure>
			</t>
			

      
      <t></t>
    </section>

    <section title="Acknowledgements">
      <t>Adrian Farrel and Brian Haberman observed that there were no reservations for Experimental Use for the PIM Join Attribute Type.</t>

      <t></t>

      
    </section>

    
  </middle>

  <back>
    <references title="Normative References">
      &RFC2119;

      &RFC4601;
      
      &RFC5384;
      
      
    </references>

    <references title="Informative References">
      
      &RFC3692;
      
      &RFC5226;
      
      
    </references>
  </back>
</rfc>
