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