smilint output for ./MPLS-LDP-FRAME-RELAY-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 2 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 1 |
| object-identifier-not-prefix (error) | 1 |
Messages:
MPLS-LDP-FRAME-RELAY-MIB
1: -- extracted from draft-ietf-mpls-ldp-mib-10.txt
2: -- at Fri May 2 06:12:55 2003
3:
4: MPLS-LDP-FRAME-RELAY-MIB DEFINITIONS ::= BEGIN
5:
6:
7: IMPORTS
8: OBJECT-TYPE,
9: MODULE-IDENTITY,
10: Unsigned32
11: FROM SNMPv2-SMI
12: MODULE-COMPLIANCE,
13: OBJECT-GROUP
14: FROM SNMPv2-CONF
15:
16: RowStatus,
17: StorageType
18: FROM SNMPv2-TC
19:
20: DLCI
21: FROM FRAME-RELAY-DTE-MIB
22:
23: InterfaceIndexOrZero
24: FROM IF-MIB
25:
26: mplsMIB
27: FROM MPLS-TC-MIB
28:
29: mplsLdpEntityLdpId,
30: mplsLdpEntityIndex,
31: mplsLdpPeerLdpId
32: FROM MPLS-LDP-MIB
33:
34: ;
35:
36:
37: mplsLdpFrameRelayMIB MODULE-IDENTITY
38: LAST-UPDATED "200304221200Z" -- 22 April 2003
39: ORGANIZATION "Multiprotocol Label Switching (mpls)
40: Working Group"
41: CONTACT-INFO
42: "Joan Cucchiara (jcucchiara@artel.com)
43: Artel
44:
45: Hans Sjostrand (hans@ipunplugged.com)
46: ipUnplugged
47:
48: James V. Luciani (james_luciani@mindspring.com)
49: Consultant
50:
51: Working Group Chairs:
52: George Swallow, email: swallow@cisco.com
53: Loa Andersson, email: loa@pi.se
54:
55: MPLS Working Group, email: mpls@uu.net
56: "
57: DESCRIPTION
58: "Copyright (C) The Internet Society (2003). This
59: version of this MIB module is part of RFCXXX; see
60: the RFC itself for full legal notices.
61:
62: This MIB contains managed object definitions for
63: configuring and monitoring the Multiprotocol Label
64: Switching (MPLS), Label Distribution Protocol (LDP),
65: utilizing Frame Relay as the Layer 2 media."
66: REVISION "200304221200Z" -- 22 April 2003
67: DESCRIPTION
68: "Initial version published as part of RFC XXXX."
69:
70: -- Please see the IANA Considerations Section.
71: -- The requested mplsMIB subId is 6, e.g.
72: -- ::= { mplsMIB 6 }
73:
74: ::= { mplsMIB XXX } -- to be assigned by IANA
74: error -
`XXX' should start with a lower case letter
74: error -
Object identifier element `XXX' name only allowed as first element
75:
76: --****************************************************************
77:
78:
79: mplsLdpFrameRelayObjects
80: OBJECT IDENTIFIER ::= { mplsLdpFrameRelayMIB 1 }
81: mplsLdpFrameRelayConformance
82: OBJECT IDENTIFIER ::= { mplsLdpFrameRelayMIB 2 }
83:
84: --****************************************************************
85: -- MPLS LDP Frame Relay Objects
86: --****************************************************************
87:
88: --
89: -- Ldp Entity Objects for Frame Relay
90: --
91:
92: mplsLdpEntityFrameRelayObjects OBJECT IDENTIFIER ::=
93: { mplsLdpFrameRelayObjects 1 }
94:
95: mplsLdpEntityFrameRelayTable OBJECT-TYPE
96: SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayEntry
97: MAX-ACCESS not-accessible
98: STATUS current
99: DESCRIPTION
100: "This table contains information about the
101: Optional Parameters to specify what this Entity is
102: going to specify for Frame Relay specific
103: LDP Intialization Messages."
104: ::= { mplsLdpEntityFrameRelayObjects 1 }
105:
106: mplsLdpEntityFrameRelayEntry OBJECT-TYPE
107: SYNTAX MplsLdpEntityFrameRelayEntry
108: MAX-ACCESS not-accessible
109: STATUS current
110: DESCRIPTION
111: "An entry in this table represents the Frame Relay
112: optional parameters associated with the LDP entity."
113: INDEX { mplsLdpEntityLdpId,
114: mplsLdpEntityIndex
115: }
116: ::= { mplsLdpEntityFrameRelayTable 1 }
117:
118: MplsLdpEntityFrameRelayEntry ::= SEQUENCE {
119: mplsLdpEntityFrameRelayIfIndexOrZero InterfaceIndexOrZero,
120: mplsLdpEntityFrameRelayMergeCap INTEGER,
121: mplsLdpEntityFrameRelayLRComponents Unsigned32,
122: mplsLdpEntityFrameRelayVcDirectionality INTEGER,
123: mplsLdpEntityFrameRelayStorageType StorageType,
124: mplsLdpEntityFrameRelayRowStatus RowStatus
125: }
126:
127: mplsLdpEntityFrameRelayIfIndexOrZero OBJECT-TYPE
128: SYNTAX InterfaceIndexOrZero
129: MAX-ACCESS read-create
130: STATUS current
131: DESCRIPTION
132: "This value represents either the InterfaceIndex of
133: the 'ifLayer' where the Frame Relay Labels 'owned' by this
134: entry were created, or 0 (zero). The value of zero
135: means that the InterfaceIndex is not known. For example,
136: if the InterfaceIndex is created subsequent to the
137: Frame Relay Label's creation, then it would not be known.
138: However, if the InterfaceIndex is known, then it must
139: be represented by this value.
140:
141: If an InterfaceIndex becomes known, then the
142: network management entity (e.g. SNMP agent) responsible
143: for this object MUST change the value from 0 (zero) to the
144: value of the InterfaceIndex. If an Frame Relay Label is
145: being used in forwarding data, then the value of this
146: object MUST be the InterfaceIndex."
147: ::= { mplsLdpEntityFrameRelayEntry 1 }
148:
149: mplsLdpEntityFrameRelayMergeCap OBJECT-TYPE
150: SYNTAX INTEGER {
151: notSupported(0),
152: supported(1)
153: }
154: MAX-ACCESS read-create
155: STATUS current
156: DESCRIPTION
157: "This represents whether or not the Frame Relay merge
158: capability is supported. This is the EXACT value for the
159: Frame Relay Session Parameter, field M (for Frame Relay
160: Merge Capabilities). The Frame Relay Session Parameter
161: is an optional parameter in the Initialization Message.
162: The description from rfc3036.txt is:
163: 'M, Frame Relay Merge Capabilities
164: Specifies the merge capabilities of a Frame Relay switch. The
165: following values are supported in this version of the
166: specification:
167:
168: Value Meaning
169:
170: 0 Merge not supported
171: 1 Merge supported
172:
173: Non-merge and merge Frame Relay LSRs may freely interoperate.'
174:
175: Please refer to the following reference for a complete
176: description of this feature."
177: REFERENCE
178: "[RFC3036] LDP Specification, Section 3.5.3 Initialization Message."
179: ::= { mplsLdpEntityFrameRelayEntry 2 }
180:
181: mplsLdpEntityFrameRelayLRComponents OBJECT-TYPE
182: SYNTAX Unsigned32 (1..65535)
183: MAX-ACCESS read-create
184: STATUS current
185: DESCRIPTION
186: "Number of Label Range Components in the Initialization
187: message. This also represents the number of entries
188: in the mplsLdpEntityFrameRelayLRTable which correspond
189: to this entry.
190:
191: This is the EXACT value for the Frame Relay Session Parameter,
192: field N (for Number of label range components). The Frame Relay
193: Session Parameter is an optional parameter in the Initialization Message.
194:
195: The description from rfc3036.txt is:
196:
197: 'N, Number of label range components
198: Specifies the number of Frame Relay Label Range Components
199: included in the TLV.'
200:
201: Please refer to the following reference for a complete
202: description of this feature."
203: REFERENCE
204: "[RFC3036] LDP Specification, Section 3.5.3 Initialization Message."
205: ::= { mplsLdpEntityFrameRelayEntry 3 }
206:
207: mplsLdpEntityFrameRelayVcDirectionality OBJECT-TYPE
208: SYNTAX INTEGER {
209: bidirectional(0),
210: unidirection(1)
211: }
212: MAX-ACCESS read-create
213: STATUS current
214: DESCRIPTION
215: "If the value of this object is 'bidirectional(0)', then
216: the LSR supports the use of a given DLCI as a label for
217: both directions independently. If the value of
218: this object is 'unidirectional(1)', then the LSR
219: uses the given DLCI as a label in only one direction.
220:
221: This is the EXACT value for the Frame Relay Session Parameter,
222: field D (for VC Directionality). The Frame Relay Session Parameter
223: is an optional parameter in the Initialization Message.
224:
225: The description from rfc3036.txt is:
226:
227: 'D, VC Directionality
228: A value of 0 specifies bidirectional VC capability, meaning the
229: LSR can support the use of a given DLCI as a label for both
230: link directions independently. A value of 1 specifies
231: unidirectional VC capability, meaning a given DLCI may appear
232: in a label mapping for one direction on the link only. When
233: either or both of the peers specifies unidirectional VC
234: capability, both LSRs use unidirectional VC label assignment
235: for the link as follows. The LSRs compare their LDP
236: Identifiers as unsigned integers. The LSR with the larger LDP
237: Identifier may assign only odd-numbered DLCIs in the range as
238: labels. The system with the smaller LDP Identifier may assign
239: only even-numbered DLCIs in the range as labels.'
240:
241: Please refer to the following reference for a complete
242: description of this feature."
243: REFERENCE
244: "[RFC3036] LDP Specification, Section 3.5.3 Initialization Message."
245: ::= { mplsLdpEntityFrameRelayEntry 4 }
246:
247:
248: mplsLdpEntityFrameRelayStorageType OBJECT-TYPE
249: SYNTAX StorageType
250: MAX-ACCESS read-create
251: STATUS current
252: DESCRIPTION
253: "The storage type for this conceptual row. Conceptual rows
254: having the value 'permanent(4)' MAY allow write-access to any
255: columnar objects in the row, except for setting the
256: mplsLdpEntityFrameRelayRowStatus to 'destroy(6)'."
257: DEFVAL { nonVolatile }
258: ::= { mplsLdpEntityFrameRelayEntry 5 }
259:
260:
261: mplsLdpEntityFrameRelayRowStatus OBJECT-TYPE
262: SYNTAX RowStatus
263: MAX-ACCESS read-create
264: STATUS current
265: DESCRIPTION
266: "The status of this conceptual row. All writable objects in this
267: row may be modified at any time, however, as described in
268: detail in the section entitled, 'Changing Values After Session
269: Establishment', and again described in the
270: DESCRIPTION clause of the mplsLdpEntityAdminStatus object,
271: if a session has been initiated with a Peer,
272: changing objects in this table will
273: wreak havoc with the session and interrupt traffic. To repeat again:
274: the recommended procedure is to set the mplsLdpEntityAdminStatus to
275: down, thereby explicitely causing a session to be torn down. Then,
276: change objects in this entry, then set the mplsLdpEntityAdminStatus
277: to enable which enables a NEW session to be initiated.
278:
279: NOTE: This RowStatus object should
280: have the same value of the 'mplsLdpEntityRowStatus'
281: related to this entry."
282: ::= { mplsLdpEntityFrameRelayEntry 6 }
283:
284:
285: --
286: -- Frame Relay Label Range Components
287: --
288:
289: mplsLdpEntityFrameRelayLRTable OBJECT-TYPE
290: SYNTAX SEQUENCE OF MplsLdpEntityFrameRelayLREntry
291: MAX-ACCESS not-accessible
292: STATUS current
293: DESCRIPTION
294: "This table contains information about the
295: Optional Parameters for the Frame Relay Session
296: in the LDP Initialization Message, specifically
297: it contains information about the Frame Relay
298: Label Range Components."
299: ::= { mplsLdpEntityFrameRelayObjects 2 }
300:
301: mplsLdpEntityFrameRelayLREntry OBJECT-TYPE
302: SYNTAX MplsLdpEntityFrameRelayLREntry
303: MAX-ACCESS not-accessible
304: STATUS current
305: DESCRIPTION
306: "An entry in this table represents the Frame Relay
307: Label Range Component associated with the LDP entity."
308: INDEX { mplsLdpEntityLdpId,
309: mplsLdpEntityIndex,
310: mplsLdpEntityFrameRelayLRMinDlci
311: }
312: ::= { mplsLdpEntityFrameRelayLRTable 1 }
313:
314: MplsLdpEntityFrameRelayLREntry ::= SEQUENCE {
315: mplsLdpEntityFrameRelayLRMinDlci DLCI,
316: mplsLdpEntityFrameRelayLRMaxDlci DLCI,
317: mplsLdpEntityFrameRelayLRLen INTEGER,
318: mplsLdpEntityFrameRelayLRStorageType StorageType,
319: mplsLdpEntityFrameRelayLRRowStatus RowStatus
320: }
321:
322: mplsLdpEntityFrameRelayLRMinDlci OBJECT-TYPE
323: SYNTAX DLCI
324: MAX-ACCESS not-accessible
325: STATUS current
326: DESCRIPTION
327: "The lower bound which is supported. This value should
328: be the same as that in the Frame Relay Label Range
329: Component's Minimum DLCI field. The value of zero
330: is valid for the minimum DLCI field of the label."
331: REFERENCE
332: "[RFC 3034] Use of Label Switching on Frame Relay Networks
333: Specification."
334: ::= { mplsLdpEntityFrameRelayLREntry 1 }
335:
336: mplsLdpEntityFrameRelayLRMaxDlci OBJECT-TYPE
337: SYNTAX DLCI
338: MAX-ACCESS read-create
339: STATUS current
340: DESCRIPTION
341: "The upper bound which is supported. This value should
342: be the same as that in the Frame Relay Label Range
343: Component's Maximum DLCI field."
344: ::= { mplsLdpEntityFrameRelayLREntry 2 }
345:
346: mplsLdpEntityFrameRelayLRLen OBJECT-TYPE
347: SYNTAX INTEGER {
348: tenDlciBits(0),
349: twentyThreeDlciBits(2)
350: }
351: MAX-ACCESS read-create
352: STATUS current
353: DESCRIPTION
354: "This object specifies the length of the DLCI bits.
355:
356: This is the EXACT value for the Len field of the
357: Frame Relay Label Range Component.
358:
359: The description from rfc3036.txt is:
360:
361: 'Len
362: This field specifies the number of bits of the DLCI. The
363: following values are supported:
364:
365: Len DLCI bits
366:
367: 0 10
368: 2 23
369:
370: Len values 1 and 3 are reserved.'
371:
372: Please refer to the following reference for a complete
373: description of this feature."
374: REFERENCE
375: "[RFC3036] LDP Specification, Section 3.5.3 Initialization Message."
376: ::= { mplsLdpEntityFrameRelayLREntry 3 }
377:
378:
379: mplsLdpEntityFrameRelayLRStorageType OBJECT-TYPE
380: SYNTAX StorageType
381: MAX-ACCESS read-create
382: STATUS current
383: DESCRIPTION
384: "The storage type for this conceptual row. Conceptual rows
385: having the value 'permanent(4)' MAY allow write-access to any
386: columnar objects in the row, except for setting the
387: mplsLdpEntityFrameRelayLRRowStatus to 'destroy(6)'."
388: DEFVAL { nonVolatile }
389: ::= { mplsLdpEntityFrameRelayLREntry 4 }
390:
391: mplsLdpEntityFrameRelayLRRowStatus OBJECT-TYPE
392: SYNTAX RowStatus
393: MAX-ACCESS read-create
394: STATUS current
395: DESCRIPTION
396: "The status of this conceptual row. All writable objects in this
397: row may be modified at any time, however, as described in
398: detail in the section entitled, 'Changing Values After Session
399: Establishment', and again described in the
400: DESCRIPTION clause of the mplsLdpEntityAdminStatus object,
401: if a session has been initiated with a Peer,
402: changing objects in this table will
403: wreak havoc with the session and interrupt traffic. To repeat again:
404: the recommended procedure is to set the mplsLdpEntityAdminStatus to
405: down, thereby explicitely causing a session to be torn down. Then,
406: change objects in this entry, then set the mplsLdpEntityAdminStatus
407: to enable which enables a NEW session to be initiated.
408:
409: If the value of the object
410: 'mplsLdpEntityOptionalParameters' contains the
411: value of 'frameRelaySessionParameters(3)' then
412: there must be at least one corresponding entry
413: in this table.
414:
415: NOTE: This RowStatus object should
416: have the same value of the 'mplsLdpEntityRowStatus'
417: related to this entry."
418: ::= { mplsLdpEntityFrameRelayLREntry 5 }
419:
420:
421: --
422: -- MPLS LDP Frame Relay Session Information
423: --
424:
425: mplsLdpFrameRelaySesObjects OBJECT IDENTIFIER ::=
426: { mplsLdpFrameRelayObjects 2 }
427:
428:
429: mplsLdpFrameRelaySesTable OBJECT-TYPE
430: SYNTAX SEQUENCE OF MplsLdpFrameRelaySesEntry
431: MAX-ACCESS not-accessible
432: STATUS current
433: DESCRIPTION
434: "A table of Frame Relay label range intersections
435: between the LDP Entities and LDP Peers.
436: Each row represents a single label range intersection.
437: NOTE: this table cannot use the 'AUGMENTS'
438: clause because there is not necessarily a one-to-one
439: mapping between this table and the mplsLdpSessionTable."
440: ::= { mplsLdpFrameRelaySesObjects 1 }
441:
442: mplsLdpFrameRelaySesEntry OBJECT-TYPE
443: SYNTAX MplsLdpFrameRelaySesEntry
444: MAX-ACCESS not-accessible
445: STATUS current
446: DESCRIPTION
447: "An entry in this table represents information on a
448: single label range intersection between an
449: LDP Entity and LDP Peer.
450:
451: The information contained in a row is read-only."
452: INDEX { mplsLdpEntityLdpId,
453: mplsLdpEntityIndex,
454: mplsLdpPeerLdpId,
455: mplsLdpFrameRelaySesMinDlci
456: }
457: ::= { mplsLdpFrameRelaySesTable 1 }
458:
459: MplsLdpFrameRelaySesEntry ::= SEQUENCE {
460: mplsLdpFrameRelaySesMinDlci DLCI,
461: mplsLdpFrameRelaySesMaxDlci DLCI,
462: mplsLdpFrameRelaySesLen INTEGER
463: }
464:
465:
466: mplsLdpFrameRelaySesMinDlci OBJECT-TYPE
467: SYNTAX DLCI
468: MAX-ACCESS not-accessible
469: STATUS current
470: DESCRIPTION
471: "The lower bound of DLCIs which are supported.
472: The value of zero is a valid value for the
473: minimum DLCI field of the label."
474: REFERENCE
475: "[RFC 3034] Use of Label Switching on Frame Relay Networks
476: Specification."
477: ::= { mplsLdpFrameRelaySesEntry 1 }
478:
479: mplsLdpFrameRelaySesMaxDlci OBJECT-TYPE
480: SYNTAX DLCI
481: MAX-ACCESS read-only
482: STATUS current
483: DESCRIPTION
484: "The upper bound of DLCIs which are supported."
485: ::= { mplsLdpFrameRelaySesEntry 2 }
486:
487: mplsLdpFrameRelaySesLen OBJECT-TYPE
488: SYNTAX INTEGER {
489: tenDlciBits(0),
490: twentyThreeDlciBits(2)
491: }
492: MAX-ACCESS read-only
493: STATUS current
494: DESCRIPTION
495: "This object specifies the DLCI bits."
496: ::= { mplsLdpFrameRelaySesEntry 3 }
497:
498:
499: --****************************************************************
500: -- Module Conformance Statement
501: --****************************************************************
502:
503:
504: mplsLdpFrameRelayGroups
505: OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 1 }
506:
507: mplsLdpFrameRelayCompliances
508: OBJECT IDENTIFIER ::= { mplsLdpFrameRelayConformance 2 }
509:
510: --
511: -- Full Compliance
512: --
513:
514: mplsLdpFrameRelayModuleFullCompliance MODULE-COMPLIANCE
515: STATUS current
516: DESCRIPTION
517: "The Module is implemented with support for
518: read-create and read-write. In other words,
519: both monitoring and configuration
520: are available when using this MODULE-COMPLIANCE."
521: MODULE -- this module
522: MANDATORY-GROUPS {
523: mplsLdpFrameRelayGroup
524: }
525:
526: OBJECT mplsLdpEntityFrameRelayRowStatus
527: SYNTAX RowStatus { active(1) }
528: WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
529: DESCRIPTION
530: "Support for createAndWait and notInService is not required."
531:
532: OBJECT mplsLdpEntityFrameRelayLRRowStatus
533: SYNTAX RowStatus { active(1) }
534: WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
535: DESCRIPTION
536: "Support for createAndWait and notInService is not required."
537:
538: ::= { mplsLdpFrameRelayCompliances 1 }
539:
540: --
541: -- Read-Only Compliance
542: --
543:
544: mplsLdpFrameRelayModuleReadOnlyCompliance MODULE-COMPLIANCE
545: STATUS current
546: DESCRIPTION
547: "The Module is implemented with support for
548: read-only. In other words, only monitoring
549: is available by implementing this MODULE-COMPLIANCE."
550: MODULE -- this module
551: MANDATORY-GROUPS {
552: mplsLdpFrameRelayGroup
553: }
554:
555: OBJECT mplsLdpEntityFrameRelayIfIndexOrZero
556: MIN-ACCESS read-only
557: DESCRIPTION
558: "Write access is not required."
559:
560: OBJECT mplsLdpEntityFrameRelayMergeCap
561: MIN-ACCESS read-only
562: DESCRIPTION
563: "Write access is not required."
564:
565: OBJECT mplsLdpEntityFrameRelayLRComponents
566: MIN-ACCESS read-only
567: DESCRIPTION
568: "Write access is not required."
569:
570: OBJECT mplsLdpEntityFrameRelayVcDirectionality
571: MIN-ACCESS read-only
572: DESCRIPTION
573: "Write access is not required."
574:
575: OBJECT mplsLdpEntityFrameRelayStorageType
576: MIN-ACCESS read-only
577: DESCRIPTION
578: "Write access is not required."
579:
580: OBJECT mplsLdpEntityFrameRelayRowStatus
581: SYNTAX RowStatus { active(1) }
582: MIN-ACCESS read-only
583: DESCRIPTION
584: "Write access is not required, and active is the
585: only status that needs to be supported."
586:
587: OBJECT mplsLdpEntityFrameRelayLRMaxDlci
588: MIN-ACCESS read-only
589: DESCRIPTION
590: "Write access is not required."
591:
592: OBJECT mplsLdpEntityFrameRelayLRLen
593: MIN-ACCESS read-only
594: DESCRIPTION
595: "Write access is not required."
596:
597: OBJECT mplsLdpEntityFrameRelayLRStorageType
598: MIN-ACCESS read-only
599: DESCRIPTION
600: "Write access is not required."
601:
602: OBJECT mplsLdpEntityFrameRelayLRRowStatus
603: SYNTAX RowStatus { active(1) }
604: MIN-ACCESS read-only
605: DESCRIPTION
606: "Write access is not required, and active is the
607: only status that needs to be supported."
608: ::= { mplsLdpFrameRelayCompliances 2 }
609:
610: --
611: -- units of conformance
612: --
613:
614: mplsLdpFrameRelayGroup OBJECT-GROUP
615: OBJECTS {
616: mplsLdpEntityFrameRelayIfIndexOrZero,
617: mplsLdpEntityFrameRelayMergeCap,
618: mplsLdpEntityFrameRelayLRComponents,
619: mplsLdpEntityFrameRelayVcDirectionality,
620: mplsLdpEntityFrameRelayStorageType,
621: mplsLdpEntityFrameRelayRowStatus,
622: mplsLdpEntityFrameRelayLRMaxDlci,
623: mplsLdpEntityFrameRelayLRLen,
624: mplsLdpEntityFrameRelayLRStorageType,
625: mplsLdpEntityFrameRelayLRRowStatus,
626: mplsLdpFrameRelaySesMaxDlci,
627: mplsLdpFrameRelaySesLen
628: }
629: STATUS current
630: DESCRIPTION
631: "Objects that apply to all MPLS LDP implementations over
632: Frame Relay."
633: ::= { mplsLdpFrameRelayGroups 1 }
634:
635:
636:
637: END
638:
639: --
640: -- Copyright (C) The Internet Society (2003). All Rights Reserved.
641: --
642: --
643: -- This document and translations of it may be copied and furnished to
644: -- others, and derivative works that comment on or otherwise explain it
645: -- or assist in its implementation may be prepared, copied, published
646: -- and distributed, in whole or in part, without restriction of any
647: -- kind, provided that the above copyright notice and this paragraph are
648: -- included on all such copies and derivative works. However, this
649: -- document itself may not be modified in any way, such as by removing
650: -- the copyright notice or references to the Internet Society or other
651: -- Internet organizations, except as needed for the purpose of
652: -- developing Internet standards in which case the procedures for
653: -- copyrights defined in the Internet Standards process must be
654: -- followed, or as required to translate it into languages other than
655: -- English.
656: --
657: -- The limited permissions granted above are perpetual and will not be
658: -- revoked by the Internet Society or its successors or assigns.
659: --
660: -- This document and the information contained herein is provided on an
661: -- "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
662: -- TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
663: -- BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
664: -- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
665: -- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
666: