![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to rfc1162.txt CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / doc / rfcs|
Return to rfc1162.txt CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / doc / rfcs |
1.1 root 1:
2:
3:
4:
5:
6:
7: Network Working Group Greg Satz
8: Request for Comments: 1162 cisco Systems, Inc.
9: June 1990
10:
11:
12: Connectionless Network Protocol (ISO 8473)
13: and
14: End System to Intermediate System (ISO 9542)
15: Management Information Base
16:
17: Table of Contents
18:
19: 1. Status of this Memo .................................. 1
20: 2. Historical Perspective................................ 2
21: 3. Objects .............................................. 3
22: 3.1 Format of Definitions ............................... 3
23: 4. Object Definitions ................................... 4
24: 4.1 The CLNP Group ...................................... 5
25: 4.1.1 The CLNP Interfaces table ......................... 14
26: 4.1.2 The CLNP Routing table ............................ 16
27: 4.1.3 The CLNP Address Translation Tables ............... 22
28: 4.2 The CLNP Error Group ................................ 30
29: 4.3 The ESIS Group ...................................... 47
30: 5. Definitions .......................................... 50
31: 6. Identification of OBJECT instances for use with the
32: SNMP ................................................. 66
33: 6.1 clnpAddrTable Object Type Names ..................... 67
34: 6.2 clnpRoutingTable Object Type Names .................. 67
35: 6.3 clnpNetToMediaTable Object Type Names ............... 68
36: 6.4 clnpMediaToNetTable Object Type Names ............... 68
37: 7. References ........................................... 69
38: 8. Security Considerations............................... 70
39: 9. Author's Address...................................... 70
40:
41: 1. Status of this Memo
42:
43: This memo defines an experimental portion of the Management
44: Information Base (MIB) for use with network management protocols in
45: TCP/IP-based internets.
46:
47: This memo does not specify a standard for the Internet community.
48: However, after experimentation, if sufficient consensus is reached in
49: the Internet community, then a subsequent revision of this document
50: may be placed in the Internet-standard MIB.
51:
52: Distribution of this memo is unlimited.
53:
54:
55:
56:
57:
58: Satz [Page 1]
59:
60: RFC 1162 CLNS MIB June 1990
61:
62:
63: 2. Historical Perspective
64:
65: As reported in RFC 1052, IAB Recommendations for the Development of
66: Internet Network Management Standards [1], a two-prong strategy for
67: network management of TCP/IP-based internets was undertaken. In the
68: short-term, the Simple Network Management Protocol (SNMP), defined in
69: RFC 1067, was to be used to manage nodes in the Internet community.
70: In the long-term, the use of the OSI network management framework was
71: to be examined. Two documents were produced to define the management
72: information: RFC 1065, which defined the Structure of Management
73: Information (SMI), and RFC 1066, which defined the Management
74: Information Base (MIB). Both of these documents were designed so as
75: to be compatible with both the SNMP and the OSI network management
76: framework.
77:
78: This strategy was quite successful in the short-term: Internet-based
79: network management technology was fielded, by both the research and
80: commercial communities, within a few months. As a result of this,
81: portions of the Internet community became network manageable in a
82: timely fashion.
83:
84: As reported in RFC 1109, Report of the Second Ad Hoc Network
85: Management Review Group [2], the requirements of the SNMP and the OSI
86: network management frameworks were more different than anticipated.
87: As such, the requirement for compatibility between the SMI/MIB and
88: both frameworks was suspended. This action permitted the operational
89: network management framework, based on the SNMP, to respond to new
90: operational needs in the Internet community by producing MIB-II.
91:
92: In May of 1990, the core documents were elevated to "Standard
93: Protocols" with "Recommended" status. As such, the Internet-
94: standard network management framework consists of: Structure and
95: Identification of Management Information for TCP/IP-based internets,
96: RFC 1155 [3], which describes how managed objects contained in the
97: MIB are defined; Management Information Base for Network Management
98: of TCP/IP-based internets, which describes the managed objects
99: contained in the MIB, RFC 1156 [4]; and, the Simple Network
100: Management Protocol, RFC 1157 [5], which defines the protocol used to
101: manage these objects.
102:
103: Consistent with the IAB directive to produce simple, workable systems
104: in the short-term, the list of managed objects defined in the
105: Internet-standard MIB was derived by taking only those elements which
106: are considered essential. However, the SMI defined three
107: extensibility mechanisms: one, the addition of new standard objects
108: through the definitions of new versions of the MIB; two, the addition
109: of widely-available but non-standard objects through the experimental
110: subtree; and three, the addition of private objects through the
111:
112:
113:
114: Satz [Page 2]
115:
116: RFC 1162 CLNS MIB June 1990
117:
118:
119: enterprises subtree. Such additional objects can not only be used
120: for vendor-specific elements, but also for experimentation as
121: required to further the knowledge of which other objects are
122: essential.
123:
124: Since the publication of the Internet-standard MIB, experience has
125: lead to a new document, termed MIB-II [6], being defined.
126:
127: This memo defines extensions to the MIB using the second method. It
128: contains definitions of managed objects used for experimentation.
129: After experimentation, if sufficient consensus is reached in the
130: Internet community, then a subsequent revision of this memo may be
131: placed in the Internet-standard MIB.
132:
133: 3. Objects
134:
135: Managed objects are accessed via a virtual information store, termed
136: the Management Information Base or MIB. Objects in the MIB are
137: defined using the subset of Abstract Syntax Notation One (ASN.1) [7]
138: defined in the SMI. In particular, each object has a name, a syntax,
139: and an encoding. The name is an object identifier, an
140: administratively assigned name, which specifies an object type. The
141: object type together with an object instance serves to uniquely
142: identify a specific instantiation of the object. For human
143: convenience, we often use a textual string, termed the OBJECT
144: DESCRIPTOR, to also refer to the object type.
145:
146: The syntax of an object type defines the abstract data structure
147: corresponding to that object type. The ASN.1 language is used for
148: this purpose. However, the SMI [3] purposely restricts the ASN.1
149: constructs which may be used. These restrictions are explicitly made
150: for simplicity.
151:
152: The encoding of an object type is simply how that object type is
153: represented using the object type's syntax. Implicitly tied to the
154: notion of an object type's syntax and encoding is how the object type
155: is represented when being transmitted on the network.
156:
157: This SMI specifies the use of the basic encoding rules of ASN.1 [8],
158: subject to the additional requirements imposed by the SNMP.
159:
160: 3.1. Format of Definitions
161:
162: The next section contains the specification of all object types
163: contained in the MIB. Following the conventions of the companion
164: memo, the object types are defined using the following fields:
165:
166:
167:
168:
169:
170: Satz [Page 3]
171:
172: RFC 1162 CLNS MIB June 1990
173:
174:
175: OBJECT:
176: -------
177: A textual name, termed the OBJECT DESCRIPTOR, for the
178: object type, along with its corresponding OBJECT
179: IDENTIFIER.
180:
181: Syntax:
182: The abstract syntax for the object type, presented using
183: ASN.1. This must resolve to an instance of the ASN.1
184: type ObjectSyntax defined in the SMI.
185:
186: Definition:
187: A textual description of the semantics of the object
188: type. Implementations should ensure that their
189: interpretation of the object type fulfills this
190: definition since this MIB is intended for use in multi-
191: vendor environments. As such it is vital that object
192: types have consistent meaning across all machines.
193:
194: Access:
195: A keyword, one of read-only, read-write, write-only, or
196: not-accessible. Note that this designation specifies the
197: minimum level of support required. As a local matter,
198: implementations may support other access types (e.g., an
199: implementation may elect to permitting writing a variable
200: marked herein as read-only). Further, protocol-specific
201: "views" (e.g., those implied by an SNMP community) may
202: make further restrictions on access to a variable.
203:
204: Status:
205: A keyword, one of mandatory, optional, obsolete, or
206: deprecated. Use of deprecated implies mandatory status.
207:
208: 4. Object Definitions
209:
210: CLNS-MIB DEFINITIONS ::= BEGIN
211:
212: IMPORTS
213: experimental, OBJECT-TYPE, Counter
214: FROM RFC1155-SMI;
215:
216: -- new type of NetworkAddress
217:
218: ClnpAddress ::=
219: [APPLICATION 5]
220: IMPLICIT OCTET STRING (SIZE (1..21))
221:
222:
223:
224:
225:
226: Satz [Page 4]
227:
228: RFC 1162 CLNS MIB June 1990
229:
230:
231: clns OBJECT IDENTIFIER ::= { experimental 1 }
232:
233: clnp OBJECT IDENTIFIER ::= { clns 1 }
234: error OBJECT IDENTIFIER ::= { clns 2 }
235: echo OBJECT IDENTIFIER ::= { clns 3 }
236: es-is OBJECT IDENTIFIER ::= { clns 4 }
237:
238: END
239:
240: These objects can be used when the ISO Connectionless-mode Network
241: Protocol [9] and End System to Intermediate System [10] protocols are
242: present. No assumptions are made as to what underlying protocol is
243: being used to carry the SNMP.
244:
245: This memo uses the string encoding of [11] to textually describe OSI
246: addresses.
247:
248: The ASN.1 type ClnpAddress is used to denote an OSI address. This
249: consists of a string of octets. The first octet of the string
250: contains a binary value in the range of 0..20, and indicates the the
251: length in octets of the NSAP. Following the first octet, is the
252: NSAP, expressed in concrete binary notation, starting with the most
253: significant octet. A zero- length NSAP is used as a "special"
254: address meaning "the default NSAP" (analogous to the IP address of
255: 0.0.0.0). Such an NSAP is encoded as a single octet, containing the
256: value 0.
257:
258: All other NSAPs are encoded in at least 2 octets.
259:
260: 4.1. The CLNP Group
261:
262: Implementation is experimental and is recommended for all systems
263: that support a CLNP.
264:
265:
266: OBJECT:
267: -------
268: clnpForwarding { clnp 1 }
269:
270: Syntax:
271: INTEGER {
272: is(1), -- entity is an intermediate system
273: es(2), -- entity is an end system and does not
274: forward PDUs
275: }
276:
277: Definition:
278: The indication of whether this entity is active as an
279:
280:
281:
282: Satz [Page 5]
283:
284: RFC 1162 CLNS MIB June 1990
285:
286:
287: intermediate or end system. Only intermediate systems
288: will forward PDUs onward that are not addressed to them.
289:
290: Access:
291: read-write.
292:
293: Status:
294: mandatory.
295:
296:
297: OBJECT:
298: -------
299: clnpDefaultLifeTime { clnp 2 }
300:
301: Syntax:
302: INTEGER
303:
304: Definition:
305: The default value inserted into the Lifetime field of the
306: CLNP PDU header of PDUs sourced by this entity.
307:
308: Access:
309: read-write.
310:
311: Status:
312: mandatory.
313:
314:
315: OBJECT:
316: -------
317: clnpInReceives { clnp 3 }
318:
319: Syntax:
320: Counter
321:
322: Definition:
323: The total number of input PDUs received from all
324: connected network interfaces running CLNP, including
325: errors.
326:
327: Access:
328: read-only.
329:
330: Status:
331: mandatory.
332:
333:
334:
335:
336:
337:
338: Satz [Page 6]
339:
340: RFC 1162 CLNS MIB June 1990
341:
342:
343: OBJECT:
344: -------
345: clnpInHdrErrors { clnp 4 }
346:
347: Syntax:
348: Counter
349:
350: Definition:
351: The number of input PDUs discarded due to errors in the
352: CLNP header, including bad checksums, version mismatch,
353: lifetime exceeded, errors discovered in processing
354: options, etc.
355:
356: Access:
357: read-only.
358:
359: Status:
360: mandatory.
361:
362:
363: OBJECT:
364: -------
365: clnpInAddrErrors { clnp 5 }
366:
367: Syntax:
368: Counter
369:
370: Definition:
371: The number of input PDUs discarded because the NSAP
372: address in the CLNP header's destination field was not a
373: valid NSAP to be received at this entity. This count
374: includes addresses not understood. For end systems, this
375: is a count of PDUs which arrived with a destination NSAP
376: which was not local.
377:
378: Access:
379: read-only.
380:
381: Status:
382: mandatory.
383:
384:
385: OBJECT:
386: -------
387: clnpForwPDUs { clnp 6 }
388:
389: Syntax:
390: Counter
391:
392:
393:
394: Satz [Page 7]
395:
396: RFC 1162 CLNS MIB June 1990
397:
398:
399: Definition:
400: The number of input PDUs for which this entity was not
401: the final destination and which an attempt was made to
402: forward them onward.
403:
404: Access:
405: read-only.
406:
407: Status:
408: mandatory.
409:
410:
411: OBJECT:
412: -------
413: clnpInUnknownNLPs { clnp 7 }
414:
415: Syntax:
416: Counter
417:
418: Definition:
419: The number of locally-addressed PDUs successfully
420: received but discarded because the network layer protocol
421: was unknown or unsupported (e.g., not CLNP or ES-IS).
422:
423: Access:
424: read-only.
425:
426: Status:
427: mandatory.
428:
429:
430: OBJECT:
431: -------
432: clnpInUnknownULPs { clnp 8 }
433:
434: Syntax:
435: Counter
436:
437: Definition:
438: The number of locally-addressed PDUs successfully
439: received but discarded because the upper layer protocol
440: was unknown or unsupported (e.g., not TP4).
441:
442: Access:
443: read-only.
444:
445: Status:
446: mandatory.
447:
448:
449:
450: Satz [Page 8]
451:
452: RFC 1162 CLNS MIB June 1990
453:
454:
455: OBJECT:
456: -------
457: clnpInDiscards { clnp 9 }
458:
459: Syntax:
460: Counter
461:
462: Definition:
463: The number of input CLNP PDUs for which no problems were
464: encountered to prevent their continued processing, but
465: were discarded (e.g., for lack of buffer space). Note that
466: this counter does not include any PDUs discarded while
467: awaiting re-assembly.
468:
469: Access:
470: read-only.
471:
472: Status:
473: mandatory.
474:
475:
476: OBJECT:
477: -------
478: clnpInDelivers { clnp 10 }
479:
480: Syntax:
481: Counter
482:
483: Definition:
484: The total number of input PDUs successfully delivered to
485: the CLNS transport user.
486:
487: Access:
488: read-only.
489:
490: Status:
491: mandatory.
492:
493:
494: OBJECT:
495: -------
496: clnpOutRequests { clnp 11 }
497:
498: Syntax:
499: Counter
500:
501: Definition:
502: The total number of CLNP PDUs which local CLNS user
503:
504:
505:
506: Satz [Page 9]
507:
508: RFC 1162 CLNS MIB June 1990
509:
510:
511: protocols supplied to CLNP for transmission requests.
512: This counter does not include any PDUs counted in
513: clnpForwPDUs.
514:
515: Access:
516: read-only.
517:
518: Status:
519: mandatory.
520:
521:
522: OBJECT:
523: -------
524: clnpOutDiscards { clnp 12 }
525:
526: Syntax:
527: Counter
528:
529: Definition:
530: The number of output CLNP PDUs for which no other problem
531: was encountered to prevent their transmission but were
532: discarded (e.g., for lack of buffer space). Note this
533: counter includes PDUs counted in clnpForwPDUs.
534:
535: Access:
536: read-only.
537:
538: Status:
539: mandatory.
540:
541:
542: OBJECT:
543: -------
544: clnpOutNoRoutes { clnp 13 }
545:
546: Syntax:
547: Counter
548:
549: Definition:
550: The number of CLNP PDUs discarded because no route could
551: be found to transmit them to their destination. This
552: counter includes any PDUs counted in clnpForwPDUs.
553:
554: Access:
555: read-only.
556:
557: Status:
558: mandatory.
559:
560:
561:
562: Satz [Page 10]
563:
564: RFC 1162 CLNS MIB June 1990
565:
566:
567: OBJECT:
568: -------
569: clnpReasmTimeout { clnp 14 }
570:
571: Syntax:
572: INTEGER
573:
574: Definition:
575: The maximum number of seconds which received segments are
576: held while they are awaiting reassembly at this entity.
577:
578: Access:
579: read-only.
580:
581: Status:
582: mandatory.
583:
584:
585: OBJECT:
586: -------
587: clnpReasmReqds { clnp 15 }
588:
589: Syntax:
590: Counter
591:
592: Definition:
593: The number of CLNP segments received which needed to be
594: reassembled at this entity.
595:
596: Access:
597: read-only.
598:
599: Status:
600: mandatory.
601:
602:
603: OBJECT:
604: -------
605: clnpReasmOKs { clnp 16 }
606:
607: Syntax:
608: Counter
609:
610: Definition:
611: The number of CLNP PDUs successfully re-assembled at this
612: entity.
613:
614:
615:
616:
617:
618: Satz [Page 11]
619:
620: RFC 1162 CLNS MIB June 1990
621:
622:
623: Access:
624: read-only.
625:
626: Status:
627: mandatory.
628:
629:
630: OBJECT:
631: -------
632: clnpReasmFails { clnp 17 }
633:
634: Syntax:
635: Counter
636:
637: Definition:
638: The number of failures detected by the CLNP reassembly
639: algorithm (for any reason: timed out, buffer size, etc).
640:
641: Access:
642: read-only.
643:
644: Status:
645: mandatory.
646:
647:
648: OBJECT:
649: -------
650: clnpSegOKs { clnp 18 }
651:
652: Syntax:
653: Counter
654:
655: Definition:
656: The number of CLNP PDUs that have been successfully
657: segmented at this entity.
658:
659: Access:
660: read-only.
661:
662: Status:
663: mandatory.
664:
665:
666: OBJECT:
667: -------
668: clnpSegFails { clnp 19 }
669:
670:
671:
672:
673:
674: Satz [Page 12]
675:
676: RFC 1162 CLNS MIB June 1990
677:
678:
679: Syntax:
680: Counter
681:
682: Definition:
683: The number of CLNP PDUs that have been discarded because
684: they needed to be fragmented at this entity but could
685: not.
686:
687: Access:
688: read-only.
689:
690: Status:
691: mandatory.
692:
693:
694: OBJECT:
695: -------
696: clnpSegCreates { clnp 20 }
697:
698: Syntax:
699: Counter
700:
701: Definition:
702: The number of CLNP PDU segments that have been generated
703: as a result of segmentation at this entity.
704:
705: Access:
706: read-only.
707:
708: Status:
709: mandatory.
710:
711:
712: OBJECT:
713: -------
714: clnpInOpts { clnp 25 }
715:
716: Syntax:
717: Counter
718:
719: Definition:
720: The number of CLNP PDU segments that have been input with
721: options at this entity.
722:
723: Access:
724: read-only.
725:
726:
727:
728:
729:
730: Satz [Page 13]
731:
732: RFC 1162 CLNS MIB June 1990
733:
734:
735: Status:
736: mandatory.
737:
738:
739: OBJECT:
740: -------
741: clnpOutOpts { clnp 26 }
742:
743: Syntax:
744: Counter
745:
746: Definition:
747: The number of CLNP PDU segments that have been generated
748: with options by this entity.
749:
750: Access:
751: read-only.
752:
753: Status:
754: mandatory.
755:
756: 4.1.1. The CLNP Interfaces table
757:
758: The CLNP Interfaces table contains information on the entity's
759: interfaces which are running the CLNP.
760:
761:
762: OBJECT:
763: -------
764: clnpAddrTable { clnp 21 }
765:
766: Syntax:
767: SEQUENCE OF ClnpAddrEntry
768:
769: Definition:
770: The table of addressing information relevant to this
771: entity's CLNP addresses.
772:
773: Access:
774: not-accessible.
775:
776: Status:
777: mandatory.
778:
779:
780: OBJECT:
781: -------
782: clnpAddrEntry { clnpAddrTable 1 }
783:
784:
785:
786: Satz [Page 14]
787:
788: RFC 1162 CLNS MIB June 1990
789:
790:
791: Syntax:
792: ClnpAddrEntry :: = SEQUENCE {
793: clnpAdEntAddr
794: ClnpAddress,
795: clnpAdEntIfIndex
796: INTEGER,
797: clnpAdEntReasmMaxSize
798: INTEGER (0..65535)
799: }
800:
801: Definition:
802: The addressing information for one of this entity's CLNP
803: addresses.
804:
805: Access:
806: not-accessible.
807:
808: Status:
809: mandatory.
810:
811:
812: OBJECT:
813: -------
814: clnpAdEntAddr { clnpAddrEntry 1 }
815:
816: Syntax:
817: ClnpAddress
818:
819: Definition:
820: The CLNP address to which this entry's addressing
821: information pertains.
822:
823: Access:
824: read-only.
825:
826: Status:
827: mandatory.
828:
829:
830: OBJECT:
831: -------
832: clnpAdEntIfIndex { clnpAddrEntry 2 }
833:
834: Syntax:
835: INTEGER
836:
837: Definition:
838: The index value which uniquely identifies the interface
839:
840:
841:
842: Satz [Page 15]
843:
844: RFC 1162 CLNS MIB June 1990
845:
846:
847: to which this entry is applicable. The interface
848: identified by a particular value of this index is the
849: same interface as identified by the same value of
850: ifIndex.
851:
852: Access:
853: read-only.
854:
855: Status:
856: mandatory.
857:
858:
859: OBJECT:
860: -------
861: clnpAdEntReasmMaxSize { clnpAddrEntry 3 }
862:
863: Syntax:
864: INTEGER (0..65535)
865:
866: Definition:
867: The size of the largest CLNP PDU which this entity can
868: re-assemble from incoming CLNP segmented PDUs received on
869: this interface.
870:
871: Access:
872: read-only.
873:
874: Status:
875: mandatory.
876:
877: 4.1.2. The CLNP Routing table
878:
879: The CLNP Routing table contains an entry for each route known to the
880: entity.
881:
882:
883: OBJECT:
884: -------
885: clnpRoutingTable { clnp 22 }
886:
887: Syntax:
888: SEQUENCE OF ClnpRouteEntry
889:
890: Definition:
891: This entity's CLNP routing table.
892:
893: Access:
894: not-accessible.
895:
896:
897:
898: Satz [Page 16]
899:
900: RFC 1162 CLNS MIB June 1990
901:
902:
903: Status:
904: mandatory.
905:
906:
907: OBJECT:
908: -------
909: clnpRouteEntry { clnpRoutingTable 1 }
910:
911: Syntax:
912: ClnpRouteEntry ::= SEQUENCE {
913: clnpRouteDest
914: ClnpAddress,
915: clnpRouteIfIndex
916: INTEGER,
917: clnpRouteMetric1
918: INTEGER,
919: clnpRouteMetric2
920: INTEGER,
921: clnpRouteMetric3
922: INTEGER,
923: clnpRouteMetric4
924: INTEGER,
925: clnpRouteNextHop
926: ClnpAddress,
927: clnpRouteType
928: INTEGER,
929: clnpRouteProto
930: INTEGER,
931: clnpRouteAge
932: INTEGER
933: }
934:
935: Definition:
936: A route to a particular destination.
937:
938: Access:
939: not-accessible.
940:
941: Status:
942: mandatory.
943:
944:
945: OBJECT:
946: -------
947: clnpRouteDest { clnpRouteEntry 1 }
948:
949: Syntax:
950: ClnpAddress
951:
952:
953:
954: Satz [Page 17]
955:
956: RFC 1162 CLNS MIB June 1990
957:
958:
959: Definition:
960: The destination CLNP address of this route.
961:
962: Access:
963: read-write.
964:
965: Status:
966: mandatory.
967:
968:
969: OBJECT:
970: -------
971: clnpRouteIfIndex { clnpRouteEntry 2 }
972:
973: Syntax:
974: INTEGER
975:
976: Definition:
977: The index value which uniquely identifies the local
978: interface through which the next hop of this route should
979: be reached. The interface identified by a particular
980: value of this index is the same as identified by the same
981: value of ifIndex.
982:
983: Access:
984: read-write.
985:
986: Status:
987: mandatory.
988:
989:
990: OBJECT:
991: -------
992: clnpRouteMetric1 { clnpRouteEntry 3 }
993:
994: Syntax:
995: INTEGER
996:
997: Definition:
998: The primary routing metric for this route. The semantics
999: of this metric are determined by the routing-protocol
1000: specified in the route's clnpRouteProto value. If this
1001: metric is not used, its value should be set to -1.
1002:
1003: Access:
1004: read-write.
1005:
1006:
1007:
1008:
1009:
1010: Satz [Page 18]
1011:
1012: RFC 1162 CLNS MIB June 1990
1013:
1014:
1015: Status:
1016: mandatory.
1017:
1018:
1019: OBJECT:
1020: -------
1021: clnpRouteMetric2 { clnpRouteEntry 4 }
1022:
1023: Syntax:
1024: INTEGER
1025:
1026: Definition:
1027: An alternate routing metric for this route. The
1028: semantics of this metric are determined by the routing-
1029: protocol specified in the route's clnpRouteProto value.
1030: If this metric is not used, its value should be set to
1031: -1.
1032:
1033: Access:
1034: read-write.
1035:
1036: Status:
1037: mandatory.
1038:
1039:
1040: OBJECT:
1041: -------
1042: clnpRouteMetric3 { clnpRouteEntry 5 }
1043:
1044: Syntax:
1045: INTEGER
1046:
1047: Definition:
1048: An alternate routing metric for this route. The
1049: semantics of this metric are determined by the routing-
1050: protocol specified in the route's clnpRouteProto value.
1051: If this metric is not used, its value should be set to
1052: -1.
1053:
1054: Access:
1055: read-write.
1056:
1057: Status:
1058: mandatory.
1059:
1060:
1061:
1062:
1063:
1064:
1065:
1066: Satz [Page 19]
1067:
1068: RFC 1162 CLNS MIB June 1990
1069:
1070:
1071: OBJECT:
1072: -------
1073: clnpRouteMetric4 { clnpRouteEntry 6 }
1074:
1075: Syntax:
1076: INTEGER
1077:
1078: Definition:
1079: An alternate routing metric for this route. The
1080: semantics of this metric are determined by the routing-
1081: protocol specified in the route's clnpRouteProto value.
1082: If this metric is not used, its value should be set to
1083: -1.
1084:
1085: Access:
1086: read-write.
1087:
1088: Status:
1089: mandatory.
1090:
1091:
1092: OBJECT:
1093: -------
1094: clnpRouteNextHop { clnpRouteEntry 7 }
1095:
1096: Syntax:
1097: ClnpAddress
1098:
1099: Definition:
1100: The CLNP address of the next hop of this route.
1101:
1102: Access:
1103: read-write.
1104:
1105: Status:
1106: mandatory.
1107:
1108:
1109: OBJECT:
1110: -------
1111: clnpRouteType { clnpRouteEntry 8 }
1112:
1113: Syntax:
1114: INTEGER {
1115: other(1), -- none of the following
1116:
1117: invalid(2), -- an invalidated route
1118:
1119:
1120:
1121:
1122: Satz [Page 20]
1123:
1124: RFC 1162 CLNS MIB June 1990
1125:
1126:
1127: -- route to directly
1128: direct(3), -- connected (sub-)network
1129:
1130: -- route to a non-local
1131: remote(4) -- host/network/sub-network
1132: }
1133:
1134: Definition:
1135: The type of route.
1136:
1137: Setting this object to the value invalid(2) has the effect of
1138: invaliding the corresponding entry in the clnpRoutingTable.
1139: That is, it effectively dissasociates the destination
1140: identified with said entry from the route identified with said
1141: entry. It is an implementation-specific matter as to whether
1142: the agent removes an invalidated entry from the table.
1143: Accordingly, management stations must be prepared to receive
1144: tabular information from agents that corresponds to entries
1145: not currently in use. Proper interpretation of such entries
1146: requires examination of the relevant clnpRouteType object.
1147:
1148: Access:
1149: read-write.
1150:
1151: Status:
1152: mandatory.
1153:
1154:
1155: OBJECT:
1156: -------
1157: clnpRouteProto { clnpRouteEntry 9 }
1158:
1159: Syntax:
1160: INTEGER {
1161: other(1), -- none of the following
1162:
1163: -- non-protocol information
1164: -- e.g., manually
1165: local(2), -- configured entries
1166:
1167: -- set via a network
1168: netmgmt(3), -- management protocol
1169:
1170: -- similar to ipRouteProto
1171: -- but omits several IP-specific
1172: -- protocols
1173:
1174: is-is(9),
1175:
1176:
1177:
1178: Satz [Page 21]
1179:
1180: RFC 1162 CLNS MIB June 1990
1181:
1182:
1183: ciscoIgrp(11),
1184: bbnSpfIgp(12),
1185: ospf(13),
1186: bgp(14)
1187: }
1188:
1189: Definition:
1190: The routing mechanism via which this route was learned.
1191: Inclusion of values for gateway routing protocols is not
1192: intended to imply that hosts should support those
1193: protocols.
1194:
1195: Access:
1196: read-write.
1197:
1198: Status:
1199: mandatory.
1200:
1201:
1202: OBJECT:
1203: -------
1204: clnpRouteAge { clnpRouteEntry 10 }
1205:
1206: Syntax:
1207: INTEGER
1208:
1209: Definition:
1210: The number of seconds since this route was last updated
1211: or otherwise determined to be correct. Note that no
1212: semantics of "too old" can be implied except through
1213: knowledge of the routing protocol by which the route was
1214: learned.
1215:
1216: Access:
1217: read-write.
1218:
1219: Status:
1220: mandatory.
1221:
1222: 4.1.3. The CLNP Address Translation Tables
1223:
1224: The Address Translation tables contain the CLNP address to physical
1225: address equivalences. Some interfaces do not use translation tables
1226: for determining address equivalences; if all interfaces are of this
1227: type, then the Address Translation table is empty, i.e., has zero
1228: entries.
1229:
1230:
1231:
1232:
1233:
1234: Satz [Page 22]
1235:
1236: RFC 1162 CLNS MIB June 1990
1237:
1238:
1239: OBJECT:
1240: -------
1241: clnpNetToMediaTable { clnp 23 }
1242:
1243: Syntax:
1244: SEQUENCE OF ClnpNetToMediaEntry
1245:
1246: Definition:
1247: The CLNP Address Translation table used for mapping from
1248: CLNP addresses to physical addresses.
1249:
1250: Access:
1251: not-accessible
1252:
1253:
1254: Status:
1255: mandatory.
1256:
1257:
1258: OBJECT:
1259: -------
1260: clnpNetToMediaEntry { clnpNetToMediaTable 1 }
1261:
1262: Syntax:
1263: ClnpNetToMediaEntry ::= SEQUENCE {
1264: clnpNetToMediaIfIndex
1265: INTEGER,
1266: clnpNetToMediaPhysAddress
1267: OCTET STRING,
1268: clnpNetToMediaNetAddress
1269: ClnpAddress,
1270: clnpNetToMediaType
1271: INTEGER,
1272: clnpNetToMediaAge
1273: INTEGER,
1274: clnpNetToMediaHoldTime
1275: INTEGER
1276: }
1277:
1278: Definition:
1279: Each entry contains one CLNP address to "physical"
1280: address equivalence.
1281:
1282: Access:
1283: not-accessible.
1284:
1285: Status:
1286: mandatory.
1287:
1288:
1289:
1290: Satz [Page 23]
1291:
1292: RFC 1162 CLNS MIB June 1990
1293:
1294:
1295: OBJECT:
1296: -------
1297: clnpNetToMediaIfIndex { clnpNetToMediaEntry 1 }
1298:
1299: Syntax:
1300: INTEGER
1301:
1302: Definition:
1303: The interface on which this entry's equivalence is
1304: effective. The interface identified by a particular
1305: value of this index is the same interface as identified
1306: by the same value of ifIndex.
1307:
1308: Access:
1309: read-write.
1310:
1311: Status:
1312: mandatory.
1313:
1314:
1315: OBJECT:
1316: -------
1317: clnpNetToMediaPhysAddress { clnpNetToMediaEntry 2 }
1318:
1319: Syntax:
1320: OCTET STRING
1321:
1322: Definition:
1323: The media-dependent "physical" address.
1324:
1325: Access:
1326: read-write.
1327:
1328: Status:
1329: mandatory.
1330:
1331:
1332: OBJECT:
1333: -------
1334: clnpNetToMediaNetAddress { clnpNetToMediaEntry 3 }
1335:
1336: Syntax:
1337: ClnpAddress
1338:
1339: Definition:
1340: The CLNP address corresponding to the media-dependent
1341: "physical" address.
1342:
1343:
1344:
1345:
1346: Satz [Page 24]
1347:
1348: RFC 1162 CLNS MIB June 1990
1349:
1350:
1351: Access:
1352: read-write.
1353:
1354: Status:
1355: mandatory.
1356:
1357:
1358: OBJECT:
1359: -------
1360: clnpNetToMediaType { clnpNetToMediaEntry 4 }
1361:
1362: Syntax:
1363: INTEGER {
1364: other(1), -- none of the following
1365: invalid(2), -- an invalidated mapping
1366: dynamic(3),
1367: static(4)
1368: }
1369:
1370: Definition:
1371: The type of mapping.
1372:
1373: Setting this object to the value invalid(2) has the effect of
1374: invalidating the corresponding entry in the
1375: clnpNetToMediaTable. That is, it effectively dissassociates
1376: the interface identified with said entry from the mapping
1377: identified with said entry. It is an implementation-specific
1378: matter as to whether the agent removes an invalidated entry
1379: from the table. Accordingly, management stations must be
1380: prepared to receive tabular information from agents that
1381: corresponds to entries not currently in use. Proper
1382: interpretation of such entries requires examination of the
1383: relevant clnpNetToMediaType object.
1384:
1385: Access:
1386: read-write.
1387:
1388: Status:
1389: mandatory.
1390:
1391:
1392: OBJECT:
1393: -------
1394: clnpNetToMediaAge { clnpNetToMediaEntry 5 }
1395:
1396: Syntax:
1397: INTEGER
1398:
1399:
1400:
1401:
1402: Satz [Page 25]
1403:
1404: RFC 1162 CLNS MIB June 1990
1405:
1406:
1407: Definition:
1408: The number of seconds since this entry was last updated
1409: or otherwise determined to be correct. Note that no
1410: semantics of "too old" can be implied except through
1411: knowledge of the type of entry.
1412:
1413: Access:
1414: read-write.
1415:
1416: Status:
1417: mandatory.
1418:
1419:
1420: OBJECT:
1421: -------
1422: clnpNetToMediaHoldTime { clnpNetToMediaEntry 6 }
1423:
1424: Syntax:
1425: INTEGER
1426:
1427: Definition:
1428: The time in seconds this entry will be valid. Static
1429: entries should always report this field as -1.
1430:
1431: Access:
1432: read-write.
1433:
1434: Status:
1435: mandatory.
1436:
1437:
1438: OBJECT:
1439: -------
1440: clnpMediaToNetTable { clnp 24 }
1441:
1442: Syntax:
1443: SEQUENCE OF ClnpMediaToNetEntry
1444:
1445: Definition:
1446: The CLNP Address Translation table used for mapping from
1447: physical addresses to CLNP addresses.
1448:
1449: Access:
1450: not-accessible.
1451:
1452: Status:
1453: mandatory.
1454:
1455:
1456:
1457:
1458: Satz [Page 26]
1459:
1460: RFC 1162 CLNS MIB June 1990
1461:
1462:
1463: OBJECT:
1464: -------
1465: clnpMediaToNetEntry { clnpMediaToNetTable 1 }
1466:
1467: Syntax:
1468: ClnpMediaToNetEntry ::= SEQUENCE {
1469: clnpMediaToNetIfIndex
1470: INTEGER,
1471: clnpMediaToNetNetAddress
1472: ClnpAddress,
1473: clnpMediaToNetPhysAddress
1474: OCTET STRING,
1475: clnpMediaToNetType
1476: INTEGER,
1477: clnpMediaToNetAge
1478: INTEGER,
1479: clnpMediaToNetHoldTime
1480: INTEGER
1481: }
1482:
1483: Definition:
1484: Each entry contains on ClnpAddress to "physical" address
1485: equivalence.
1486:
1487: Access:
1488: not-accessible.
1489:
1490: Status:
1491: mandatory.
1492:
1493:
1494: OBJECT:
1495: -------
1496: clnpMediaToNetIfIndex { clnpMediaToNetEntry 1 }
1497:
1498: Syntax:
1499: INTEGER
1500:
1501: Definition:
1502: The interface on which this entry's equivalence is
1503: effective. The interface identified by a particular
1504: value of this index is the same interface as identified
1505: by the same value of ifIndex.
1506:
1507: Access:
1508: read-write.
1509:
1510:
1511:
1512:
1513:
1514: Satz [Page 27]
1515:
1516: RFC 1162 CLNS MIB June 1990
1517:
1518:
1519: Status:
1520: mandatory.
1521:
1522:
1523: OBJECT:
1524: -------
1525: clnpMediaToNetAddress { clnpMediaToNetEntry 2 }
1526:
1527: Syntax:
1528: ClnpAddress
1529:
1530: Definition:
1531: The ClnpAddress corresponding to the media-dependent
1532: "physical" address.
1533:
1534: Access:
1535: read-write.
1536:
1537: Status:
1538: mandatory.
1539:
1540:
1541: OBJECT:
1542: -------
1543: clnpMediaToNetPhysAddress { clnpMediaToNetEntry 3 }
1544:
1545: Syntax:
1546: OCTET STRING
1547:
1548: Definition:
1549: The media-dependent "physical" address.
1550:
1551: Access:
1552: read-write.
1553:
1554: Status:
1555: mandatory.
1556:
1557:
1558: OBJECT:
1559: -------
1560: clnpMediaToNetType { clnpMediaToNetEntry 4 }
1561:
1562: Syntax:
1563: INTEGER {
1564: other(1), -- none of the following
1565: invalid(2), -- an invalidated mapping
1566: dynamic(3),
1567:
1568:
1569:
1570: Satz [Page 28]
1571:
1572: RFC 1162 CLNS MIB June 1990
1573:
1574:
1575: static(4)
1576: }
1577:
1578: Definition:
1579: The type of mapping.
1580:
1581: Setting this object to the value invalid(2) has the effect of
1582: invalidating the corresponding entry in the
1583: clnpMediaToNetTable. That is, it effectively dissassociates
1584: the interface identified with said entry from the mapping
1585: identified with said entry. It is an implementation-specific
1586: matter as to whether the agent removes an invalidated entry
1587: from the table. Accordingly, management stations must be
1588: prepared to receive tabular information from agents that
1589: corresponds to entries not currently in use. Proper
1590: interpretation of such entries requires examination of the
1591: relevant clnpMediaToNetType object.
1592:
1593: Access:
1594: read-write.
1595:
1596: Status:
1597: mandatory.
1598:
1599:
1600: OBJECT:
1601: -------
1602: clnpMediaToNetAge { clnpMediaToNetEntry 5 }
1603:
1604: Syntax:
1605: INTEGER
1606:
1607: Definition:
1608: The number of seconds since this entry was last updated
1609: or otherwise determined to be correct. Note that no
1610: semantics of "too old" can be implied except through
1611: knowledge of the type of entry.
1612:
1613: Access:
1614: read-write.
1615:
1616: Status:
1617: mandatory.
1618:
1619:
1620: OBJECT:
1621: -------
1622: clnpMediaToNetHoldTime { clnpMediaToNetEntry 6 }
1623:
1624:
1625:
1626: Satz [Page 29]
1627:
1628: RFC 1162 CLNS MIB June 1990
1629:
1630:
1631: Syntax:
1632: INTEGER
1633:
1634: Definition:
1635: The time in seconds this entry will be valid. Static
1636: entries should always report this field as -1.
1637:
1638: Access:
1639: read-write.
1640:
1641: Status:
1642: mandatory.
1643:
1644: 4.2. The CLNP Error Group
1645:
1646: This group records the CLNP Error protocol and is recommended for all
1647: systems which support CLNP.
1648:
1649:
1650: OBJECT:
1651: -------
1652: clnpInErrors { error 1 }
1653:
1654: Syntax:
1655: Counter
1656:
1657: Definition:
1658: The number of CLNP Error PDUs received by this entity.
1659:
1660: Access:
1661: read-only.
1662:
1663: Status:
1664: mandatory.
1665:
1666:
1667: OBJECT:
1668: -------
1669: clnpOutErrors { error 2 }
1670:
1671: Syntax:
1672: Counter
1673:
1674: Definition:
1675: The number of CLNP Error PDUs sent by this entity.
1676:
1677: Access:
1678: read-only.
1679:
1680:
1681:
1682: Satz [Page 30]
1683:
1684: RFC 1162 CLNS MIB June 1990
1685:
1686:
1687: Status:
1688: mandatory.
1689:
1690:
1691: OBJECT:
1692: -------
1693: clnpInErrUnspecs { error 3 }
1694:
1695: Syntax:
1696: Counter
1697:
1698: Definition:
1699: The number of unspecified CLNP Error PDUs received by
1700: this entity.
1701:
1702: Access:
1703: read-only.
1704:
1705: Status:
1706: mandatory.
1707:
1708:
1709: OBJECT:
1710: -------
1711: clnpInErrProcs { error 4 }
1712:
1713: Syntax:
1714: Counter
1715:
1716: Definition:
1717: The number of protocol procedure CLNP Error PDUs received
1718: by this entity.
1719:
1720: Access:
1721: read-only.
1722:
1723: Status:
1724: mandatory.
1725:
1726:
1727: OBJECT:
1728: -------
1729: clnpInErrCksums { error 5 }
1730:
1731: Syntax:
1732: Counter
1733:
1734:
1735:
1736:
1737:
1738: Satz [Page 31]
1739:
1740: RFC 1162 CLNS MIB June 1990
1741:
1742:
1743: Definition:
1744: The number of checksum CLNP Error PDUs received by this
1745: entity.
1746:
1747: Access:
1748: read-only.
1749:
1750: Status:
1751: mandatory.
1752:
1753:
1754: OBJECT:
1755: -------
1756: clnpInErrCongests { error 6 }
1757:
1758: Syntax:
1759: Counter
1760:
1761: Definition:
1762: The number of congestion drop CLNP Error PDUs received by
1763: this entity.
1764:
1765: Access:
1766: read-only.
1767:
1768: Status:
1769: mandatory.
1770:
1771:
1772: OBJECT:
1773: -------
1774: clnpInErrHdrs { error 7 }
1775:
1776: Syntax:
1777: Counter
1778:
1779: Definition:
1780: The number of header syntax CLNP Error PDUs received by
1781: this entity.
1782:
1783: Access:
1784: read-only.
1785:
1786: Status:
1787: mandatory.
1788:
1789:
1790:
1791:
1792:
1793:
1794: Satz [Page 32]
1795:
1796: RFC 1162 CLNS MIB June 1990
1797:
1798:
1799: OBJECT:
1800: -------
1801: clnpInErrSegs { error 8 }
1802:
1803: Syntax:
1804: Counter
1805:
1806: Definition:
1807: The number of segmentation disallowed CLNP Error PDUs
1808: received by this entity.
1809:
1810: Access:
1811: read-only.
1812:
1813: Status:
1814: mandatory.
1815:
1816:
1817: OBJECT:
1818: -------
1819: clnpInErrIncomps { error 9 }
1820:
1821: Syntax:
1822: Counter
1823:
1824: Definition:
1825: The number of incomplete PDU CLNP Error PDUs received by
1826: this entity.
1827:
1828: Access:
1829: read-only.
1830:
1831: Status:
1832: mandatory.
1833:
1834:
1835: OBJECT:
1836: -------
1837: clnpInErrDups { error 10 }
1838:
1839: Syntax:
1840: Counter
1841:
1842: Definition:
1843: The number of duplicate option CLNP Error PDUs received
1844: by this entity.
1845:
1846:
1847:
1848:
1849:
1850: Satz [Page 33]
1851:
1852: RFC 1162 CLNS MIB June 1990
1853:
1854:
1855: Access:
1856: read-only.
1857:
1858: Status:
1859: mandatory.
1860:
1861:
1862: OBJECT:
1863: -------
1864: clnpInErrUnreachDsts { error 11 }
1865:
1866: Syntax:
1867: Counter
1868:
1869: Definition:
1870: The number of unreachable destination CLNP Error PDUs
1871: received by this entity.
1872:
1873: Access:
1874: read-only.
1875:
1876: Status:
1877: mandatory.
1878:
1879:
1880: OBJECT:
1881: -------
1882: clnpInErrUnknownDsts { error 12 }
1883:
1884: Syntax:
1885: Counter
1886:
1887: Definition:
1888: The number of unknown destination CLNP Error PDUs
1889: received by this entity.
1890:
1891: Access:
1892: read-only.
1893:
1894: Status:
1895: mandatory.
1896:
1897:
1898: OBJECT:
1899: -------
1900: clnpInErrSRUnspecs { error 13 }
1901:
1902:
1903:
1904:
1905:
1906: Satz [Page 34]
1907:
1908: RFC 1162 CLNS MIB June 1990
1909:
1910:
1911: Syntax:
1912: Counter
1913:
1914: Definition:
1915: The number of unspecified source route CLNP Error PDUs
1916: received by this entity.
1917:
1918: Access:
1919: read-only.
1920:
1921: Status:
1922: mandatory.
1923:
1924:
1925: OBJECT:
1926: -------
1927: clnpInErrSRSyntaxes { error 14 }
1928:
1929: Syntax:
1930: Counter
1931:
1932: Definition:
1933: The number of source route syntax CLNP Error PDUs
1934: received by this entity.
1935:
1936: Access:
1937: read-only.
1938:
1939: Status:
1940: mandatory.
1941:
1942:
1943: OBJECT:
1944: -------
1945: clnpInErrSRUnkAddrs { error 15 }
1946:
1947: Syntax:
1948: Counter
1949:
1950: Definition:
1951: The number of source route unknown address CLNP Error
1952: PDUs received by this entity.
1953:
1954: Access:
1955: read-only.
1956:
1957: Status:
1958: mandatory.
1959:
1960:
1961:
1962: Satz [Page 35]
1963:
1964: RFC 1162 CLNS MIB June 1990
1965:
1966:
1967: OBJECT:
1968: -------
1969: clnpInErrSRBadPaths { error 16 }
1970:
1971: Syntax:
1972: Counter
1973:
1974: Definition:
1975: The number of source route bad path CLNP Error PDUs
1976: received by this entity.
1977:
1978: Access:
1979: read-only.
1980:
1981: Status:
1982: mandatory.
1983:
1984:
1985: OBJECT:
1986: -------
1987: clnpInErrHops { error 17 }
1988:
1989: Syntax:
1990: Counter
1991:
1992: Definition:
1993: The number of hop count exceeded CLNP Error PDUs received
1994: by this entity.
1995:
1996: Access:
1997: read-only.
1998:
1999: Status:
2000: mandatory.
2001:
2002:
2003: OBJECT:
2004: -------
2005: clnpInErrHopReassms { error 18 }
2006:
2007: Syntax:
2008: Counter
2009:
2010: Definition:
2011: The number of hop count exceeded while reassembling CLNP
2012: Error PDUs received by this entity.
2013:
2014:
2015:
2016:
2017:
2018: Satz [Page 36]
2019:
2020: RFC 1162 CLNS MIB June 1990
2021:
2022:
2023: Access:
2024: read-only.
2025:
2026: Status:
2027: mandatory.
2028:
2029:
2030: OBJECT:
2031: -------
2032: clnpInErrUnsOptions { error 19 }
2033:
2034: Syntax:
2035: Counter
2036:
2037: Definition:
2038: The number of unsupported option CLNP Error PDUs received
2039: by this entity.
2040:
2041: Access:
2042: read-only.
2043:
2044: Status:
2045: mandatory.
2046:
2047:
2048: OBJECT:
2049: -------
2050: clnpInErrUnsVersions { error 20 }
2051:
2052: Syntax:
2053: Counter
2054:
2055: Definition:
2056: The number of version mismatch CLNP Error PDUs received
2057: by this entity.
2058:
2059: Access:
2060: read-only.
2061:
2062: Status:
2063: mandatory.
2064:
2065:
2066: OBJECT:
2067: -------
2068: clnpInErrUnsSecurities { error 21 }
2069:
2070:
2071:
2072:
2073:
2074: Satz [Page 37]
2075:
2076: RFC 1162 CLNS MIB June 1990
2077:
2078:
2079: Syntax:
2080: Counter
2081:
2082: Definition:
2083: The number of unsupported security option CLNP Error PDUs
2084: received by this entity.
2085:
2086: Access:
2087: read-only.
2088:
2089: Status:
2090: mandatory.
2091:
2092:
2093: OBJECT:
2094: -------
2095: clnpInErrUnsSRs { error 22 }
2096:
2097: Syntax:
2098: Counter
2099:
2100: Definition:
2101: The number of unsupported source route option CLNP Error
2102: PDUs received by this entity.
2103:
2104: Access:
2105: read-only.
2106:
2107: Status:
2108: mandatory.
2109:
2110:
2111: OBJECT:
2112: -------
2113: clnpInErrUnsRRs { error 23 }
2114:
2115: Syntax:
2116: Counter
2117:
2118: Definition:
2119: The number of unsupported record route option CLNP Error
2120: PDUs received by this entity.
2121:
2122: Access:
2123: read-only.
2124:
2125: Status:
2126: mandatory.
2127:
2128:
2129:
2130: Satz [Page 38]
2131:
2132: RFC 1162 CLNS MIB June 1990
2133:
2134:
2135: OBJECT:
2136: -------
2137: clnpInErrInterferences { error 24 }
2138:
2139: Syntax:
2140: Counter
2141:
2142: Definition:
2143: The number of reassembly interference CLNP Error PDUs
2144: received by this entity.
2145:
2146: Access:
2147: read-only.
2148:
2149: Status:
2150: mandatory.
2151:
2152:
2153: OBJECT:
2154: -------
2155: clnpOutErrUnspecs { error 25 }
2156:
2157: Syntax:
2158: Counter
2159:
2160: Definition:
2161: The number of unspecified CLNP Error PDUs sent by this
2162: entity.
2163:
2164: Access:
2165: read-only.
2166:
2167: Status:
2168: mandatory.
2169:
2170:
2171: OBJECT:
2172: -------
2173: clnpOutErrProcs { error 26 }
2174:
2175: Syntax:
2176: Counter
2177:
2178: Definition:
2179: The number of protocol procedure CLNP Error PDUs sent by
2180: this entity.
2181:
2182:
2183:
2184:
2185:
2186: Satz [Page 39]
2187:
2188: RFC 1162 CLNS MIB June 1990
2189:
2190:
2191: Access:
2192: read-only.
2193:
2194: Status:
2195: mandatory.
2196:
2197:
2198: OBJECT:
2199: -------
2200: clnpOutErrCksums { error 27 }
2201:
2202: Syntax:
2203: Counter
2204:
2205: Definition:
2206: The number of checksum CLNP Error PDUs sent by this
2207: entity.
2208:
2209: Access:
2210: read-only.
2211:
2212: Status:
2213: mandatory.
2214:
2215:
2216: OBJECT:
2217: -------
2218: clnpOutErrCongests { error 28 }
2219:
2220: Syntax:
2221: Counter
2222:
2223: Definition:
2224: The number of congestion drop CLNP Error PDUs sent by
2225: this entity.
2226:
2227: Access:
2228: read-only.
2229:
2230: Status:
2231: mandatory.
2232:
2233:
2234: OBJECT:
2235: -------
2236: clnpOutErrHdrs { error 29 }
2237:
2238:
2239:
2240:
2241:
2242: Satz [Page 40]
2243:
2244: RFC 1162 CLNS MIB June 1990
2245:
2246:
2247: Syntax:
2248: Counter
2249:
2250: Definition:
2251: The number of header syntax CLNP Error PDUs sent by this
2252: entity.
2253:
2254: Access:
2255: read-only.
2256:
2257: Status:
2258: mandatory.
2259:
2260:
2261: OBJECT:
2262: -------
2263: clnpOutErrSegs { error 30 }
2264:
2265: Syntax:
2266: Counter
2267:
2268: Definition:
2269: The number of segmentation disallowed CLNP Error PDUs
2270: sent by this entity.
2271:
2272: Access:
2273: read-only.
2274:
2275: Status:
2276: mandatory.
2277:
2278:
2279: OBJECT:
2280: -------
2281: clnpOutErrIncomps { error 31 }
2282:
2283: Syntax:
2284: Counter
2285:
2286: Definition:
2287: The number of incomplete PDU CLNP Error PDUs sent by this
2288: entity.
2289:
2290: Access:
2291: read-only.
2292:
2293: Status:
2294: mandatory.
2295:
2296:
2297:
2298: Satz [Page 41]
2299:
2300: RFC 1162 CLNS MIB June 1990
2301:
2302:
2303: OBJECT:
2304: -------
2305: clnpOutErrDups { error 32 }
2306:
2307: Syntax:
2308: Counter
2309:
2310: Definition:
2311: The number of duplicate option CLNP Error PDUs sent by
2312: this entity.
2313:
2314: Access:
2315: read-only.
2316:
2317: Status:
2318: mandatory.
2319:
2320:
2321: OBJECT:
2322: -------
2323: clnpOutErrUnreachDsts { error 33 }
2324:
2325: Syntax:
2326: Counter
2327:
2328: Definition:
2329: The number of unreachable destination CLNP Error PDUs
2330: sent by this entity.
2331:
2332: Access:
2333: read-only.
2334:
2335: Status:
2336: mandatory.
2337:
2338:
2339: OBJECT:
2340: -------
2341: clnpOutErrUnknownDsts { error 34 }
2342:
2343: Syntax:
2344: Counter
2345:
2346: Definition:
2347: The number of unknown destination CLNP Error PDUs sent by
2348: this entity.
2349:
2350:
2351:
2352:
2353:
2354: Satz [Page 42]
2355:
2356: RFC 1162 CLNS MIB June 1990
2357:
2358:
2359: Access:
2360: read-only.
2361:
2362: Status:
2363: mandatory.
2364:
2365:
2366: OBJECT:
2367: -------
2368: clnpOutErrSRUnspecs { error 35 }
2369:
2370: Syntax:
2371: Counter
2372:
2373: Definition:
2374: The number of unspecified source route CLNP Error PDUs
2375: sent by this entity.
2376:
2377: Access:
2378: read-only.
2379:
2380: Status:
2381: mandatory.
2382:
2383:
2384: OBJECT:
2385: -------
2386: clnpOutErrSRSyntaxes { error 36 }
2387:
2388: Syntax:
2389: Counter
2390:
2391: Definition:
2392: The number of source route syntax CLNP Error PDUs sent by
2393: this entity.
2394:
2395: Access:
2396: read-only.
2397:
2398: Status:
2399: mandatory.
2400:
2401:
2402: OBJECT:
2403: -------
2404: clnpOutErrSRUnkAddrs { error 37 }
2405:
2406:
2407:
2408:
2409:
2410: Satz [Page 43]
2411:
2412: RFC 1162 CLNS MIB June 1990
2413:
2414:
2415: Syntax:
2416: Counter
2417:
2418: Definition:
2419: The number of source route unknown address CLNP Error
2420: PDUs sent by this entity.
2421:
2422: Access:
2423: read-only.
2424:
2425: Status:
2426: mandatory.
2427:
2428:
2429: OBJECT:
2430: -------
2431: clnpOutErrSRBadPaths { error 38 }
2432:
2433: Syntax:
2434: Counter
2435:
2436: Definition:
2437: The number of source route bad path CLNP Error PDUs sent
2438: by this entity.
2439:
2440: Access:
2441: read-only.
2442:
2443: Status:
2444: mandatory.
2445:
2446:
2447: OBJECT:
2448: -------
2449: clnpOutErrHopss { error 39 }
2450:
2451: Syntax:
2452: Counter
2453:
2454: Definition:
2455: The number of hop count exceeded CLNP Error PDUs sent by
2456: this entity.
2457:
2458: Access:
2459: read-only.
2460:
2461: Status:
2462: mandatory.
2463:
2464:
2465:
2466: Satz [Page 44]
2467:
2468: RFC 1162 CLNS MIB June 1990
2469:
2470:
2471: OBJECT:
2472: -------
2473: clnpOutErrHopReassms { error 40 }
2474:
2475: Syntax:
2476: Counter
2477:
2478: Definition:
2479: The number of hop count exceeded while reassembling CLNP
2480: Error PDUs sent by this entity.
2481:
2482: Access:
2483: read-only.
2484:
2485: Status:
2486: mandatory.
2487:
2488:
2489: OBJECT:
2490: -------
2491: clnpOutErrUnsOptions { error 41 }
2492:
2493: Syntax:
2494: Counter
2495:
2496: Definition:
2497: The number of unsupported option CLNP Error PDUs sent by
2498: this entity.
2499:
2500: Access:
2501: read-only.
2502:
2503: Status:
2504: mandatory.
2505:
2506:
2507: OBJECT:
2508: -------
2509: clnpOutErrUnsVersions { error 42 }
2510:
2511: Syntax:
2512: Counter
2513:
2514: Definition:
2515: The number of version mismatch CLNP Error PDUs sent by
2516: this entity.
2517:
2518:
2519:
2520:
2521:
2522: Satz [Page 45]
2523:
2524: RFC 1162 CLNS MIB June 1990
2525:
2526:
2527: Access:
2528: read-only.
2529:
2530: Status:
2531: mandatory.
2532:
2533:
2534: OBJECT:
2535: -------
2536: clnpOutErrUnsSecurities { error 43 }
2537:
2538: Syntax:
2539: Counter
2540:
2541: Definition:
2542: The number of unsupported security option CLNP Error PDUs
2543: sent by this entity.
2544:
2545: Access:
2546: read-only.
2547:
2548: Status:
2549: mandatory.
2550:
2551:
2552: OBJECT:
2553: -------
2554: clnpOutErrUnsSRs { error 44 }
2555:
2556: Syntax:
2557: Counter
2558:
2559: Definition:
2560: The number of unsupported source route option CLNP Error
2561: PDUs sent by this entity.
2562:
2563: Access:
2564: read-only.
2565:
2566: Status:
2567: mandatory.
2568:
2569:
2570: OBJECT:
2571: -------
2572: clnpOutErrUnsRRs { error 45 }
2573:
2574:
2575:
2576:
2577:
2578: Satz [Page 46]
2579:
2580: RFC 1162 CLNS MIB June 1990
2581:
2582:
2583: Syntax:
2584: Counter
2585:
2586: Definition:
2587: The number of unsupported record route option CLNP Error
2588: PDUs sent by this entity.
2589:
2590: Access:
2591: read-only.
2592:
2593: Status:
2594: mandatory.
2595:
2596:
2597: OBJECT:
2598: -------
2599: clnpOutErrInterferences { error 46 }
2600:
2601: Syntax:
2602: Counter
2603:
2604: Definition:
2605: The number of reassembly interference CLNP Error PDUs
2606: sent by this entity.
2607:
2608: Access:
2609: read-only.
2610:
2611: Status:
2612: mandatory.
2613:
2614: 4.3. The ESIS Group
2615:
2616: The ESIS group contains information about the End System Intermediate
2617: System protocol used to maintain neighbor reachibility information.
2618: Both ESs and ISs are expected to implement this group if they running
2619: a CLNP.
2620:
2621:
2622: OBJECT:
2623: -------
2624: esisESHin { es-is 1 }
2625:
2626: Syntax:
2627: Counter
2628:
2629: Definition:
2630: The number of ESH PDUs received by this entity.
2631:
2632:
2633:
2634: Satz [Page 47]
2635:
2636: RFC 1162 CLNS MIB June 1990
2637:
2638:
2639: Access:
2640: read-only.
2641:
2642: Status:
2643: mandatory.
2644:
2645:
2646: OBJECT:
2647: -------
2648: esisESHout { es-is 2 }
2649:
2650: Syntax:
2651: Counter
2652:
2653: Definition:
2654: The number of ESH PDUs sent by this entity.
2655:
2656: Access:
2657: read-only.
2658:
2659: Status:
2660: mandatory.
2661:
2662:
2663: OBJECT:
2664: -------
2665: esisISHin { es-is 3 }
2666:
2667: Syntax:
2668: Counter
2669:
2670: Definition:
2671: The number of ISH PDUs received by this entity.
2672:
2673: Access:
2674: read-only.
2675:
2676: Status:
2677: mandatory.
2678:
2679:
2680: OBJECT:
2681: -------
2682: esisISHout { es-is 4 }
2683:
2684: Syntax:
2685: Counter
2686:
2687:
2688:
2689:
2690: Satz [Page 48]
2691:
2692: RFC 1162 CLNS MIB June 1990
2693:
2694:
2695: Definition:
2696: The number of ISH PDUs sent by this entity.
2697:
2698: Access:
2699: read-only.
2700:
2701: Status:
2702: mandatory.
2703:
2704:
2705: OBJECT:
2706: -------
2707: esisRDUin { es-is 5 }
2708:
2709: Syntax:
2710: Counter
2711:
2712: Definition:
2713: The number of RDU PDUs received by this entity.
2714:
2715: Access:
2716: read-only.
2717:
2718: Status:
2719: mandatory.
2720:
2721:
2722: OBJECT:
2723: -------
2724: esisRDUout { es-is 6 }
2725:
2726: Syntax:
2727: Counter
2728:
2729: Definition:
2730: The number of RDU PDUs sent by this entity.
2731:
2732: Access:
2733: read-only.
2734:
2735: Status:
2736: mandatory.
2737:
2738:
2739:
2740:
2741:
2742:
2743:
2744:
2745:
2746: Satz [Page 49]
2747:
2748: RFC 1162 CLNS MIB June 1990
2749:
2750:
2751: 5. Definitions
2752:
2753: CLNS-MIB DEFINITIONS ::= BEGIN
2754:
2755: IMPORTS
2756: experimental, OBJECT-TYPE, Counter
2757: FROM RFC1155-SMI;
2758:
2759: -- new type of NetworkAddress
2760:
2761: ClnpAddress ::=
2762: [APPLICATION 5]
2763: IMPLICIT OCTET STRING (SIZE (1..21))
2764:
2765:
2766: clns OBJECT IDENTIFIER ::= { experimental 1 }
2767:
2768: clnp OBJECT IDENTIFIER ::= { clns 1 }
2769: error OBJECT IDENTIFIER ::= { clns 2 }
2770: echo OBJECT IDENTIFIER ::= { clns 3 }
2771: es-is OBJECT IDENTIFIER ::= { clns 4 }
2772:
2773:
2774: -- the General CLNP group
2775:
2776: clnpForwarding OBJECT-TYPE
2777: SYNTAX INTEGER {
2778: is(1), -- entity is an
2779: -- intermediate system
2780: es(2) -- entity is an end system
2781: -- and does not forward pdus
2782: }
2783: ACCESS read-write
2784: STATUS mandatory
2785: ::= { clnp 1 }
2786:
2787: clnpDefaultLifeTime OBJECT-TYPE
2788: SYNTAX INTEGER
2789: ACCESS read-write
2790: STATUS mandatory
2791: ::= { clnp 2 }
2792:
2793: clnpInReceives OBJECT-TYPE
2794: SYNTAX Counter
2795: ACCESS read-only
2796: STATUS mandatory
2797: ::= { clnp 3 }
2798:
2799:
2800:
2801:
2802: Satz [Page 50]
2803:
2804: RFC 1162 CLNS MIB June 1990
2805:
2806:
2807: clnpInHdrErrors OBJECT-TYPE
2808: SYNTAX Counter
2809: ACCESS read-only
2810: STATUS mandatory
2811: ::= { clnp 4 }
2812:
2813: clnpInAddrErrors OBJECT-TYPE
2814: SYNTAX Counter
2815: ACCESS read-only
2816: STATUS mandatory
2817: ::= { clnp 5 }
2818:
2819: clnpForwPDUs OBJECT-TYPE
2820: SYNTAX Counter
2821: ACCESS read-only
2822: STATUS mandatory
2823: ::= { clnp 6 }
2824:
2825: clnpInUnknownNLPs OBJECT-TYPE
2826: SYNTAX Counter
2827: ACCESS read-only
2828: STATUS mandatory
2829: ::= { clnp 7 }
2830:
2831: clnpInUnknownULPs OBJECT-TYPE
2832: SYNTAX Counter
2833: ACCESS read-only
2834: STATUS mandatory
2835: ::= { clnp 8 }
2836:
2837: clnpInDiscards OBJECT-TYPE
2838: SYNTAX Counter
2839: ACCESS read-only
2840: STATUS mandatory
2841: ::= { clnp 9 }
2842:
2843: clnpInDelivers OBJECT-TYPE
2844: SYNTAX Counter
2845: ACCESS read-only
2846: STATUS mandatory
2847: ::= { clnp 10 }
2848:
2849: clnpOutRequests OBJECT-TYPE
2850: SYNTAX Counter
2851: ACCESS read-only
2852: STATUS mandatory
2853: ::= { clnp 11 }
2854:
2855:
2856:
2857:
2858: Satz [Page 51]
2859:
2860: RFC 1162 CLNS MIB June 1990
2861:
2862:
2863: clnpOutDiscards OBJECT-TYPE
2864: SYNTAX Counter
2865: ACCESS read-only
2866: STATUS mandatory
2867: ::= { clnp 12 }
2868:
2869: clnpOutNoRoutes OBJECT-TYPE
2870: SYNTAX Counter
2871: ACCESS read-only
2872: STATUS mandatory
2873: ::= { clnp 13 }
2874:
2875: clnpReasmTimeout OBJECT-TYPE
2876: SYNTAX INTEGER
2877: ACCESS read-only
2878: STATUS mandatory
2879: ::= { clnp 14 }
2880:
2881: clnpReasmReqds OBJECT-TYPE
2882: SYNTAX Counter
2883: ACCESS read-only
2884: STATUS mandatory
2885: ::= { clnp 15 }
2886:
2887: clnpReasmOKs OBJECT-TYPE
2888: SYNTAX Counter
2889: ACCESS read-only
2890: STATUS mandatory
2891: ::= { clnp 16 }
2892:
2893: clnpReasmFails OBJECT-TYPE
2894: SYNTAX Counter
2895: ACCESS read-only
2896: STATUS mandatory
2897: ::= { clnp 17 }
2898:
2899: clnpSegOKs OBJECT-TYPE
2900: SYNTAX Counter
2901: ACCESS read-only
2902: STATUS mandatory
2903: ::= { clnp 18 }
2904:
2905: clnpSegFails OBJECT-TYPE
2906: SYNTAX Counter
2907: ACCESS read-only
2908: STATUS mandatory
2909: ::= { clnp 19 }
2910:
2911:
2912:
2913:
2914: Satz [Page 52]
2915:
2916: RFC 1162 CLNS MIB June 1990
2917:
2918:
2919: clnpSegCreates OBJECT-TYPE
2920: SYNTAX Counter
2921: ACCESS read-only
2922: STATUS mandatory
2923: ::= { clnp 20 }
2924:
2925: clnpInOpts OBJECT-TYPE
2926: SYNTAX Counter
2927: ACCESS read-only
2928: STATUS mandatory
2929: ::= { clnp 25 }
2930:
2931: clnpOutOpts OBJECT-TYPE
2932: SYNTAX Counter
2933: ACCESS read-only
2934: STATUS mandatory
2935: ::= { clnp 26 }
2936:
2937: -- the CLNP Interface table
2938:
2939: clnpAddrTable OBJECT-TYPE
2940: SYNTAX SEQUENCE OF ClnpAddrEntry
2941: ACCESS not-accessible
2942: STATUS mandatory
2943: ::= { clnp 21 }
2944:
2945: clnpAddrEntry OBJECT-TYPE
2946: SYNTAX ClnpAddrEntry
2947: ACCESS not-accessible
2948: STATUS mandatory
2949: -- INDEX { clnpAdEntAddr }
2950: ::= { clnpAddrTable 1 }
2951:
2952: ClnpAddrEntry ::= SEQUENCE {
2953: clnpAdEntAddr
2954: ClnpAddress,
2955: clnpAdEntIfIndex
2956: INTEGER,
2957: clnpAdEntReasmMaxSize
2958: INTEGER (0..65535)
2959: }
2960:
2961: clnpAdEntAddr OBJECT-TYPE
2962: SYNTAX ClnpAddress
2963: ACCESS read-only
2964: STATUS mandatory
2965: ::= { clnpAddrEntry 1 }
2966:
2967:
2968:
2969:
2970: Satz [Page 53]
2971:
2972: RFC 1162 CLNS MIB June 1990
2973:
2974:
2975: clnpAdEntIfIndex OBJECT-TYPE
2976: SYNTAX INTEGER
2977: ACCESS read-only
2978: STATUS mandatory
2979: ::= { clnpAddrEntry 2 }
2980:
2981: clnpAdEntReasmMaxSize OBJECT-TYPE
2982: SYNTAX INTEGER (0..65535)
2983: ACCESS read-only
2984: STATUS mandatory
2985: ::= { clnpAddrEntry 3 }
2986:
2987: -- the CLNP Routing table
2988:
2989: clnpRoutingTable OBJECT-TYPE
2990: SYNTAX SEQUENCE OF ClnpRouteEntry
2991: ACCESS not-accessible
2992: STATUS mandatory
2993: ::= { clnp 22 }
2994:
2995: clnpRouteEntry OBJECT-TYPE
2996: SYNTAX ClnpRouteEntry
2997: ACCESS not-accessible
2998: STATUS mandatory
2999: -- INDEX { clnpRouteDest }
3000: ::= { clnpRoutingTable 1 }
3001:
3002: ClnpRouteEntry ::= SEQUENCE {
3003: clnpRouteDest
3004: ClnpAddress,
3005: clnpRouteIfIndex
3006: INTEGER,
3007: clnpRouteMetric1
3008: INTEGER,
3009: clnpRouteMetric2
3010: INTEGER,
3011: clnpRouteMetric3
3012: INTEGER,
3013: clnpRouteMetric4
3014: INTEGER,
3015: clnpRouteNextHop
3016: ClnpAddress,
3017: clnpRouteType
3018: INTEGER,
3019: clnpRouteProto
3020: INTEGER,
3021: clnpRouteAge
3022: INTEGER
3023:
3024:
3025:
3026: Satz [Page 54]
3027:
3028: RFC 1162 CLNS MIB June 1990
3029:
3030:
3031: }
3032:
3033: clnpRouteDest OBJECT-TYPE
3034: SYNTAX ClnpAddress
3035: ACCESS read-write
3036: STATUS mandatory
3037: ::= { clnpRouteEntry 1 }
3038:
3039: clnpRouteIfIndex OBJECT-TYPE
3040: SYNTAX INTEGER
3041: ACCESS read-write
3042: STATUS mandatory
3043: ::= { clnpRouteEntry 2 }
3044:
3045: clnpRouteMetric1 OBJECT-TYPE
3046: SYNTAX INTEGER
3047: ACCESS read-write
3048: STATUS mandatory
3049: ::= { clnpRouteEntry 3 }
3050:
3051: clnpRouteMetric2 OBJECT-TYPE
3052: SYNTAX INTEGER
3053: ACCESS read-write
3054: STATUS mandatory
3055: ::= { clnpRouteEntry 4 }
3056:
3057: clnpRouteMetric3 OBJECT-TYPE
3058: SYNTAX INTEGER
3059: ACCESS read-write
3060: STATUS mandatory
3061: ::= { clnpRouteEntry 5 }
3062:
3063: clnpRouteMetric4 OBJECT-TYPE
3064: SYNTAX INTEGER
3065: ACCESS read-write
3066: STATUS mandatory
3067: ::= { clnpRouteEntry 6 }
3068:
3069: clnpRouteNextHop OBJECT-TYPE
3070: SYNTAX ClnpAddress
3071: ACCESS read-write
3072: STATUS mandatory
3073: ::= { clnpRouteEntry 7 }
3074:
3075: clnpRouteType OBJECT-TYPE
3076: SYNTAX INTEGER {
3077: other(1), -- none of the
3078: -- following
3079:
3080:
3081:
3082: Satz [Page 55]
3083:
3084: RFC 1162 CLNS MIB June 1990
3085:
3086:
3087: invalid(2), -- an invalidated
3088: -- route
3089:
3090: -- route to directly
3091: direct(3), -- connected
3092: -- (sub-)network
3093:
3094: -- route to a
3095: -- non-local
3096: remote(4) -- host/network
3097: -- /sub-network
3098: }
3099: ACCESS read-write
3100: STATUS mandatory
3101: ::= { clnpRouteEntry 8 }
3102:
3103: clnpRouteProto OBJECT-TYPE
3104: SYNTAX INTEGER {
3105: other(1), -- none of the
3106: -- following
3107:
3108: -- non-protocol
3109: -- information
3110: -- e.g., manually
3111: local(2), -- configured entries
3112:
3113: -- set via a network
3114: netmgmt(3), -- management
3115: -- protocol
3116:
3117: -- similar to
3118: -- ipRouteProto
3119: -- but omits several
3120: -- IP-specific
3121: -- protocols
3122: is-is(9),
3123: ciscoIgrp(11),
3124: bbnSpfIgp(12),
3125: ospf(13),
3126: bgp(14)
3127: }
3128: ACCESS read-only
3129: STATUS mandatory
3130: ::= { clnpRouteEntry 9 }
3131:
3132: clnpRouteAge OBJECT-TYPE
3133: SYNTAX INTEGER
3134: ACCESS read-write
3135:
3136:
3137:
3138: Satz [Page 56]
3139:
3140: RFC 1162 CLNS MIB June 1990
3141:
3142:
3143: STATUS mandatory
3144: ::= { clnpRouteEntry 10 }
3145:
3146: -- the CLNP Address Translation tables
3147:
3148: clnpNetToMediaTable OBJECT-TYPE
3149: SYNTAX SEQUENCE OF ClnpNetToMediaEntry
3150: ACCESS not-accessible
3151: STATUS mandatory
3152: ::= { clnp 23 }
3153:
3154: clnpNetToMediaEntry OBJECT-TYPE
3155: SYNTAX ClnpNetToMediaEntry
3156: ACCESS not-accessible
3157: STATUS mandatory
3158: -- INDEX { clnpNetToMediaIfIndex,
3159: -- clnpNetToMediaNetAddress }
3160: ::= { clnpNetToMediaTable 1 }
3161:
3162: ClnpNetToMediaEntry ::= SEQUENCE {
3163: clnpNetToMediaIfIndex
3164: INTEGER,
3165: clnpNetToMediaPhysAddress
3166: OCTET STRING,
3167: clnpNetToMediaNetAddress
3168: ClnpAddress,
3169: clnpNetToMediaType
3170: INTEGER,
3171: clnpNetToMediaAge
3172: INTEGER,
3173: clnpNetToMediaHoldTime
3174: INTEGER
3175: }
3176:
3177: clnpNetToMediaIfIndex OBJECT-TYPE
3178: SYNTAX INTEGER
3179: ACCESS read-write
3180: STATUS mandatory
3181: ::= { clnpNetToMediaEntry 1 }
3182:
3183: clnpNetToMediaPhysAddress OBJECT-TYPE
3184: SYNTAX OCTET STRING
3185: ACCESS read-write
3186: STATUS mandatory
3187: ::= { clnpNetToMediaEntry 2 }
3188:
3189: clnpNetToMediaNetAddress OBJECT-TYPE
3190: SYNTAX ClnpAddress
3191:
3192:
3193:
3194: Satz [Page 57]
3195:
3196: RFC 1162 CLNS MIB June 1990
3197:
3198:
3199: ACCESS read-write
3200: STATUS mandatory
3201: ::= { clnpNetToMediaEntry 3 }
3202:
3203: clnpNetToMediaType OBJECT-TYPE
3204: SYNTAX INTEGER {
3205: other(1), -- none of the
3206: -- following
3207: invalid(2), -- an invalidated
3208: -- mapping
3209: dynamic(3),
3210: static(4)
3211: }
3212: ACCESS read-write
3213: STATUS mandatory
3214: ::= { clnpNetToMediaEntry 4 }
3215:
3216: clnpNetToMediaAge OBJECT-TYPE
3217: SYNTAX INTEGER
3218: ACCESS read-write
3219: STATUS mandatory
3220: ::= { clnpNetToMediaEntry 5 }
3221:
3222: clnpNetToMediaHoldTime OBJECT-TYPE
3223: SYNTAX INTEGER
3224: ACCESS read-write
3225: STATUS mandatory
3226: ::= { clnpNetToMediaEntry 6 }
3227:
3228: clnpMediaToNetTable OBJECT-TYPE
3229: SYNTAX SEQUENCE OF ClnpMediaToNetEntry
3230: ACCESS not-accessible
3231: STATUS mandatory
3232: ::= { clnp 24 }
3233:
3234: clnpMediaToNetEntry OBJECT-TYPE
3235: SYNTAX ClnpMediaToNetEntry
3236: ACCESS not-accessible
3237: STATUS mandatory
3238: -- INDEX { clnpMediaToNetIfIndex,
3239: -- clnpMediaToNetPhysAddress }
3240: ::= { clnpMediaToNetTable 1 }
3241:
3242: ClnpMediaToNetEntry ::= SEQUENCE {
3243: clnpMediaToNetIfIndex
3244: INTEGER,
3245: clnpMediaToNetNetAddress
3246: ClnpAddress,
3247:
3248:
3249:
3250: Satz [Page 58]
3251:
3252: RFC 1162 CLNS MIB June 1990
3253:
3254:
3255: clnpMediaToNetPhysAddress
3256: OCTET STRING,
3257: clnpMediaToNetType
3258: INTEGER,
3259: clnpMediaToNetAge
3260: INTEGER,
3261: clnpMediaToNetHoldTime
3262: INTEGER
3263: }
3264:
3265: clnpMediaToNetIfIndex OBJECT-TYPE
3266: SYNTAX INTEGER
3267: ACCESS read-write
3268: STATUS mandatory
3269: ::= { clnpMediaToNetEntry 1 }
3270:
3271: clnpMediaToNetNetAddress OBJECT-TYPE
3272: SYNTAX ClnpAddress
3273: ACCESS read-write
3274: STATUS mandatory
3275: ::= { clnpMediaToNetEntry 2 }
3276:
3277: clnpMediaToNetPhysAddress OBJECT-TYPE
3278: SYNTAX OCTET STRING
3279: ACCESS read-write
3280: STATUS mandatory
3281: ::= { clnpMediaToNetEntry 3 }
3282:
3283: clnpMediaToNetType OBJECT-TYPE
3284: SYNTAX INTEGER {
3285: other(1), -- none of the
3286: -- following
3287: invalid(2), -- an invalidated
3288: -- mapping
3289: dynamic(3),
3290: static(4)
3291: }
3292: ACCESS read-write
3293: STATUS mandatory
3294: ::= { clnpMediaToNetEntry 4 }
3295:
3296: clnpMediaToNetAge OBJECT-TYPE
3297: SYNTAX INTEGER
3298: ACCESS read-write
3299: STATUS mandatory
3300: ::= { clnpMediaToNetEntry 5 }
3301:
3302: clnpMediaToNetHoldTime OBJECT-TYPE
3303:
3304:
3305:
3306: Satz [Page 59]
3307:
3308: RFC 1162 CLNS MIB June 1990
3309:
3310:
3311: SYNTAX INTEGER
3312: ACCESS read-write
3313: STATUS mandatory
3314: ::= { clnpMediaToNetEntry 6 }
3315:
3316: -- the CLNP Error Group
3317:
3318: clnpInErrors OBJECT-TYPE
3319: SYNTAX Counter
3320: ACCESS read-only
3321: STATUS mandatory
3322: ::= { error 1 }
3323:
3324: clnpOutErrors OBJECT-TYPE
3325: SYNTAX Counter
3326: ACCESS read-only
3327: STATUS mandatory
3328: ::= { error 2 }
3329:
3330: clnpInErrUnspecs OBJECT-TYPE
3331: SYNTAX Counter
3332: ACCESS read-only
3333: STATUS mandatory
3334: ::= { error 3 }
3335:
3336: clnpInErrProcs OBJECT-TYPE
3337: SYNTAX Counter
3338: ACCESS read-only
3339: STATUS mandatory
3340: ::= { error 4 }
3341:
3342: clnpInErrCksums OBJECT-TYPE
3343: SYNTAX Counter
3344: ACCESS read-only
3345: STATUS mandatory
3346: ::= { error 5 }
3347:
3348: clnpInErrCongests OBJECT-TYPE
3349: SYNTAX Counter
3350: ACCESS read-only
3351: STATUS mandatory
3352: ::= { error 6 }
3353:
3354: clnpInErrHdrs OBJECT-TYPE
3355: SYNTAX Counter
3356: ACCESS read-only
3357: STATUS mandatory
3358: ::= { error 7 }
3359:
3360:
3361:
3362: Satz [Page 60]
3363:
3364: RFC 1162 CLNS MIB June 1990
3365:
3366:
3367: clnpInErrSegs OBJECT-TYPE
3368: SYNTAX Counter
3369: ACCESS read-only
3370: STATUS mandatory
3371: ::= { error 8 }
3372:
3373: clnpInErrIncomps OBJECT-TYPE
3374: SYNTAX Counter
3375: ACCESS read-only
3376: STATUS mandatory
3377: ::= { error 9 }
3378:
3379: clnpInErrDups OBJECT-TYPE
3380: SYNTAX Counter
3381: ACCESS read-only
3382: STATUS mandatory
3383: ::= { error 10 }
3384:
3385: clnpInErrUnreachDsts OBJECT-TYPE
3386: SYNTAX Counter
3387: ACCESS read-only
3388: STATUS mandatory
3389: ::= { error 11 }
3390:
3391: clnpInErrUnknownDsts OBJECT-TYPE
3392: SYNTAX Counter
3393: ACCESS read-only
3394: STATUS mandatory
3395: ::= { error 12 }
3396:
3397: clnpInErrSRUnspecs OBJECT-TYPE
3398: SYNTAX Counter
3399: ACCESS read-only
3400: STATUS mandatory
3401: ::= { error 13 }
3402:
3403: clnpInErrSRSyntaxes OBJECT-TYPE
3404: SYNTAX Counter
3405: ACCESS read-only
3406: STATUS mandatory
3407: ::= { error 14 }
3408:
3409: clnpInErrSRUnkAddrs OBJECT-TYPE
3410: SYNTAX Counter
3411: ACCESS read-only
3412: STATUS mandatory
3413: ::= { error 15 }
3414:
3415:
3416:
3417:
3418: Satz [Page 61]
3419:
3420: RFC 1162 CLNS MIB June 1990
3421:
3422:
3423: clnpInErrSRBadPaths OBJECT-TYPE
3424: SYNTAX Counter
3425: ACCESS read-only
3426: STATUS mandatory
3427: ::= { error 16 }
3428:
3429: clnpInErrHops OBJECT-TYPE
3430: SYNTAX Counter
3431: ACCESS read-only
3432: STATUS mandatory
3433: ::= { error 17 }
3434:
3435: clnpInErrHopReassms OBJECT-TYPE
3436: SYNTAX Counter
3437: ACCESS read-only
3438: STATUS mandatory
3439: ::= { error 18 }
3440:
3441: clnpInErrUnsOptions OBJECT-TYPE
3442: SYNTAX Counter
3443: ACCESS read-only
3444: STATUS mandatory
3445: ::= { error 19 }
3446:
3447: clnpInErrUnsVersions OBJECT-TYPE
3448: SYNTAX Counter
3449: ACCESS read-only
3450: STATUS mandatory
3451: ::= { error 20 }
3452:
3453: clnpInErrUnsSecurities OBJECT-TYPE
3454: SYNTAX Counter
3455: ACCESS read-only
3456: STATUS mandatory
3457: ::= { error 21 }
3458:
3459: clnpInErrUnsSRs OBJECT-TYPE
3460: SYNTAX Counter
3461: ACCESS read-only
3462: STATUS mandatory
3463: ::= { error 22 }
3464:
3465: clnpInErrUnsRRs OBJECT-TYPE
3466: SYNTAX Counter
3467: ACCESS read-only
3468: STATUS mandatory
3469: ::= { error 23 }
3470:
3471:
3472:
3473:
3474: Satz [Page 62]
3475:
3476: RFC 1162 CLNS MIB June 1990
3477:
3478:
3479: clnpInErrInterferences OBJECT-TYPE
3480: SYNTAX Counter
3481: ACCESS read-only
3482: STATUS mandatory
3483: ::= { error 24 }
3484:
3485: clnpOutErrUnspecs OBJECT-TYPE
3486: SYNTAX Counter
3487: ACCESS read-only
3488: STATUS mandatory
3489: ::= { error 25 }
3490:
3491: clnpOutErrProcs OBJECT-TYPE
3492: SYNTAX Counter
3493: ACCESS read-only
3494: STATUS mandatory
3495: ::= { error 26 }
3496:
3497: clnpOutErrCksums OBJECT-TYPE
3498: SYNTAX Counter
3499: ACCESS read-only
3500: STATUS mandatory
3501: ::= { error 27 }
3502:
3503: clnpOutErrCongests OBJECT-TYPE
3504: SYNTAX Counter
3505: ACCESS read-only
3506: STATUS mandatory
3507: ::= { error 28 }
3508:
3509: clnpOutErrHdrs OBJECT-TYPE
3510: SYNTAX Counter
3511: ACCESS read-only
3512: STATUS mandatory
3513: ::= { error 29 }
3514:
3515: clnpOutErrSegs OBJECT-TYPE
3516: SYNTAX Counter
3517: ACCESS read-only
3518: STATUS mandatory
3519: ::= { error 30 }
3520:
3521: clnpOutErrIncomps OBJECT-TYPE
3522: SYNTAX Counter
3523: ACCESS read-only
3524: STATUS mandatory
3525: ::= { error 31 }
3526:
3527:
3528:
3529:
3530: Satz [Page 63]
3531:
3532: RFC 1162 CLNS MIB June 1990
3533:
3534:
3535: clnpOutErrDups OBJECT-TYPE
3536: SYNTAX Counter
3537: ACCESS read-only
3538: STATUS mandatory
3539: ::= { error 32 }
3540:
3541: clnpOutErrUnreachDsts OBJECT-TYPE
3542: SYNTAX Counter
3543: ACCESS read-only
3544: STATUS mandatory
3545: ::= { error 33 }
3546:
3547: clnpOutErrUnknownDsts OBJECT-TYPE
3548: SYNTAX Counter
3549: ACCESS read-only
3550: STATUS mandatory
3551: ::= { error 34 }
3552:
3553: clnpOutErrSRUnspecs OBJECT-TYPE
3554: SYNTAX Counter
3555: ACCESS read-only
3556: STATUS mandatory
3557: ::= { error 35 }
3558:
3559: clnpOutErrSRSyntaxes OBJECT-TYPE
3560: SYNTAX Counter
3561: ACCESS read-only
3562: STATUS mandatory
3563: ::= { error 36 }
3564:
3565: clnpOutErrSRUnkAddrs OBJECT-TYPE
3566: SYNTAX Counter
3567: ACCESS read-only
3568: STATUS mandatory
3569: ::= { error 37 }
3570:
3571: clnpOutErrSRBadPaths OBJECT-TYPE
3572: SYNTAX Counter
3573: ACCESS read-only
3574: STATUS mandatory
3575: ::= { error 38 }
3576:
3577: clnpOutErrHops OBJECT-TYPE
3578: SYNTAX Counter
3579: ACCESS read-only
3580: STATUS mandatory
3581: ::= { error 39 }
3582:
3583:
3584:
3585:
3586: Satz [Page 64]
3587:
3588: RFC 1162 CLNS MIB June 1990
3589:
3590:
3591: clnpOutErrHopReassms OBJECT-TYPE
3592: SYNTAX Counter
3593: ACCESS read-only
3594: STATUS mandatory
3595: ::= { error 40 }
3596:
3597: clnpOutErrUnsOptions OBJECT-TYPE
3598: SYNTAX Counter
3599: ACCESS read-only
3600: STATUS mandatory
3601: ::= { error 41 }
3602:
3603: clnpOutErrUnsVersions OBJECT-TYPE
3604: SYNTAX Counter
3605: ACCESS read-only
3606: STATUS mandatory
3607: ::= { error 42 }
3608:
3609: clnpOutErrUnsSecurities OBJECT-TYPE
3610: SYNTAX Counter
3611: ACCESS read-only
3612: STATUS mandatory
3613: ::= { error 43 }
3614:
3615: clnpOutErrUnsSRs OBJECT-TYPE
3616: SYNTAX Counter
3617: ACCESS read-only
3618: STATUS mandatory
3619: ::= { error 44 }
3620:
3621: clnpOutErrUnsRRs OBJECT-TYPE
3622: SYNTAX Counter
3623: ACCESS read-only
3624: STATUS mandatory
3625: ::= { error 45 }
3626:
3627: clnpOutErrInterferences OBJECT-TYPE
3628: SYNTAX Counter
3629: ACCESS read-only
3630: STATUS mandatory
3631: ::= { error 46 }
3632:
3633:
3634: -- the CLNP Echo Group
3635:
3636: -- the ES-IS Group
3637:
3638: esisESHins OBJECT-TYPE
3639:
3640:
3641:
3642: Satz [Page 65]
3643:
3644: RFC 1162 CLNS MIB June 1990
3645:
3646:
3647: SYNTAX Counter
3648: ACCESS read-only
3649: STATUS mandatory
3650: ::= { es-is 1 }
3651:
3652: esisESHouts OBJECT-TYPE
3653: SYNTAX Counter
3654: ACCESS read-only
3655: STATUS mandatory
3656: ::= { es-is 2 }
3657:
3658: esisISHins OBJECT-TYPE
3659: SYNTAX Counter
3660: ACCESS read-only
3661: STATUS mandatory
3662: ::= { es-is 3 }
3663:
3664: esisISHouts OBJECT-TYPE
3665: SYNTAX Counter
3666: ACCESS read-only
3667: STATUS mandatory
3668: ::= { es-is 4 }
3669:
3670: esisRDUins OBJECT-TYPE
3671: SYNTAX Counter
3672: ACCESS read-only
3673: STATUS mandatory
3674: ::= { es-is 5 }
3675:
3676: esisRDUouts OBJECT-TYPE
3677: SYNTAX Counter
3678: ACCESS read-only
3679: STATUS mandatory
3680: ::= { es-is 6 }
3681:
3682: END
3683:
3684: 6. Identification of OBJECT instances for use with the SNMP
3685:
3686: The names for all object types in the MIB are defined explicitly
3687: either in the Internet-standard MIB or in other documents which
3688: conform to the naming conventions of the SMI. The SMI requires that
3689: conformant management protocols define mechanisms for identifying
3690: individual instances of those object types for a particular network
3691: element.
3692:
3693: Each instance of any object type defined in the MIB is identified in
3694: SNMP operations by a unique name called its "variable name." In
3695:
3696:
3697:
3698: Satz [Page 66]
3699:
3700: RFC 1162 CLNS MIB June 1990
3701:
3702:
3703: general, the name of an SNMP variable is an OBJECT IDENTIFIER of the
3704: form x.y, where x is the name of a non-aggregate object type defined
3705: in the MIB and y is an OBJECT IDENTIFIER fragment that, in a way
3706: specific to the named object type, identifies the desired instance.
3707:
3708: This naming strategy admits the fullest exploitation of the semantics
3709: of the powerful SNMP get-next operator, because it assigns names for
3710: related variables so as to be contiguous in the lexicographical
3711: ordering of all variable names known in the MIB.
3712:
3713: The type-specific naming of object instances is defined below for a
3714: number of classes of object types. Instances of an object type to
3715: which none of the following naming conventions are applicable are
3716: named by OBJECT IDENTIFIERs of the form x.0, where x is the name of
3717: said object type in the MIB definition.
3718:
3719: For example, suppose one wanted to identify an instance of the
3720: variable sysDescr in the Internet-standard MIB. The object class for
3721: sysDescr is:
3722:
3723: iso org dod internet mgmt mib system sysDescr
3724: 1 3 6 1 2 1 1 1
3725:
3726: Hence, the object type, x, would be 1.3.6.1.2.1.1.1 to which is
3727: appended an instance sub-identifier of 0. That is, 1.3.6.1.2.1.1.1.0
3728: identifies the one and only instance of sysDescr.
3729:
3730: 6.1. clnpAddrTable Object Type Names
3731:
3732: The name of an CLNP-addressable network element, x, is the OBJECT
3733: IDENTIFIER of the form z such that z is the value (in which each
3734: octet of the ClnpAddress type is expressed as a sub-identifier of the
3735: OBJECT IDENTIFIER) of that instance of the clnpAdEntAddr object type
3736: associated with x.
3737:
3738: For each object type, t, for which the defined name, n, has a prefix
3739: of clnpAddrEntry, an instance, i, of t is named by an OBJECT
3740: IDENTIFIER of the form n.y, where y is the name of the CLNP-
3741: addressable network element about which i represents information.
3742:
3743: For example, suppose one wanted to find the maximum reassembly size
3744: of an entry in the CLNP interface table associated with an CLNP
3745: address of NS+0504030201. Accordingly, clnpAdEntNetMask.5.5.4.3.2.1
3746: would identify the desired instance.
3747:
3748: 6.2. clnpRoutingTable Object Type Names
3749:
3750: The name of an CLNP route, x, is the OBJECT IDENTIFIER of the form z
3751:
3752:
3753:
3754: Satz [Page 67]
3755:
3756: RFC 1162 CLNS MIB June 1990
3757:
3758:
3759: such that z is the value (in which each octet of the ClnpAddress type
3760: is expressed as a sub-identifier of the OBJECT IDENTIFIER) of that
3761: instance of the clnpRouteDest object type associated with x.
3762:
3763: For each object type, t, for which the defined name, n, has a prefix
3764: of clnpRoutingEntry, an instance, i, of t is named by an OBJECT
3765: IDENTIFIER of the form n.y, where y is the name of the CLNP route
3766: about which i represents information.
3767:
3768: For example, suppose one wanted to find the next hop of an entry in
3769: the CLNP routing table associated with the destination of
3770: NS+0504030201. Accordingly, clnpRouteNextHop.5.5.4.3.2.1 would
3771: identify the desired instance.
3772:
3773: At the option of the agent, multiple routes to the same destination
3774: may be visible. To realize this, the agent, while required to return
3775: a single entry for an CLNP route, x, of the form n.y, may also return
3776: information about other routes to the same destination using the form
3777: n.y.v, where v is a implementation-dependent small, non-negative
3778: integer.
3779:
3780: 6.3. clnpNetToMediaTable Object Type Names
3781:
3782: The name of a cached CLNP address, x, is an OBJECT IDENTIFIER of the
3783: form s.z, such that s is the value of that instance of the
3784: clnpNetToMediaIfIndex object type associated with the entry and z is
3785: the value of the CLNP address of the clnpNetToMediaNetAddress object
3786: type associated with x, in which each octet of the ClnpAddress type
3787: is expressed as a sub-identifier of the OBJECT IDENTIFIER.
3788:
3789: For each object type, t, for which the defined name, n, has a prefix
3790: of clnpNetToMediaEntry, an instance, i, of t is named by an OBJECT
3791: IDENTIFIER of the form n.y, where y is the name of the cached CLNP
3792: address about which i represents information.
3793:
3794: For example, suppose one wanted to find the media address of an entry
3795: in the address translation table associated with a CLNP address of
3796: NS+0504030201 and interface 3. Accordingly,
3797: clnpNetToMediaPhysAddress.3.5.5.4.3.2.1 would identify the desired
3798: instance.
3799:
3800: 6.4. clnpMediaToNetTable Object Type Names
3801:
3802: The name of a cached media address, x, is an OBJECT IDENTIFIER of the
3803: form s.z, such that s is the value of that instance of the
3804: clnpMediaToNetIfIndex object type associated with the entry and z is
3805: the value of the media address of the clnpMediaToNetMediaAddress
3806: object type associated with x, in which each octet of the media
3807:
3808:
3809:
3810: Satz [Page 68]
3811:
3812: RFC 1162 CLNS MIB June 1990
3813:
3814:
3815: address is expressed as a sub- identifier of the OBJECT IDENTIFIER.
3816:
3817: For each object type, t, for which the defined name, n, has a prefix
3818: of clnpMediaToNetEntry, an instance, i, of t is named by an OBJECT
3819: IDENTIFIER of the form n.y, where y is the name of the cached media
3820: address about which i represents information.
3821:
3822: For example, suppose one wanted to find the CLNP address of an entry
3823: in the address translation table associated with a media address of
3824: 08:00:20:00:38:ba and interface 3. Accordingly,
3825: clnpMediaToNetNetAddress.3.8.0.32.0.56.186 would identify the desired
3826: instance.
3827:
3828: 7. References
3829:
3830: [1] Cerf, V., "IAB Recommendations for the Development of Internet
3831: Network Management Standards", RFC 1052, IAB, April 1988.
3832:
3833: [2] Cerf, V., "Report of the Second Ad Hoc Network Management Review
3834: Group", RFC 1109, NRI, August 1989.
3835:
3836: [3] Rose, M., and K. McCloghrie, "Structure and Identification of
3837: Management Information for TCP/IP-based Internets", RFC 1155,
3838: Performance Systems International and Hughes LAN Systems, May
3839: 1990.
3840:
3841: [4] McCloghrie, K., and M. Rose, "Management Information Base for
3842: Network Management of TCP/IP-based Internets", RFC 1156, Hughes
3843: LAN Systems and Performance Systems International, May 1990.
3844:
3845: [5] Case, J., M. Fedor, M. Schoffstall, and J. Davin, The Simple
3846: Network Management Protocol", RFC 1157, University of Tennessee
3847: at Knoxville, Performance Systems International, Performance
3848: Systems International, and the MIT Laboratory for Computer
3849: Science, May 1990.
3850:
3851: [6] Rose, M., "Management Information Base for Network Management of
3852: TCP/IP-based internets: MIB-II", RFC 1158, Performance Systems
3853: International, May 1990.
3854:
3855: [7] Information processing systems - Open Systems Interconnection,
3856: "Specification of Abstract Syntax Notation One (ASN.1)",
3857: International Organization for Standardization, International
3858: Standard 8824, December 1987.
3859:
3860: [8] Information processing systems - Open Systems Interconnection,
3861: "Specification of Basic Encoding Rules for Abstract Notation One
3862: (ASN.1)", International Organization for Standardization,
3863:
3864:
3865:
3866: Satz [Page 69]
3867:
3868: RFC 1162 CLNS MIB June 1990
3869:
3870:
3871: International Standard 8825, December 1987.
3872:
3873: [9] Information processing systems - Data Communications - "Protocol
3874: for providing the Connectionless-mode Network Service and
3875: Provision of Underlying Service", International Organization for
3876: Standardization", International Standard 8473, May 1987.
3877:
3878: [10] "End System to Intermediate System Routing Exchange Protocol for
3879: Use in Conjunction with the Protocol for the Provision of the
3880: Connectionless-mode Network Service (ISO 8473)", International
3881: Draft Proposal 9542.
3882:
3883: [11] Kille, S., "A String Encoding of Presentation Address", Research
3884: Note RN/89/14, Department of Computer Science, University College
3885: London, February 1989.
3886:
3887:
3888: 8. Security Considerations
3889:
3890: Security issues are not discussed in this memo.
3891:
3892: 9. Author's Address:
3893:
3894: Greg Satz
3895: cisco Systems, Inc.
3896: 1350 Willow Road
3897: Menlo Park, CA 94025
3898:
3899: Phone: (415) 326-1941
3900:
3901: Email: [email protected]
3902:
3903:
3904:
3905:
3906:
3907:
3908:
3909:
3910:
3911:
3912:
3913:
3914:
3915:
3916:
3917:
3918:
3919:
3920:
3921:
3922: Satz [Page 70]
3923:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.