MIB Reassignment: Reassignment of experimental MIBs to standard MIBs
Moves five MIB assignments from the experimental namespace to standard namespaces.
Reynolds, J.K., "Reassignment of experimental MIBs to standard MIBs", RFC 1239, DOI 10.17487/RFC1239, June 1991, <https://www.rfc-editor.org/info/rfc1239>.
@misc{rfc1239,
series = {Request for Comments},
number = 1239,
howpublished = {RFC 1239},
publisher = {RFC Editor},
doi = {10.17487/RFC1239},
url = {https://www.rfc-editor.org/info/rfc1239},
author = {J.K. Reynolds},
title = {{Reassignment of experimental MIBs to standard MIBs}},
pagetotal = 2,
year = 1991,
month = jun,
} RFC text
Contents
Network Working Group J. Reynolds
Request for Comments: 1239 ISI
Updates: RFCs 1229, 1230, 1231, 1232, 1233 June 1991
Reassignment of Experimental MIBs to Standard MIBs
Status of this Memo
This RFC specifies an IAB standards track protocol for the Internet
community, and requests discussion and suggestions for improvements.
Please refer to the current edition of the "IAB Official Protocol
Standards" for the standardization state and status of this protocol.
Distribution of this memo is unlimited.
Statement
In the past, MIBs have been assigned arcs in the experimental MIB
namespace early in their development and then were not assigned arcs
in the standard MIB namespace until they reached Full Standard
status. This practice required vendors to revise their
implementations when a MIB went from Draft to Full Standard status,
even though there was probably no substantive technical change in the
definitions. This practice could also engender operational problems
in the field at an undesirably late stage of the standardization
process. It was also observed that this practice could discourage
implementation until the Full Standard stage and that this, too,
would be undesirable. So, a preferable practice is to assign arcs in
the standard MIB namespace at the earliest phase of standardization
and to preserve these assignments as the standard progresses.
This memo specifically updates:
RFC 1229 - "Extensions to the Generic-Interface MIB"
RFC 1230 - "IEEE 802.4 Token Bus MIB"
RFC 1231 - "IEEE 802.5 Token Ring MIB"
RFC 1232 - "Definitions of Managed Objects for the DS1 Interface
Type"
RFC 1233 - "Definitions of Managed Objects for the DS3 Interface
Type"
with new codes. In the future, consult each MIB publication for new
code assignments.
SMI Network Management Old Experimental Codes
Prefix: 1.3.6.1.3 (experimental)
Decimal Name Description
------- ---- -----------
2 T1-Carrier T1 Carrier Objects
4 IEEE802.5 Token Ring-like Objects
6 Interface Generic Interface Extension Objects
7 IEEE802.4 Token Bus-like Objects
15 DS3 DS3 Interface Type
SMI Network Management New Standard Codes
Prefix: 1.3.6.1.2.1 (standard-mib)
Decimal Name Description
------- ---- -----------
12 Generic IF Generic Interface Extension Objects
Prefix: 1.3.6.1.2.1.10 (transmission)
Decimal Name Description
------- ---- -----------
8 IEEE802.4 Token Bus-like Objects
9 IEEE802.5 Token Ring-like Objects
18 DS1 T1 Carrier Objects
30 DS3 DS3 Interface Type
Security Considerations
Security issues are not discussed in this memo.
Author's Address
Joyce K. Reynolds
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695
Phone: (213) 822-1511
EMail: jkrey@isi.edu
ISO Plain Language
On this page
§1Why the Assignments Changed
Previously, a MIB could receive an experimental namespace arc early and wait until Full Standard status for an arc in the standard namespace. The memo says this could make vendors revise implementations without a substantive technical change, create late operational problems and discourage implementation before Full Standard status.
It recommends assigning an arc in the standard MIB namespace at the earliest phase of standardization and preserving that assignment as the standard progresses.
Changing identifiers late can force vendors to revise working implementations. The memo recommends using the standard identifier from an early stage and keeping it.
§1The Five MIBs Covered
RFC 1239 updates RFCs 1229, 1230, 1231, 1232 and 1233 with new codes. The affected objects cover generic interface extensions, IEEE 802.4 Token Bus, IEEE 802.5 Token Ring, DS1/T1 Carrier and DS3. The memo says future code assignments should be checked in each MIB publication.
The reassignment covers five MIBs for interfaces and transmission technologies. The memo directs readers to each publication for later code assignments.
§2Experimental and Standard Prefixes
The old experimental prefix is 1.3.6.1.3. The new standard assignments use prefix 1.3.6.1.2.1 for Generic IF code 12, and the transmission prefix 1.3.6.1.2.1.10 for IEEE 802.4 code 8, IEEE 802.5 code 9, DS1 code 18 and DS3 code 30. The memo's table also lists the old codes under the experimental prefix.
The memo states that security issues are not discussed.
The RFC gives old experimental codes and their new standard prefixes and codes. It does not discuss security issues.