smilint output for ./MPLS-TC-STD-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| change recommended | 1 |
| warning | 29 |
| Message Types |
|---|
| Type | Count |
|---|
| module-identity-registration (change recommended) | 1 |
| type-unref (warning) | 22 |
| type-without-format (warning) | 7 |
Messages:
MPLS-TC-STD-MIB
1: -- extracted from rfc3811.txt
2: -- at Tue Jun 15 06:20:45 2004
14:
15: mplsTCStdMIB MODULE-IDENTITY
15: change recommended -
warning: uncontrolled MODULE-IDENTITY registration
16: LAST-UPDATED "200406030000Z" -- June 3, 2004
17: ORGANIZATION
18: "IETF Multiprotocol Label Switching (MPLS) Working
19: Group."
20: CONTACT-INFO
21: " Thomas D. Nadeau
22: Cisco Systems, Inc.
23: tnadeau@cisco.com
24:
25: Joan Cucchiara
26: Marconi Communications, Inc.
27: jcucchiara@mindspring.com
28:
29: Cheenu Srinivasan
30: Bloomberg L.P.
31: cheenu@bloomberg.net
32:
33: Arun Viswanathan
34: Force10 Networks, Inc.
35: arunv@force10networks.com
36:
37: Hans Sjostrand
38: ipUnplugged
39: hans@ipunplugged.com
40:
41: Kireeti Kompella
42: Juniper Networks
43: kireeti@juniper.net
44:
45: Email comments to the MPLS WG Mailing List at
46: mpls@uu.net."
47: DESCRIPTION
48: "Copyright (C) The Internet Society (2004). The
49: initial version of this MIB module was published
50: in RFC 3811. For full legal notices see the RFC
51: itself or see:
52: http://www.ietf.org/copyrights/ianamib.html
53:
54: This MIB module defines TEXTUAL-CONVENTIONs
55: for concepts used in Multiprotocol Label
56: Switching (MPLS) networks."
57:
58: REVISION "200406030000Z" -- June 3, 2004
59: DESCRIPTION
60: "Initial version published as part of RFC 3811."
61:
62: ::= { mplsStdMIB 1 }
...
67:
68: MplsAtmVcIdentifier ::= TEXTUAL-CONVENTION
68: warning -
warning: current type `MplsAtmVcIdentifier' is not referenced in this module
69: DISPLAY-HINT "d"
70: STATUS current
71: DESCRIPTION
72: "A Label Switching Router (LSR) that
73: creates LDP sessions on ATM interfaces
74: uses the VCI or VPI/VCI field to hold the
75: LDP Label.
76:
77: VCI values MUST NOT be in the 0-31 range.
78: The values 0 to 31 are reserved for other uses
79: by the ITU and ATM Forum. The value
80: of 32 can only be used for the Control VC,
81: although values greater than 32 could be
82: configured for the Control VC.
83:
84: If a value from 0 to 31 is used for a VCI
85: the management entity controlling the LDP
86: subsystem should reject this with an
87: inconsistentValue error. Also, if
88: the value of 32 is used for a VC which is
89: NOT the Control VC, this should
90: result in an inconsistentValue error."
91: REFERENCE
92: "MPLS using LDP and ATM VC Switching, RFC3035."
93: SYNTAX Integer32 (32..65535)
94:
95: MplsBitRate ::= TEXTUAL-CONVENTION
95: warning -
warning: current type `MplsBitRate' is not referenced in this module
96: DISPLAY-HINT "d"
97: STATUS current
98: DESCRIPTION
99: "If the value of this object is greater than zero,
100: then this represents the bandwidth of this MPLS
101: interface (or Label Switched Path) in units of
102: '1,000 bits per second'.
103:
104: The value, when greater than zero, represents the
105: bandwidth of this MPLS interface (rounded to the
106: nearest 1,000) in units of 1,000 bits per second.
107: If the bandwidth of the MPLS interface is between
108: ((n * 1000) - 500) and ((n * 1000) + 499), the value
109: of this object is n, such that n > 0.
110:
111: If the value of this object is 0 (zero), this
112: means that the traffic over this MPLS interface is
113: considered to be best effort."
114: SYNTAX Unsigned32 (0|1..4294967295)
115:
116: MplsBurstSize ::= TEXTUAL-CONVENTION
116: warning -
warning: current type `MplsBurstSize' is not referenced in this module
117: DISPLAY-HINT "d"
118: STATUS current
119: DESCRIPTION
120: "The number of octets of MPLS data that the stream
121: may send back-to-back without concern for policing.
122: The value of zero indicates that an implementation
123: does not support Burst Size."
124: SYNTAX Unsigned32 (0..4294967295)
125:
126: MplsExtendedTunnelId ::= TEXTUAL-CONVENTION
126: warning -
warning: current type `MplsExtendedTunnelId' is not referenced in this module
126: warning -
warning: type `MplsExtendedTunnelId' has no format specification
127: STATUS current
128: DESCRIPTION
129: "A unique identifier for an MPLS Tunnel. This may
130: represent an IPv4 address of the ingress or egress
131: LSR for the tunnel. This value is derived from the
132: Extended Tunnel Id in RSVP or the Ingress Router ID
133: for CR-LDP."
134: REFERENCE
135: "RSVP-TE: Extensions to RSVP for LSP Tunnels,
136: [RFC3209].
137:
138: Constraint-Based LSP Setup using LDP, [RFC3212]."
139: SYNTAX Unsigned32(0..4294967295)
140:
141: MplsLabel ::= TEXTUAL-CONVENTION
141: warning -
warning: current type `MplsLabel' is not referenced in this module
141: warning -
warning: type `MplsLabel' has no format specification
142: STATUS current
143: DESCRIPTION
144: "This value represents an MPLS label as defined in
145: [RFC3031], [RFC3032], [RFC3034], [RFC3035] and
146: [RFC3471].
147:
148: The label contents are specific to the label being
149: represented, such as:
150:
151: * The label carried in an MPLS shim header
152: (for LDP this is the Generic Label) is a 20-bit
153: number represented by 4 octets. Bits 0-19 contain
154: a label or a reserved label value. Bits 20-31
155: MUST be zero.
156:
157: The following is quoted directly from [RFC3032].
158: There are several reserved label values:
159:
160: i. A value of 0 represents the
161: 'IPv4 Explicit NULL Label'. This label
162: value is only legal at the bottom of the
163: label stack. It indicates that the label
164: stack must be popped, and the forwarding
165: of the packet must then be based on the
166: IPv4 header.
167:
168: ii. A value of 1 represents the
169: 'Router Alert Label'. This label value is
170: legal anywhere in the label stack except at
171: the bottom. When a received packet
172: contains this label value at the top of
173: the label stack, it is delivered to a
174: local software module for processing.
175: The actual forwarding of the packet
176: is determined by the label beneath it
177: in the stack. However, if the packet is
178: forwarded further, the Router Alert Label
179: should be pushed back onto the label stack
180: before forwarding. The use of this label
181: is analogous to the use of the
182: 'Router Alert Option' in IP packets
183: [RFC2113]. Since this label
184: cannot occur at the bottom of the stack,
185: it is not associated with a
186: particular network layer protocol.
187:
188: iii. A value of 2 represents the
189: 'IPv6 Explicit NULL Label'. This label
190: value is only legal at the bottom of the
191: label stack. It indicates that the label
192: stack must be popped, and the forwarding
193: of the packet must then be based on the
194: IPv6 header.
195:
196: iv. A value of 3 represents the
197: 'Implicit NULL Label'.
198: This is a label that an LSR may assign and
199: distribute, but which never actually
200: appears in the encapsulation. When an
201: LSR would otherwise replace the label
202: at the top of the stack with a new label,
203: but the new label is 'Implicit NULL',
204: the LSR will pop the stack instead of
205: doing the replacement. Although
206: this value may never appear in the
207: encapsulation, it needs to be specified in
208: the Label Distribution Protocol, so a value
209: is reserved.
210:
211: v. Values 4-15 are reserved.
212:
213: * The frame relay label can be either 10-bits or
214: 23-bits depending on the DLCI field size and the
215: upper 22-bits or upper 9-bits must be zero,
216: respectively.
217:
218: * For an ATM label the lower 16-bits represents the
219: VCI, the next 12-bits represents the VPI and the
220: remaining bits MUST be zero.
221:
222: * The Generalized-MPLS (GMPLS) label contains a
223: value greater than 2^24-1 and used in GMPLS
224: as defined in [RFC3471]."
225: REFERENCE
226: "Multiprotocol Label Switching Architecture,
227: RFC3031.
228:
229: MPLS Label Stack Encoding, [RFC3032].
230:
231: Use of Label Switching on Frame Relay Networks,
232: RFC3034.
233:
234: MPLS using LDP and ATM VC Switching, RFC3035.
235: Generalized Multiprotocol Label Switching
236: (GMPLS) Architecture, [RFC3471]."
237: SYNTAX Unsigned32 (0..4294967295)
238:
239: MplsLabelDistributionMethod ::= TEXTUAL-CONVENTION
239: warning -
warning: current type `MplsLabelDistributionMethod' is not referenced in this module
240: STATUS current
241: DESCRIPTION
242: "The label distribution method which is also called
243: the label advertisement mode [RFC3036].
244: Each interface on an LSR is configured to operate
245: in either Downstream Unsolicited or Downstream
246: on Demand."
247: REFERENCE
248: "Multiprotocol Label Switching Architecture,
249: RFC3031.
250:
251: LDP Specification, RFC3036, Section 2.6.3."
252: SYNTAX INTEGER {
253: downstreamOnDemand(1),
254: downstreamUnsolicited(2)
255: }
256:
257: MplsLdpIdentifier ::= TEXTUAL-CONVENTION
257: warning -
warning: current type `MplsLdpIdentifier' is not referenced in this module
258: DISPLAY-HINT "1d.1d.1d.1d:2d"
259: STATUS current
260: DESCRIPTION
261: "The LDP identifier is a six octet
262: quantity which is used to identify a
263: Label Switching Router (LSR) label space.
264:
265: The first four octets identify the LSR and
266: must be a globally unique value, such as a
267: 32-bit router ID assigned to the LSR, and the
268: last two octets identify a specific label
269: space within the LSR."
270: SYNTAX OCTET STRING (SIZE (6))
271:
272: MplsLsrIdentifier ::= TEXTUAL-CONVENTION
272: warning -
warning: current type `MplsLsrIdentifier' is not referenced in this module
273: STATUS current
274: DESCRIPTION
275: "The Label Switching Router (LSR) identifier is the
276: first 4 bytes of the Label Distribution Protocol
277: (LDP) identifier."
278: SYNTAX OCTET STRING (SIZE (4))
279: MplsLdpLabelType ::= TEXTUAL-CONVENTION
279: warning -
warning: current type `MplsLdpLabelType' is not referenced in this module
280: STATUS current
281: DESCRIPTION
282: "The Layer 2 label types which are defined for MPLS
283: LDP and/or CR-LDP are generic(1), atm(2), or
284: frameRelay(3)."
285: SYNTAX INTEGER {
286: generic(1),
287: atm(2),
288: frameRelay(3)
289: }
290:
291: MplsLSPID ::= TEXTUAL-CONVENTION
291: warning -
warning: current type `MplsLSPID' is not referenced in this module
292: STATUS current
293: DESCRIPTION
294: "A unique identifier within an MPLS network that is
295: assigned to each LSP. This is assigned at the head
296: end of the LSP and can be used by all LSRs
297: to identify this LSP. This value is piggybacked by
298: the signaling protocol when this LSP is signaled
299: within the network. This identifier can then be
300: used at each LSR to identify which labels are
301: being swapped to other labels for this LSP. This
302: object can also be used to disambiguate LSPs that
303: share the same RSVP sessions between the same
304: source and destination.
305:
306: For LSPs established using CR-LDP, the LSPID is
307: composed of the ingress LSR Router ID (or any of
308: its own IPv4 addresses) and a locally unique
309: CR-LSP ID to that LSR. The first two bytes carry
310: the CR-LSPID, and the remaining 4 bytes carry
311: the Router ID. The LSPID is useful in network
312: management, in CR-LSP repair, and in using
313: an already established CR-LSP as a hop in
314: an ER-TLV.
315:
316: For LSPs signaled using RSVP-TE, the LSP ID is
317: defined as a 16-bit (2 byte) identifier used
318: in the SENDER_TEMPLATE and the FILTER_SPEC
319: that can be changed to allow a sender to
320: share resources with itself. The length of this
321: object should only be 2 or 6 bytes. If the length
322: of this octet string is 2 bytes, then it must
323: identify an RSVP-TE LSPID, or it is 6 bytes,
324: it must contain a CR-LDP LSPID."
325: REFERENCE
326: "RSVP-TE: Extensions to RSVP for LSP Tunnels,
327: [RFC3209].
328:
329: Constraint-Based LSP Setup using LDP,
330: [RFC3212]."
331: SYNTAX OCTET STRING (SIZE (2|6))
332:
333: MplsLspType ::= TEXTUAL-CONVENTION
333: warning -
warning: current type `MplsLspType' is not referenced in this module
334: STATUS current
335: DESCRIPTION
336: "Types of Label Switch Paths (LSPs)
337: on a Label Switching Router (LSR) or a
338: Label Edge Router (LER) are:
339:
340: unknown(1) -- if the LSP is not known
341: to be one of the following.
342:
343: terminatingLsp(2) -- if the LSP terminates
344: on the LSR/LER, then this
345: is an egressing LSP
346: which ends on the LSR/LER,
347:
348: originatingLsp(3) -- if the LSP originates
349: from this LSR/LER, then
350: this is an ingressing LSP
351: which is the head-end of
352: the LSP,
353:
354: crossConnectingLsp(4) -- if the LSP ingresses
355: and egresses on the LSR,
356: then it is
357: cross-connecting on that
358: LSR."
359: SYNTAX INTEGER {
360: unknown(1),
361: terminatingLsp(2),
362: originatingLsp(3),
363: crossConnectingLsp(4)
364: }
365:
366: MplsOwner ::= TEXTUAL-CONVENTION
366: warning -
warning: current type `MplsOwner' is not referenced in this module
367: STATUS current
368: DESCRIPTION
369: "This object indicates the local network
370: management subsystem that originally created
371: the object(s) in question. The values of
372: this enumeration are defined as follows:
373:
374: unknown(1) - the local network management
375: subsystem cannot discern which
376: component created the object.
377:
378: other(2) - the local network management
379: subsystem is able to discern which component
380: created the object, but the component is not
381: listed within the following choices,
382: e.g., command line interface (cli).
383:
384: snmp(3) - The Simple Network Management Protocol
385: was used to configure this object initially.
386:
387: ldp(4) - The Label Distribution Protocol was
388: used to configure this object initially.
389:
390: crldp(5) - The Constraint-Based Label Distribution
391: Protocol was used to configure this object
392: initially.
393:
394: rsvpTe(6) - The Resource Reservation Protocol was
395: used to configure this object initially.
396:
397: policyAgent(7) - A policy agent (perhaps in
398: combination with one of the above protocols) was
399: used to configure this object initially.
400:
401: An object created by any of the above choices
402: MAY be modified or destroyed by the same or a
403: different choice."
404: SYNTAX INTEGER {
405: unknown(1),
406: other(2),
407: snmp(3),
408: ldp(4),
409: crldp(5),
410: rsvpTe(6),
411: policyAgent(7)
412: }
413:
414: MplsPathIndexOrZero ::= TEXTUAL-CONVENTION
414: warning -
warning: current type `MplsPathIndexOrZero' is not referenced in this module
414: warning -
warning: type `MplsPathIndexOrZero' has no format specification
415: STATUS current
416: DESCRIPTION
417: "A unique identifier used to identify a specific
418: path used by a tunnel. A value of 0 (zero) means
419: that no path is in use."
420: SYNTAX Unsigned32(0..4294967295)
421:
422: MplsPathIndex ::= TEXTUAL-CONVENTION
422: warning -
warning: current type `MplsPathIndex' is not referenced in this module
422: warning -
warning: type `MplsPathIndex' has no format specification
423: STATUS current
424: DESCRIPTION
425: "A unique value to index (by Path number) an
426: entry in a table."
427: SYNTAX Unsigned32(1..4294967295)
428:
429: MplsRetentionMode ::= TEXTUAL-CONVENTION
429: warning -
warning: current type `MplsRetentionMode' is not referenced in this module
430: STATUS current
431: DESCRIPTION
432: "The label retention mode which specifies whether
433: an LSR maintains a label binding for a FEC
434: learned from a neighbor that is not its next hop
435: for the FEC.
436:
437: If the value is conservative(1) then advertised
438: label mappings are retained only if they will be
439: used to forward packets, i.e., if label came from
440: a valid next hop.
441:
442: If the value is liberal(2) then all advertised
443: label mappings are retained whether they are from
444: a valid next hop or not."
445: REFERENCE
446: "Multiprotocol Label Switching Architecture,
447: RFC3031.
448:
449: LDP Specification, RFC3036, Section 2.6.2."
450: SYNTAX INTEGER {
451: conservative(1),
452: liberal(2)
453: }
454:
455: MplsTunnelAffinity ::= TEXTUAL-CONVENTION
455: warning -
warning: current type `MplsTunnelAffinity' is not referenced in this module
455: warning -
warning: type `MplsTunnelAffinity' has no format specification
456: STATUS current
457: DESCRIPTION
458: "Describes the configured 32-bit Include-any,
459: include-all, or exclude-all constraint for
460: constraint-based link selection."
461: REFERENCE
462: "RSVP-TE: Extensions to RSVP for LSP Tunnels,
463: RFC3209, Section 4.7.4."
464: SYNTAX Unsigned32(0..4294967295)
465:
466: MplsTunnelIndex ::= TEXTUAL-CONVENTION
466: warning -
warning: current type `MplsTunnelIndex' is not referenced in this module
466: warning -
warning: type `MplsTunnelIndex' has no format specification
467: STATUS current
468: DESCRIPTION
469: "A unique index into mplsTunnelTable.
470: For tunnels signaled using RSVP, this value
471: should correspond to the RSVP Tunnel ID
472: used for the RSVP-TE session."
473: SYNTAX Unsigned32 (0..65535)
474:
475: MplsTunnelInstanceIndex ::= TEXTUAL-CONVENTION
475: warning -
warning: current type `MplsTunnelInstanceIndex' is not referenced in this module
475: warning -
warning: type `MplsTunnelInstanceIndex' has no format specification
476: STATUS current
477: DESCRIPTION
478: "The tunnel entry with instance index 0
479: should refer to the configured tunnel
480: interface (if one exists).
481:
482: Values greater than 0, but less than or
483: equal to 65535, should be used to indicate
484: signaled (or backup) tunnel LSP instances.
485: For tunnel LSPs signaled using RSVP,
486: this value should correspond to the
487: RSVP LSP ID used for the RSVP-TE
488: LSP.
489:
490: Values greater than 65535 apply to FRR
491: detour instances."
492: SYNTAX Unsigned32(0|1..65535|65536..4294967295)
493:
494: TeHopAddressType ::= TEXTUAL-CONVENTION
494: warning -
warning: current type `TeHopAddressType' is not referenced in this module
495: STATUS current
496: DESCRIPTION
497: "A value that represents a type of address for a
498: Traffic Engineered (TE) Tunnel hop.
499:
500: unknown(0) An unknown address type. This value
501: MUST be used if the value of the
502: corresponding TeHopAddress object is a
503: zero-length string. It may also be
504: used to indicate a TeHopAddress which
505: is not in one of the formats defined
506: below.
507:
508: ipv4(1) An IPv4 network address as defined by
509: the InetAddressIPv4 TEXTUAL-CONVENTION
510: [RFC3291].
511:
512: ipv6(2) A global IPv6 address as defined by
513: the InetAddressIPv6 TEXTUAL-CONVENTION
514: [RFC3291].
515:
516: asnumber(3) An Autonomous System (AS) number as
517: defined by the TeHopAddressAS
518: TEXTUAL-CONVENTION.
519:
520: unnum(4) An unnumbered interface index as
521: defined by the TeHopAddressUnnum
522: TEXTUAL-CONVENTION.
523:
524: lspid(5) An LSP ID for TE Tunnels
525: (RFC3212) as defined by the
526: MplsLSPID TEXTUAL-CONVENTION.
527:
528: Each definition of a concrete TeHopAddressType
529: value must be accompanied by a definition
530: of a TEXTUAL-CONVENTION for use with that
531: TeHopAddress.
532:
533: To support future extensions, the TeHopAddressType
534: TEXTUAL-CONVENTION SHOULD NOT be sub-typed in
535: object type definitions. It MAY be sub-typed in
536: compliance statements in order to require only a
537: subset of these address types for a compliant
538: implementation.
539:
540: Implementations must ensure that TeHopAddressType
541: objects and any dependent objects
542: (e.g., TeHopAddress objects) are consistent.
543: An inconsistentValue error must be generated
544: if an attempt to change a TeHopAddressType
545: object would, for example, lead to an
546: undefined TeHopAddress value that is
547: not defined herein. In particular,
548: TeHopAddressType/TeHopAddress pairs
549: must be changed together if the address
550: type changes (e.g., from ipv6(2) to ipv4(1))."
551:
552: REFERENCE
553: "TEXTUAL-CONVENTIONs for Internet Network
554: Addresses, RFC3291.
555:
556: Constraint-Based LSP Setup using LDP,
557: [RFC3212]"
558:
559: SYNTAX INTEGER {
560: unknown(0),
561: ipv4(1),
562: ipv6(2),
563: asnumber(3),
564: unnum(4),
565: lspid(5)
566: }
567:
568: TeHopAddress ::= TEXTUAL-CONVENTION
568: warning -
warning: current type `TeHopAddress' is not referenced in this module
569: STATUS current
570: DESCRIPTION
571: "Denotes a generic Tunnel hop address,
572: that is, the address of a node which
573: an LSP traverses, including the source
574: and destination nodes. An address may be
575: very concrete, for example, an IPv4 host
576: address (i.e., with prefix length 32);
577: if this IPv4 address is an interface
578: address, then that particular interface
579: must be traversed. An address may also
580: specify an 'abstract node', for example,
581: an IPv4 address with prefix length
582: less than 32, in which case, the LSP
583: can traverse any node whose address
584: falls in that range. An address may
585: also specify an Autonomous System (AS),
586: in which case the LSP can traverse any
587: node that falls within that AS.
588:
589: A TeHopAddress value is always interpreted within
590: the context of an TeHopAddressType value. Every
591: usage of the TeHopAddress TEXTUAL-CONVENTION
592: is required to specify the TeHopAddressType object
593: which provides the context. It is suggested that
594: the TeHopAddressType object is logically registered
595: before the object(s) which use the TeHopAddress
596: TEXTUAL-CONVENTION if they appear in the
597: same logical row.
598:
599: The value of a TeHopAddress object must always be
600: consistent with the value of the associated
601: TeHopAddressType object. Attempts to set a
602: TeHopAddress object to a value which is
603: inconsistent with the associated TeHopAddressType
604: must fail with an inconsistentValue error."
605: SYNTAX OCTET STRING (SIZE (0..32))
606:
607: TeHopAddressAS ::= TEXTUAL-CONVENTION
607: warning -
warning: current type `TeHopAddressAS' is not referenced in this module
608: STATUS current
609: DESCRIPTION
610: "Represents a two or four octet AS number.
611: The AS number is represented in network byte
612: order (MSB first). A two-octet AS number has
613: the two MSB octets set to zero."
614: REFERENCE
615: "Textual Conventions for Internet Network
616: Addresses, [RFC3291]. The
617: InetAutonomousSystemsNumber TEXTUAL-CONVENTION
618: has a SYNTAX of Unsigned32, whereas this TC
619: has a SYNTAX of OCTET STRING (SIZE (4)).
620: Both TCs represent an autonomous system number
621: but use different syntaxes to do so."
622: SYNTAX OCTET STRING (SIZE (4))
623:
624: TeHopAddressUnnum ::= TEXTUAL-CONVENTION
624: warning -
warning: current type `TeHopAddressUnnum' is not referenced in this module
625: STATUS current
626: DESCRIPTION
627: "Represents an unnumbered interface:
628:
629: octets contents encoding
630: 1-4 unnumbered interface network-byte order
631:
632: The corresponding TeHopAddressType value is
633: unnum(5)."
634: SYNTAX OCTET STRING(SIZE(4))
635:
636: END
637:
638: --
639: -- Copyright (C) The Internet Society (2004). This document is subject
640: -- to the rights, licenses and restrictions contained in BCP 78, and
641: -- except as set forth therein, the authors retain all their rights.
642: --
643: -- This document and the information contained herein are provided on an
644: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
645: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
646: -- ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
647: -- INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
648: -- INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
649: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
650: --
651: -- Intellectual Property
652: --
653: -- The IETF takes no position regarding the validity or scope of any
654: -- Intellectual Property Rights or other rights that might be claimed to
655: -- pertain to the implementation or use of the technology described in
656: -- this document or the extent to which any license under such rights
657: -- might or might not be available; nor does it represent that it has
658: -- made any independent effort to identify any such rights. Information
659: -- on the procedures with respect to rights in RFC documents can be
660: -- found in BCP 78 and BCP 79.
661: --
662: -- Copies of IPR disclosures made to the IETF Secretariat and any
663: -- assurances of licenses to be made available, or the result of an
664: -- attempt made to obtain a general license or permission for the use of
665: -- such proprietary rights by implementers or users of this
666: -- specification can be obtained from the IETF on-line IPR repository at
667: -- http://www.ietf.org/ipr.
668: --
669: -- The IETF invites any interested party to bring to its attention any
670: -- copyrights, patents or patent applications, or other proprietary
671: -- rights that may cover technology that may be required to implement
672: -- this standard. Please address the information to the IETF at ietf-
673: -- ipr@ietf.org.
674: --
675: