Tech-invite3GPPspaceIETFspace
96959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 1239

Reassignment of experimental MIBs to standard MIBs

Pages: 2
Historic
Updates:  12291230123112321233

ToP   noToC   RFC1239 - Page 1
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.
ToP   noToC   RFC1239 - Page 2
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