smilint output for ./IANA-GMPLS-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 2 |
| warning | 4 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 1 |
| object-identifier-not-prefix (error) | 1 |
| type-unref (warning) | 4 |
Messages:
IANA-GMPLS-MIB
1: -- extracted from draft-ietf-ccamp-gmpls-te-mib-09.txt
2: -- at Fri Jun 3 06:33:28 2005
3:
4: IANA-GMPLS-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, transmission FROM SNMPv2-SMI -- RFC2578
8: TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC2579
9:
10: ianaGmpls MODULE-IDENTITY
11: LAST-UPDATED "200505200001Z" -- 20 May 2005 00:00:01 GMT
12: ORGANIZATION "IANA"
13: CONTACT-INFO
14: " Internet Assigned Numbers Authority
15: Postal: USC/Information Sciences Institute
16: 4676 Admiralty Way, Marina del Rey, CA 90292
17: Tel: +1 310 822 1511
18: E-Mail: iana@isi.edu"
19: DESCRIPTION
20: "The MIB module which defines the GMPLS textual
21: conventions for use as enumerations within GMPLS MIB
22: modules, thus protecting those MIB modules from changes
23: to the enumerations."
24: -- Revision history.
25: REVISION
26: "200505200001Z" -- 20 May 2005 00:00:01 GMT
27: DESCRIPTION
28: -- RFC Editor: Please see the IANA Considerations Section.
29: -- RFC-editor please fill in XXXX
30: "Initial version issued as part of RFC XXXX."
31: ::= { transmission YYY }
31: error -
`YYY' should start with a lower case letter
31: error -
Object identifier element `YYY' name only allowed as first element
32:
33: IANAGmplsLSPEncoding ::= TEXTUAL-CONVENTION
33: warning -
warning: current type `IANAGmplsLSPEncoding' is not referenced in this module
34: STATUS current
35: DESCRIPTION
36: "This data type is used as the syntax of the
37: gmplsTunnelLSPEncoding object in the definition of
38: GMPLS-TE-MIB's gmplsTunnelTable.
39:
40: The definition of this textual convention with the
41: addition of newly assigned values is published
42: periodically by the IANA, in either the Assigned
43: Numbers RFC, or some derivative of it specific to
44: Internet Network Management number assignments. (The
45: latest arrangements can be obtained by contacting the
46: IANA.)
47:
48: Requests for new values should be made to IANA via
49: email (iana@isi.edu).
50:
51: gmplsTunnelLSPEncoding is used to represent and control
52: the LSP encoding type of an LSP signaled by a GMPLS
53: signaling protocol. The relationship between the
54: assignment of gmplsTunnelLSPEncoding values and of the
55: values used to represent LSP encoding types within the
56: GMPLS signaling protocols is solely the purview of IANA
57: and is subject to change without notice."
58: REFERENCE
59: "1. Berger, L., et al., Generalized Multi-Protocol
60: Label Switching (GMPLS) Signaling Functional
61: Description, RFC 3471, January 2003.
62: 2. D. Papadimitriou (Editor), Generalized MPLS
63: Signalling Extensions for G.709 Optical Transport
64: Networks Control, draft-ietf-ccamp-gmpls-g709,
65: work in progress."
66: SYNTAX INTEGER {
67: tunnelLspNotGmpls (0), -- GMPLS is not in use
68: tunnelLspPacket (1), -- Packet
69: tunnelLspEthernet (2), -- Ethernet
70: tunnelLspAnsiEtsiPdh (3), -- PDH
71: -- the value 4 is deprecated
72: tunnelLspSdhSonet (5), -- SDH or SONET
73: -- the value 6 is deprecated
74: tunnelLspDigitalWrapper (7), -- Digital Wrapper
75: tunnelLspLambda (8), -- Lambda
76: tunnelLspFiber (9), -- Fiber
77: -- the value 10 is deprecated
78: tunnelLspFiberChannel (11), -- Fiber Channel
79: tunnelDigitalPath (12), -- Digital Path
80: tunnelOpticalChannel (13) -- Optical Channel
81: }
82:
83: IANAGmplsSwitchingType ::= TEXTUAL-CONVENTION
83: warning -
warning: current type `IANAGmplsSwitchingType' is not referenced in this module
84: STATUS current
85: DESCRIPTION
86: "This data type is used as the syntax of the
87: gmplsTunnelSwitchingType object in the definition of
88: GMPLS-TE-MIB's gmplsTunnelTable.
89:
90: The definition of this textual convention with the
91: addition of newly assigned values is published
92: periodically by the IANA, in either the Assigned
93: Numbers RFC, or some derivative of it specific to
94: Internet Network Management number assignments. (The
95: latest arrangements can be obtained by contacting the
96: IANA.)
97:
98: Requests for new values should be made to IANA via
99: email (iana@isi.edu).
100:
101: gmplsTunnelSwitchingType is used to represent and
102: control the LSP switching type of an LSP signaled by a
103: GMPLS signaling protocol. The relationship between the
104: assignment of gmplsTunnelSwitchingType values and of the
105: values used to represent LSP switching types within the
106: GMPLS signaling protocols is solely the purview of IANA
107: and is subject to change without notice."
108: REFERENCE
109: "1. Kompella, K., Rekhter, Y. (Editors), Routing Extensions
110: in Support of Generalized Multi-Protocol Label Switching
111: draft-ietf-ccamp-gmpls-routing, work in progress.
112: 2. Berger, L., et al., Generalized Multi-Protocol
113: Label Switching (GMPLS) Signaling Functional
114: Description, RFC 3471, January 2003."
115: SYNTAX INTEGER {
116: unknown (0), -- none of the following, or not known
117: psc1 (1), -- Packet-Switch-Capable 1
118: psc2 (2), -- Packet-Switch-Capable 2
119: psc3 (3), -- Packet-Switch-Capable 3
120: psc4 (4), -- Packet-Switch-Capable 4
121: l2sc (51), -- Layer-2-Switch-Capable
122: tdm (100), -- Time-Division-Multiplex
123: lsc (150), -- Lambda-Switch-Capable
124: fsc (200) -- Fiber-Switch-Capable
125: }
126:
127: IANAGmplsGPid ::= TEXTUAL-CONVENTION
127: warning -
warning: current type `IANAGmplsGPid' is not referenced in this module
128: STATUS current
129: DESCRIPTION
130: "This data type is used as the syntax of the
131: gmplsTunnelGPid object in the definition of
132: GMPLS-TE-MIB's gmplsTunnelTable.
133: The definition of this textual convention with the
134: addition of newly assigned values is published
135: periodically by the IANA, in either the Assigned
136: Numbers RFC, or some derivative of it specific to
137: Internet Network Management number assignments. (The
138: latest arrangements can be obtained by contacting the
139: IANA.)
140:
141: Requests for new values should be made to IANA via
142: email (iana@isi.edu).
143:
144: gmplsTunnelGPid is used to represent and control the LSP
145: Generalized Protocol Identifier (G-PID) of an LSP
146: signaled by a GMPLS signaling protocol. The relationship
147: between the assignment of gmplsTunnelGPid values and of
148: the values used to represent G-PIDs within the GMPLS
149: signaling protocols is solely the purview of IANA and is
150: subject to change without notice."
151: REFERENCE
152: "1. Berger, L., et al., Generalized Multi-Protocol
153: Label Switching (GMPLS) Signaling Functional
154: Description, RFC 3471, January 2003.
155: 2. D. Papadimitriou (Editor), Generalized MPLS
156: Signalling Extensions for G.709 Optical Transport
157: Networks Control, draft-ietf-ccamp-gmpls-g709,
158: work in progress."
159: SYNTAX INTEGER {
160: unknown(0), -- unknown or none of the following
161: asynchE4(5),
162: asynchDS3T3(6),
163: asynchE3(7),
164: bitsynchE3(8),
165: bytesynchE3(9),
166: asynchDS2T2(10),
167: bitsynchDS2T2(11),
168: asynchE1(13),
169: bytesynchE1(14),
170: bytesynch31ByDS0(15),
171: asynchDS1T1(16),
172: bitsynchDS1T1(17),
173: bytesynchDS1T1(18),
174: vc1vc12(19),
175: ds1SFAsynch(22),
176: ds1ESFAsynch(23),
177: ds3M23Asynch(24),
178: ds3CBitParityAsynch(25),
179: vtLovc(26),
180: stsSpeHovc(27),
181: posNoScramble16BitCrc(28),
182: posNoScramble32BitCrc(29),
183: posScramble16BitCrc(30),
184: posScramble32BitCrc(31),
185: atm(32),
186: ethernet(33),
187: sdhSonet(34),
188: digitalwrapper(36),
189: lambda(37),
190: ansiEtsiPdh (38),
191: lapsSdh (40),
192: fddi (41),
193: dqdb (42),
194: fiberChannel3 (43),
195: hdlc (44),
196: ethernetV2DixOnly (45),
197: ethernet802dot3Only (46),
198: g709ODUj (47),
199: g709OTUk (48),
200: g709CBRorCBRa (49),
201: g709CBRb (50),
202: g709BSOT (51),
203: g709BSNT (52),
204: gfpIPorPPP (53),
205: gfpEthernetMAC (54),
206: gfpEthernetPHY (55),
207: g709ESCON (56),
208: g709FICON (57),
209: g709FiberChannel (58)
210: }
211:
212: IANAGmplsAdminStatusFlags ::= TEXTUAL-CONVENTION
212: warning -
warning: current type `IANAGmplsAdminStatusFlags' is not referenced in this module
213: STATUS current
214: DESCRIPTION
215: "This data type is used as the syntax of the
216: gmplsTunnelAdminStatusFlags object in the definition of
217: GMPLS-TE-MIB's gmplsTunnelTable.
218:
219: The definition of this textual convention with the
220: addition of newly assigned values is published
221: periodically by the IANA, in either the Assigned
222: Numbers RFC, or some derivative of it specific to
223: Internet Network Management number assignments. (The
224: latest arrangements can be obtained by contacting the
225: IANA.)
226:
227: Requests for new values should be made to IANA via
228: email (iana@isi.edu).
229:
230: gmplsTunnelAdminStatusFlags determines the setting of the
231: Admin Status flags in the Admin Status object or TLV, as
232: described in RFC 3471. Setting this object to a non-zero
233: value will result in the inclusion of the Admin Status
234: object or TLV on signaling messages.
235:
236: The relationship between the assignment of
237: gmplsTunnelAdminStatusFlags values and of the bit flags
238: in the Admin Status object or TLV within the GMPLS
239: signaling protocols is solely the purview of IANA and is
240: subject to change without notice."
241: REFERENCE
242: "Berger, L., et al., Generalized Multi-Protocol Label
243: Switching (GMPLS) Signaling Functional Description,
244: RFC 3471, January 2003."
245: SYNTAX BITS {
246: delInProgress (0),
247: adminDown (1),
248: testing (2),
249: reflect (31)
250: }
251:
252: END
253:
254: --
255: -- Copyright (C) The Internet Society (2005). This document is subject
256: -- to the rights, licenses and restrictions contained in BCP 78, and
257: -- except as set forth therein, the authors retain all their rights.
258: --
259: -- This document and the information contained herein are provided on an
260: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
261: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
262: -- ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
263: -- INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
264: -- INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
265: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
266: