<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="manet-parameters.xsl"?>
<?oxygen RNGSchema="manet-parameters.rng" type="xml"?>
<registry xmlns="http://www.iana.org/assignments" id="manet-parameters">
  <title>Mobile Ad hoc NETwork (MANET) Parameters</title>
  <created>2008-12-23</created>
  <updated>2013-04-14</updated>
  
  <registry id="message-types">
    <title>Message Types</title>
    <registration_rule>Expert Review</registration_rule>
    <xref type="rfc" data="rfc5444"/>
    <expert>Joe Macker and Stan Ratliff</expert>
    <record>
      <value>0</value>
      <description>HELLO : Local signaling</description>
      <xref type="rfc" data="rfc6130"/>
    </record>    
    <record>
      <value>1</value>
      <description>TC : Topology Control (MANET-wide signaling)</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>
    <record>
      <value>2-223</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>224-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc5444"/>
    </record>
  </registry>  
  
  
    <registry id="tc-message-type-specific-message">
    <title>TC Message-Type-specific Message TLV Types</title>
    <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    <expert>Unassigned</expert>    
    <range>
      <value>0-127</value>
      <registration_rule>Reserved</registration_rule>
      <note>Common to all Message Types, per <xref type="rfc" data="rfc5444"/></note>
    </range>
    <range>
      <value>128-223</value>
      <registration_rule>Expert Review</registration_rule>
    </range>
    <range>
      <value>224-255</value>
      <registration_rule>Reserved</registration_rule>
      <note>Common to all Message Types, per <xref type="rfc" data="rfc5444"/></note>
    </range>
    <record>
      <value>0-127</value>
      <description>Reserved</description>
      <xref type="rfc" data="rfc5444"/>
    </record>
    <record>
      <value>128-223</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>224-255</value>
      <description>Reserved</description>
      <xref type="rfc" data="rfc5444"/>
    </record>
  </registry>  
  
  
    <registry id="tc-message-type-specific-address-block">
    <title>TC Message-Type-specific Address Block TLV Types</title>
    <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    <expert>Unassigned</expert>    
    <range>
      <value>0-127</value>
      <registration_rule>Reserved</registration_rule>
      <note>Common to all Message Types, per <xref type="rfc" data="rfc5444"/></note>
    </range>
    <range>
      <value>128-223</value>
      <registration_rule>Expert Review</registration_rule>
    </range>
    <range>
      <value>224-255</value>
      <registration_rule>Reserved</registration_rule>
      <note>Common to all Message Types, per <xref type="rfc" data="rfc5444"/></note>
    </range>
    <record>
      <value>0-127</value>
      <description>Reserved</description>
      <xref type="rfc" data="rfc5444"/>
    </record>
    <record>
      <value>128-223</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>224-255</value>
      <description>Reserved</description>
      <xref type="rfc" data="rfc5444"/>
    </record>
  </registry>


  <registry id="packet-tlv-types">
    <title>Packet TLV Types</title>
    <xref type="rfc" data="rfc5444"/>
    <registration_rule>Expert Review</registration_rule>
    <expert>Joe Macker and Stan Ratliff</expert>
    <record>
      <value>0-4</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>5</value>
      <description>ICV</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>6</value>
      <description>TIMESTAMP</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>7-223</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>224-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc5444"/>
    </record>
  </registry>


  <registry id="message-tlv-types">
    <title>Message TLV Types</title>
    <xref type="rfc" data="rfc5444"/>
    <expert>Joe Macker and Stan Ratliff</expert>
    <range>
      <value>0-127</value>
      <registration_rule>Expert Review</registration_rule>
    </range>
    <range>
      <value>128-223</value>
      <registration_rule>Expert Review</registration_rule>
      <note>Reserved for Message Type Specific Message TLVs</note>
    </range>
    <range>
      <value>224-255</value>
      <registration_rule>Reserved for Experimental Use</registration_rule>
    </range>
    <record>
      <value>0</value>
      <description>INTERVAL_TIME</description>
      <xref type="rfc" data="rfc5497"/>
    </record>
    <record>
      <value>1</value>
      <description>VALIDITY_TIME</description>
      <xref type="rfc" data="rfc5497"/>
    </record>
    <record>
      <value>2-4</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>5</value>
      <description>ICV</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>6</value>
      <description>TIMESTAMP</description>
      <xref type="rfc" data="rfc6622"/>
    </record>    
    <record>
      <value>7</value>
      <description>MPR_WILLING</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>    
    <record>
      <value>8</value>
      <description>CONT_SEQ_NUM</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>
    <record>
      <value>9-223</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>224-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc5444"/>
    </record>
  </registry>


  <registry id="interval-time-message-type-extension">
    <title>INTERVAL_TIME Message Type Extensions</title>
    <registration_rule>Expert Review</registration_rule>
    <expert>Joe Macker and Stan Ratliff</expert>
    <xref type="rfc" data="rfc5497"/>
    <record>
      <value>0</value>
      <description>The maximum time before another message of the same 
        type as this message from the same originator should be received</description>
      <xref type="rfc" data="rfc5497"/>
    </record>
    <record>
      <value>1-223</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>224-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc5497"/>
    </record>
  </registry>


  <registry id="validity-time-message-type-extension">
    <title>VALIDITY_TIME Message Type Extensions</title>
    <registration_rule>Expert Review</registration_rule>
    <expert>Joe Macker and Stan Ratliff</expert>
    <xref type="rfc" data="rfc5497"/>
    <record>
      <value>0</value>
      <description>The time from receipt of the message during which the  
        information contained in the message is to be considered valid</description>
      <xref type="rfc" data="rfc5497"/>
    </record>
    <record>
      <value>1-223</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>224-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc5497"/>
    </record>
  </registry>
  
  
  <registry id="mpr-willing-message-type-extension">
    <title>MPR_WILLING Message Type Extensions</title>
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    <record>
      <value>0</value>
      <description>Bits 0-3 specify the originating router's willingness to act as a flooding MPR; 
bits 4-7 specify the originating router's willingness to act as a routing MPR.</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>
    <record>
      <value>1-255</value>
      <description>Unassigned</description>
    </record>
  </registry>  
  
  
  <registry id="cont-seq-num-message-type-extension">
    <title>CONT_SEQ_NUM Message Type Extensions</title>
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    <record>
      <value>0</value>
      <description>COMPLETE: Specifies a content sequence number for this complete message.</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>    
    <record>
      <value>1</value>
      <description>INCOMPLETE: Specifies a content sequence number for this incomplete message.</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>
    <record>
      <value>2-255</value>
      <description>Unassigned</description>
    </record>
  </registry>


  <registry id="message-tlv-hello">
    <title>HELLO Message-Type-specific Message TLV Types</title>
    <xref type="rfc" data="rfc6130"/>
    <expert>Unassigned</expert>
    <range>
      <value>0-127</value>
      <registration_rule>Reserved</registration_rule>
      <note>Common to all Message Types, <xref type="rfc" data="rfc5444"/></note>
    </range>
    <range>
      <value>128-223</value>
      <registration_rule>Expert Review</registration_rule>
    </range>
    <range>
      <value>224-255</value>
      <registration_rule>Reserved</registration_rule>
      <note>Common to all Message Types, <xref type="rfc" data="rfc5444"/></note>
    </range>
    <record>
      <value>0-127</value>
      <description>Reserved</description>
      <xref type="rfc" data="rfc5444"/>
    </record>
    <record>
      <value>128</value>
      <description>SMF_TYPE</description>
      <xref type="rfc" data="rfc6621"/>
    </record>
    <record>
      <value>129-223</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>224-255</value>
      <description>Reserved</description>
      <xref type="rfc" data="rfc5444"/>
    </record>
  </registry>
  
  
  <registry id="address-block-tlv-types">
    <title>Address Block TLV Types</title>
    <xref type="rfc" data="rfc5444"/>
    <expert>Joe Macker and Stan Ratliff</expert>
    <range>
      <value>0-127</value>
      <registration_rule>Expert Review</registration_rule>
    </range>
    <range>
      <value>128-223</value>
      <registration_rule>Expert Review</registration_rule>
      <note>Reserved for Message Type Specific Address Block TLVs</note>
    </range>
    <range>
      <value>224-255</value>
      <registration_rule>Reserved for Experimental Use</registration_rule>
    </range>
    <record>
      <value>0</value>
      <description>INTERVAL_TIME</description>
      <xref type="rfc" data="rfc5497"/>
    </record>
    <record>
      <value>1</value>
      <description>VALIDITY_TIME</description>
      <xref type="rfc" data="rfc5497"/>
    </record>
    <record>
      <value>2</value>
      <description>LOCAL_IF</description>
      <xref type="rfc" data="rfc6130"/>
    </record>
    <record>
      <value>3</value>
      <description>LINK_STATUS</description>
      <xref type="rfc" data="rfc6130"/>
    </record>
    <record>
      <value>4</value>
      <description>OTHER_NEIGHB</description>
      <xref type="rfc" data="rfc6130"/>
    </record>
    <record>
      <value>5</value>
      <description>ICV</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>6</value>
      <description>TIMESTAMP</description>
      <xref type="rfc" data="rfc6622"/>
    </record>    
    <record>
      <value>7</value>
      <description>LINK_METRIC</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>    
    <record>
      <value>8</value>
      <description>MPR</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>    
    <record>
      <value>9</value>
      <description>NBR_ADDR_TYPE</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>    
    <record>
      <value>10</value>
      <description>GATEWAY</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>
    <record>
      <value>11-223</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>224-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc5444"/>
    </record>
  </registry>


  <registry id="interval-time-address-block-tlv-type-extension">
    <title>INTERVAL_TIME Address Block TLV Type Extensions</title>
    <registration_rule>Expert Review</registration_rule>
    <expert>Joe Macker and Stan Ratliff</expert>
    <xref type="rfc" data="rfc5497"/>
    <record>
      <value>0</value>
      <description>The maximum time before another message of the same 
        type as this message from the same originator and containing this address should be received</description>
      <xref type="rfc" data="rfc5497"/>
    </record>
    <record>
      <value>1-223</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>224-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc5497"/>
    </record>
  </registry>


  <registry id="validity-time-address-block-tlv-type-extension">
    <title>VALIDITY_TIME Address Block TLV Type Extensions</title>
    <registration_rule>Expert Review</registration_rule>
    <expert>Joe Macker and Stan Ratliff</expert>
    <xref type="rfc" data="rfc5497"/>
    <record>
      <value>0</value>
      <description>The time from receipt of the address during which the  
        information regarding this address is to be considered valid</description>
      <xref type="rfc" data="rfc5497"/>
    </record>
    <record>
      <value>1-223</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>224-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc5497"/>
    </record>
  </registry>


  <registry id="local-if-address-block-tlv-type-extension">
    <title>LOCAL_IF Address Block TLV Type Extensions</title>
    <registration_rule>Expert Review</registration_rule>
    <xref type="rfc" data="rfc6130"/>
    <record>
      <value>0</value>
      <description>Specifies that the network address is associated with this local 
        interface of the sending router (THIS_IF = 0) or another local interface of 
      the sending router (OTHER_IF = 1)</description>
      <xref type="rfc" data="rfc6130"/>
    </record>
    <record>
      <value>1-255</value>
      <description>Unassigned</description>
    </record>
  </registry>


  <registry id="link-status-address-block-tlv-type-extension">
    <title>LINK_STATUS Address Block TLV Type Extensions</title>
    <registration_rule>Expert Review</registration_rule>
    <xref type="rfc" data="rfc6130"/>
    <record>
      <value>0</value>
      <description>Specifies the status of the link from the indicated network 
      address (LOST = 0, SYMMETRIC = 1, or HEARD = 2)</description>
      <xref type="rfc" data="rfc6130"/>
    </record>
    <record>
      <value>1-255</value>
      <description>Unassigned</description>
    </record>
  </registry>
  
  
  <registry id="other-neighb-address-block-tlv-type-extension">
    <title>OTHER_NEIGHB Address Block TLV Type Extensions</title>
    <registration_rule>Expert Review</registration_rule>
    <xref type="rfc" data="rfc6130"/>
    <record>
      <value>0</value>
      <description>Specifies that the network address is (SYMMETRIC = 1) or 
      recently was (LOST = 0) of an interface of a symmetric 1-hop neighbor of 
      the router transmitting the message</description>
      <xref type="rfc" data="rfc6130"/>
    </record>
    <record>
      <value>1-255</value>
      <description>Unassigned</description>
    </record>
  </registry>


  <registry id="link-metric-address-block-tlv-type-extension">
    <title>LINK_METRIC Address Block TLV Type Extensions</title>
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    <record>
      <value>0</value>
      <description>Link metric meaning assigned by administrative action.</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>    
    <record>
      <value>1-223</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>224-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>
  </registry>
  
  
    <registry id="mpr-address-block-tlv-type-extension">
    <title>MPR Address Block TLV Type Extensions</title>
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    <record>
      <value>0</value>
      <description>Specifies that a given network address is of a router selected as a flooding MPR (FLOODING = 1), that a give 
      network address is of a router selected as a routing MPR (ROUTING = 2), or both (FLOOD ROUTE = 3).</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>    
    <record>
      <value>1-255</value>
      <description>Unassigned</description>
    </record>
  </registry>
  
  <registry id="nbr-addr-type-address-block-tlv-type-extension">
    <title>NBR_ADDR_TYPE Address Block TLV Type Extensions</title>
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    <record>
      <value>0</value>
      <description>Specifies that a given network address is of a neighbor reached via the originating 
router, if it is an originator address (ORIGINATOR = 1), is a routable address (ROUTABLE = 2), or if 
it is both (ROUTABLE ORIG = 3).</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>    
    <record>
      <value>1-255</value>
      <description>Unassigned</description>
    </record>
  </registry>
  
 <registry id="gateway-address-block-tlv-type-extension">
    <title>GATEWAY Address Block TLV Type Extensions</title>
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    <record>
      <value>0</value>
      <description>Specifies that a given network address is reached via a gateway on the originating router, 
        with value equal to the number of hops.</description>
      <xref type="draft" data="RFC-ietf-manet-olsrv2-19"/>
    </record>    
    <record>
      <value>1-255</value>
      <description>Unassigned</description>
    </record>
  </registry>


  <registry id="address-tlv-hello">
    <title>HELLO Message-Type-specific Address Block TLV Types</title>
    <xref type="rfc" data="rfc6130"/>
    <range>
      <value>0-127</value>
      <registration_rule>Reserved</registration_rule>
      <note>Common to all Message Types, per <xref type="rfc" data="rfc5444"/></note>
    </range>
    <range>
      <value>128-223</value>
      <registration_rule>Expert Review</registration_rule>
    </range>
    <range>
      <value>224-255</value>
      <registration_rule>Reserved</registration_rule>
      <note>Common to all Message Types, per <xref type="rfc" data="rfc5444"/></note>
    </range>
    <record>
      <value>0-127</value>
      <description>Reserved</description>
      <xref type="rfc" data="rfc5444"/>
    </record>
    <record>
      <value>128</value>
      <description>SMF_NBR_TYPE</description>
      <xref type="rfc" data="rfc6621"/>
    </record>
    <record>
      <value>129-223</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>224-255</value>
      <description>Reserved</description>
      <xref type="rfc" data="rfc5444"/>
    </record>
  </registry>
 
 
  <registry id="icv-packet-tlv-types">
    <title>ICV Packet TLV Type Extensions</title>
    <xref type="rfc" data="rfc6622"/>
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <record>
      <value>0</value>
      <description>ICV of a packet</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>1</value>
      <description>ICV, decomposed into cryptographic function over a hash value, as specified in Section 12 of this document</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>2-251</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>252-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
  </registry>
  

  <registry id="timestamp-packet-tlv-types">
    <title>TIMESTAMP Packet TLV Type Extensions</title>
    <xref type="rfc" data="rfc6622"/>    
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <record>
      <value>0</value>
      <description>Unsigned timestamp of arbitrary length, given by the TLV Length field. The MANET routing protocol has to define how to interpret this timestamp</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>1</value>
      <description>Unsigned 32-bit timestamp, as specified in <xref type="uri" data="http://pubs.opengroup.org/onlinepubs/9699919799/">IEEE 1003.1-2008 (POSIX)</xref></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>2</value>
      <description>NTP timestamp format, as defined in <xref type="rfc" data="rfc5905"/></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>3</value>
      <description>Signed timestamp of arbitrary length with no constraints such as monotonicity. In particular, it may represent any random value</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>4-251</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>252-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
  </registry>
  
  
  <registry id="icv-message-tlv-types">
    <title>ICV Message TLV Type Extensions</title>
    <xref type="rfc" data="rfc6622"/>    
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <record>
      <value>0</value>
      <description>ICV of a message</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>1</value>
      <description>ICV, decomposed into cryptographic function over a hash value, as specified in Section 12 of this document</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>2-251</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>252-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
  </registry>
  

  <registry id="timestamp-message-tlv-types">    
    <title>TIMESTAMP Message TLV Type Extensions</title>    
    <xref type="rfc" data="rfc6622"/>    
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <record>
      <value>0</value>
      <description>Unsigned timestamp of arbitrary length, given by the TLV Length field</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>1</value>
      <description>Unsigned 32-bit timestamp, as specified in <xref type="uri" data="http://pubs.opengroup.org/onlinepubs/9699919799/">IEEE 1003.1-2008 (POSIX)</xref></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>2</value>
      <description>NTP timestamp format, as defined in <xref type="rfc" data="rfc5905"/></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>3</value>
      <description>Signed timestamp of arbitrary length with no constraints such as monotonicity. In particular, it may represent any random value</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>4-251</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>252-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
  </registry>
  
  
  <registry id="icv-address-tlv-types">    
    <title>ICV Address TLV Type Extensions</title>    
    <xref type="rfc" data="rfc6622"/>    
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <record>
      <value>0</value>
      <description>ICV of an object (e.g. an address)</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>1</value>
      <description>ICV, decomposed into cryptographic function over a hash value, as specified in Section 12 of this document</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>2-251</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>252-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
  </registry>
  
  
  <registry id="timestamp-address-tlv-types">    
    <title>TIMESTAMP Address TLV Type Extensions</title>    
    <xref type="rfc" data="rfc6622"/>    
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <record>
      <value>0</value>
      <description>Unsigned timestamp of arbitrary length, given by the TLV Length field</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>1</value>
      <description>Unsigned 32-bit timestamp, as specified in <xref type="uri" data="http://pubs.opengroup.org/onlinepubs/9699919799/">IEEE 1003.1-2008 (POSIX)</xref></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>2</value>
      <description>NTP timestamp format, as defined in <xref type="rfc" data="rfc5905"/></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>3</value>
      <description>Signed timestamp of arbitrary length with no constraints such as monotonicity. In particular, it may represent any random value</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>4-251</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>252-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
  </registry>
  
  
  <registry id="hash-functions">    
    <title>Hash Functions</title>    
    <xref type="rfc" data="rfc6622"/>    
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <record>
      <value>0</value>
      <algorithm>none</algorithm>
      <description>The "identity function": The hash value of an object is the object itself</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>1</value>
      <algorithm>SHA1</algorithm>
      <description><xref type="uri" data="http://csrc.nist.gov/publications/fips/fips180-2/fips180-2.pdf">NIST-FIPS-180-2</xref></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>2</value>
      <algorithm>SHA224</algorithm>
      <description><xref type="uri" data="http://csrc.nist.gov/publications/fips/fips180-2/fips180-2withchangenotice.pdf">NIST-FIPS-180-2-change</xref></description>
        <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>3</value>
      <algorithm>SHA256</algorithm>
      <description><xref type="uri" data="http://csrc.nist.gov/publications/fips/fips180-2/fips180-2.pdf">NIST-FIPS-180-2</xref></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>4</value>
      <algorithm>SHA384</algorithm>
      <description><xref type="uri" data="http://csrc.nist.gov/publications/fips/fips180-2/fips180-2.pdf">NIST-FIPS-180-2</xref></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>5</value>
      <algorithm>SHA512</algorithm>
      <description><xref type="uri" data="http://csrc.nist.gov/publications/fips/fips180-2/fips180-2.pdf">NIST-FIPS-180-2</xref></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>6-251</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>252-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
  </registry>
  

  <registry id="cryptographic-algorithm">    
    <title>Cryptographic Functions</title>   
    <xref type="rfc" data="rfc6622"/>    
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>
    <record>
      <value>0</value>
      <algorithm>none</algorithm>
      <description>The "identity function": The value of an encrypted hash is the hash itself</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>1</value>
      <algorithm>RSA</algorithm>
      <description><xref type="rfc" data="rfc3447"/></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>2</value>
      <algorithm>DSA</algorithm>
      <description><xref type="uri" data="http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf">NIST-FIPS-186-3</xref></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>3</value>
      <algorithm>HMAC</algorithm>
      <description><xref type="rfc" data="rfc2104"/></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>4</value>
      <algorithm>3DES</algorithm>
      <description><xref type="uri" data="http://csrc.nist.gov/publications/nistpubs/800-67/SP800-67.pdf">NIST-SP-800-67</xref></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>5</value>
      <algorithm>AES</algorithm>
      <description><xref type="uri" data="http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf">NIST-FIPS-197</xref></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>6</value>
      <algorithm>ECDSA</algorithm>
      <description><xref type="uri" data="http://webstore.ansi.org/RecordDetail.aspx?sku=ANSI+X9.62:2005">ANSI-X9-62-2005</xref></description>
      <xref type="rfc" data="rfc6622"/>
    </record>
    <record>
      <value>7-251</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>252-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc6622"/>
    </record>
  </registry>
  
  
  <registry id="smf-type-extensions">    
    <title>SMF_TYPE Message TLV Type Extensions</title>
    <xref type="rfc" data="rfc6621"/>  
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>    
    <note>Specifies relay algorithm supported by the SMF router, 
originating the HELLO message, according to Section 11.4.4.</note>
    <record>
      <value>0-127</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>128-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc6621"/>
    </record>
  </registry>
  
  
  <registry id="smf-nbr-types">    
    <title>SMF_NBR_TYPE Address Block TLV Type Extensions</title>
    <xref type="rfc" data="rfc6621"/>    
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert>  
    <note>Specifies relay algorithm supported by the SMF router corresponding 
to the advertised address, according to Section 11.4.4.</note>
    <record>
      <value>0-127</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>128-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc6621"/>
    </record>
  </registry>
  
  
  <registry id="smf-relay-ids">    
    <title>SMF Relay Algorithm IDs</title>
    <xref type="rfc" data="rfc6621"/>    
    <registration_rule>Expert Review</registration_rule>
    <expert>Unassigned</expert> 
    <note>A specification requesting an allocation from the 4-127 range from 
the SMF Relay Algorithm ID Registry MUST specify the interpretation of 
the &lt;value&gt; field (if any).</note>
    <record>
      <value>0</value>
      <name>CF</name>
      <description>Section 4</description>
      <xref type="rfc" data="rfc6621"/>
    </record>
    <record>
      <value>1</value>
      <name>S-MPR</name>
      <description>Appendix B</description>
      <xref type="rfc" data="rfc6621"/>
    </record>
    <record>
      <value>2</value>
      <name>E-CDS</name>
      <description>Appendix A</description>
      <xref type="rfc" data="rfc6621"/>
    </record>
    <record>
      <value>3</value>
      <name>MPR-CDS</name>
      <description>Appendix C</description>
      <xref type="rfc" data="rfc6621"/>
    </record>
    <record>
      <value>4-127</value>
      <description>Unassigned</description>
    </record>
    <record>
      <value>128-255</value>
      <description>Reserved for Experimental Use</description>
      <xref type="rfc" data="rfc6621"/>
    </record>
  </registry>
  
  <people/>
</registry>
