smilint output for ./IANA-GMPLS-TC-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| warning | 4 |
| Message Types |
|---|
| Type | Count |
|---|
| type-unref (warning) | 4 |
Messages:
IANA-GMPLS-TC-MIB
1: -- extracted from rfc4802.txt
2: -- at Thu Mar 1 06:08:22 2007
33:
34: IANAGmplsLSPEncodingTypeTC ::= TEXTUAL-CONVENTION
34: warning -
warning: current type `IANAGmplsLSPEncodingTypeTC' is not referenced in this module
35: STATUS current
36: DESCRIPTION
37: "This type is used to represent and control
38: the LSP encoding type of an LSP signaled by a GMPLS
39: signaling protocol.
40:
41: This textual convention is strongly tied to the LSP
42: Encoding Types sub-registry of the GMPLS Signaling
43: Parameters registry managed by IANA. Values should be
44: assigned by IANA in step with the LSP Encoding Types
45: sub-registry and using the same registry management rules.
46: However, the actual values used in this textual convention
47: are solely within the purview of IANA and do not
48: necessarily match the values in the LSP Encoding Types
49: sub-registry.
50:
51: The definition of this textual convention with the
52: addition of newly assigned values is published
53: periodically by the IANA, in either the Assigned
54: Numbers RFC, or some derivative of it specific to
55: Internet Network Management number assignments. (The
56: latest arrangements can be obtained by contacting the
57: IANA.)
58:
59: Requests for new values should be made to IANA via
60: email (iana@iana.org)."
61: REFERENCE
62: "1. Generalized Multi-Protocol Label Switching (GMPLS)
63: Signaling Functional Description, RFC 3471, section
64: 3.1.1.
65: 2. Generalized MPLS Signalling Extensions for G.709 Optical
66: Transport Networks Control, RFC 4328, section 3.1.1."
67: SYNTAX INTEGER {
68: tunnelLspNotGmpls(0), -- GMPLS is not in use
69: tunnelLspPacket(1), -- Packet
70: tunnelLspEthernet(2), -- Ethernet
71: tunnelLspAnsiEtsiPdh(3), -- PDH
72: -- the value 4 is deprecated
73: tunnelLspSdhSonet(5), -- SDH or SONET
74: -- the value 6 is deprecated
75: tunnelLspDigitalWrapper(7), -- Digital Wrapper
76: tunnelLspLambda(8), -- Lambda
77: tunnelLspFiber(9), -- Fiber
78: -- the value 10 is deprecated
79: tunnelLspFiberChannel(11), -- Fiber Channel
80: tunnelDigitalPath(12), -- Digital Path
81: tunnelOpticalChannel(13) -- Optical Channel
82: }
83:
84: IANAGmplsSwitchingTypeTC ::= TEXTUAL-CONVENTION
84: warning -
warning: current type `IANAGmplsSwitchingTypeTC' is not referenced in this module
85: STATUS current
86: DESCRIPTION
87: "This type is used to represent and
88: control the LSP switching type of an LSP signaled by a
89: GMPLS signaling protocol.
90:
91: This textual convention is strongly tied to the Switching
92: Types sub-registry of the GMPLS Signaling Parameters
93: registry managed by IANA. Values should be assigned by
94: IANA in step with the Switching Types sub-registry and
95: using the same registry management rules. However, the
96: actual values used in this textual convention are solely
97: within the purview of IANA and do not necessarily match
98: the values in the Switching Types sub-registry.
99:
100: The definition of this textual convention with the
101: addition of newly assigned values is published
102: periodically by the IANA, in either the Assigned
103: Numbers RFC, or some derivative of it specific to
104: Internet Network Management number assignments. (The
105: latest arrangements can be obtained by contacting the
106: IANA.)
107:
108: Requests for new values should be made to IANA via
109: email (iana@iana.org)."
110: REFERENCE
111: "1. Routing Extensions in Support of Generalized
112: Multi-Protocol Label Switching, RFC 4202, section 2.4.
113: 2. Generalized Multi-Protocol Label Switching (GMPLS)
114: Signaling Functional Description, RFC 3471, section
115: 3.1.1."
116: SYNTAX INTEGER {
117: unknown(0), -- none of the following, or not known
118: psc1(1), -- Packet-Switch-Capable 1
119: psc2(2), -- Packet-Switch-Capable 2
120: psc3(3), -- Packet-Switch-Capable 3
121: psc4(4), -- Packet-Switch-Capable 4
122: l2sc(51), -- Layer-2-Switch-Capable
123: tdm(100), -- Time-Division-Multiplex
124: lsc(150), -- Lambda-Switch-Capable
125: fsc(200) -- Fiber-Switch-Capable
126: }
127:
128: IANAGmplsGeneralizedPidTC ::= TEXTUAL-CONVENTION
128: warning -
warning: current type `IANAGmplsGeneralizedPidTC' is not referenced in this module
129: STATUS current
130: DESCRIPTION
131: "This data type is used to represent and control the LSP
132: Generalized Protocol Identifier (G-PID) of an LSP
133: signaled by a GMPLS signaling protocol.
134:
135: This textual convention is strongly tied to the Generalized
136: PIDs (G-PID) sub-registry of the GMPLS Signaling Parameters
137: registry managed by IANA. Values should be assigned by
138: IANA in step with the Generalized PIDs (G-PID) sub-registry
139: and using the same registry management rules. However, the
140: actual values used in this textual convention are solely
141: within the purview of IANA and do not necessarily match the
142: values in the Generalized PIDs (G-PID) sub-registry.
143:
144: The definition of this textual convention with the
145: addition of newly assigned values is published
146: periodically by the IANA, in either the Assigned
147: Numbers RFC, or some derivative of it specific to
148: Internet Network Management number assignments. (The
149: latest arrangements can be obtained by contacting the
150: IANA.)
151:
152: Requests for new values should be made to IANA via
153: email (iana@iana.org)."
154: REFERENCE
155: "1. Generalized Multi-Protocol Label Switching (GMPLS)
156: Signaling Functional Description, RFC 3471, section
157: 3.1.1.
158: 2. Generalized MPLS Signalling Extensions for G.709 Optical
159: Transport Networks Control, RFC 4328, section 3.1.3."
160: SYNTAX INTEGER {
161: unknown(0), -- unknown or none of the following
162: -- the values 1, 2, 3 and 4 are reserved in RFC 3471
163: asynchE4(5),
164: asynchDS3T3(6),
165: asynchE3(7),
166: bitsynchE3(8),
167: bytesynchE3(9),
168: asynchDS2T2(10),
169: bitsynchDS2T2(11),
170: reservedByRFC3471first(12),
171: asynchE1(13),
172: bytesynchE1(14),
173: bytesynch31ByDS0(15),
174: asynchDS1T1(16),
175: bitsynchDS1T1(17),
176: bytesynchDS1T1(18),
177: vc1vc12(19),
178: reservedByRFC3471second(20),
179: reservedByRFC3471third(21),
180: ds1SFAsynch(22),
181: ds1ESFAsynch(23),
182: ds3M23Asynch(24),
183: ds3CBitParityAsynch(25),
184: vtLovc(26),
185: stsSpeHovc(27),
186: posNoScramble16BitCrc(28),
187: posNoScramble32BitCrc(29),
188: posScramble16BitCrc(30),
189: posScramble32BitCrc(31),
190: atm(32),
191: ethernet(33),
192: sdhSonet(34),
193: digitalwrapper(36),
194: lambda(37),
195: ansiEtsiPdh(38),
196: lapsSdh(40),
197: fddi(41),
198: dqdb(42),
199: fiberChannel3(43),
200: hdlc(44),
201: ethernetV2DixOnly(45),
202: ethernet802dot3Only(46),
203: g709ODUj(47),
204: g709OTUk(48),
205: g709CBRorCBRa(49),
206: g709CBRb(50),
207: g709BSOT(51),
208: g709BSNT(52),
209: gfpIPorPPP(53),
210: gfpEthernetMAC(54),
211: gfpEthernetPHY(55),
212: g709ESCON(56),
213: g709FICON(57),
214: g709FiberChannel(58)
215: }
216:
217: IANAGmplsAdminStatusInformationTC ::= TEXTUAL-CONVENTION
217: warning -
warning: current type `IANAGmplsAdminStatusInformationTC' is not referenced in this module
218: STATUS current
219: DESCRIPTION
220: "This data type determines the setting of the
221: Admin Status flags in the Admin Status object or TLV, as
222: described in RFC 3471. Setting this object to a non-zero
223: value will result in the inclusion of the Admin Status
224: object or TLV on signaling messages.
225:
226: This textual convention is strongly tied to the
227: Administrative Status Information Flags sub-registry of
228: the GMPLS Signaling Parameters registry managed by IANA.
229: Values should be assigned by IANA in step with the
230: Administrative Status Flags sub-registry and using the
231: same registry management rules. However, the actual
232: values used in this textual convention are solely
233: within the purview of IANA and do not necessarily match
234: the values in the Administrative Status Information
235: Flags sub-registry.
236:
237: The definition of this textual convention with the
238: addition of newly assigned values is published
239: periodically by the IANA, in either the Assigned
240: Numbers RFC, or some derivative of it specific to
241: Internet Network Management number assignments. (The
242: latest arrangements can be obtained by contacting the
243: IANA.)
244:
245: Requests for new values should be made to IANA via
246: email (iana@iana.org)."
247: REFERENCE
248: "1. Generalized Multi-Protocol Label Switching (GMPLS)
249: Signaling Functional Description, RFC 3471, section 8.
250: 2. Generalized MPLS Signaling - RSVP-TE Extensions,
251: RFC 3473, section 7.
252: 3. GMPLS - Communication of Alarm Information,
253: RFC 4783, section 3.2.1."
254: SYNTAX BITS {
255: reflect(0), -- Reflect bit (RFC 3471)
256: reserved1(1), -- reserved
257: reserved2(2), -- reserved
258: reserved3(3), -- reserved
259: reserved4(4), -- reserved
260: reserved5(5), -- reserved
261: reserved6(6), -- reserved
262: reserved7(7), -- reserved
263: reserved8(8), -- reserved
264: reserved9(9), -- reserved
265: reserved10(10), -- reserved
266: reserved11(11), -- reserved
267: reserved12(12), -- reserved
268: reserved13(13), -- reserved
269: reserved14(14), -- reserved
270: reserved15(15), -- reserved
271: reserved16(16), -- reserved
272: reserved17(17), -- reserved
273: reserved18(18), -- reserved
274: reserved19(19), -- reserved
275: reserved20(20), -- reserved
276: reserved21(21), -- reserved
277: reserved22(22), -- reserved
278: reserved23(23), -- reserved
279: reserved24(24), -- reserved
280: reserved25(25), -- reserved
281: reserved26(26), -- reserved
282: reserved27(27), -- Inhibit Alarm bit (RFC 4783)
283: reserved28(28), -- reserved
284: testing(29), -- Testing bit (RFC 3473)
285: administrativelyDown(30), -- Admin down (RFC 3473)
286: deleteInProgress(31) -- Delete bit (RFC 3473)
287: }
288: END
289:
290: --
291: -- Copyright (C) The IETF Trust (2007).
292: --
293: -- This document is subject to the rights, licenses and restrictions
294: -- contained in BCP 78, and except as set forth therein, the authors
295: -- retain all their rights.
296: --
297: -- This document and the information contained herein are provided on an
298: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
299: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
300: -- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
301: -- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
302: -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
303: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
304: --
305: -- Intellectual Property
306: --
307: -- The IETF takes no position regarding the validity or scope of any
308: -- Intellectual Property Rights or other rights that might be claimed to
309: -- pertain to the implementation or use of the technology described in
310: -- this document or the extent to which any license under such rights
311: -- might or might not be available; nor does it represent that it has
312: -- made any independent effort to identify any such rights. Information
313: -- on the procedures with respect to rights in RFC documents can be
314: -- found in BCP 78 and BCP 79.
315: --
316: -- Copies of IPR disclosures made to the IETF Secretariat and any
317: -- assurances of licenses to be made available, or the result of an
318: -- attempt made to obtain a general license or permission for the use of
319: -- such proprietary rights by implementers or users of this
320: -- specification can be obtained from the IETF on-line IPR repository at
321: -- http://www.ietf.org/ipr.
322: --
323: -- The IETF invites any interested party to bring to its attention any
324: -- copyrights, patents or patent applications, or other proprietary
325: -- rights that may cover technology that may be required to implement
326: -- this standard. Please address the information to the IETF at
327: -- ietf-ipr@ietf.org.
328: --
329: