smilint output for ./PW-TC-MIB
Message Severities |
Severity | Count |
minor error | 3 |
change recommended | 2 |
warning | 20 |
Message Types |
Type | Count |
date-in-past (change recommended) | 2 |
date-year-2digits (warning) | 2 |
revision-not-descending (minor error) | 2 |
textual-convention-nested (minor error) | 1 |
type-unref (warning) | 13 |
type-without-format (warning) | 5 |
Messages:
PW-TC-MIB
1: -- extracted from draft-ietf-pwe3-pw-tc-mib-02.txt
2: -- at Thu Oct 23 06:15:14 2003
12:
13: pwTCMIB MODULE-IDENTITY
14: LAST-UPDATED "200307281200Z" -- 28 July 2003 12:00:00 GMT
15: ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working
16: Group"
17: CONTACT-INFO
18: " Thomas D. Nadeau
19: Postal: Cisco Systems, Inc.
20: 250 Apollo Drive
21: Chelmsford, MA 01824
22: Tel: +1-978-497-3051
23: Email: tnadeau@cisco.com
24:
25: Dave Danenberg
26: Postal: Litchfield Communications, Inc.
27: 76 Westbury Park Rd
28: Princeton Building East
29: Watertown, CT 06795
30: Tel: +1-860-945-1573 x3180
31: Email: dave_danenberg@litchfieldcomm.com
32:
33: David Zelig
34: Postal: Corrigent Systems.
35: 126, Yigal Alon St.
36: Tel Aviv, ISRAEL
37: Phone: +972-3-6945273
38: E-mail: davidz@corrigent.com
39:
40: Andrew G. Malis
41: Postal: Tellabs, Inc.
42: 2730 Orchard Parkway
43: San Jose, CA 95134
44: Email: Andy.Malis@tellabs.com
45:
46: PWE3 Working Group Mailing List: pwe3@ietf.org"
47:
48: DESCRIPTION
49: "This MIB Module provides Textual Conventions
50: and OBJECT-IDENTITY Objects to be used PW services."
51:
52: -- Revision history.
53:
54: REVISION "200307281200Z" -- 28 July 2003 12:00:00 GMT
55: DESCRIPTION "Adding objects to cover new control draft.
56: Adapt VC types for current values in WG documents."
57:
58: REVISION "200305011200Z" -- 1 May 2003 12:00:00 GMT
59: DESCRIPTION "Adding PwVcAttachmentIdentifierType,
60: Adapt VC types for current values in WG documents."
61:
62: REVISION "0205281200Z" -- 28 May 2002 12:00:00 GMT
62: warning -
warning: date specification `0205281200Z' contains a two-digit year representing `1902'
62: change recommended -
warning: date specification `0205281200Z' predates the SMI standard
63: DESCRIPTION "Adding PwVcType, and enhance some descriptions."
64:
65: REVISION "0201301200Z" -- 30 January 2002 12:00:00 GMT
65: warning -
warning: date specification `0201301200Z' contains a two-digit year representing `1902'
65: change recommended -
warning: date specification `0201301200Z' predates the SMI standard
66: DESCRIPTION "Adding PwVcVlanCfg, PwAddressType and
67: PwOperStatus."
68:
69: REVISION "200112201200Z" -- 20 Dec 2001 12:00:00 GMT
69: minor error -
revision not in reverse chronological order
70: DESCRIPTION "Remove PwVcInstance"
71:
72: REVISION "200107121200Z" -- 12 July 2001 12:00:00 GMT
72: minor error -
revision not in reverse chronological order
73: DESCRIPTION "Initial version."
74:
75: ::= { pwMIB 1 } -- pwMIB To Be Assigned by IANA
...
81:
82: PwGroupID ::= TEXTUAL-CONVENTION
82: warning -
warning: current type `PwGroupID' is not referenced in this module
82: warning -
warning: type `PwGroupID' has no format specification
83: STATUS current
84: DESCRIPTION
85: "An administrative identification mechanism for grouping a
86: set of service-specific pseudo-wire services. May only
87: have local significance."
88: SYNTAX Unsigned32
89:
90: PwVcIDType ::= TEXTUAL-CONVENTION
90: warning -
warning: current type `PwVcIDType' is not referenced in this module
90: warning -
warning: type `PwVcIDType' has no format specification
91: STATUS current
92: DESCRIPTION
93: "Virtual Circuit Identifier. Used to identify the VC
94: (together with some other fields) in the signaling
95: session. Zero if the VC is set-up manually."
96: SYNTAX Unsigned32
97:
98: PwVcIndexType ::= TEXTUAL-CONVENTION
98: warning -
warning: current type `PwVcIndexType' is not referenced in this module
98: warning -
warning: type `PwVcIndexType' has no format specification
99: STATUS current
100: DESCRIPTION
101: "Virtual Circuit Index. Locally unique index for indexing
102: several MIB tables associated with a particular VC."
103: SYNTAX Unsigned32
104:
105: PwVcVlanCfg ::= TEXTUAL-CONVENTION
105: warning -
warning: current type `PwVcVlanCfg' is not referenced in this module
105: warning -
warning: type `PwVcVlanCfg' has no format specification
106: STATUS current
107: DESCRIPTION
108: "VLAN configuration for Ethernet PW.
109: Values between 0 to 4095 indicate the actual VLAN field
110: value.
111: A value of 4096 indicates that the object refer to
112: untagged frames, i.e. frames without 802.1Q field.
113: A value of 4097 indicates that the object is not
114: relevant."
115: SYNTAX Integer32 (0..4097)
116:
117: PwOperStatus ::= TEXTUAL-CONVENTION
117: warning -
warning: current type `PwOperStatus' is not referenced in this module
118: STATUS current
119: DESCRIPTION
120: "Indicate the operational status of the PW VC.
121:
122: - up: Ready to pass packets.
123: - down: If PW signaling has not yet finished, or
124: indications available at the service
125: level indicate that the VC is not
126: passing packets.
127: - testing: If AdminStatus at the PW level is set to
128: test.
129: - dormant: The PW is not available because of the
130: required resources are occupied PW with
131: higher priority PWs .
132: - notPresent: Some component is missing to accomplish
133: the set up of the PW.
134: - lowerLayerDown: The underlying PSN or outer tunnel is not
135: in OperStatus 'up'.
136: "
137: SYNTAX INTEGER {
138: up(1),
139: down(2),
140: testing(3),
141: unknown(4),
142: dormant(5),
143: notPresent(6),
144: lowerLayerDown(7)
145: }
146:
147: PwVcType ::= TEXTUAL-CONVENTION
147: warning -
warning: current type `PwVcType' is not referenced in this module
148: STATUS current
149: DESCRIPTION
150: "Indicate the VC type (i.e. the carried service).
151: Note: the exact set of VC types is yet to be worked
152: out by the WG.
153: "
154: SYNTAX INTEGER {
155: other(0),
156: frameRelayDlci(1),
157: atmAal5SduVcc(2),
158: atmTransparent(3),
159: ethernetTagged(4),
160: ethernet(5),
161: hdlc(6),
162: ppp(7),
163: cem(8), -- old format
164: atmCellNto1Vcc(9),
165: atmCellNto1Vpc(10),
166: ipLayer2Transport(11),
167: atmCell1to1Vcc(12),
168: atmCell1to1Vpc(13),
169: atmAal5PduVcc(14),
170: frameRelayPortMode(15),
171: cep(16)
172: }
173:
174: PwVcAttachmentIdentifierType ::= TEXTUAL-CONVENTION
174: warning -
warning: current type `PwVcAttachmentIdentifierType' is not referenced in this module
175:
176: STATUS current
177: DESCRIPTION
178: "An octet string used in the generalized FEC element for
179: identifying attachment forwarder and groups. The NULL
180: identifier is of zero length.
181: "
182: SYNTAX OCTET STRING (SIZE (0..255))
183:
184: PwVcCw ::= TEXTUAL-CONVENTION
184: warning -
warning: current type `PwVcCw' is not referenced in this module
184: minor error -
textual convention `PwVcCw' can not be derived from the textual convention `TruthValue'
185:
186: STATUS current
187: DESCRIPTION
188: "If true, indicate the existence or configuration
189: of control word.
190: "
191: SYNTAX TruthValue
192:
193: PwVcRemoteCwStatus ::= TEXTUAL-CONVENTION
193: warning -
warning: current type `PwVcRemoteCwStatus' is not referenced in this module
194:
195: STATUS current
196: DESCRIPTION
197: "Indicate the status of the control word as advertized by
198: the remote.
199: notApplicable is set by the agent for manulaly configured PW.
200:
201: waitingForNextMsg indicate that the node is waiting for
202: another
203: label mapping from the remote.
204: sentWrongBitErrorCode indicate that the local node has
205: notified the
206: peer about mismatch in the C bit.
207: rxWithdrawWithWrongBitErrorCode indicate that a withdraw
208: message
209: has been recieved with wrong C-bit error code.
210: illegalRecievedBit indicate a C bit configuration with the
211: remote
212: which is not compatible with the PW type.
213: sameAsSent indicate consistent C bit setting between the
214: peers.
215: notYetKnown indicate that a label mapping has not yet
216: recieved
217: from the peer.
218: "
219: SYNTAX INTEGER {
220: notApplicable (0),
221: waitingForNextMsg (1),
222: sentWrongBitErrorCode (2),
223: rxWithdrawWithWrongBitErrorCode (3),
224: illegalRecievedBit (4),
225: sameAsSent (5),
226: notYetKnown(6)
227: }
228:
229: PwVcCapabilities ::= TEXTUAL-CONVENTION
229: warning -
warning: current type `PwVcCapabilities' is not referenced in this module
230: STATUS current
231: DESCRIPTION
232: "Indicate the optional capabilities of the control protocol.
233: A value of zero indicate the basic LDP PW signaling.
234: Values may be added in the future based on
235: new capabilities introduced in IETF documents.
236: "
237: SYNTAX BITS {
238: pwStatusIndication (0)
239: }
240:
241: PwVcStatus ::= TEXTUAL-CONVENTION
241: warning -
warning: current type `PwVcStatus' is not referenced in this module
242: STATUS current
243: DESCRIPTION
244: "The status of the PW and the interfaces affecting this PW.
245: "
246: SYNTAX BITS {
247: pwNotForwarding (0),
248: customerFacingPwRxFault (1),
249: customerFacingPwTxFault (2),
250: psnFacingPwRxFault (3),
251: psnFacingPwTxFault (4)
252: }
253:
254: PwVcFragSize ::= TEXTUAL-CONVENTION
254: warning -
warning: current type `PwVcFragSize' is not referenced in this module
254: warning -
warning: type `PwVcFragSize' has no format specification
255: STATUS current
256: DESCRIPTION
257: "If set to value other than zero, it indicates desired
258: fragmantation
259: to the value set. If set to zero, fragmantation is not desired
260: for
261: PSN bound packets.
262: "
263: SYNTAX Unsigned32
264:
265: PwVcFragStatus ::= TEXTUAL-CONVENTION
265: warning -
warning: current type `PwVcFragStatus' is not referenced in this module
266: STATUS current
267: DESCRIPTION
268: "The status of the fragmantation process based on local
269: configuration
270: and the remote capability.
271:
272: noFragmantation bit indicate that local configuration is for no
273: fragmantation.
274: cfgFragGreaterThanPsnMtu bit indicate the local desire to
275: fragment, but the
276: fragamentation size desired is greater than the MTU available at
277: the PSN between
278: peers. Fragmantation is not done in this case.
279: cfgFragButRemoteIncapable bit
280: indicate local configuration indicate the desire for
281: fragmantation but the remote
282: is not capable of fragmantation. remoteFragCapable bit indicate
283: that the remote
284: has advertized it's fragmantation capability.
285: fragmantationEnabled bit indicate that both the local was
286: configured for
287: fragmantation and the remote has the cabability
288: to accept fragmented packets.
289: "
290: SYNTAX BITS {
291: noFragmantation (0),
292: cfgFragGreaterThanPsnMtu (1),
293: cfgFragButRemoteIncapable (2),
294: remoteFragCapable (3),
295: fragmantationEnabled (4)
296: }
297:
298: END
299:
300: --
301: -- Copyright (C) The Internet Society (2000). All Rights Reserved.
302: -- This document and translations of it may be copied and furnished to
303: -- others, and derivative works that comment on or otherwise explain
304: -- it or assist in its implementation may be prepared, copied,
305: -- published and distributed, in whole or in part, without restriction
306: -- of any kind, provided that the above copyright notice and this
307: -- paragraph are included on all such copies and derivative works.
308: -- However, this document itself may not be modified in any way, such
309: -- as by removing the copyright notice or references to the Internet
310: -- Society or other Internet organizations, except as needed for the
311: -- purpose of developing Internet standards in which case the
312: -- procedures for copyrights defined in the Internet Standards process
313: -- must be followed, or as required to translate it into languages
314: -- other than English.
315: -- The limited permissions granted above are perpetual and will not be
316: -- revoked by the Internet Society or its successors or assigns. This
317: -- document and the information contained herein is provided on an "AS
318: -- IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
319: -- TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
320: -- BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
321: -- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
322: -- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
323: