<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="isakmp-registry.xsl"?>
<?xml-model href="isakmp-registry.rng" schematypens="http://relaxng.org/ns/structure/1.0" ?>
<registry xmlns="http://www.iana.org/assignments" id="isakmp-registry">
  <title>"Magic Numbers" for ISAKMP Protocol</title>
  <updated>2023-04-25</updated>

  <note>All registries listed below have been closed. See <xref type="rfc" data="rfc9395"/>. 
  </note>

  <registry id="isakmp-registry-1">
    <title>IPSEC Situation Definition</title>
    <xref type="rfc" data="rfc2407"/>
    <xref type="rfc" data="rfc9395"/>
    <registration_rule>Registry closed</registration_rule>
    <note>The Situation Definition is a 32-bit bitmask which represents the
environment under which the IPSEC SA proposal and negotiation is
carried out.  Requests for assignments of new situations must be
accompanied by an RFC which describes the interpretation for the
associated bit.

If the RFC is not on the standards-track (i.e., it is an informational
or experimental RFC), it must be explicitly reviewed and approved by
the IESG before the RFC is published and the transform identifier is
assigned.

The upper two bits are reserved for private use amongst cooperating
systems.
    </note>
    <record>
      <value>0x01</value>
      <name>SIT_IDENTITY_ONLY</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>0x02</value>
      <name>SIT_SECRECY</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>0x04</value>
      <name>SIT_INTEGRITY</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
  </registry>
  
  <registry id="isakmp-registry-3">
    <title>IPSEC Security Protocol Identifiers</title>
    <xref type="rfc" data="rfc2407"/>
    <xref type="rfc" data="rfc9395"/>
    <note>The Security Protocol Identifier is an 8-bit value which identifies a
security protocol suite being negotiated.  Requests for assignments of
new security protocol identifiers must be accompanied by an RFC which
describes the requested security protocol.  <xref type="text">AH</xref> and <xref type="text">ESP</xref> are
examples of security protocol documents.

If the RFC is not on the standards-track (i.e., it is an informational
or experimental RFC), it must be explicitly reviewed and approved by
the IESG before the RFC is published and the transform identifier is
assigned.
    </note>
    <registration_rule>Registry closed</registration_rule>
    <record>
      <value>0</value>
      <name>RESERVED</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>1</value>
      <name>PROTO_ISAKMP</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>2</value>
      <name>PROTO_IPSEC_AH</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>3</value>
      <name>PROTO_IPSEC_ESP</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>4</value>
      <name>PROTO_IPCOMP</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>5</value>
      <name>PROTO_GIGABEAM_RADIO</name>
      <xref type="rfc" data="rfc4705"/>
    </record>
    <record>
      <value>6-248</value>
      <name>Unassigned</name>
    </record>
    <record>
      <value>249-255</value>
      <name>Reserved for private use</name>
    </record>
  </registry>

  <registry id="isakmp-registry-5">
    <title>IPSEC ISAKMP Transform Identifiers</title>
    <xref type="rfc" data="rfc2407"/>
    <xref type="rfc" data="rfc9395"/>
    <note>The IPSEC ISAKMP Transform Identifier is an 8-bit value which
identifies a key exchange protocol to be used for the negotiation.
Requests for assignments of new ISAKMP transform identifiers must be
accompanied by an RFC which describes the requested key exchange
protocol.  <xref type="text">IKE</xref> is an example of one such document.

If the RFC is not on the standards-track (i.e., it is an informational
or experimental RFC), it must be explicitly reviewed and approved by
the IESG before the RFC is published and the transform identifier is
assigned.
    </note>
    <registration_rule>Registry closed</registration_rule>
    <record>
      <value>0</value>
      <name>RESERVED</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>1</value>
      <name>KEY_IKE</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>2-248</value>
      <name>Unassigned</name>
    </record>
    <record>
      <value>249-255</value>
      <name>Reserved for private use</name>
    </record>
  </registry>

  <registry id="isakmp-registry-7">
    <title>IPSEC AH Transform Identifiers</title>
    <xref type="rfc" data="rfc2407"/>
    <xref type="rfc" data="rfc9395"/>
    <note>The IPSEC AH Transform Identifier is an 8-bit value which identifies a
particular algorithm to be used to provide integrity protection for
AH.  Requests for assignments of new AH transform identifiers must be
accompanied by an RFC which describes how to use the algorithm within
the AH framework (<xref type="text">AH</xref>).

If the RFC is not on the standards-track (i.e., it is an informational
or experimental RFC), it must be explicitly reviewed and approved by
the IESG before the RFC is published and the transform identifier is
assigned.
    </note>
    <registration_rule>Registry closed</registration_rule>
    <record>
      <value>0-1</value>
      <name>RESERVED</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>2</value>
      <name>AH_MD5</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>3</value>
      <name>AH_SHA</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>4</value>
      <name>AH_DES</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record date="2000-10">
      <value>5</value>
      <name>AH_SHA2-256</name>
      <xref type="rfc" data="rfc4868"/>
    </record>
    <record date="2000-10">
      <value>6</value>
      <name>AH_SHA2-384</name>
      <xref type="rfc" data="rfc4868"/>
    </record>
    <record date="2000-10">
      <value>7</value>
      <name>AH_SHA2-512</name>
      <xref type="rfc" data="rfc4868"/>
    </record>
    <record>
      <value>8</value>
      <name>AH_RIPEMD</name>
      <xref type="rfc" data="rfc2857"/>
    </record>
    <record>
      <value>9</value>
      <name>AH_AES-XCBC-MAC</name>
      <xref type="rfc" data="rfc3566"/>
    </record>
    <record>
      <value>10</value>
      <name>AH_RSA</name>
      <xref type="rfc" data="rfc4359"/>
    </record>
    <record>
      <value>11</value>
      <name>AH_AES-128-GMAC</name>
      <xref type="rfc" data="rfc4543"/>
      <xref type="rfc-errata" data="1821"/>
    </record>
    <record>
      <value>12</value>
      <name>AH_AES-192-GMAC</name>
      <xref type="rfc" data="rfc4543"/>
      <xref type="rfc-errata" data="1821"/>
    </record>
    <record>
      <value>13</value>
      <name>AH_AES-256-GMAC</name>
      <xref type="rfc" data="rfc4543"/>
      <xref type="rfc-errata" data="1821"/>
    </record>
    <record>
      <value>14-248</value>
      <name>Unassigned</name>
    </record>
    <record>
      <value>249-255</value>
      <name>Reserved for private use</name>
    </record>
  </registry>

  <registry id="isakmp-registry-9">
    <title>IPSEC ESP Transform Identifiers</title>
    <xref type="rfc" data="rfc2407"/>
    <xref type="rfc" data="rfc9395"/>
    <note>The IPSEC ESP Transform Identifier is an 8-bit value which identifies
a particular algorithm to be used to provide secrecy protection for
ESP.  Requests for assignments of new ESP transform identifiers must
be accompanied by an RFC which describes how to use the algorithm
within the ESP framework (<xref type="text">ESP</xref>).

If the RFC is not on the standards-track (i.e., it is an informational
or experimental RFC), it must be explicitly reviewed and approved by
the IESG before the RFC is published and the transform identifier is
assigned.
    </note>
    <registration_rule>Registry closed</registration_rule>
    <record>
      <value>0</value>
      <name>RESERVED</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>1</value>
      <name>ESP_DES_IV64</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>2</value>
      <name>ESP_DES</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>3</value>
      <name>ESP_3DES</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>4</value>
      <name>ESP_RC5</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>5</value>
      <name>ESP_IDEA</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>6</value>
      <name>ESP_CAST</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>7</value>
      <name>ESP_BLOWFISH</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>8</value>
      <name>ESP_3IDEA</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>9</value>
      <name>ESP_DES_IV32</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>10</value>
      <name>ESP_RC4</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>11</value>
      <name>ESP_NULL</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>12</value>
      <name>ESP_AES-CBC</name>
      <xref type="rfc" data="rfc3602"/>
    </record>
    <record>
      <value>13</value>
      <name>ESP_AES-CTR</name>
      <xref type="rfc" data="rfc3686"/>
    </record>
    <record>
      <value>14</value>
      <name>ESP_AES-CCM_8</name>
      <xref type="rfc" data="rfc4309"/>
      <xref type="note" data="1"/>
    </record>
    <record>
      <value>15</value>
      <name>ESP_AES-CCM_12</name>
      <xref type="rfc" data="rfc4309"/>
      <xref type="note" data="1"/>
    </record>
    <record>
      <value>16</value>
      <name>ESP_AES-CCM_16</name>
      <xref type="rfc" data="rfc4309"/>
      <xref type="note" data="1"/>
    </record>
    <record>
      <value>17</value>
      <name>Unassigned</name>
    </record>
    <record>
      <value>18</value>
      <name>ESP_AES-GCM_8</name>
      <xref type="rfc" data="rfc4106"/>
      <xref type="note" data="1"/>
    </record>
    <record>
      <value>19</value>
      <name>ESP_AES-GCM_12</name>
      <xref type="rfc" data="rfc4106"/>
      <xref type="note" data="1"/>
    </record>
    <record>
      <value>20</value>
      <name>ESP_AES-GCM_16</name>
      <xref type="rfc" data="rfc4106"/>
      <xref type="note" data="1"/>
    </record>
    <record>
      <value>21</value>
      <name>ESP_SEED_CBC</name>
      <xref type="rfc" data="rfc4196"/>
    </record>
    <record>
      <value>22</value>
      <name>ESP_CAMELLIA</name>
      <xref type="rfc" data="rfc4312"/>
    </record>
    <record>
      <value>23</value>
      <name>ESP_NULL_AUTH_AES-GMAC</name>
      <xref type="rfc" data="rfc4543"/>
      <xref type="rfc-errata" data="1821"/>
    </record>
    <record>
      <value>24-248</value>
      <name>Unassigned</name>
    </record>
    <record>
      <value>249-255</value>
      <name>Reserved for private use</name>
    </record>
    <footnote anchor="1">This is combined mode cipher, but combined mode algorithms are not
a ature of IPsec-v2. Although some IKEv1/IPsec-v2 implementations 
inude this capability (see <xref type="rfc" data="rfc6071"/> Section 5.4), it is not part of 
thprotocol.
    </footnote>
  </registry>

  <registry id="isakmp-registry-11">
    <title>IPSEC IPCOMP Transform Identifiers</title>
    <xref type="rfc" data="rfc2407"/>
    <xref type="rfc" data="rfc9395"/>
    <note>The IPSEC IPCOMP Transform Identifier is an 8-bit value which
identifier a particular algorithm to be used to provide IP-level
compression before ESP.  Requests for assignments of new IPCOMP
transform identifiers must be accompanied by an RFC which describes
how to use the algorithm within the IPCOMP framework (<xref type="text">IPCOMP</xref>).  In
addition, the requested algorithm must be published and in the public
domain.

If the RFC is not on the standards-track (i.e., it is an informational
or experimental RFC), it must be explicitly reviewed and approved by
the IESG before the RFC is published and the transform identifier is
assigned.
    </note>
    <registration_rule>Registry closed</registration_rule>
    <record>
      <value>0</value>
      <name>RESERVED</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>1</value>
      <name>IPCOMP_OUI</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>2</value>
      <name>IPCOMP_DEFLATE</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>3</value>
      <name>IPCOMP_LZS</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>4</value>
      <name>IPCOMP_LZJH</name>
      <xref type="rfc" data="rfc3051"/>
    </record>
    <record>
      <value>5-47</value>
      <name>Reserved for approved algorithms</name>
    </record>
    <record>
      <value>48-63</value>
      <name>Reserved for private use</name>
    </record>
    <record>
      <value>64-255</value>
      <name>Unassigned</name>
    </record>
  </registry>

  <registry id="isakmp-registry-13">
    <title>IPSEC Security Association Attributes</title>
    <xref type="rfc" data="rfc2407"/>
    <xref type="rfc" data="rfc9395"/>
    <note>The IPSEC Security Association Attribute consists of a 16-bit type and
its associated value.  IPSEC SA attributes are used to pass
miscellaneous values between ISAKMP peers.  Requests for assignments
of new IPSEC SA attributes must be accompanied by an Internet Draft
which describes the attribute encoding (Basic/Variable-Length) and its
legal values.  Section 4.5 of this document provides an example of
such a description.
    </note>
    <registration_rule>Registry closed</registration_rule>
    <record>
      <value>1</value>
      <type>B</type>
      <name>SA Life Type</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>2</value>
      <type>V</type>
      <name>SA Life Duration</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>3</value>
      <type>B</type>
      <name>Group Description</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>4</value>
      <type>B</type>
      <name>Encapsulation Mode</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>5</value>
      <type>B</type>
      <name>Authentication Algorithm</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>6</value>
      <type>B</type>
      <name>Key Length</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>7</value>
      <type>B</type>
      <name>Key Rounds</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>8</value>
      <type>B</type>
      <name>Compress Dictionary Size</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>9</value>
      <type>V</type>
      <name>Compress Private Algorithm</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>10</value>
      <type>B</type>
      <name>ECN Tunnel</name>
      <xref type="rfc" data="rfc3168"/>
    </record>
    <record>
      <value>11</value>
      <type>B</type>
      <name>Extended (64-bit) Sequence Number</name>
      <xref type="rfc" data="rfc4304"/>
    </record>
    <record>
      <value>12</value>
      <type>V</type>
      <name>Authentication Key Length</name>
      <xref type="rfc" data="rfc4359"/>
    </record>
    <record>
      <value>13</value>
      <type>B</type>
      <name>Signature Encoding Algorithm</name>
      <xref type="rfc" data="rfc4359"/>
    </record>
    <record>
      <value>14</value>
      <type>B</type>
      <name>Address Preservation</name>
      <xref type="rfc" data="rfc6407"/>
    </record>
    <record>
      <value>15</value>
      <type>B</type>
      <name>SA Direction</name>
      <xref type="rfc" data="rfc6407"/>
    </record>
    <record>
      <value>16-32000</value>
      <name>Unassigned</name>
    </record>
    <record>
      <value>32001-32767</value>
      <name>Reserved for private use</name>
    </record>
    
    <registry id="isakmp-registry-15">
      <title>SA Life Type Values (Value 1)</title>
      <xref type="rfc" data="rfc2407"/>
      <xref type="rfc" data="rfc9395"/>
      <registration_rule>Registry closed</registration_rule>
      <record>
        <value>0</value>
        <name>Reserved</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record>
        <value>1</value>
        <name>seconds</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record>
        <value>2</value>
        <name>kilobytes</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record>
        <value>3-61439</value>
        <name>Unassigned</name>
      </record>
      <record>
        <value>61440-65535</value>
        <name>Reserved for private use</name>
      </record>
    </registry>

    <registry id="isakmp-registry-16">
      <title>Group Description (Value 3)</title>
      <note>Please refer to the registry Group Description (Value 4) at <xref type="registry" data="ipsec-registry"/></note>
    </registry>
    
    <registry id="isakmp-registry-18">
      <title>Encapsulation Mode (Value 4)</title>
      <xref type="rfc" data="rfc2407"/>
      <xref type="rfc" data="rfc9395"/>
      <registration_rule>Registry closed</registration_rule>
      <record>
        <value>0</value>
        <name>Reserved</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record>
        <value>1</value>
        <name>Tunnel</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record>
        <value>2</value>
        <name>Transport</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record>
        <value>3</value>
        <name>UDP-Encapsulated-Tunnel</name>
        <xref type="rfc" data="rfc3947"/>
      </record>
      <record>
        <value>4</value>
        <name>UDP-Encapsulated-Transport</name>
        <xref type="rfc" data="rfc3947"/>
      </record>
      <record>
        <value>5-61439</value>
        <name>Unassigned</name>
      </record>
      <record>
        <value>61440-65535</value>
        <name>Reserved for private use</name>
      </record>
    </registry>
    
    <registry id="isakmp-registry-20">
      <title>Authentication Algorithm (Value 5)</title>
      <xref type="rfc" data="rfc2407"/>
      <xref type="rfc" data="rfc9395"/>
      <registration_rule>Registry closed</registration_rule>
      <record>
        <value>0</value>
        <name>Reserved</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record>
        <value>1</value>
        <name>HMAC-MD5</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record>
        <value>2</value>
        <name>HMAC-SHA</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record>
        <value>3</value>
        <name>DES-MAC</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record>
        <value>4</value>
        <name>KPDK</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record date="2000-10">
        <value>5</value>
        <name>HMAC-SHA2-256</name>
        <xref type="person" data="Marcus_Leech"/>
        <xref type="person" data="IPSEC"/>
      </record>
      <record date="2000-10">
        <value>6</value>
        <name>HMAC-SHA2-384</name>
        <xref type="person" data="Marcus_Leech"/>
        <xref type="person" data="IPSEC"/>
      </record>
      <record date="2000-10">
        <value>7</value>
        <name>HMAC-SHA2-512</name>
        <xref type="person" data="Marcus_Leech"/>
        <xref type="person" data="IPSEC"/>
      </record>
      <record>
        <value>8</value>
        <name>HMAC-RIPEMD</name>
        <xref type="rfc" data="rfc2857"/>
      </record>
      <record>
        <value>9</value>
        <name>AES-XCBC-MAC</name>
        <xref type="rfc" data="rfc3566"/>
      </record>
      <record>
        <value>10</value>
        <name>SIG-RSA</name>
        <xref type="rfc" data="rfc4359"/>
      </record>
      <record>
        <value>11</value>
        <name>AES-128-GMAC</name>
        <xref type="rfc" data="rfc4543"/>
        <xref type="rfc-errata" data="1821"/>
      </record>
      <record>
        <value>12</value>
        <name>AES-192-GMAC</name>
        <xref type="rfc" data="rfc4543"/>
        <xref type="rfc-errata" data="1821"/>
      </record>
      <record>
        <value>13</value>
        <name>AES-256-GMAC</name>
        <xref type="rfc" data="rfc4543"/>
        <xref type="rfc-errata" data="1821"/>
      </record>
      <record>
        <value>14-61439</value>
        <name>Unassigned</name>
      </record>
      <record>
        <value>61440-65535</value>
        <name>Reserved for private use</name>
      </record>
    </registry>

    <registry id="isakmp-registry-21">
      <title>Compression Private Algorithm (Value 9)</title>
      <xref type="rfc" data="rfc2407"/>
      <registration_rule>IANA does not assign</registration_rule>
      <note>Specifies a private vendor compression algorithm.  The first
three (3) octets must be an IEEE assigned company_id (OUI).
The next octet may be a vendor specific compression subtype,
followed by zero or more octets of vendor data.</note>
    </registry>
    
    <registry id="isakmp-registry-23">
      <title>ECN Tunnel (Value 10)</title>
      <xref type="rfc" data="rfc3168"/>
      <xref type="rfc" data="rfc9395"/>
      <note>If unspecified, the default shall be assumed to be Forbidden.</note>
      <registration_rule>Registry closed</registration_rule>
      <record>
        <value>0</value>
        <name>Reserved</name>
        <xref type="rfc" data="rfc3168"/>
      </record>
      <record>
        <value>1</value>
        <name>Allowed</name>
        <xref type="rfc" data="rfc3168"/>
      </record>
      <record>
        <value>2</value>
        <name>Forbidden</name>
        <xref type="rfc" data="rfc3168"/>
      </record>
      <record>
        <value>3-61439</value>
        <name>Unassigned</name>
      </record>
      <record>
        <value>61440-65535</value>
        <name>Reserved for private use</name>
      </record>
    </registry>

    <registry id="isakmp-registry-24">
      <title>Extended (64-bit) Sequence Number (Value 11)</title>
      <xref type="rfc" data="rfc4304"/>
      <xref type="rfc" data="rfc9395"/>
      <registration_rule>No additional class values will be assigned for this attribute.</registration_rule>
      <record>
        <value>0</value>
        <name>RESERVED</name>
        <xref type="rfc" data="rfc4304"/>
      </record>
      <record>
        <value>1</value>
        <name>64-bit Sequence Number</name>
        <xref type="rfc" data="rfc4304"/>
      </record>
    </registry>
    
    <registry id="isakmp-registry-26">
      <title>Signature Encoding Algorithm Values (Value 13)</title>
      <xref type="rfc" data="rfc4359"/>
      <xref type="rfc" data="rfc9395"/>
      <registration_rule>Registry closed</registration_rule>
      <record>
        <value>0</value>
        <name>Reserved</name>
        <xref type="rfc" data="rfc4359"/>
      </record>
      <record>
        <value>1</value>
        <name>RSASSA-PKCS1-v1_5</name>
        <xref type="rfc" data="rfc4359"/>
      </record>
      <record>
        <value>2</value>
        <name>RSASSA-PSS</name>
        <xref type="rfc" data="rfc4359"/>
      </record>
      <record>
        <value>3-61439</value>
        <name>Unassigned</name>
      </record>
      <record>
        <value>61440-65535</value>
        <name>Reserved for private use</name>
      </record>
    </registry>

    <registry id="isakmp-registry-27">
      <title>Address Preservation (Value 14)</title>
      <xref type="rfc" data="rfc6407"/>
      <xref type="rfc" data="rfc9395"/>
      <registration_rule>Registry closed</registration_rule>
      <record>
        <value>0</value>
        <name>Reserved</name>
        <xref type="rfc" data="rfc6407"/>
      </record>
      <record>
        <value>1</value>
        <name>None</name>
        <xref type="rfc" data="rfc6407"/>
      </record>
      <record>
        <value>2</value>
        <name>Source-Only</name>
        <xref type="rfc" data="rfc6407"/>
      </record>
      <record>
        <value>3</value>
        <name>Destination-Only</name>
        <xref type="rfc" data="rfc6407"/>
      </record>
      <record>
        <value>4</value>
        <name>Source-and-Destination</name>
        <xref type="rfc" data="rfc6407"/>
      </record>
      <record>
        <value>5-61439</value>
        <name>Unassigned</name>
      </record>
      <record>
        <value>61440-65535</value>
        <name>Private Use</name>
        <xref type="rfc" data="rfc6407"/>
      </record>
    </registry>

    <registry id="isakmp-registry-28">
      <title>SA Direction (Value 15)</title>
      <xref type="rfc" data="rfc6407"/>
      <xref type="rfc" data="rfc9395"/>
      <registration_rule>Registry closed</registration_rule>
      <record>
        <value>0</value>
        <name>Reserved</name>
        <xref type="rfc" data="rfc6407"/>
      </record>
      <record>
        <value>1</value>
        <name>Sender-Only</name>
        <xref type="rfc" data="rfc6407"/>
      </record>
      <record>
        <value>2</value>
        <name>Receiver-Only</name>
        <xref type="rfc" data="rfc6407"/>
      </record>
      <record>
        <value>3</value>
        <name>Symmetric</name>
        <xref type="rfc" data="rfc6407"/>
      </record>
      <record>
        <value>4-61439</value>
        <name>Unassigned</name>
        <xref type="rfc" data="rfc6407"/>
      </record>
      <record>
        <value>61440-65535</value>
        <name>Private Use</name>
        <xref type="rfc" data="rfc6407"/>
      </record>
    </registry>
    
  </registry>

  <registry id="isakmp-registry-29">
    <title>IPSEC Labeled Domain Identifiers</title>
    <xref type="rfc" data="rfc2407"/>
    <xref type="rfc" data="rfc9395"/>
    <registration_rule>Registry closed</registration_rule>
    <note>The IPSEC Labeled Domain Identifier is a 32-bit value which identifies
a namespace in which the Secrecy and Integrity levels and categories
values are said to exist.  Requests for assignments of new IPSEC
Labeled Domain Identifiers should be granted on demand.  No
accompanying documentation is required, though Internet Drafts are
encouraged when appropriate.
    </note>
    <record>
      <value>0</value>
      <name>Reserved</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>0x80000000-0xffffffff</value>
      <name>Reserved for private use</name>
    </record>
  </registry>

  <registry id="isakmp-registry-31">
    <title>IPSEC Identification Type</title>
    <xref type="rfc" data="rfc2407"/>
    <xref type="rfc" data="rfc9395"/>
    <note>The IPSEC Identification Type is an 8-bit value which is used as a
discriminant for interpretation of the variable-length Identification
Payload.  Requests for assignments of new IPSEC Identification Types
must be accompanied by an RFC which describes how to use the
identification type within IPSEC.

If the RFC is not on the standards track (i.e., it is an informational
or experimental RFC), it must be explicitly reviewed and approved by
the IESG before the RFC is published and the transform identifier is
assigned.
    </note>
    <registration_rule>Registry closed</registration_rule>
    <record>
      <value>0</value>
      <name>RESERVED</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>1</value>
      <name>ID_IPV4_ADDR</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>2</value>
      <name>ID_FQDN</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>3</value>
      <name>ID_USER_FQDN</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>4</value>
      <name>ID_IPV4_ADDR_SUBNET</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>5</value>
      <name>ID_IPV6_ADDR</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>6</value>
      <name>ID_IPV6_ADDR_SUBNET</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>7</value>
      <name>ID_IPV4_ADDR_RANGE</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>8</value>
      <name>ID_IPV6_ADDR_RANGE</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>9</value>
      <name>ID_DER_ASN1_DN</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>10</value>
      <name>ID_DER_ASN1_GN</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>11</value>
      <name>ID_KEY_ID</name>
      <xref type="rfc" data="rfc2407"/>
    </record>
    <record>
      <value>12</value>
      <name>ID_LIST</name>
      <xref type="rfc" data="rfc3554"/>
    </record>
    <record>
      <value>13-248</value>
      <name>Unassigned</name>
    </record>
    <record>
      <value>249-255</value>
      <name>Reserved for private use</name>
    </record>
  </registry>

  <registry id="isakmp-registry-32">
    <title>IPSEC Notify Message Types</title>
    <xref type="rfc" data="rfc2407"/>
    <xref type="rfc" data="rfc9395"/>
    <registration_rule>Registry closed</registration_rule>
    <note>The IPSEC Notify Message Type is a 16-bit value taken from the range
of values reserved by ISAKMP for each DOI.  There is one range for
error messages (8192-16383) and a different range for status messages
(24576-32767).  Requests for assignments of new Notify Message Types
must be accompanied by an Internet Draft which describes how to use
the identification type within IPSEC.
    </note>
    <registry id="isakmp-registry-34">
      <xref type="rfc" data="rfc9395"/>
      <title>Notify Messages - Error Types (8192-16383)</title>
      <registration_rule>Registry closed</registration_rule>
      <record>
        <value>8192</value>
        <name>Reserved</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record>
        <value>8193-16000</value>
        <name>Unassigned</name>
      </record>
      <record>
        <value>16001-16383</value>
        <name>Reserved for private use</name>
      </record>
    </registry>
    <registry id="isakmp-registry-36">
      <xref type="rfc" data="rfc9395"/>
      <title>Notify Messages - Status Types (24576-32767)</title>
      <registration_rule>Registry closed</registration_rule>
      <record>
        <value>24576</value>
        <name>RESPONDER-LIFETIME</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record>
        <value>24577</value>
        <name>REPLAY-STATUS</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record>
        <value>24578</value>
        <name>INITIAL-CONTACT</name>
        <xref type="rfc" data="rfc2407"/>
      </record>
      <record>
        <value>24579-32000</value>
        <name>Unassigned</name>
      </record>
      <record>
        <value>32001-32767</value>
        <name>Reserved for private use</name>
      </record>
    </registry>
  </registry>

  <people>
    <person id="IPSEC">
      <name>IETF IPSEC WG</name>
      <uri>mailto:ipsec&amp;ietf.org</uri>
      <updated>2023-01-04</updated>
    </person>
    <person id="Marcus_Leech">
      <name>Marcus Leech</name>
      <uri>mailto:mleech&amp;nortelnetworks.com</uri>
      <updated>2000-10</updated>
    </person>
  </people>
</registry>
