draft-ietf-hubmib-rfc3636bis-00.txt   draft-ietf-hubmib-rfc3636bis-01.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Expires: September 30, 2005 Apr 2005 Expires: October 15, 2005 Apr 16, 2005
Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units
(MAUs) (MAUs)
draft-ietf-hubmib-rfc3636bis-00.txt draft-ietf-hubmib-rfc3636bis-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of which he or she is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with which he or she become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 30, 2005. This Internet-Draft will expire on October 15, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it defines objects for managing IEEE 802.3 Medium In particular, it defines objects for managing IEEE 802.3 Medium
skipping to change at page 2, line 30 skipping to change at page 2, line 30
3.5 Relationship to other MIBs . . . . . . . . . . . . . . . . 5 3.5 Relationship to other MIBs . . . . . . . . . . . . . . . . 5
3.5.1 Relationship to the Interfaces MIB . . . . . . . . . . 5 3.5.1 Relationship to the Interfaces MIB . . . . . . . . . . 5
3.5.2 Relationship to the 802.3 Repeater MIB module . . . . 6 3.5.2 Relationship to the 802.3 Repeater MIB module . . . . 6
3.6 Management of Internal MAUs . . . . . . . . . . . . . . . 6 3.6 Management of Internal MAUs . . . . . . . . . . . . . . . 6
3.7 Management of IEEE 802.3 Managed Objects . . . . . . . . . 7 3.7 Management of IEEE 802.3 Managed Objects . . . . . . . . . 7
3.8 Addition of new MAU Types . . . . . . . . . . . . . . . . 8 3.8 Addition of new MAU Types . . . . . . . . . . . . . . . . 8
3.8.1 dot3MauType OBJECT-IDENTITIES . . . . . . . . . . . . 8 3.8.1 dot3MauType OBJECT-IDENTITIES . . . . . . . . . . . . 8
3.8.2 IANAifMauTypeListBits Textual Convention . . . . . . . 8 3.8.2 IANAifMauTypeListBits Textual Convention . . . . . . . 8
3.8.3 JackType Textual Convention . . . . . . . . . . . . . 9 3.8.3 JackType Textual Convention . . . . . . . . . . . . . 9
4. MAU MIB Definitions . . . . . . . . . . . . . . . . . . . . . 9 4. MAU MIB Definitions . . . . . . . . . . . . . . . . . . . . . 9
5. IANA maintained MAU TC Definitions . . . . . . . . . . . . . . 50 5. IANA maintained MAU TC Definitions . . . . . . . . . . . . . . 51
6. Security Considerations . . . . . . . . . . . . . . . . . . . 61 6. Security Considerations . . . . . . . . . . . . . . . . . . . 61
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 62 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 62 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 62
8.1 Normative References . . . . . . . . . . . . . . . . . . . . 62 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 63
8.2 Informative References . . . . . . . . . . . . . . . . . . . 64 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 63
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 65 9.2 Informative References . . . . . . . . . . . . . . . . . . . 65
Intellectual Property and Copyright Statements . . . . . . . . 66 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 66
Intellectual Property and Copyright Statements . . . . . . . . 67
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it defines objects for managing IEEE 802.3 Medium In particular, it defines objects for managing IEEE 802.3 Medium
Attachment Units (MAUs). Attachment Units (MAUs).
The previous version of this memo, RFC 3636 [RFC3636], defined a The previous version of this memo, RFC 3636 [RFC3636], defined a
single MIB module. This memo splits the original MIB module into single MIB module. This memo splits the original MIB module into
skipping to change at page 3, line 46 skipping to change at page 3, line 46
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. A detailed introduction to the current SNMP Management [RFC2580].
Framework can be found in RFC 2570 [RFC2570].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Overview 3. Overview
Instances of these object types represent attributes of an IEEE 802.3 Instances of these object types represent attributes of an IEEE 802.3
MAU. Several types of MAUs are defined in the IEEE 802.3 CSMA/CD MAU. Several types of MAUs are defined in the IEEE 802.3 CSMA/CD
standard [IEEE802.3]. These MAUs may be connected to IEEE 802.3 standard [IEEE802.3]. These MAUs may be connected to IEEE 802.3
skipping to change at page 8, line 34 skipping to change at page 8, line 34
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
Table 2 Table 2
3.8 Addition of new MAU Types 3.8 Addition of new MAU Types
3.8.1 dot3MauType OBJECT-IDENTITIES 3.8.1 dot3MauType OBJECT-IDENTITIES
The dot3MauType OBJECT IDENTIFIER and its OBJECT-IDENTITY definitions The dot3MauType OBJECT IDENTIFIER and its OBJECT-IDENTITY definitions
has been moved from the MAU-MIB into the IANA maintained has been moved from the MAU-MIB into the IANA maintained
IANA-MAU-TC-MIB, first version of which is defined in this memo. IANA-MAU-MIB, first version of which is defined in this memo.
When a new IEEE 802.3 MAU is defined, IANA can re-issue a version of When a new IEEE 802.3 MAU is defined, IANA can re-issue a version of
IANA-MAU-TC-MIB with the new dot3MauType OBJECT-IDENTITY and its IANA-MAU-MIB with the new dot3MauType OBJECT-IDENTITY and its
matching IANAifMauTypeListBits textual convention value and, matching IANAifMauTypeListBits textual convention value and,
possibly, with a new JackType value. possibly, with a new IANAifJackType value.
An Expert Review is REQUIRED for the addition of the new MAU types. An Expert Review is REQUIRED for the addition of the new MAU and Jack
types.
Any document that proposes such an addition is REQUIRED to note any Any document that proposes such an addition is REQUIRED to note any
special properties of the MAU types that it defines - for example, special properties of the MAU types that it defines - for example,
side effects on the ifStackTable as noted for 10GBASE-W MAUs. side effects on the ifStackTable as noted for 10GBASE-W MAUs.
3.8.2 IANAifMauTypeListBits Textual Convention 3.8.2 IANAifMauTypeListBits Textual Convention
The syntax of ifMauTypeListBits is changed to be a textual The syntax of ifMauTypeListBits is changed to be a textual
convention, such that the enumerated integer values are now defined convention, such that the enumerated integer values are now defined
in the textual convention, IANAifMauTypeListBits, which can be in the textual convention, IANAifMauTypeListBits, which can be
re-specified (with additional values) in the IANA mainained MIB re-specified (with additional values) in the IANA mainained MIB
module, without issuing a new version of this document. module, without issuing a new version of this document.
3.8.3 JackType Textual Convention 3.8.3 JackType Textual Convention
The JackType Textual Convention has been moved to the IANA mainained The JackType Textual Convention has been deprecated in favor of
MIB module, so it can be re-specified with additional values without IANAifJackType defined in the IANA mainained MIB module, so the new
issuing a new version of this document. Jack types can be added (when defined by IEEE 802.3) without issuing
a new version of this document.
4. MAU MIB Definitions 4. MAU MIB Definitions
MAU-MIB DEFINITIONS ::= BEGIN MAU-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Counter32, Integer32, Counter64, zeroDotZero, Counter32, Integer32, Counter64, zeroDotZero,
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2
OBJECT-IDENTITY, mib-2 FROM SNMPv2-SMI -- RFC 2578
FROM SNMPv2-SMI -- [RFC2578]
TruthValue, AutonomousType, TEXTUAL-CONVENTION TruthValue, AutonomousType, TEXTUAL-CONVENTION
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- RFC 2579
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- RFC 2580
InterfaceIndex InterfaceIndex
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- RFC 2863
IANAifMauTypeListBits, JackType IANAifMauTypeListBits, IANAifJackType
FROM IANA-MAU-TC-MIB -- [RFC3636BIS] FROM IANA-MAU-MIB -- RFC 3636bis
-- EdNote: Replace RFC 3636bis above with the URL of the
-- actual IANA-maintained module & remove this note.
; ;
mauMod MODULE-IDENTITY mauMod MODULE-IDENTITY
LAST-UPDATED "200502240000Z" -- February 24, 2005 LAST-UPDATED "200504150000Z" -- April 15, 2005
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/hubmib-charter.html http://www.ietf.org/html.charters/hubmib-charter.html
Mailing Lists: Mailing Lists:
General Discussion: hubmib@ietf.org General Discussion: hubmib@ietf.org
To Subscribe: hubmib-request@ietf.org To Subscribe: hubmib-request@ietf.org
In Body: subscribe your_email_address In Body: subscribe your_email_address
skipping to change at page 10, line 36 skipping to change at page 10, line 40
amended by IEEE Std 802.3ae-2002: amended by IEEE Std 802.3ae-2002:
'Amendment: Media Access Control (MAC) 'Amendment: Media Access Control (MAC)
Parameters, Physical Layer, and Management Parameters, Physical Layer, and Management
Parameters for 10 Gb/s Operation', August, Parameters for 10 Gb/s Operation', August,
2002. 2002.
Of particular interest is Clause 30, '10Mb/s, Of particular interest is Clause 30, '10Mb/s,
100Mb/s, 1000Mb/s and 10 Gb/s Management'. 100Mb/s, 1000Mb/s and 10 Gb/s Management'.
Copyright (C) The Internet Society (2004). This Copyright (C) The Internet Society (2004). This
version of this MIB module is part of RFC 3636bis; version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices." see the RFC itself for full legal notices."
REVISION "200502240000Z" -- February 24, 2005 REVISION "200504150000Z" -- April 15, 2005
DESCRIPTION "Updated to reference IANA maintaned textual DESCRIPTION "Updated to reference IANA maintaned textual
conventions for MAU types, instead of using conventions for MAU types and jack types,
internally defined values. instead of using internally defined values.
This version is published as RFC XXXX." This version is published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number & remove -- EdNote: Replace XXXX with the actual RFC number
-- this note. -- & remove this note.
REVISION "200309190000Z" -- September 19, 2003 REVISION "200309190000Z" -- September 19, 2003
DESCRIPTION "Updated to include support for 10 Gb/s MAUs. DESCRIPTION "Updated to include support for 10 Gb/s MAUs.
This resulted in the following revisions: This resulted in the following revisions:
- Added OBJECT-IDENTITY definitions for - Added OBJECT-IDENTITY definitions for
10 gigabit MAU types 10 gigabit MAU types
- Added fiberLC jack type to JackType TC - Added fiberLC jack type to JackType TC
- Extended ifMauTypeListBits with bits for - Extended ifMauTypeListBits with bits for
the 10 gigabit MAU types the 10 gigabit MAU types
- Added enumerations to ifMauMediaAvailable, - Added enumerations to ifMauMediaAvailable,
skipping to change at page 11, line 35 skipping to change at page 11, line 40
REVISION "199710310000Z" -- October 31, 1997 REVISION "199710310000Z" -- October 31, 1997
DESCRIPTION "Version published as RFC 2239." DESCRIPTION "Version published as RFC 2239."
REVISION "199309300000Z" -- September30, 1993 REVISION "199309300000Z" -- September30, 1993
DESCRIPTION "Initial version, published as RFC 1515." DESCRIPTION "Initial version, published as RFC 1515."
::= { snmpDot3MauMgt 6 } ::= { snmpDot3MauMgt 6 }
snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 } snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 }
-- Textual Conventions
JackType ::= TEXTUAL-CONVENTION
STATUS deprecated
DESCRIPTION "********* THIS TC IS DEPRECATED **********
This TC has been deprecated in favour of
IANAifJackType.
Common enumeration values for repeater
and interface MAU jack types."
SYNTAX INTEGER {
other(1),
rj45(2),
rj45S(3), -- rj45 shielded
db9(4),
bnc(5),
fAUI(6), -- female aui
mAUI(7), -- male aui
fiberSC(8),
fiberMIC(9),
fiberST(10),
telco(11),
mtrj(12), -- fiber MT-RJ
hssdc(13), -- fiber channel style-2
fiberLC(14)
}
dot3RpMauBasicGroup dot3RpMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 }
dot3IfMauBasicGroup dot3IfMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 }
dot3BroadMauBasicGroup dot3BroadMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 }
dot3IfMauAutoNegGroup dot3IfMauAutoNegGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 }
skipping to change at page 13, line 38 skipping to change at page 14, line 22
(rpMauPortIndex)." (rpMauPortIndex)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."
::= { rpMauEntry 3 } ::= { rpMauEntry 3 }
rpMauType OBJECT-TYPE rpMauType OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "This object identifies the MAU type. Values for DESCRIPTION "This object identifies the MAU type. Values for
standard IEEE 802.3 MAU types are defined in the standard IEEE 802.3 MAU types are defined in the
IANA maintained IANA-MAU-TC-MIB module, as IANA maintained IANA-MAU-MIB module, as
OBJECT-IDENTITIES of dot3MauType. OBJECT-IDENTITIES of dot3MauType.
If the MAU type is unknown, the object identifier If the MAU type is unknown, the object identifier
zeroDotZero is returned." zeroDotZero is returned."
DEFVAL { zeroDotZero }
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType."
DEFVAL { zeroDotZero }
::= { rpMauEntry 4 } ::= { rpMauEntry 4 }
rpMauStatus OBJECT-TYPE rpMauStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
operational(3), operational(3),
standby(4), standby(4),
shutdown(5), shutdown(5),
reset(6) reset(6)
skipping to change at page 19, line 29 skipping to change at page 20, line 12
INDEX { rpMauGroupIndex, INDEX { rpMauGroupIndex,
rpMauPortIndex, rpMauPortIndex,
rpMauIndex, rpMauIndex,
rpJackIndex rpJackIndex
} }
::= { rpJackTable 1 } ::= { rpJackTable 1 }
RpJackEntry ::= RpJackEntry ::=
SEQUENCE { SEQUENCE {
rpJackIndex Integer32, rpJackIndex Integer32,
rpJackType JackType rpJackType IANAifJackType
} }
rpJackIndex OBJECT-TYPE rpJackIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "This variable uniquely identifies the jack DESCRIPTION "This variable uniquely identifies the jack
described by this entry from among other jacks described by this entry from among other jacks
attached to the same MAU (rpMauIndex)." attached to the same MAU (rpMauIndex)."
::= { rpJackEntry 1 } ::= { rpJackEntry 1 }
rpJackType OBJECT-TYPE rpJackType OBJECT-TYPE
SYNTAX JackType SYNTAX IANAifJackType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The jack connector type, as it appears on the DESCRIPTION "The jack connector type, as it appears on the
outside of the system." outside of the system."
::= { rpJackEntry 2 } ::= { rpJackEntry 2 }
-- --
-- The Basic Interface MAU Table -- The Basic Interface MAU Table
-- --
ifMauTable OBJECT-TYPE ifMauTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfMauEntry SYNTAX SEQUENCE OF IfMauEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "Table of descriptive and status information DESCRIPTION "Table of descriptive and status information
about MAU(s) attached to an interface." about MAU(s) attached to an interface."
::= { dot3IfMauBasicGroup 1 } ::= { dot3IfMauBasicGroup 1 }
ifMauEntry OBJECT-TYPE ifMauEntry OBJECT-TYPE
SYNTAX IfMauEntry SYNTAX IfMauEntry
skipping to change at page 21, line 21 skipping to change at page 22, line 5
connected to the same interface (ifMauIfIndex)." connected to the same interface (ifMauIfIndex)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."
::= { ifMauEntry 2 } ::= { ifMauEntry 2 }
ifMauType OBJECT-TYPE ifMauType OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "This object identifies the MAU type. Values for DESCRIPTION "This object identifies the MAU type. Values for
standard IEEE 802.3 MAU types are defined in the standard IEEE 802.3 MAU types are defined in the
IANA maintained IANA-MAU-TC-MIB module, as IANA maintained IANA-MAU-MIB module, as
OBJECT-IDENTITIES of dot3MauType. OBJECT-IDENTITIES of dot3MauType.
If the MAU type is unknown, the object identifier If the MAU type is unknown, the object identifier
zeroDotZero is returned. zeroDotZero is returned.
This object represents the operational type of This object represents the operational type of
the MAU, as determined by either (1) the result the MAU, as determined by either (1) the result
of the auto-negotiation function or (2) if of the auto-negotiation function or (2) if
auto-negotiation is not enabled or is not auto-negotiation is not enabled or is not
implemented for this MAU, by the value of the implemented for this MAU, by the value of the
object ifMauDefaultType. In case (2), a set to object ifMauDefaultType. In case (2), a set to
the object ifMauDefaultType will force the MAU the object ifMauDefaultType will force the MAU
into the new operating mode." into the new operating mode."
DEFVAL { zeroDotZero }
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType."
DEFVAL { zeroDotZero }
::= { ifMauEntry 3 } ::= { ifMauEntry 3 }
ifMauStatus OBJECT-TYPE ifMauStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
operational(3), operational(3),
standby(4), standby(4),
shutdown(5), shutdown(5),
reset(6) reset(6)
skipping to change at page 31, line 4 skipping to change at page 31, line 35
about a particular jack." about a particular jack."
INDEX { ifMauIfIndex, INDEX { ifMauIfIndex,
ifMauIndex, ifMauIndex,
ifJackIndex ifJackIndex
} }
::= { ifJackTable 1 } ::= { ifJackTable 1 }
IfJackEntry ::= IfJackEntry ::=
SEQUENCE { SEQUENCE {
ifJackIndex Integer32, ifJackIndex Integer32,
ifJackType JackType ifJackType IANAifJackType
} }
ifJackIndex OBJECT-TYPE ifJackIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "This variable uniquely identifies the jack DESCRIPTION "This variable uniquely identifies the jack
described by this entry from among other jacks described by this entry from among other jacks
attached to the same MAU." attached to the same MAU."
::= { ifJackEntry 1 } ::= { ifJackEntry 1 }
ifJackType OBJECT-TYPE ifJackType OBJECT-TYPE
SYNTAX JackType SYNTAX IANAifJackType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The jack connector type, as it appears on the DESCRIPTION "The jack connector type, as it appears on the
outside of the system." outside of the system."
::= { ifJackEntry 2 } ::= { ifJackEntry 2 }
-- --
-- The MAU Auto-Negotiation Table -- The MAU Auto-Negotiation Table
-- --
skipping to change at page 50, line 16 skipping to change at page 51, line 4
for MAUs attached to interfaces." for MAUs attached to interfaces."
OBJECT ifMauStatus OBJECT ifMauStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
::= { mauModCompls 5 } ::= { mauModCompls 5 }
END END
5. IANA maintained MAU TC Definitions 5. IANA maintained MAU TC Definitions
IANA-MAU-MIB DEFINITIONS ::= BEGIN
IANA-MAU-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, mib-2 MODULE-IDENTITY, OBJECT-IDENTITY, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
; ;
ianaMauTC MODULE-IDENTITY ianaMauMIB MODULE-IDENTITY
LAST-UPDATED "200410240000Z" -- Oct 24, 2004 LAST-UPDATED "200504160000Z" -- April 16, 2005
ORGANIZATION "IANA" ORGANIZATION "IANA"
CONTACT-INFO " Internet Assigned Numbers Authority CONTACT-INFO " Internet Assigned Numbers Authority
Postal: ICANN Postal: ICANN
4676 Admiralty Way, Suite 330 4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292 Marina del Rey, CA 90292
Tel: +1 310 823 9358 Tel: +1 310 823 9358
E-Mail: iana@iana.org" E-Mail: iana@iana.org"
DESCRIPTION DESCRIPTION
"This MIB module defines dot3MauType OBJECT-IDENTITIES and "This MIB module defines dot3MauType OBJECT-IDENTITIES and
IANAifMauListBits and JackType Textual Conventions, IANAifMauListBits and IANAifJackType Textual Conventions,
specifying enumerated values of the ifMauTypeListBits and specifying enumerated values of the ifMauTypeListBits and
ifJackType objects respectively, defined in the MAU-MIB. ifJackType objects respectively, defined in the MAU-MIB.
A Standards Action (as defined in RFC 2434) is REQUIRED for An Expert Review is REQUIRED for the addition of the new
the addition of the new MAU types, so that any prospective MAU types, when they are defined in the [IEEE 802.3 Std.].
assignments are documented in an RFC.
Any document that proposes such an addition is REQUIRED to Any document that proposes such an addition is REQUIRED to
note any special properties of the MAU types that it defines note any special properties of the MAU types that it defines
-- for example, side effects on the ifStackTable such as are - for example, side effects on the ifStackTable such as those
noted in RFC 3636 Section 3.4.1 for 10GBASE-W MAUs." noted in RFC 3636 Section 3.4.1 for 10GBASE-W MAUs.
REVISION "200410240000Z" -- Oct 24, 2004 Copyright (C) The Internet Society (2004).
The initial version of this MIB module was published in
RFC XXXX; for full legal notices see the RFC itself.
Supplementary information may be available at:
http://www.ietf.org/copyrights/ianamib.html"
REVISION "200504160000Z" -- April 16, 2005
DESCRIPTION "Initial version of this MIB as published in DESCRIPTION "Initial version of this MIB as published in
RFC XXX." RFC XXX."
-- EdNote: Replace XXXX with the actual RFC number & remove this note -- EdNote: Replace XXXX with the actual RFC number & remove this note
::= { mib-2 snmpDot3MauMgt(26) 7 } -- mauMod+1 ::= { mib-2 snmpDot3MauMgt(26) 7 } -- mauMod+1
-- Textual Conventions -- Textual Conventions
IANAifMauTypeListBits ::= TEXTUAL-CONVENTION IANAifMauTypeListBits ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used as the syntax of the ifMauTypeListBits "This data type is used as the syntax of the ifMauTypeListBits
object in the (updated) definition of MAU-MIB's ifMauTable. object in the (updated) definition of MAU-MIB's ifMauTable.
The definition of this textual convention with the addition of The definition of this textual convention with the addition of
newly assigned values is published periodically by the IANA, newly assigned values is published periodically by the IANA,
in either the Assigned Numbers RFC, or some derivative of it in either the Assigned Numbers RFC, or some derivative of it
specific to Internet Network Management number assignments. specific to Internet Network Management number assignments.
skipping to change at page 52, line 46 skipping to change at page 53, line 36
b100BaseLX10(46), -- 100BASE-LX10 b100BaseLX10(46), -- 100BASE-LX10
b1000BaseBX10D(47), -- 1000BASE-BX10D b1000BaseBX10D(47), -- 1000BASE-BX10D
b1000BaseBX10U(48), -- 1000BASE-BX10U b1000BaseBX10U(48), -- 1000BASE-BX10U
b1000BaseLX10(49), -- 1000BASE-LX10 b1000BaseLX10(49), -- 1000BASE-LX10
b1000BasePX10D(50), -- 1000BASE-PX10D b1000BasePX10D(50), -- 1000BASE-PX10D
b1000BasePX10U(51), -- 1000BASE-PX10U b1000BasePX10U(51), -- 1000BASE-PX10U
b1000BasePX20D(52), -- 1000BASE-PX20D b1000BasePX20D(52), -- 1000BASE-PX20D
b1000BasePX20U(53) -- 1000BASE-PX20U b1000BasePX20U(53) -- 1000BASE-PX20U
} }
JackType ::= TEXTUAL-CONVENTION IANAifJackType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Common enumeration values for repeater and interface MAU "Common enumeration values for repeater and interface MAU
jack types. This data type is used as the syntax of the jack types. This data type is used as the syntax of the
ifJackType and rpJackType objects in the (updated) definition ifJackType and rpJackType objects in the (updated) definition
of MAU-MIB's ifJackTable and RpJackTable respectively. of MAU-MIB's ifJackTable and RpJackTable respectively.
The definition of this textual convention with the addition of The definition of this textual convention with the addition of
newly assigned values is published periodically by the IANA, newly assigned values is published periodically by the IANA,
in either the Assigned Numbers RFC, or some derivative of it in either the Assigned Numbers RFC, or some derivative of it
skipping to change at page 62, line 5 skipping to change at page 62, line 40
(for authentication and privacy). (for authentication and privacy).
Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
7. Acknowledgments 7. IANA Considerations
This document defines first version of the IANA maintaned MIB module.
When a new MAU type and/or Jack type is defined by the IEEE 802.3
working group, it MAY be added to the IANA maintaned module via an
Expert Review.
8. Acknowledgments
This document was produced by the IETF Ethernet Interfaces and Hub This document was produced by the IETF Ethernet Interfaces and Hub
MIB Working Group, whose efforts were greatly advanced by the MIB Working Group, whose efforts were greatly advanced by the
contributions of the following people: contributions of the following people:
Mike Heard Mike Heard
John Flick John Flick
Dan Romascanu Dan Romascanu
skipping to change at page 62, line 45 skipping to change at page 63, line 39
providing support for 1000 Mb/sec MAUs as defined in [IEEE802.3]. providing support for 1000 Mb/sec MAUs as defined in [IEEE802.3].
RFC 2239, in turn, was based on the Proposed Standard MAU MIB, RFC RFC 2239, in turn, was based on the Proposed Standard MAU MIB, RFC
1515 [RFC1515], edited by Donna McMaster, then of SynOptics 1515 [RFC1515], edited by Donna McMaster, then of SynOptics
Communications, Keith McCloghrie, then of Hughes LAN Systems, and Sam Communications, Keith McCloghrie, then of Hughes LAN Systems, and Sam
Roberts, then of Farallon Computing, and produced by the Hub MIB Roberts, then of Farallon Computing, and produced by the Hub MIB
Working Group. It extends that document by providing support for 100 Working Group. It extends that document by providing support for 100
Mb/sec MAUs, full duplex MAUs, and auto-negotiation, as defined in Mb/sec MAUs, full duplex MAUs, and auto-negotiation, as defined in
[IEEE802.3]. [IEEE802.3].
8. References 9. References
8.1 Normative References 9.1 Normative References
[IEEE802.3] [IEEE802.3]
IEEE, "IEEE Standard for Information technology - IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific systems - Local and metropolitan area networks - Specific
requirements - Part 3: Carrier sense multiple access with requirements - Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) access method and physical collision detection (CSMA/CD) access method and physical
layer specifications", IEEE Std 802.3-2002, March 2002. layer specifications", IEEE Std 802.3-2002, March 2002.
[IEEE802.3ae] [IEEE802.3ae]
skipping to change at page 63, line 45 skipping to change at page 64, line 39
Parameters for 10Gb/s Operation, Type 10GBASE-CX4", IEEE Parameters for 10Gb/s Operation, Type 10GBASE-CX4", IEEE
Std 802.3ak-2004, March 2004. Std 802.3ak-2004, March 2004.
[RFC2108] de Graaf, K., Romascanu, D., McMaster, D. and K. [RFC2108] de Graaf, K., Romascanu, D., McMaster, D. and K.
McCloghrie, "Definitions of Managed Objects for IEEE 802.3 McCloghrie, "Definitions of Managed Objects for IEEE 802.3
Repeater Devices using SMIv2", RFC 2108, February 1997. Repeater Devices using SMIv2", RFC 2108, February 1997.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999. 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual McCloghrie, K., Rose, M. and S. Waldbusser, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April 1999. Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3635] Flick, J., "Definitions of Managed Objects for the [RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 3635, September 2003. Ethernet-like Interface Types", RFC 3635, September 2003.
8.2 Informative References 9.2 Informative References
[RFC1515] McMaster, D., McCloghrie, K. and S. Roberts, "Definitions [RFC1515] McMaster, D., McCloghrie, K. and S. Roberts, "Definitions
of Managed Objects for IEEE 802.3 Medium Attachment Units of Managed Objects for IEEE 802.3 Medium Attachment Units
(MAUs)", RFC 1515, September 1993. (MAUs)", RFC 1515, September 1993.
[RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, K. [RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, K.
and S. Roberts, "Definitions of Managed Objects for IEEE and S. Roberts, "Definitions of Managed Objects for IEEE
802.3 Medium Attachment Units (MAUs) using SMIv2", RFC 802.3 Medium Attachment Units (MAUs) using SMIv2", RFC
2239, November 1997. 2239, November 1997.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/