smilint output for ./IANA-MAU-TC-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| change recommended | 1 |
| warning | 2 |
| Message Types |
|---|
| Type | Count |
|---|
| module-identity-registration (change recommended) | 1 |
| type-unref (warning) | 2 |
Messages:
IANA-MAU-TC-MIB
1: -- extracted from draft-ietf-hubmib-rfc3636bis-00.txt
2: -- at Wed Apr 6 06:24:25 2005
12:
13: ianaMauTC MODULE-IDENTITY
13: change recommended -
warning: uncontrolled MODULE-IDENTITY registration
14: LAST-UPDATED "200410240000Z" -- Oct 24, 2004
15: ORGANIZATION "IANA"
16: CONTACT-INFO " Internet Assigned Numbers Authority
17:
18: Postal: ICANN
19: 4676 Admiralty Way, Suite 330
20: Marina del Rey, CA 90292
21:
22: Tel: +1 310 823 9358
23: E-Mail: iana@iana.org"
24:
25: DESCRIPTION
26: "This MIB module defines dot3MauType OBJECT-IDENTITIES and
27: IANAifMauListBits and JackType Textual Conventions,
28: specifying enumerated values of the ifMauTypeListBits and
29: ifJackType objects respectively, defined in the MAU-MIB.
30:
31: A Standards Action (as defined in RFC 2434) is REQUIRED for
32: the addition of the new MAU types, so that any prospective
33: assignments are documented in an RFC.
34: Any document that proposes such an addition is REQUIRED to
35: note any special properties of the MAU types that it defines
36: -- for example, side effects on the ifStackTable such as are
37: noted in RFC 3636 Section 3.4.1 for 10GBASE-W MAUs."
38:
39: REVISION "200410240000Z" -- Oct 24, 2004
40: DESCRIPTION "Initial version of this MIB as published in
41: RFC XXX."
...
46:
47: IANAifMauTypeListBits ::= TEXTUAL-CONVENTION
47: warning -
warning: current type `IANAifMauTypeListBits' is not referenced in this module
48: STATUS current
49: DESCRIPTION
50: "This data type is used as the syntax of the ifMauTypeListBits
51: object in the (updated) definition of MAU-MIB's ifMauTable.
52:
53: The definition of this textual convention with the addition of
54: newly assigned values is published periodically by the IANA,
55: in either the Assigned Numbers RFC, or some derivative of it
56: specific to Internet Network Management number assignments.
57: (The latest arrangements can be obtained by contacting the
58: IANA.)
59:
60: Requests for new values should be made to IANA via email
61: (iana@iana.org).
62:
63: Note that changes in this textual convention SHALL be
64: synchronized with relevant changes in the dot3MauType
65: OBJECT-IDENTITIES."
66: SYNTAX BITS {
67: bOther(0), -- other or unknown
68: bAUI(1), -- AUI
69: b10base5(2), -- 10BASE-5
70: bFoirl(3), -- FOIRL
71:
72: b10base2(4), -- 10BASE-2
73: b10baseT(5), -- 10BASE-T duplex mode unknown
74: b10baseFP(6), -- 10BASE-FP
75: b10baseFB(7), -- 10BASE-FB
76: b10baseFL(8), -- 10BASE-FL duplex mode unknown
77: b10broad36(9), -- 10BROAD36
78: b10baseTHD(10), -- 10BASE-T half duplex mode
79: b10baseTFD(11), -- 10BASE-T full duplex mode
80: b10baseFLHD(12), -- 10BASE-FL half duplex mode
81: b10baseFLFD(13), -- 10BASE-FL full duplex mode
82: b100baseT4(14), -- 100BASE-T4
83: b100baseTXHD(15), -- 100BASE-TX half duplex mode
84: b100baseTXFD(16), -- 100BASE-TX full duplex mode
85: b100baseFXHD(17), -- 100BASE-FX half duplex mode
86: b100baseFXFD(18), -- 100BASE-FX full duplex mode
87: b100baseT2HD(19), -- 100BASE-T2 half duplex mode
88: b100baseT2FD(20), -- 100BASE-T2 full duplex mode
89:
90: b1000baseXHD(21), -- 1000BASE-X half duplex mode
91: b1000baseXFD(22), -- 1000BASE-X full duplex mode
92: b1000baseLXHD(23), -- 1000BASE-LX half duplex mode
93: b1000baseLXFD(24), -- 1000BASE-LX full duplex mode
94: b1000baseSXHD(25), -- 1000BASE-SX half duplex mode
95: b1000baseSXFD(26), -- 1000BASE-SX full duplex mode
96: b1000baseCXHD(27), -- 1000BASE-CX half duplex mode
97: b1000baseCXFD(28), -- 1000BASE-CX full duplex mode
98: b1000baseTHD(29), -- 1000BASE-T half duplex mode
99: b1000baseTFD(30), -- 1000BASE-T full duplex mode
100:
101: b10GbaseX(31), -- 10GBASE-X
102: b10GbaseLX4(32), -- 10GBASE-LX4
103: b10GbaseR(33), -- 10GBASE-R
104: b10GbaseER(34), -- 10GBASE-ER
105: b10GbaseLR(35), -- 10GBASE-LR
106: b10GbaseSR(36), -- 10GBASE-SR
107: b10GbaseW(37), -- 10GBASE-W
108: b10GbaseEW(38), -- 10GBASE-EW
109: b10GbaseLW(39), -- 10GBASE-LW
110: b10GbaseSW(40), -- 10GBASE-SW
111: -- new since RFC 3636
112: b10GbaseCX4(41), -- 10GBASE-CX4
113: b2BaseTL(42), -- 2BASE-TL
114: b10PassTS(43), -- 10PASS-TS
115: b100BaseBX10D(44), -- 100BASE-BX10D
116: b100BaseBX10U(45), -- 100BASE-BX10U
117: b100BaseLX10(46), -- 100BASE-LX10
118: b1000BaseBX10D(47), -- 1000BASE-BX10D
119: b1000BaseBX10U(48), -- 1000BASE-BX10U
120: b1000BaseLX10(49), -- 1000BASE-LX10
121: b1000BasePX10D(50), -- 1000BASE-PX10D
122: b1000BasePX10U(51), -- 1000BASE-PX10U
123: b1000BasePX20D(52), -- 1000BASE-PX20D
124: b1000BasePX20U(53) -- 1000BASE-PX20U
125: }
126:
127: JackType ::= TEXTUAL-CONVENTION
127: warning -
warning: current type `JackType' is not referenced in this module
128: STATUS current
129: DESCRIPTION
130: "Common enumeration values for repeater and interface MAU
131: jack types. This data type is used as the syntax of the
132: ifJackType and rpJackType objects in the (updated) definition
133: of MAU-MIB's ifJackTable and RpJackTable respectively.
134:
135: The definition of this textual convention with the addition of
136: newly assigned values is published periodically by the IANA,
137: in either the Assigned Numbers RFC, or some derivative of it
138: specific to Internet Network Management number assignments.
139: (The latest arrangements can be obtained by contacting the
140: IANA.)
141:
142: Requests for new values should be made to IANA via email
143: (iana@iana.org)."
144: SYNTAX INTEGER {
145: other(1),
146: rj45(2),
147: rj45S(3), -- rj45 shielded
148: db9(4),
149: bnc(5),
150: fAUI(6), -- female aui
151: mAUI(7), -- male aui
152: fiberSC(8),
153: fiberMIC(9),
154: fiberST(10),
155: telco(11),
156: mtrj(12), -- fiber MT-RJ
157: hssdc(13), -- fiber channel style-2
158: fiberLC(14),
159: -- new since RFC 3636
160: cx4(15) -- IB4X for 10GBASE-CX4
161: }
162:
163: -- OBJECT IDENTITIES for MAU types
164: -- (see rpMauType and ifMauType of MAU-MIB for usage)
165: -- The following definitions has been moved from RFC 3636 and
166: -- no longer appear in its revision.