<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="snmp-number-spaces.xsl"?>
<?xml-model href="snmp-number-spaces.rng" schematypens="http://relaxng.org/ns/structure/1.0" ?>
<registry xmlns="http://www.iana.org/assignments" id="snmp-number-spaces">
  <title>Simple Network Management Protocol (SNMP) Number Spaces</title>
  <updated>2016-05-03</updated>

  <registry id="snmp-number-spaces-1">
    <title>Security Models</title>
    <xref type="rfc" data="rfc3411"/>
    <registration_rule>Standards Action</registration_rule>
    <note>The SnmpSecurityModel TEXTUAL-CONVENTION values managed by IANA are in
the range from 0 to 255 inclusive, and are reserved for standards-
track Security Models.  If this range should in the future prove
insufficient, an enterprise number can be allocated to obtain an
additional 255 possible values.

There are several values of securityModel defined for use with SNMP or
reserved for use with supporting MIB objects.  They are as follows:
    </note>
    <record>
      <value>0</value>
      <description>reserved for 'any'</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <value>1</value>
      <description>reserved for SNMPv1</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <value>2</value>
      <description>reserved for SNMPv2c</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <value>3</value>
      <description>User-Based Security Model (USM)</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <value>4</value>
      <description>Transport Security Model (TSM)</description>
      <xref type="rfc" data="rfc5591"/>
    </record>
    <record>
      <value>5-255</value>
      <description>Unassigned</description>
    </record>
  </registry>

  <registry id="snmp-number-spaces-2">
    <title>Message Processing Models</title>
    <xref type="rfc" data="rfc3411"/>
    <registration_rule>Standards Action</registration_rule>
    <note>The SnmpMessageProcessingModel TEXTUAL-CONVENTION values managed by
IANA are in the range 0 to 255, inclusive.  Each value uniquely
identifies a standards-track Message Processing Model of the Message
Processing Subsystem within a SNMP Management Architecture.

Should this range prove insufficient in the future, an enterprise
number may be obtained for the standards committee to get an
additional 256 possible values.
    </note>
    <record>
      <value>0</value>
      <description>reserved for SNMPv1</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <value>1</value>
      <description>reserved for SNMPv2c</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <value>2</value>
      <description>reserved for SNMPv2u and SNMPv2*</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <value>3</value>
      <description>reserved for SNMPv3</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <value>4-255</value>
      <description>Unassigned</description>
    </record>
  </registry>

  <registry id="snmp-number-spaces-4">
    <title>SnmpEngineID Formats</title>
    <xref type="rfc" data="rfc3411"/>
    <xref type="rfc" data="rfc5343"/>
    <expert>Unassigned</expert>
    <range>
      <value>1-127</value>
      <registration_rule>Specification Required</registration_rule>
    </range>
    <range>
      <value>128-255</value>
      <registration_rule>Enterprise-specific</registration_rule>
      <note>IANA does not assign</note>
    </range>
    <record>
      <format>0</format>
      <description>Reserved</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <format>1</format>
      <description>IPv4 address</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <format>2</format>
      <description>IPv6 address</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <format>3</format>
      <description>MAC address</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <format>4</format>
      <description>administratively assigned text</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <format>5</format>
      <description>administratively assigned octets</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <format>6</format>
      <description>local engine</description>
      <xref type="rfc" data="rfc5343"/>
    </record>
    <record>
      <format>7-127</format>
      <description>Unassigned</description>
    </record>
    <record>
      <format>128-255</format>
      <description>Enterprise-specific</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
  </registry>

  <registry id="snmp-number-spaces-5">
    <title>SnmpAuthProtocols</title>
    <xref type="rfc" data="rfc3411"/>
    <registration_rule>Standards Action</registration_rule>
    <note>IETF standard protocols for SNMPv3 authentication and privacy

The MIB module defined in <xref type="rfc" data="rfc3411"/> defines this OBJECT-IDENTITY
as registration points.
    </note>
    <record>
      <value>0</value>
      <description>Reserved</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <value>1</value>
      <description>usmNoAuthProtocol - no authentication</description>
      <xref type="rfc" data="rfc3414"/>
    </record>
    <record>
      <value>2</value>
      <description>usmHMACMD5AuthProtocol - HMAC-MD5-96</description>
      <xref type="rfc" data="rfc3414"/>
    </record>
    <record>
      <value>3</value>
      <description>usmHMACSHAAuthProtocol - HMAC-SHA-96</description>
      <xref type="rfc" data="rfc3414"/>
    </record>
    <record date="2015-06-26" updated="2016-05-03">
      <value>4</value>
      <description>usmHMAC128SHA224AuthProtocol</description>
      <xref type="rfc" data="rfc7860"/>
    </record>
    <record date="2015-06-26" updated="2016-05-03">
      <value>5</value>
      <description>usmHMAC192SHA256AuthProtocol</description>
      <xref type="rfc" data="rfc7860"/>
    </record>
    <record date="2015-06-26" updated="2016-05-03">
      <value>6</value>
      <description>usmHMAC256SHA384AuthProtocol</description>
      <xref type="rfc" data="rfc7860"/>
    </record>
    <record date="2015-06-26" updated="2016-05-03">
      <value>7</value>
      <description>usmHMAC384SHA512AuthProtocol</description>
      <xref type="rfc" data="rfc7860"/>
    </record>
  </registry>

  <registry id="snmp-number-spaces-6">
    <title>SnmpPrivProtocols</title>
    <xref type="rfc" data="rfc3411"/>
    <registration_rule>Standards Action</registration_rule>
    <note>IETF standard protocols for SNMPv3 authentication and privacy

The MIB module defined in <xref type="rfc" data="rfc3411"/> defines this OBJECT-IDENTITY
as registration points.
    </note>
    <record>
      <value>0</value>
      <description>Reserved</description>
      <xref type="rfc" data="rfc3411"/>
    </record>
    <record>
      <value>1</value>
      <description>usmNoPrivProtocol - no privacy</description>
      <xref type="rfc" data="rfc3414"/>
    </record>
    <record>
      <value>2</value>
      <description>usmDESPrivProtocol - CBC-DES</description>
      <xref type="rfc" data="rfc3414"/>
    </record>
    <record>
      <value>3</value>
      <description>Reserved</description>
    </record>
    <record>
      <value>4</value>
      <description>usmAesCfb128Protocol - AES-CFB-128</description>
      <xref type="rfc" data="rfc3826"/>
    </record>
  </registry>

  <registry id="snmp-number-spaces-7">
    <title>SNMP Transport Domains</title>
    <xref type="rfc" data="rfc2578"/>
    <xref type="rfc" data="rfc3417"/>
    <xref type="rfc" data="rfc5590"/>
    <registration_rule>Specification Required</registration_rule>
    <expert>Unassigned</expert>
    <note>Each domain is assigned a MIB-defined OID under snmpDomains.</note>
    <record>
      <prefix>udp</prefix>
      <snmpDomains>snmpUDPDomain</snmpDomains>
      <xref type="rfc" data="rfc3417"/>
      <xref type="rfc" data="rfc5590"/>
    </record>
    <record>
      <prefix>clns</prefix>
      <snmpDomains>snmpCLNSDomain</snmpDomains>
      <xref type="rfc" data="rfc3417"/>
      <xref type="rfc" data="rfc5590"/>
    </record>
    <record>
      <prefix>cons</prefix>
      <snmpDomains>snmpCONSDomain</snmpDomains>
      <xref type="rfc" data="rfc3417"/>
      <xref type="rfc" data="rfc5590"/>
    </record>
    <record>
      <prefix>ddp</prefix>
      <snmpDomains>snmpDDPDomain</snmpDomains>
      <xref type="rfc" data="rfc3417"/>
      <xref type="rfc" data="rfc5590"/>
    </record>
    <record>
      <prefix>ipx</prefix>
      <snmpDomains>snmpIPXDomain</snmpDomains>
      <xref type="rfc" data="rfc3417"/>
      <xref type="rfc" data="rfc5590"/>
    </record>
    <record>
      <prefix>prxy</prefix>
      <snmpDomains>rfc1157Domain</snmpDomains>
      <xref type="rfc" data="rfc3417"/>
      <xref type="rfc" data="rfc5590"/>
    </record>
    <record>
      <prefix>ssh</prefix>
      <snmpDomains>snmpSSHDomain</snmpDomains>
      <xref type="rfc" data="rfc5592"/>
    </record>
    <record>
      <prefix>tls</prefix>
      <snmpDomains>snmpTLSTCPDomain</snmpDomains>
      <xref type="rfc" data="rfc6353"/>
    </record>
    <record>
      <prefix>dtls</prefix>
      <snmpDomains>snmpDTLSUDPDomain</snmpDomains>
      <xref type="rfc" data="rfc6353"/>
    </record>
  </registry>
  
  <people/>
</registry>
