SNMP Number Spaces

(last updated 2004-09-05)

Registries included below:
- Security Models
- Message Processing Models
- SnmpEngineID Formats
- snmpAuthProtocols
- snmpPrivProtocols


Registry Name: Security Models
Reference: [RFC3411]
Registration Procedures: Standards track 

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:

Registry:
Value   Description                         References
------  ---------------------------------   ----------
0       reserved for 'any'                  [RFC3411]
1       reserved for SNMPv1                 [RFC3411]
2       reserved for SNMPv2c                [RFC3411]
3       User-Based Security Model (USM)     [RFC3411]
4-255   Unassigned


Registry Name: Message Processing Models
Reference: [RFC3411]
Registration Procedures: Standards track  

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.

Registry:
Value   Description                             References
------  ------------------------------------    ----------
0       reserved for SNMPv1                     [RFC3411]
1       reserved for SNMPv2c                    [RFC3411]
2       reserved for SNMPv2u and SNMPv2*        [RFC3411]
3       reserved for SNMPv3                     [RFC3411]
4-255   Unassigned


SnmpEngineID Formats

The SnmpEngineID TEXTUAL-CONVENTION's fifth octet contains a format
identifier.  The values managed by IANA are in the range 6 to 127, 
inclusive.  Each value uniquely identifies a standards-track 
SnmpEngineID format.

IETF standard protocols for SNMPv3 authentication and privacy

The MIB module defined in RFC 3411 defines two OBJECT-IDENTITYs
as registration points:

1. snmpAuthProtocols -- "Registration point for standards-track
                        authentication protocols used in SNMP 
                        Management Frameworks."

The values defined under this registration point are:

Value  Description                              References
-----  -----------                              ----------
0      Reserved                                 [RFC3411]
1      usmNoAuthProtocol - no authentication    [RFC3414]
2      usmHMACMD5AuthProtocol - HMAC-MD5-96     [RFC3414]
3      usmHMACSHAAuthProtocol - HMAC-SHA-96     [RFC3414]

2. snmpPrivProtocols -- "Registration point for standards-track privacy
                          protocols used in SNMP Management Frameworks."

The values defined under this registration point are:

Value  Description                          References
-----  -----------                          ----------
0      Reserved                             [RFC3411]
1      usmNoPrivProtocol - no privacy       [RFC3414]
2      usmDESPrivProtocol - CBC-DES         [RFC3414]
3      Reserved                             
4      usmAesCfb128Protocol - AES-CFB-128   [RFC3826]


References
----------
[RFC3411]  D. Harrington, R. Presuhn, and B. Wijnen, "An Architecture for 
           Describing SNMP Management Frameworks", RFC 3411, December 2002.

[RFC3414]  D. Harrington, R. Presuhn, and B. Wijnen, "User-based Security
           Model (USM) for version 3 of the Simple Network Management
           Protocol (SNMPv3)", RFC 3414, December 2002.

[RFC3826]  U. Blumenthal, F. Maino, and K. McCloghrie, "The AES Cipher 
           Algorithm in the SNMP User-based Security Model", RFC 3826,
           June 2004.

[]
