smilint output for ./PW-MPLS-DRAFT06-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| severe | 24 |
| error | 9 |
| minor error | 3 |
| change recommended | 1 |
| warning | 21 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 3 |
| description-missing (error) | 1 |
| group-membership (change recommended) | 1 |
| group-unref (warning) | 4 |
| import-failed (error) | 1 |
| index-element-no-range (error) | 1 |
| internal-flushing (warning) | 14 |
| internal-other (severe) | 15 |
| object-identifier-not-prefix (error) | 1 |
| object-identifier-unknown (severe) | 9 |
| parent-row (error) | 1 |
| sequence-no-column (minor error) | 3 |
| sequence-order (warning) | 3 |
| type-unknown (error) | 1 |
Messages:
PW-MPLS-DRAFT06-MIB
1: -- extracted from draft-ietf-pwe3-pw-mpls-mib-06.txt
2: -- at Thu Jul 8 06:21:50 2004
3:
4: PW-MPLS-DRAFT06-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE,
8: Unsigned32
9: FROM SNMPv2-SMI
10:
11: MODULE-COMPLIANCE, OBJECT-GROUP
12: FROM SNMPv2-CONF
13:
14: StorageType
15: FROM SNMPv2-TC
16:
17: InterfaceIndexOrZero
18: FROM IF-MIB
19:
20: MplsTunnelIndex, MplsTunnelInstanceIndex,
21: MplsLdpIdentifier, MplsLsrIdentifier
22: FROM MPLS-TC-STD-MIB
23:
24: MplsIndexType
25: FROM MPLS-LSR-STD-MIB
26:
27: PwVcIndexType, pwStdMIB
28: FROM PW-TC-DRAFT05-MIB
29:
30: pwVcIndex
31: FROM PW-DRAFT05-MIB
31: error -
identifier `pwVcIndex' cannot be imported from module `PW-DRAFT05-MIB'
32:
33: ;
34:
35: pwVcMplsMIB MODULE-IDENTITY
36: LAST-UPDATED "200406131200Z" -- 13 June 2004 12:00:00 GMT
37: ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working
38: Group"
39: CONTACT-INFO
40: "
41: David Zelig
42: Postal: Corrigent Systems
43: 126, Yigal Alon St.
44: Tel Aviv, ISRAEL
45: Phone: +972-3-6945273
46: E-mail: davidz@corrigent.com
47:
48: Thomas D. Nadeau
49: Postal: Cisco Systems, Inc.
50: 250 Apollo Drive
51: Chelmsford, MA 01824
52: Pseudo Wire (PW) Over MPLS June 2004
53: Management Information Base
54:
55:
56: Tel: +1-978-497-3051
57: Email: tnadeau@cisco.com
58:
59: Dave Danenberg
60: Email: dave_danenberg@yahoo.com
61:
62: Sharon Mantin
63: Postal: AxONLink (Israel) Ltd
64: 9 Bareket St.
65: Petah Tikva 49517, Israel
66: Tel: +972-3-9263972
67: Email: sharon.mantin@axonlink.com
68:
69: The PWE3 Working Group (email distribution pwe3@ietf.org,
70: http://www.ietf.org/html.charters/pwe3-charter.html)
71: "
72: DESCRIPTION
73: "This MIB module complements the PW MIB module for PW
74: operation over MPLS.
75:
76: Copyright (C) The Internet Society (date). This version
77: of this MIB module is part of RFC yyyy; see the RFC
78: itself for full legal notices.
79: -- RFC Ed.: replace yyyy with actual RFC number & remove this note
80: "
81:
82: -- Revision history.
83:
84: REVISION
85: "200406131200Z" -- 13 June 2004 12:00:00 GMT
86: DESCRIPTION
87:
88: "Draft-ietf-pwe3-pw-mpls-mib-06 version. Changes from
89: previous version:
90: 1) Compliance section details.
91: "
92:
93: REVISION
94: "200402121200Z" -- 12 February 2004 12:00:00 GMT
95: DESCRIPTION
96:
97: "Draft-ietf-pwe3-pw-mpls-mib-05 version. Changes from
98: previous version:
99: 1) Add inbound/outbound index for the nonTe mapping table
100: 2) Clarify the pwVcMplsTeMappingTunnelInstance usage in
101: pwVcMplsTeMappingTable.
102: 3) Remove an index from pwVcMplsOutboundTable and adding
103: an indication of Te or non-TE usage.
104: 4) Removing the RowStatus from the outbound tables since it
105: possible to configure a PW to a single TE tunnel head-end
106: and/or a single nonTE tunnel, so the agent can open the
107: Pseudo Wire (PW) Over MPLS June 2004
108: Management Information Base
109:
110:
111: row automatically.
112: 5) Adding a nonTe inbound table in order to enable a quick
113: search for a PW based on pwVcIndex.
114: "
115: REVISION
116: "200311301200Z" -- 30 November 2003 12:00:00 EST
117: DESCRIPTION
118: "Draft-ietf-pwe3-pw-mpls-mib-04 version. Changes from
119: previous version:
120: 1) Adapting description to MIB boilerplate.
121: 2) Module OID changed to PWE3 tree.
122: 3) Sync descriptions of various items to table structure and
123: removing unnecessary references.
124: "
125: REVISION
126: "200307291200Z" -- 29 July 2003 12:00:00 EST
127: DESCRIPTION
128: "Draft-ietf-pwe3-pw-mpls-mib-02 version. Changes from
129: previous version:
130: 1) Removing inbound table (no strict mode and no knowledge
131: of inbound tunnel).
132: 2) Provisioning (i.e. RowCreate) done via mapping tables.
133: Outbound table is now read only for sorted search for
134: pwVcIndex.
135: "
136:
137: REVISION
138: "200206021200Z" -- 02 June 2002 12:00:00 EST
139: DESCRIPTION
140: "Draft-ietf-pwe3-pw-mpls-mib-00 version. Changes from
141: previous version:
142: 1) Splitting the mapping table into two tables, one for
143: Non TE application and one for TE application.
144: 2) Object types alignment with MPLS MIBs.
145: "
146: REVISION
147: "200201291200Z" -- 29 January 2002 12:00:00 EST
148: DESCRIPTION
149: "Changes from previous version:
150: 1) Add LDP entity association.
151: 2) Clarify inbound/outbound directions.
152: 3) Simplify indexing of outbound and inbound tables
153: and providing get next variables.
154: "
155: REVISION
156: "200111071200Z" -- 7 November 2001 12:00:00 EST
157: DESCRIPTION
158: "Changes from previous version:
159: 1) Remove Vc instance from table indexing.
160: 2) Update descriptions of indexing and protection.
161: 3) Remove the need for MPLS-LSR in case of VC only.
162: Pseudo Wire (PW) Over MPLS June 2004
163: Management Information Base
164:
165:
166: 4) Change pwVcMplsMplsType to BITS in order to enable
167: multiple types of outer tunnel.
168: 5) Add ifindex to outer tunnel tables to support vcOnly
169: option.
170: 6) change naming of outbound, inbound and mapping tables to
171: reflect addition of VC only port ifindexes.
172: 7) Adapt order of items in mapping table to SNMP convention.
173: "
174: REVISION
175: "200107111200Z" -- July 11 2001 12:00:00 EST
176: DESCRIPTION
177: "draft-zelig-pw-mib-00.txt - initial version"
178:
179: ::= { pwStdMIB x } -- To be assigned by IANA
179: error -
Object identifier element `x' name only allowed as first element
180: -- the value 3 is requested for this
181: -- specific Module.
182:
183: -- Top-level components of this MIB.
184:
185: -- Tables, Scalars
186: pwVcMplsObjects OBJECT IDENTIFIER
187: ::= { pwVcMplsMIB 1 }
188: -- Conformance
189: pwVcMplsConformance OBJECT IDENTIFIER
190: ::= { pwVcMplsMIB 2 }
191:
192: -- PW MPLS table
193:
194: pwVcMplsTable OBJECT-TYPE
195: SYNTAX SEQUENCE OF PwVcMplsEntry
195: error -
unknown type `PwVcMplsEntry'
196: MAX-ACCESS not-accessible
197: STATUS current
198: DESCRIPTION
199: "This table controls MPLS specific parameters when the PW is
200: going to be carried over MPLS PSN."
201: ::= { pwVcMplsObjects 1 }
202:
203: pwVcMplsEntry OBJECT-TYPE
204: SYNTAX PwVcMplsEntry
205: MAX-ACCESS not-accessible
206: STATUS current
207: DESCRIPTION
208: "A row in this table represents parameters specific to MPLS
209: PSN for a pseudo wire (PW). The row is created
210: automatically by the local agent if the pwVcPsnType is
211: MPLS. It is indexed by pwVcIndex, which uniquely
212: identifying a singular PW.
213: "
214: INDEX { pwVcIndex }
214: severe -
unknown object identifier label `pwVcIndex'
215:
216: ::= { pwVcMplsTable 1 }
217: Pseudo Wire (PW) Over MPLS June 2004
217: error -
`Pseudo' should start with a lower case letter
217: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
218: Management Information Base
219:
220:
221:
222: PwVcMplsEntry ::= SEQUENCE {
223: pwVcMplsMplsType BITS,
224: pwVcMplsExpBitsMode INTEGER,
225: pwVcMplsExpBits Unsigned32,
226: pwVcMplsTtl Unsigned32,
227: pwVcMplsLocalLdpID MplsLdpIdentifier,
228: pwVcMplsLocalLdpEntityID MplsLsrIdentifier,
229: pwVcMplsPeerLdpID MplsLdpIdentifier,
230: pwVcMplsStorageType StorageType
231: }
231: warning -
warning: flushing recent incorrect declaration, see previous error(s)
232:
233: pwVcMplsMplsType OBJECT-TYPE
234: SYNTAX BITS {
235: mplsTe (0),
236: mplsNonTe (1),
237: vcOnly (2)
238: }
239: MAX-ACCESS read-write
240: STATUS current
241: DESCRIPTION
242: "Set by the operator to indicate the outer tunnel types, if
243: exists. mplsTe(0) is used if the outer tunnel was set-up
244: by MPLS-TE, and mplsNonTe(1) is used the outer tunnel was
245: set up by LDP or manually. Combination of mplsTe(0) and
246: mplsNonTe(1) may exist together.
247: vcOnly(2) is used if there is no outer tunnel label, i.e.
248: in static provisioning without MPLS tunnel. vcOnly(2)
249: cannot be combined with mplsNonTe(1) or mplsTe(0)."
250: DEFVAL { { mplsNonTe } }
251: ::= { pwVcMplsEntry 1 }
252:
253:
254: pwVcMplsExpBitsMode OBJECT-TYPE
255: SYNTAX INTEGER {
256: outerTunnel (1),
257: specifiedValue (2),
258: serviceDependant (3)
259: }
260:
261: MAX-ACCESS read-write
262: STATUS current
263: DESCRIPTION
264: "Set by the operator to indicate the way the PW shim label
265: EXP bits are to be determined. The value of outerTunnel(1)
266: is used where there is an outer tunnel - pwVcMplsMplsType
267: is mplsTe(0) or mplsNonTe(1). Note that in this case there
268: is no need to mark the PW label with the EXP bits since the
269: PW label is not visible to the intermediate nodes.
270: If there is no outer tunnel, specifiedValue(2) indicates
271: that the value is specified by pwVcMplsExpBits, and
272: Pseudo Wire (PW) Over MPLS June 2004
273: Management Information Base
274:
275:
276: serviceDependant(3) indicates that the EXP bits are setup
277: based on a rule specified in the emulated service specific
278: tables, for example when the EXP bits are a function of
279: 802.1p marking for Ethernet emulated service."
280:
281: DEFVAL { outerTunnel }
282: ::= { pwVcMplsEntry 2 }
283:
284: pwVcMplsExpBits OBJECT-TYPE
285: SYNTAX Unsigned32 (0..7)
286: MAX-ACCESS read-write
287: STATUS current
288: DESCRIPTION
289: "Set by the operator to indicate the MPLS EXP bits to be
290: used on the PW shim label if pwVcMplsExpBitsMode is
291: specifiedValue(2), zero otherwise."
292: DEFVAL { 0 }
293: ::= { pwVcMplsEntry 3 }
294:
295: pwVcMplsTtl OBJECT-TYPE
296: SYNTAX Unsigned32 (0..255)
297: MAX-ACCESS read-write
298: STATUS current
299: DESCRIPTION
300: "Set by the operator to indicate the PW TTL value to be
301: used on the PW shim label."
302: DEFVAL { 2 }
303: ::= { pwVcMplsEntry 4 }
304:
305: pwVcMplsLocalLdpID OBJECT-TYPE
306: SYNTAX MplsLdpIdentifier
307: MAX-ACCESS read-write
308: STATUS current
309: DESCRIPTION
310: "The local LDP identifier of the LDP entity creating
311: this PW in the local node. As the PW labels are always
312: set from the per platform label space, the last two octets
313: in the LDP ID MUST be always both zeros."
314: REFERENCE
315: "'LDP specifications', RFC 3036 section 2.2.2."
316: ::= { pwVcMplsEntry 5 }
317:
318: pwVcMplsLocalLdpEntityID OBJECT-TYPE
319: SYNTAX MplsLsrIdentifier
320: MAX-ACCESS read-write
321: STATUS current
322: DESCRIPTION
323: "The local node LDP Entity ID of the LDP entity creating
324: this PW. Should return the value of all zeros if not
325: used."
326: ::= { pwVcMplsEntry 6 }
327: Pseudo Wire (PW) Over MPLS June 2004
327: error -
`Pseudo' should start with a lower case letter
327: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
328: Management Information Base
329:
330:
331:
332: pwVcMplsPeerLdpID OBJECT-TYPE
333: SYNTAX MplsLdpIdentifier
334: MAX-ACCESS read-only
335: STATUS current
336: DESCRIPTION
337: "The peer LDP identifier as identified from the LDP
338: session. Should return the value of zero if not applicable
339: or not known yet."
340: ::= { pwVcMplsEntry 7 }
340: warning -
warning: flushing recent incorrect declaration, see previous error(s)
341:
342: pwVcMplsStorageType OBJECT-TYPE
343: SYNTAX StorageType
344: MAX-ACCESS read-write
345: STATUS current
346: DESCRIPTION
347: "This variable indicates the storage type for this row."
348: ::= { pwVcMplsEntry 8 }
349:
350: -- End of PW MPLS table
351:
352: -- Pseudo Wire MPLS Outbound Tunnel table
353:
354: pwVcMplsOutboundTable OBJECT-TYPE
355: SYNTAX SEQUENCE OF PwVcMplsOutboundEntry
356: MAX-ACCESS not-accessible
357: STATUS current
358: DESCRIPTION
359: "This table reports and configure the current outbound MPLS
360: tunnels (i.e. toward the PSN) or the physical interface in
361: case of PW label only that carry the PW traffic. It also
362: reports the current outer tunnel and LSP which forward the
363: PW traffic."
364: ::= { pwVcMplsObjects 2 }
365:
366: pwVcMplsOutboundEntry OBJECT-TYPE
367: SYNTAX PwVcMplsOutboundEntry
368: MAX-ACCESS not-accessible
369: STATUS current
370: DESCRIPTION
371: "A row in this table configured the outer tunnel used for
372: carrying the PW traffic toward the PSN.
373: In the case of PW label only, it configures the interface
374: that will carry the PW traffic.
375:
376: An entry in this table augments the pwVcMplsEntry, and is
377: created automatically when the corresponding row has been
378: created by the agent in the pwVcMplsEntry.
379:
380: This table points to the appropriate MPLS MIB module.
381: In the MPLS-TE case, the 3 variables relevant to the
382: Pseudo Wire (PW) Over MPLS June 2004
383: Management Information Base
384:
385:
386: indexing of a TE tunnel head-end are used as in
387: MPLS-TE-STD-MIB are to be configured, and the tunnel
388: instance indicates the LSP that is currently in use for
389: forwarding the traffic.
390:
391: In case of signaled Non-TE MPLS (an outer tunnel label
392: assigned by LDP) the table points to the XC entry in the
393: LSR-STD-MIB. If the Non-TE MPLS tunnel is manually
394: configured, the operator configure the XC pointer to this
395: tunnel.
396:
397: In case of PW label only (no outer tunnel) the ifIndex of
398: the port to carry the PW is configured here.
399:
400: It is possible to associate a PW to one TE tunnel head-end
401: and a non-TE tunnel together. An indication in this table
402: will report the currently active one, In addition, in the
403: TE case the table reports the active tunnel instance
404: (i.e. the specific LSP in use).
405: "
406:
407: AUGMENTS { pwVcMplsEntry }
408:
409: ::= { pwVcMplsOutboundTable 1 }
410:
411: PwVcMplsOutboundEntry ::= SEQUENCE {
411: minor error -
SEQUENCE element #2 `pwVcMplsOutboundTunnelIndex' is not a child node under `pwVcMplsOutboundEntry'
411: warning -
warning: SEQUENCE element #3 `pwVcMplsOutboundTunnelInstance' does not match order of columnar objects under `pwVcMplsOutboundEntry'
412: pwVcMplsOutboundLsrXcIndex MplsIndexType,
413: pwVcMplsOutboundTunnelIndex MplsTunnelIndex,
413: severe -
unknown object identifier label `pwVcMplsOutboundTunnelIndex'
414: pwVcMplsOutboundTunnelInstance MplsTunnelInstanceIndex,
415: pwVcMplsOutboundTunnelLclLSR MplsLsrIdentifier,
416: pwVcMplsOutboundTunnelPeerLSR MplsLsrIdentifier,
416: severe -
unknown object identifier label `pwVcMplsOutboundTunnelPeerLSR'
417: pwVcMplsOutboundIfIndex InterfaceIndexOrZero,
418: pwVcMplsOutboundTunnelTypeInUse INTEGER
419: }
420:
421: pwVcMplsOutboundLsrXcIndex OBJECT-TYPE
422: SYNTAX MplsIndexType
423: MAX-ACCESS read-write
424: STATUS current
425: DESCRIPTION
426: "This object is applicable if pwVcMplsMplsType mplsNonTe(1)
427: bit is set, and MUST return a value of zero otherwise.
428: If the outer tunnel is signaled, the object is read-only
429: and indicate the XC index in the MPLS-LSR-STD-MIB of the
430: outer tunnel toward the peer. Otherwise (tunnel is set-up
431: manually) the operator define the XC index of the manually
432: created outer tunnel through this object.
433: "
434: ::= { pwVcMplsOutboundEntry 1 }
435:
436: pwVcMplsOutboundTunnelIndex OBJECT-TYPE
437: Pseudo Wire (PW) Over MPLS June 2004
437: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting SYNTAX
438: Management Information Base
439:
440:
441: SYNTAX MplsTunnelIndex
442: MAX-ACCESS read-write
443: STATUS current
444: DESCRIPTION
445: "This object is applicable if pwVcMplsMplsType mplsTe(0)
446: bit is set, and MUST return a value of zero otherwise.
447: It is Part of set of indexes for outbound tunnel.
448: The operator set this object to represent the desired
449: tunnel head-end toward the peer for carrying the PW
450: traffic.
451: "
452: ::= { pwVcMplsOutboundEntry 2 }
452: warning -
warning: flushing recent incorrect declaration, see previous error(s)
453:
454: pwVcMplsOutboundTunnelInstance OBJECT-TYPE
455: SYNTAX MplsTunnelInstanceIndex
456: MAX-ACCESS read-only
457: STATUS current
458: DESCRIPTION
459: "This object is applicable if pwVcMplsMplsType mplsTe(0)
460: bit is set, and MUST return a value of zero otherwise.
461: It indicates the actual tunnel instance that is currently
462: active and carrying the PW traffic - it should return the
463: value of zero until if the information from the MPLS-TE
464: application is not yet known.
465: "
466: ::= { pwVcMplsOutboundEntry 3 }
467:
468: pwVcMplsOutboundTunnelLclLSR OBJECT-TYPE
469: SYNTAX MplsLsrIdentifier
470: MAX-ACCESS read-write
471: STATUS current
472: DESCRIPTION
473: "This object is applicable if pwVcMplsMplsType mplsTe(0)
474: bit is set, and MUST return a value of all zeros otherwise.
475: It is part of set of indexes for outbound tunnel.
476: The operator set this object to represent the desired
477: tunnel head-end toward the peer for carrying the PW
478: traffic.
479: "
480: ::= { pwVcMplsOutboundEntry 4 }
481:
482: pwVcMplsOutboundTunnelPeerLSR OBJECT-TYPE
483: SYNTAX MplsLsrIdentifier
484: MAX-ACCESS read-write
485: STATUS current
486: DESCRIPTION
487: "This object is applicable if pwVcMplsMplsType mplsTe(0)
488: bit is set, and MUST return a value of zero otherwise.
489: It is part of set of indexes for outbound tunnel. It is
490: typically equal to pwVcPeerAddr.
491: "
492: Pseudo Wire (PW) Over MPLS June 2004
492: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
493: Management Information Base
494:
495:
496: ::= { pwVcMplsOutboundEntry 5 }
496: warning -
warning: flushing recent incorrect declaration, see previous error(s)
497:
498: pwVcMplsOutboundIfIndex OBJECT-TYPE
499: SYNTAX InterfaceIndexOrZero
500: MAX-ACCESS read-write
501: STATUS current
502: DESCRIPTION
503: "This object is applicable if pwVcMplsMplsType mplsTe(0)
504: bit is set, and MUST return a value of zero otherwise.
505: The operator configure the ifIndex of the outbound port
506: in this case.
507: "
508: ::= { pwVcMplsOutboundEntry 6 }
509:
510: pwVcMplsOutboundTunnelTypeInUse OBJECT-TYPE
511: SYNTAX INTEGER {
512: notYetKnown (1),
513: mplsTe (2),
514: mplsNonTe (3),
515: vcOnly (4)
516: }
517: MAX-ACCESS read-only
518: STATUS current
519: DESCRIPTION
520: "This object indicates the current tunnel that is carrying
521: the PW traffic.
522: The value of notYetKnown(1) should be used if the agent is
523: currently unable to determine which tunnel or interface is
524: carrying the PW, for example because both tunnels are in
525: operational status down.
526: "
527: ::= { pwVcMplsOutboundEntry 7 }
528:
529:
530: -- End of PW MPLS Outbound Tunnel table
531:
532: -- PW MPLS inbound table
533:
534: pwVcMplsInboundTable OBJECT-TYPE
535: SYNTAX SEQUENCE OF PwVcMplsInboundEntry
536: MAX-ACCESS not-accessible
537: STATUS current
538: DESCRIPTION
539: "This table indicates the PW LDP XC entry in the
540: MPLS-LSR-STD-MIB for signaled PWs.
541: "
542: ::= { pwVcMplsObjects 3 }
543:
544: pwVcMplsInboundEntry OBJECT-TYPE
545: SYNTAX PwVcMplsInboundEntry
546: MAX-ACCESS not-accessible
547: Pseudo Wire (PW) Over MPLS June 2004
547: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
548: Management Information Base
549:
550:
551: STATUS current
552: DESCRIPTION
553: "A row in this table is created by the agent
554: for each signaled PW, and shows the XC index related to
555: the PW signaling in the inbound direction in the
556: MPLS-LSR-STD-MIB that controls and display the information
557: for all the LDP signaling processes in the local node.
558: "
559:
560: INDEX { pwVcIndex }
560: warning -
warning: flushing recent incorrect declaration, see previous error(s)
561:
562: ::= { pwVcMplsInboundTable 1 }
562: severe -
syntax error, unexpected COLON_COLON_EQUAL
562: warning -
warning: flushing recent incorrect declaration, see previous error(s)
563:
564: PwVcMplsInboundEntry ::= SEQUENCE {
565: pwVcMplsInboundXcIndex MplsIndexType
566: }
567:
568: pwVcMplsInboundXcIndex OBJECT-TYPE
568: change recommended -
warning: node `pwVcMplsInboundXcIndex' must be contained in at least one conformance group
569: SYNTAX MplsIndexType
570: MAX-ACCESS read-only
571: STATUS current
572: DESCRIPTION
573: "The XC index representing this PW in the inbound
574: direction. Should return the value of zero if the
575: information is not yet known."
576: ::= { pwVcMplsInboundEntry 1 }
576: severe -
unknown object identifier label `pwVcMplsInboundEntry'
577:
578: -- End of PW MPLS inbound table
579:
580: -- PW to Non-TE mapping Table.
581:
582: pwVcMplsNonTeMappingTable OBJECT-TYPE
583: SYNTAX SEQUENCE OF PwVcMplsNonTeMappingEntry
584: MAX-ACCESS not-accessible
585: STATUS current
586: DESCRIPTION
587: "This table indicates outbound Tunnel to a PW in non-TE
588: applications, maps the PW to it's (inbound) XC entry, and
589: indicates the PW to physical interface mapping for a PW
590: label to physical interface a PW label is in use without
591: outer tunnel.
592: "
593: ::= { pwVcMplsObjects 4 }
594:
595: pwVcMplsNonTeMappingEntry OBJECT-TYPE
596: SYNTAX PwVcMplsNonTeMappingEntry
597: MAX-ACCESS not-accessible
598: STATUS current
599: DESCRIPTION
600: "A row in this table displays the association
601: between the PW and
602: Pseudo Wire (PW) Over MPLS June 2004
603: Management Information Base
604:
605:
606: - it's non-TE MPLS outbound outer Tunnel or,
607: - it's XC entry in the MPLS-LSR-STD-MIB,
608: - it's physical interface if there is no outer tunnel
609: (PW label only) and manual configuration.
610:
611: Rows are created in this table by the by the
612: agent depending on the setting of pwVcMplsMplsType:
613:
614: - If pwVcMplsMplsType mplsNonTe(1) bit is set, the agent
615: creates a row for the outbound direction
616: (pwVcMplsNonTeMappingDirection set to psnBound(1)).
617: The pwVcMplsNonTeMappingXcIndex holds the XC index in the
618: MPLS-LSR-STD-MIB of the PSN bound outer tunnel.
619: pwVcMplsNonTeMappingIfIndex MUST be zero for this row.
620:
621: - If pwVcMplsMplsType vcOnly(2) bit is set, the agent
622: creates a row for the outbound direction
623: (pwVcMplsNonTeMappingDirection set to psnBound(1)).
624: The pwVcMplsNonTeMappingIfIndex holds the ifIndex of the
625: physical port this PW will use in the outbound direction.
626: pwVcMplsNonTeMappingXcIndex MUST be zero for this row.
627:
628: - If the PW has been set-up by signaling protocol (i.e.
629: pwVcOwner equal pwIdFecSignaling(2) or
630: genFecSignaling(3)), the agent creates a row for the
631: inbound direction (pwVcMplsNonTeMappingDirection set to
632: fromPsn(2)).
633: The pwVcMplsNonTeMappingXcIndex holds the XC index in the
634: MPLS-LSR-STD-MIB of the PW LDP generated XC entry.
635: pwVcMplsNonTeMappingIfIndex MUST be zero for this row.
636:
637: An application can use this table to quickly retrieve the
638: PW carried over specific non-TE MPLS outer tunnel or
639: physical interface.
640: "
641:
642: INDEX { pwVcMplsNonTeMappingDirection,
642: severe -
unknown object identifier label `pwVcMplsNonTeMappingDirection'
642: error -
index element `pwVcMplsNonTeMappingDirection' of row `pwVcMplsNonTeMappingEntry' must have a range restriction
643: pwVcMplsNonTeMappingXcIndex,
644: pwVcMplsNonTeMappingIfIndex,
645: pwVcMplsNonTeMappingVcIndex }
646:
647: ::= { pwVcMplsNonTeMappingTable 1 }
648:
649: PwVcMplsNonTeMappingEntry ::= SEQUENCE {
649: minor error -
SEQUENCE element #1 `pwVcMplsNonTeMappingDirection' is not a child node under `pwVcMplsNonTeMappingEntry'
649: warning -
warning: SEQUENCE element #2 `pwVcMplsNonTeMappingXcIndex' does not match order of columnar objects under `pwVcMplsNonTeMappingEntry'
650: pwVcMplsNonTeMappingDirection INTEGER,
651: pwVcMplsNonTeMappingXcIndex MplsIndexType,
652: pwVcMplsNonTeMappingIfIndex InterfaceIndexOrZero,
653: pwVcMplsNonTeMappingVcIndex PwVcIndexType
654: }
655:
656: pwVcMplsNonTeMappingDirection OBJECT-TYPE
657: Pseudo Wire (PW) Over MPLS June 2004
657: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting SYNTAX
658: Management Information Base
659:
660:
661: SYNTAX INTEGER {
662: psnBound (1),
663: fromPsn (2)
664: }
664: warning -
warning: flushing recent incorrect declaration, see previous error(s)
665: MAX-ACCESS not-accessible
665: severe -
syntax error, unexpected MAX_ACCESS
666: STATUS current
667: DESCRIPTION
668: "Index for the conceptual XC row identifying Tunnel to PW
669: mappings, indicating the direction of packet flow the entry
670: is related too.
671: psnBound(1) indicates that the entry is related to
672: packets toward the PSN.
673: fromPsn(2) indicates that the entry is related to
674: packets coming from the PSN.
675: "
676: ::= { pwVcMplsNonTeMappingEntry 1 }
676: warning -
warning: flushing recent incorrect declaration, see previous error(s)
677:
678: pwVcMplsNonTeMappingXcIndex OBJECT-TYPE
679: SYNTAX MplsIndexType
680: MAX-ACCESS not-accessible
681: STATUS current
682: DESCRIPTION
683: "See the description clause of pwVcMplsNonTeMappingEntry for
684: the usage guidelines of this object."
685: ::= { pwVcMplsNonTeMappingEntry 2 }
686:
687: pwVcMplsNonTeMappingIfIndex OBJECT-TYPE
688: SYNTAX InterfaceIndexOrZero
689: MAX-ACCESS not-accessible
690: STATUS current
691: DESCRIPTION
692: "See the description clause of pwVcMplsNonTeMappingEntry for
693: the usage guidelines of this object."
694: ::= { pwVcMplsNonTeMappingEntry 3 }
695:
696: pwVcMplsNonTeMappingVcIndex OBJECT-TYPE
697: SYNTAX PwVcIndexType
698: MAX-ACCESS read-only
699: STATUS current
700: DESCRIPTION
701: "The value that represent the PW in the pwVcTable."
702: ::= { pwVcMplsNonTeMappingEntry 4 }
703:
704: -- End of PW to Non-TE mapping Table.
705:
706: -- PW to TE MPLS tunnels mapping Table.
707:
708: pwVcMplsTeMappingTable OBJECT-TYPE
709: SYNTAX SEQUENCE OF PwVcMplsTeMappingEntry
710: MAX-ACCESS not-accessible
711: STATUS current
712: Pseudo Wire (PW) Over MPLS June 2004
712: error -
description missing in object definition
712: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
713: Management Information Base
714:
715:
716: DESCRIPTION
717: "This table enable the retrieval of a PW association to the
718: outbound MPLS tunnel for MPLS-TE applications."
719: ::= { pwVcMplsObjects 5 }
719: warning -
warning: flushing recent incorrect declaration, see previous error(s)
720:
721: pwVcMplsTeMappingEntry OBJECT-TYPE
721: error -
row's parent node must be a table node
722: SYNTAX PwVcMplsTeMappingEntry
723: MAX-ACCESS not-accessible
724: STATUS current
725: DESCRIPTION
726: "A row in this table represents the association
727: between a PW and it's MPLS-TE outer (head-end) Tunnel.
728:
729: An application can use this table to quickly retrieve the
730: list of the PWs that are configured on a specific MPLS TE
731: outer tunnel.
732:
733: The pwVcMplsTeMappingTunnelInstance reports the actual
734: LSP out of the tunnel head-end that is currently
735: forwarding the traffic.
736:
737: The table in indexed by the head-end indexes of a TE
738: tunnel and the PW index.
739: "
740:
741: INDEX { pwVcMplsTeMappingTunnelIndex,
742: pwVcMplsTeMappingTunnelInstance,
742: severe -
unknown object identifier label `pwVcMplsTeMappingTunnelInstance'
743: pwVcMplsTeMappingTunnelPeerLsrID,
744: pwVcMplsTeMappingTunnelLocalLsrID,
745: pwVcMplsTeMappingVcIndex }
746:
747: ::= { pwVcMplsTeMappingTable 1 }
747: severe -
unknown object identifier label `pwVcMplsTeMappingTable'
748:
749: PwVcMplsTeMappingEntry ::= SEQUENCE {
749: minor error -
SEQUENCE element #2 `pwVcMplsTeMappingTunnelInstance' is not a child node under `pwVcMplsTeMappingEntry'
749: warning -
warning: SEQUENCE element #3 `pwVcMplsTeMappingTunnelPeerLsrID' does not match order of columnar objects under `pwVcMplsTeMappingEntry'
750: pwVcMplsTeMappingTunnelIndex MplsTunnelIndex,
751: pwVcMplsTeMappingTunnelInstance MplsTunnelInstanceIndex,
752: pwVcMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier,
753: pwVcMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier,
754: pwVcMplsTeMappingVcIndex PwVcIndexType
755: }
756:
757: pwVcMplsTeMappingTunnelIndex OBJECT-TYPE
758: SYNTAX MplsTunnelIndex
759: MAX-ACCESS not-accessible
760: STATUS current
761: DESCRIPTION
762: "Primary index for the conceptual row identifying the
763: MPLS-TE tunnel that is carrying the PW traffic."
764: ::= { pwVcMplsTeMappingEntry 1 }
765:
766: pwVcMplsTeMappingTunnelInstance OBJECT-TYPE
767: Pseudo Wire (PW) Over MPLS June 2004
767: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting SYNTAX
768: Management Information Base
769:
770:
771: SYNTAX MplsTunnelInstanceIndex
772: MAX-ACCESS not-accessible
773: STATUS current
774: DESCRIPTION
775: "This object identify the MPLS-TE LSP that is carrying the
776: PW traffic. Should return the value of zero if the
777: information of the specific LSP is not yet known.
778: Note that based on the recommendation in the
779: MPLS-TC-STD-MIB, instance index 0 should refer to the
780: configured tunnel interface."
781: ::= { pwVcMplsTeMappingEntry 2 }
781: warning -
warning: flushing recent incorrect declaration, see previous error(s)
782:
783: pwVcMplsTeMappingTunnelPeerLsrID OBJECT-TYPE
784: SYNTAX MplsLsrIdentifier
785: MAX-ACCESS not-accessible
786: STATUS current
787: DESCRIPTION
788: "Identifies the Peer LSR when the outer tunnel is MPLS-TE
789: based."
790: ::= { pwVcMplsTeMappingEntry 3 }
791:
792: pwVcMplsTeMappingTunnelLocalLsrID OBJECT-TYPE
793: SYNTAX MplsLsrIdentifier
794: MAX-ACCESS not-accessible
795: STATUS current
796: DESCRIPTION
797: "Identifies the local LSR."
798: ::= { pwVcMplsTeMappingEntry 4 }
799:
800: pwVcMplsTeMappingVcIndex OBJECT-TYPE
801: SYNTAX PwVcIndexType
802: MAX-ACCESS read-only
803: STATUS current
804: DESCRIPTION
805: "The value that represent the PW in the pwVcTable."
806: ::= { pwVcMplsTeMappingEntry 5 }
807:
808: -- End of PW to TE MPLS tunnels mapping Table.
809:
810: -- conformance information
811:
812: pwVcMplsGroups OBJECT IDENTIFIER ::= { pwVcMplsConformance 1 }
813: pwVcMplsCompliances OBJECT IDENTIFIER ::= { pwVcMplsConformance 2 }
814:
815: -- Compliance requirement for fully compliant implementations.
816:
817: pwMplsModuleFullCompliance MODULE-COMPLIANCE
818: STATUS current
819: DESCRIPTION
820: "The compliance statement for agents that provide full
821: support for PW-MPLS MIB Module. Such devices can
822: Pseudo Wire (PW) Over MPLS June 2004
823: Management Information Base
824:
825:
826: then be monitored and also be configured using
827: this MIB module."
828:
829: MODULE -- this module
830: MANDATORY-GROUPS { pwVcMplsGroup,
831: pwVcMplsOutboundMainGroup,
832: pwVcMplsInboundGroup,
832: severe -
unknown object identifier label `pwVcMplsInboundGroup'
833: pwVcMplsMappingGroup
834: }
835:
836: GROUP pwVcMplsOutboundTeGroup
837: DESCRIPTION "This group MUST be supported if the implementation
838: allows MPLS TE tunnels to carry PW traffic.
839: "
840:
841: OBJECT pwVcMplsMplsType
842: DESCRIPTION "Support of vcOnly(2) is not required. At least one
843: of mplsTe(0) or mplsNonTe(1) MUST be supported if
844: signaling of PW is supported.
845: "
846:
847: OBJECT pwVcMplsExpBitsMode
848: DESCRIPTION "Support of specifiedValue(2) and
849: serviceDependant(3)
850: is optional.
851: "
852:
853: OBJECT pwVcMplsLocalLdpID
854: MIN-ACCESS read-only
855: DESCRIPTION "A read-write access is required if the
856: implementation supports more than one LDP entity
857: identifier for PW signaling.
858: "
859:
860: OBJECT pwVcMplsLocalLdpEntityID
861: MIN-ACCESS read-only
862: DESCRIPTION "A read-write access is required if the
863: implementation supports more than one LDP entity
864: index for PW signaling.
865: "
866:
867: OBJECT pwVcMplsOutboundLsrXcIndex
868: MIN-ACCESS read-only
869: DESCRIPTION "A value other than zero MUST be supported if the
870: implementation support non TE signaling of the
871: outer tunnel.
872: A read-write access MUST be supported if the
873: implementation supports manually setting of the PW
874: labels and carrying them over non-TE tunnels.
875: "
876: Pseudo Wire (PW) Over MPLS June 2004
876: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
877: Management Information Base
878:
879:
880: OBJECT pwVcMplsOutboundIfIndex
881: MIN-ACCESS read-only
882: DESCRIPTION "A value other than zero and read-write operations
883: MUST be supported if the implementation supports
884: manully configured PW without MPLS outer tunnel.
885: "
886: ::= { pwVcMplsCompliances 1 }
886: warning -
warning: flushing recent incorrect declaration, see previous error(s)
887:
888: -- Compliance requirement for Read Only compliant implementations.
889:
890: pwMplsModuleReadOnlyCompliance MODULE-COMPLIANCE
891: STATUS current
892: DESCRIPTION
893: "The compliance statement for agents that provide read
894: only support for PW-MPLS MIB Module. Such devices can
895: then be monitored but cannot be configured using this
896: MIB module."
897:
898: MODULE -- this module
899: MANDATORY-GROUPS { pwVcMplsGroup,
900: pwVcMplsOutboundMainGroup,
901: pwVcMplsInboundGroup,
902: pwVcMplsMappingGroup
903: }
904:
905: GROUP pwVcMplsOutboundTeGroup
906: DESCRIPTION "This group MUST be supported if the implementation
907: allows MPLS TE tunnels to carry PW traffic.
908: "
909:
910: OBJECT pwVcMplsMplsType
911: MIN-ACCESS read-only
912: DESCRIPTION "Write access is not required.
913: Support of vcOnly(2) is not required. At least one
914: of mplsTe(0) or mplsNonTe(1) MUST be supported if
915: signaling of PW is supported.
916: "
917:
918: OBJECT pwVcMplsExpBitsMode
919: MIN-ACCESS read-only
920: DESCRIPTION "Write access is not required.
921: Support of specifiedValue(2) and
922: serviceDependant(3)
923: is optional.
924: "
925:
926: OBJECT pwVcMplsExpBits
927: MIN-ACCESS read-only
928: DESCRIPTION "Write access is not required.
929: "
930: Pseudo Wire (PW) Over MPLS June 2004
930: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
931: Management Information Base
932:
933:
934: OBJECT pwVcMplsTtl
935: MIN-ACCESS read-only
936: DESCRIPTION "Write access is not required.
937: "
938:
939: OBJECT pwVcMplsLocalLdpID
940: MIN-ACCESS read-only
941: DESCRIPTION "Write access is not required.
942: "
943:
944: OBJECT pwVcMplsLocalLdpEntityID
945: MIN-ACCESS read-only
946: DESCRIPTION "Write access is not required.
947: "
948:
949: OBJECT pwVcMplsStorageType
950: MIN-ACCESS read-only
951: DESCRIPTION "Write access is not required.
952: "
953:
954: OBJECT pwVcMplsOutboundLsrXcIndex
955: MIN-ACCESS read-only
956: DESCRIPTION "Write access is not required.
957: A value other than zero MUST be supported if the
958: implementation support non TE signaling of the
959: outer tunnel.
960: "
961:
962: OBJECT pwVcMplsOutboundTunnelIndex
963: MIN-ACCESS read-only
964: DESCRIPTION "Write access is not required.
965: "
966:
967: OBJECT pwVcMplsOutboundTunnelLclLSR
968: MIN-ACCESS read-only
969: DESCRIPTION "Write access is not required.
970: "
971:
972: OBJECT pwVcMplsOutboundTunnelPeerLSR
973: MIN-ACCESS read-only
974: DESCRIPTION "Write access is not required.
975: "
976:
977: OBJECT pwVcMplsOutboundIfIndex
978: MIN-ACCESS read-only
979: DESCRIPTION "Write access is not required.
980: A value other than zero MUST be supported if the
981: implementation supports manually configured PW
982: without MPLS outer tunnel.
983: "
984: Pseudo Wire (PW) Over MPLS June 2004
985: Management Information Base
986:
987:
988: ::= { pwVcMplsCompliances 2 }
988: warning -
warning: flushing recent incorrect declaration, see previous error(s)
989:
990:
991: -- Units of conformance.
992:
993: pwVcMplsGroup OBJECT-GROUP
993: warning -
warning: current group `pwVcMplsGroup' is not referenced in this module
994: OBJECTS {
995: pwVcMplsMplsType,
996: pwVcMplsExpBitsMode,
997: pwVcMplsExpBits,
998: pwVcMplsTtl,
999: pwVcMplsLocalLdpID,
1000: pwVcMplsLocalLdpEntityID,
1001: pwVcMplsPeerLdpID,
1001: severe -
unknown object identifier label `pwVcMplsPeerLdpID'
1002: pwVcMplsStorageType
1003: }
1004:
1005: STATUS current
1006: DESCRIPTION
1007: "Collection of objects needed for PW over MPLS PSN
1008: configuration."
1009: ::= { pwVcMplsGroups 1 }
1010:
1011:
1012:
1013: pwVcMplsOutboundMainGroup OBJECT-GROUP
1013: warning -
warning: current group `pwVcMplsOutboundMainGroup' is not referenced in this module
1014: OBJECTS {
1015: pwVcMplsOutboundLsrXcIndex,
1016: pwVcMplsOutboundIfIndex,
1017: pwVcMplsOutboundTunnelTypeInUse
1018: }
1019:
1020: STATUS current
1021: DESCRIPTION
1022: "Collection of objects needed for outbound association of
1023: PW and MPLS tunnel."
1024: ::= { pwVcMplsGroups 2 }
1025:
1026: pwVcMplsOutboundTeGroup OBJECT-GROUP
1026: warning -
warning: current group `pwVcMplsOutboundTeGroup' is not referenced in this module
1027: OBJECTS {
1028: pwVcMplsOutboundTunnelIndex,
1029: pwVcMplsOutboundTunnelInstance,
1030: pwVcMplsOutboundTunnelLclLSR,
1031: pwVcMplsOutboundTunnelPeerLSR
1032: }
1033:
1034: STATUS current
1035: DESCRIPTION
1036: "Collection of objects needed for outbound association of
1037: PW and MPLS TE tunnel."
1038: ::= { pwVcMplsGroups 3 }
1039: Pseudo Wire (PW) Over MPLS June 2004
1039: error -
`Pseudo' should start with a lower case letter
1039: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
1040: Management Information Base
1041:
1042:
1043:
1044: pwVcMplsInboundGroup OBJECT-GROUP
1045: OBJECTS {
1046: pwVcMplsInboundXcIndex
1047: }
1047: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1048:
1049: STATUS current
1049: severe -
syntax error, unexpected STATUS
1050: DESCRIPTION
1051: "Collection of objects needed for inbound PW presentation.
1052: This group MUST be supported if PW signaling through LDP is
1053: used."
1054: ::= { pwVcMplsGroups 4 }
1054: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1055:
1056: pwVcMplsMappingGroup OBJECT-GROUP
1056: warning -
warning: current group `pwVcMplsMappingGroup' is not referenced in this module
1057: OBJECTS {
1058: pwVcMplsNonTeMappingVcIndex,
1059: pwVcMplsTeMappingVcIndex
1060: }
1061:
1062: STATUS current
1063: DESCRIPTION
1064: "Collection of objects needed for mapping association of
1065: PW and MPLS tunnel."
1066: ::= { pwVcMplsGroups 5 }
1067:
1068: END -- of PW MPLS MIB Module
1069:
1070: 8 Security Considerations
1070: severe -
syntax error, unexpected NUMBER, expecting $end
1071:
1072: It is clear that this MIB module is potentially useful for
1073: monitoring of PW capable PEs. This MIB module can also be used for
1074: configuration of certain objects, and anything that can be
1075: configured can be incorrectly configured, with potentially
1076: disastrous results.
1077:
1078: There are a number of management objects defined in this MIB module
1079: with a MAX-ACCESS clause of read-write and/or read-create. Such
1080: objects may be considered sensitive or vulnerable in some network
1081: environments. The support for SET operations in a non-secure
1082: environment without proper protection can have a negative effect on
1083: network operations. These are the tables and objects and their
1084: sensitivity/vulnerability:
1085:
1086: o the pwVcMplsTable, pwVcMplsNonTeMappingTable and
1087: pwVcMplsTeMappingTable collectively contain objects to
1088: provision PW over MPLS tunnels. Unauthorized access to
1089: objects in these tables, could result in disruption of
1090: traffic on the network. The use of stronger mechanisms
1091: such as SNMPv3 security should be considered where
1092: possible. Specifically, SNMPv3 VACM and USM MUST be used
1093: with any v3 agent which implements this MIB module.
1094: Pseudo Wire (PW) Over MPLS June 2004
1095: Management Information Base
1096:
1097:
1098: Administrators should consider whether read access to these
1099: objects should be allowed, since read access may be
1100: undesirable under certain circumstances.
1101:
1102: Some of the readable objects in this MIB module "i.e., objects with
1103: a MAX-ACCESS other than not-accessible" may be considered sensitive
1104: or vulnerable in some network environments. It is thus important
1105: to control even GET and/or NOTIFY access to these objects and
1106: possibly to even encrypt the values of these objects when sending
1107: them over the network via SNMP. These are the tables and objects
1108: and their sensitivity/vulnerability:
1109:
1110: o the pwVcMplsTable, pwVcMplsNonTeMappingTable,
1111: pwVcMplsTeMappingTable and pwVcMplsOutboundTable
1112: collectively show the PW over MPLS association.
1113: If an Administrator does not want to reveal this
1114: information, then these tables should be
1115: considered sensitive/vulnerable.
1116:
1117: SNMP versions prior to SNMPv3 did not include adequate security.
1118: Even if the network itself is secure "for example by using IPSec",
1119: even then, there is no control as to who on the secure network is
1120: allowed to access and GET/SET "read/change/create/delete" the
1121: objects in this MIB module.
1122:
1123: It is RECOMMENDED that implementers consider the security features
1124: as provided by the SNMPv3 framework "see [RFC3410], section 8",
1125: including full support for the SNMPv3 cryptographic mechanisms "for
1126: authentication and privacy".
1127:
1128: Further, deployment of SNMP versions prior to SNMPv3 is NOT
1129: RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
1130: enable cryptographic security. It is then a customer/operator
1131: responsibility to ensure that the SNMP entity giving access to an
1132: instance of this MIB module, is properly configured to give access
1133: to the objects only to those principals "users" that have
1134: legitimate rights to indeed GET or SET "change/create/delete" them.
1135:
1136: 9 IANA considerations
1137:
1138: As requested in the PW-TC-STD-MIB [PWTCMIB], PWE3 related standards
1139: track MIB modules should be rooted under the pwStdMIB subtree. The
1140: IANA is requested to assign { pwStdMIB 3 } to the PW-MPLS-STD-MIB
1141: module specified in this document.
1142:
1143:
1144: 10 References
1145:
1146: 0.1 Normative references
1147: Pseudo Wire (PW) Over MPLS June 2004
1148: Management Information Base
1149:
1150:
1151: [PWARCH] Bryant, S., et al, "PWE3 Architecture", work-in-
1152: progress.
1153:
1154: [PWREQ] Xiao, X., et al, "Requirements for Pseudo Wire
1155: Emulation Edge-to-Edge (PWE3)", work-in-progress.
1156:
1157: [PWTC] Nadeau, T., et al, "Definitions for Textual Conventions
1158: and OBJECT-IDENTITIES for Pseudo-Wires Management",
1159: work-in-progress.
1160:
1161: [PW-MIB] Zelig, D., et al, "Pseudo Wire (PW) Management
1162: Information Base", work-in-progress.
1163:
1164: [IF-MIB] McCloghrie, K., Kastenholz, F., ôThe Interfaces Group
1165: MIBö, RFC 2863, June 2000.
1166:
1167: [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon,
1168: "Multiprotocol Label Switching Architecture", RFC 3031,
1169: Jan 2001.
1170:
1171: [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D.,
1172: Federokow, G., Li, T., and A. Conta, "MPLS Label Stack
1173: Encoding", RFC 3032, January 2001.
1174:
1175: [LSRMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T., "MPLS
1176: Label Switch Router Management Information Base Using
1177: SMIv2", work-in-progress.
1178:
1179: [TEMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T., "MPLS
1180: Traffic Engineering Management Information Base Using
1181: SMIv2", work-in-progress.
1182:
1183: [MPLSTCMIB] Nadeau, T., Cucchiara, J., "Definition of Textual
1184: Conventions and OBJECT-IDENTITIES for Multi-Protocol
1185: Label Switching (MPLS) Management", RFC 3811, June
1186: 2004.
1187:
1188: [LDP] Andersson, L., et al, "LDP specificationö, RFC 3036,
1189: January 2001.
1190:
1191: [BCP14] Bradner, S., "Key words for use in RFCs to Indicate
1192: requirement Levels", BCP 14, RFC 2119, March 1997.
1193:
1194: [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
1195: J.,Rose, M. and S. Waldbusser, "Structure of Management
1196: Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1197: 1999.
1198: Pseudo Wire (PW) Over MPLS June 2004
1199: Management Information Base
1200:
1201:
1202: [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
1203: J., Rose, M. and S. Waldbusser, "Textual Conventions
1204: for SMIv2", STD 58, RFC 2579, April 1999.
1205:
1206: [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
1207: J., Rose, M. and S. Waldbusser, "Conformance Statements
1208: for SMIv2", STD 58, RFC 2580, April 1999.
1209:
1210: 0.2 Informative references
1211:
1212:
1213: [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
1214: Introduction and Applicability Statements for Internet-
1215: Standard Management Framework", RFC 3410, December
1216: 2002.
1217:
1218:
1219: 11 Author's Addresses
1220:
1221: David Zelig
1222: Corrigent Systems
1223: 126, Yigal Alon st.
1224: Tel Aviv, ISRAEL
1225: Phone: +972-3-6945273
1226: Email: davidz@corrigent.com
1227:
1228: Thomas D. Nadeau
1229: Cisco Systems, Inc.
1230: 250 Apollo Drive
1231: Chelmsford, MA 01824
1232: Email: tnadeau@cisco.com
1233:
1234:
1235: Dave Danenberg
1236: Email: dave_danenberg@yahoo.com
1237:
1238: Andrew G. Malis
1239: Tellabs, Inc.
1240: 2730 Orchard Parkway
1241: San Jose, CA 95134
1242: Email: Andy.Malis@tellabs.com
1243:
1244: Sharon Mantin
1245: AxONLink (Israel) Ltd
1246: 9 Bareket St.
1247: Petah Tikva 49517, Israel
1248: Phone: +972-3-9263972
1249: Email: sharon.mantin@axonlink.com
1250:
1251: 12 Full Copyright Statement
1252: Pseudo Wire (PW) Over MPLS June 2004
1253: Management Information Base
1254:
1255:
1256:
1257: Copyright (C) The Internet Society (2000). All Rights Reserved.
1258:
1259: This document and translations of it may be copied and furnished to
1260: others, and derivative works that comment on or otherwise explain
1261: it or assist in its implementation may be prepared, copied,
1262: published and distributed, in whole or in part, without restriction
1263: of any kind, provided that the above copyright notice and this
1264: paragraph are included on all such copies and derivative works.
1265: However, this document itself may not be modified in any way, such
1266: as by removing the copyright notice or references to the Internet
1267: Society or other Internet organizations, except as needed for the
1268: purpose of developing Internet standards in which case the
1269: procedures for copyrights defined in the Internet Standards process
1270: must be followed, or as required to translate it into languages
1271: other than English.
1272:
1273: The limited permissions granted above are perpetual and will not be
1274: revoked by the Internet Society or its successors or assigns. This
1275: document and the information contained herein is provided on an "AS
1276: IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
1277: TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
1278: BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
1279: HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
1280: MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1281:
1282: 13 Intellectual Property Notice
1283:
1284: The IETF takes no position regarding the validity or scope of any
1285: intellectual property or other rights that might be claimed to
1286: pertain to the implementation or use of the technology described in
1287: this document or the extent to which any license under such rights
1288: might or might not be available; neither does it represent that it
1289: has made any effort to identify any such rights. Information on
1290: the IETF's procedures with respect to rights in standards-track and
1291: standards-related documentation can be found in BCP-11 [RFC2028].
1292: Copies of claims of rights made available for publication and any
1293: assurances of licenses to be made available, or the result of an
1294: attempt made to obtain a general license or permission for the use
1295: of such proprietary rights by implementors or users of this
1296: specification can be obtained from the IETF Secretariat.
1297: The IETF invites any interested party to bring to its attention any
1298: copyrights, patents or patent applications, or other proprietary
1299: rights that may cover technology that may be required to practice
1300: this standard. Please address the information to the IETF
1301: Executive Director.