Internet Standards

home *** CD-ROM | disk | FTP | other *** search

/ Internet Standards / CD1.mdf / MISC / MERIT / IDRP / IDRP.MIB < prev next >

Wrap

Text File | 1992-07-24 | 94.4 KB | 2,707 lines

Network Working Group Susan Hares Request for Comments: DRAFT NSFNET/MERIT July 1992 Definition of Managed Objects for the IP for IDRP 1.) Status of this memo This memo proposes an extension to the SNMP MIB to support the adaptation of the ISO Inter-Domain Routing Protocol ([1]) for that enables it to be used as an Inter-Autonomous System routing protocol in the TCP/IP Internet. This adaptation will be called "IDRP for IP" [2] in this document. Dual IDRP is defined to be a single instance of IDRP that can simultaneously support Inter-Domain/Inter-Autonomous System routing in the TCP/IP and OSI Internets. An OSI IDRP for the purposes of this paper is defined to be an implementation of the ISO Inter-Domain Routing Protocol as defined in [1]. The whole family of IDRP related documents and their functoins are listed in [3]. This memo has two main parts and one appendix: - IDRP General MIB , and - IDRP for IP MIB - appendix A - IDRP for IP MIB in GDMO This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a "working draft" or "work in progress." 2. Acknowledgements The author wishes to note that BGP-3 MIB was used extensively in deciding on what managed objects should go into the IDRP GDMO. From the IDRP GDMO, the same managed objects plus additions have been extracted. The author notes with joy that ideas do recycle. 3.) The Network Management Framework The Internet-standard Network Management Framework consists of three components. They are: RFC 1155 [5] which defines the SMI, the mechanisms used for Expiration Date December 1992 FORMFEED[Page 1] RFC DRAFT June 1992 describing and naming objects for the purpose of management. RFC 1212 [6] defines a more concise description mechanism, which is wholly consistent with the SMI. RFC 1156 [7] which defines MIB-I, the core set of managed objects for the Internet suite of protocols. RFC 1213 [8], defines MIB-II, an evolution of MIB-I based on implementation experience and new operational requirements. RFC 1157 [9] which defines the SNMP, the protocol used for network access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. 4. Objects Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) [10] defined in the SMI. In particular, each object has a name, a syntax, and an encoding. The name is an object identifier, an administratively assigned name, which specifies an object type. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the OBJECT DESCRIPTOR, to also refer to the object type. The syntax of an object type defines the abstract data structure corresponding to that object type. The ASN.1 language is used for this purpose. However, the SMI [5] purposely restricts the ASN.1 constructs which may be used. These restrictions are explicitly made for simplicity. The encoding of an object type is simply how that object type is represented using the object type's syntax. Implicitly tied to the notion of an object type's syntax and encoding is how the object type is represented when being transmitted on the network. The SMI specifies the use of the basic encoding rules of ASN.1 [11], subject to the additional requirements imposed by the SNMP. 3.1. Format of Definitions Section 5 contains contains the specification of all object types contained in this MIB module. The object types are defined using the conventions defined in the SMI, as amended by the extensions specified in [6,12]. Expiration Date December 1992 FORMFEED[Page 2] RFC DRAFT June 1992 4.) Overview These objects are used to control and manage a IDRP for IP [x] implementation. IDRP ([1]) is defined as the protocol for exchange of Inter-Domain routing information between routers to support forwarding of ISO 8473 (Connectionless Network Layer Protocol (CLNP))[4] PDUs. The "IDRP for IP" document [2] contains the a description adaptation of the IDRP protocol definition that enables it to be used as protocol for the exchange of inter-autonomous system information among routers to support the forwarding of IP packets across multiple autonomous systems. The adaptation is defined is such a way that a Dual IDRP will be able to fully interoperate with IDRP for IP. This document contains two main parts, and two informative appendices: -IDRP General MIB (section 5) -IDRP for IP MIB (section 6) -Appendix A - IDRP for IP MIB in GDMO -Appendix B - ISO IDRP GMDO for CLNP (8473) only (What to not implement for IDRP for IP) The IDRP General MIB specifies the managed objects which are protocol specific, and may be used in either an IDRP for IP, OSI IDRP, or Dual IDRP. The IDRP for IP MIB section lists managed objects needed for the IDRP for IP MIB. Appendix A - "IDRP for IP MIB in GDMO" recast the IDRP for IP MIB in ISO GDMO language. This appendix will allow implementors of the IDRP GDMO to quickly add in the IDRP for IP MIB. Appendix B - ISO IDRP GDMO for CLNP only will list the GDMO contained in the ISO IDRP document which does not need to be implemented for the IDRP for IP implementations. Again, this appendix will allow implementors of the IDRP GDMO to quickly delete all CLNP references from the general IDRP implementations. The GMDO definitions in Appendix A and Appendix B are listed in with GDMO variable and reference to the IDRP document. These definitions are tied to a specific version of the ISO IDRP standard [1]. The version will be noted in each appendix. As new version of the IDRP standard is released, these GDMO definitions may change. The reader should refer to the ISO standard for the authortative GDMO definitions. 5. IDRP for IP General MIB Expiration Date December 1992 FORMFEED[Page 3] RFC DRAFT June 1992 5.1 IDRP for IP General MIB comments The IDRP for IP General MIB contains four sets of general IDRP variables from the ISO IDRP protocol: 1.) idrpConfig package 2.) adjacentBis package 3.) Actions 4.) Traps which Notify about IDRP problem The idrpConfig package is a group of attributes which are needed to configure a IDRP for IP BIS. One example of such BIS configuration variable is idrpVersion which indicates the version of the IDRP that this BIS defaults to using. --EDITOR's note: IDRP Configuration information can take two tacts: -- for IDRP for IP only. The IDRP for IP only can simply leave the -- CLNPAddress as null or not there. Or an IDRP for IP MIB can -- simply delete these Variables and have different tables. I -- have taken the first approach since it seems the overhead is -- just a little for the Dual MIB, and will be more cohesive in -- the end. An IDRP for IP MIB parsers could simply -- ignore any request for CLNP variable, or could simply enter -- a MIB with a null value. The total extra overhead for CLNP -- on top of the IDRP for IP package seems very little -- The adjacentBis package is a group of attributes which configure or record statistics for a connection with an adjacent BIS. A similar group of variables in the BGP-3 mib is the bgpPeerTable. The actions in the ISO protocols must be translated to attributes for SNMP's support. The two IDRP actions - start a BIS-BIS connection and stop a BIS-BIS connection are encoded in one action variable. The TRAP section encodes the ISO IDRP protocol's notifications into SNMP traps. The variables included in the Notifications are dependent on whether the protocol is running IDRP for IP only, OSI IDRP or Dual IDRP. IDRP for IP MIB assumes that: - the IpAddress from RFC-1213 will exist in any router using IDRP for IP; - clnpAddress from RFC-1238 will be in any router using OSI IDRP; and - IpAddress from RFC-1213 and clnpAddress from the RFC-1213 will be exist in any router router doing Dual-IDRP. 5.1.1) IdrpConfig Package Variables n configured for this IDRP router (Border Intermediate System (BIS)). The idrpConfig package does not has only two counterparts in the BGP-3 MIB: bgpVersion and bgpLocalAS. The equivalent IDRP for IP MIB variables are: Expiration Date December 1992 FORMFEED[Page 4] RFC DRAFT June 1992 BGP-3 MIB Variable ISO MIB Variable IDRP for IP MIB Variable ------------------------------------------------------------------ bgpVersion version idrpVersion bgpLocalAS localRDI idrpLocalRdi Please note that bgpLocalAS corresponds to the idrpLocalRDI, but is not the same type of variable. Only systems which need to translate between BGP-3/4 and IDRP-for-IP will have a relationship between local AS number and idrpLocalRDI. Please refer to the IDRP for IP document for details [2]. The idrpConfig package contains (in the order found in the ISO IDRP specification): Expiration Date December 1992 FORMFEED[Page 5] RFC DRAFT June 1992 ISO Variable MIB Variable Meaning ----------------------------------------------------------- internalBIS idrpInternalBisTable BIS peers within RD intraIS idrpIntraIsTable IS which this BIS can send packets to to be delivered within RD externalBIS- idrpExternalBis- List of BIS peers outside Neighbor NeighborTable this RD. internalSystems idrpInternalSystems Internal systems loaded Table into network layer reachability information of IDRP localRDI idrplocalRDI RDI of RD this BIS resides in rdcConfig idrpRdcConfigTable, Routing Domain Confederation (RDC) information for this BIS. localSNPA idrpLocalSnpaTable SNPA of each interface on this machine multiExit idrpMultExit Indication whether this BIS will use MULTI_EXIT_DISC to decide between otherwise identical routes. routeServer idrpRouteServer Indication whether this BIS may set IDRP_Server_Allowed field to X"FF" which allows route server function. maximumPDUSize idrpMaximumPduSize Maximum number of octets that this BIS is able to handle in incoming BISPDU holdTime idrpHoldTime Maximum number of seconds that may elapse between BISPDUs of type: KEEPALIVE, UPDATE, RIB REFRESH PDU outstandingPDUs idrpOutstandingPdu Maximum number of BISPDUs sent with receipt of acknowledgement retransmission- idrpRetransmission- Number of seconds between Time Time KEEPALIVE messages if no other traffic sent closeWaitDelay idrpCloseWaitDelay The number of seconds local system Period Period shall stay in Close-Wait state prior to chaing to Closed state. Expiration Date December 1992 FORMFEED[Page 6] RFC DRAFT June 1992 rdTransitDelay idrpRdTransitDelay Estimated average Delay across Rd in units of 500ms. rdLRE idrpRdlre Average Error rate in units of integer/2**32-1 = actual error locExpense idrpLocExpense Monetary Expense of transiting RD ribAttsSet idrpRibAttsSetTable Set of Rib Attributes supported by BIS idrpRibAttValueTable idrpRDCTable idrpRdc capacity idrpCapacity The traffic carrying capacity of RD priority idrpPriority (will probably be removed from from IDRP specification.) version idrpVersion Version of IDRP this BIS defaults to 5.1.2 AdjacentBIS package The AdjacentBIS set of attributes in the ISO IDRP specification contains the configured and statistical variables for IDRP. The AdjacentBIS section of the ISO IDRP specification start out from the BGP-3 MIB bgpPeerTable, and may bare a high resemblance to that section of the BGP-3 MIB. However, additions have been made for the RDC attributes, and for the ISO CLNP addresses. Below is a table which shows how BGP-3, ISO and the IDRP for IP MIB are similar: Expiration Date December 1992 FORMFEED[Page 7] RFC DRAFT June 1992 BGP-3 MIB Variable ISO MIB Variable IDRP for IP MIB Variable ------------------------------------------------------------------ none-*1 none-*1 BisPeerID-*1 none-*1 bisNet-*1 BisNET-*1 bgpPeerIdentifier none BisIpAddress bgpPeerState state bisState none lastSeqNoSent bisLastSeqNoSent none lastSeqNoRecv bisLastSeqNoRecv none lastAckSent bisLastAckSent none lastAckRecv bisLastAckRecv bgpPeerAdminStatus none - *2(action) bisPeerAdminStatus none bisRDI bisRdi none bisRDC bisRdcID plus bisRDCtable bisPeerLocalAddr none - *3 bisLocalSnpa - *3 -*3 none - *3 bisPeerSNPAs - *3 bisPeerSnpaTableId - *3 plus BisPeerTable bgpPeerLocalPort none-*4 none-*4 bgpPeerRemotePort none-*4 none-*4 bgpRemoteAS*5 none none bgpPeerInUpdates updatesIn bisUpdatesIn bgpPeerOutUpdates updatesOut bisUpdatesOut bgpPeerInTotal totalBISPDUsIn bisTotalBISPDUIn Messages bgpPeerOutTotal totalBISPDUsOut bisTotalBISPDUOut Messages none keepAlivesSinceLast bisKeepAlivesSinceLastUpdate Update Table Notes: *1 - ISO IDRP document specifies only NET to identify a BIS. BGP-3 specifies only IP. This IDRP for IP General MIB specifies both IP Address and OSI address. For an IP only implementation, The BisNET variable is NULL. The BISPeerID allows the router to know if multiple IP connections are being used between two IDRP for IP only Routers. Expiration Date December 1992 FORMFEED[Page 8] RFC DRAFT June 1992 *2 - The ISO IDRP specification specifies two actions instead of the variable. The ability to specify actions is not available in SNMP. *3 - The BisPeerLocalAddr identifies a local IP address which identifies a local port to use to send the BGP packets to reach this remote peer. However, the ISO concept uses a local SNPA address. While this MIB variable is not in the ISO specification, suggestions will be made to include it in the ISO DIS ballot. *4 - BGP-3/4 uses a TCP connection, while IDRP uses a reliable transport inside the protocol. Thus these variables are not necessary. *5 - bgpRemoteAS may relate to the bisRDI and BisRdc. Please see the IDRP for IP document for the use of of an AS as part of an IDRP RDI. 5.1.3 Actions in ISO Historically, the ISO IDRP actions came from bgp-3 MIB variable bgpPeerAdminStatus. The two ISO IDRP actions startEvent and stopEvent are encoded in the IDRP for IP MIB variable idrpPeerAdminStatus. The circle of MIB life seems to remain unbroken. 5.1.4 Traps - or ISO events The ISO IDRP Events were taken from the BGP-3 Traps and expanded upon. The following table compares BGP-3 Traps, ISO IDRP Events, and IDRP for IP TRAPs: Expiration Date December 1992 FORMFEED[Page 9] RFC DRAFT June 1992 BGP-3 Trap ISO IDRP Event IDRP for IP Trap ------------------------------------------------------------------- bgpEstablished EnterFSMState idrpEnterFSMState bgpBackwardTransition FSMStateChange-*1 idrpFSMStateChange none ErrorBISPDUsent idrpErrorBispduSent none OpenBISpduRDCError idrpOpenBispduRdcError none CorruptAdjRIBIn idrpCorruptAdjRibIn none PacketBomb idrpPacketBomb *1 - The bgpBackwardTransition- only indicates when the FSM state machine takes a lower state. The ISO event FSMStateChange and IDRP for IP Trap indicate whenever the FSM changes state. Implementations may look at turning off this TRAP notification under local control. The following order of MIB definitions is the order matching the IDRP protocol specification GDMO definitions [1]. After each managed object which has a BGP-3 a comment will occur referencing the BGP-3 MIB definition. 5.2 Definitions Expiration Date December 1992 FORMFEED[Page 10] RFC DRAFT June 1992 RFCxxxx-MIB DEFINITIONS ::= BEGIN IMPORTS NetworkAddress, IpAddress, Counter FROM RFC1155-SMI mib-2 FROM RFC1213-MIB OBJECT-TYPE FROM RFC-1212 TRAP-TYPE FROM RFC-1215; clnpAddress FROM RFC-1238; -- This MIB module uses the extended OBJECT-TYPE macro as -- defined in [6], and the TRAP-TYPE macro as defined -- in [12]. idrp OBJECT IDENTIFIER ::= { mib-x xx } idrpVersion OBJECT-type SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The version of IDRP protocol this machine defaults to using. (ISO IDRP attribute: version)" ::= {idrp 1} idrpInternalBisTable OBJECT-TYPE SYNTAX SEQUENCE OF IDRPInternalBisEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The set Network Address which identify the the BIS in this routing Domain. (ISO IDRP attribute: InternalBis)" ::={idrp 2} --internalBIS is GDMO SEQUENCE but it --is a table, so it needs to be expanded --for SNMP idrpinternalBisEntry OBJECT-TYPE SYNTAX IDRPInternalBisEntry ACCESS not-accessible Expiration Date December 1992 FORMFEED[Page 11] RFC DRAFT June 1992 STATUS mandatory DESCRIPTION "Network Address Information about an BIS internal to this routing domain." INDEX { idrpInternalBisIndex } ::= { idrpInternalBisTable 1 } idrpInternalBisEntry :: = SEQUENCE { idrpInternalBisIndex INTEGER, idrpInternalBisRouterID INTEGER, idrpInternalBisIpAddress IpAddress, idrpInternalBisNet clnpAddress } --bisNETIdentifier for IDRP for IP only will be --null value. idrpInternalBisIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Index into the idrpInternal BIS table for SNMP table walking." ::= { idrpInternalBisEntry 1 } idrpInternalBisRouterID OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Router ID for each Internal BIS router table for each remote Internal BIS router. This ties the configuration of multiple IP addresses to a single router." ::= { idrpInternalBisEntry 2 } idrpInternalBisIPAddress OBJECT-TYPE SYNTAX IPAddress ACCESS read-only STATUS mandatory Expiration Date December 1992 FORMFEED[Page 12] RFC DRAFT June 1992 DESCRIPTION "The IP Address for a BIS internal to this routing Domain." ::= { idrpInternalBisEntry 3 } idrpInternalBisNet OBJECT-TYPE SYNTAX clnpAddress ACCESS read-only STATUS mandatory DESCRIPTION "The ISO NET address for a BIS internal to this routing Domain." ::= { idrpInternalBisEntry 4 } idrpIntraIsTable OBJECT-TYPE SYNTAX SEQUENCE OF IDRPIntraIsEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A Table of Network Addresses of the IS to which the local BIS may deliver an inbound packet whose destination lies within the BIS's routing domain. These routers (ISs) must be located on the on the same common subnet as this local BIS, and must be capable of delivering packets to the destinations that are located within the local BIS's routing domain." ::= { idrp 4 } idrpIntraIsEntry OBJECT-TYPE SYNTAX IDRPIntraIsEntry ACCESS not-accesible STATUS mandatory DESCRIPTION "Information about a local router (ISs) to which the BIS may deliver an inbound packet whose destination lies within the BIS's routing domain." INDEX { idrpIntraIsIndex } ::= { idrpIntraIsTable 1} IDRPIntraIsEntry :: = SEQUENCE { idrpIntraISIndex INTEGER, idrpIntraIsRouterID INTEGER, Expiration Date December 1992 FORMFEED[Page 13] RFC DRAFT June 1992 idrpIntraBisIpIdentifier IpAddress, idrpIntraBisNetIdentifier clnpAddress } idrpIntraISIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Index into the idrpIntraIS table for SNMP table walking." ::= { idrpIntraIsEntry 1 } idrpIntraIsRouterID OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Index to idrpIntraIS Table router table for each remote Internal BIS router." ::= { idrpIntraIsEntry 2 } idrpIntraBisIPIdentifier OBJECT-TYPE SYNTAX IPAddress ACCESS read-only STATUS mandatory DESCRIPTION "The IP Address for a local router (ISs) to which the BIS may deliver an inbound packet whose destination lies within the BIS's routing domain." ::= { idrpIntraIsEntry 3 } idrpIntraBisNetIdentifier OBJECT-TYPE SYNTAX clnpAddress ACCESS read-only STATUS mandatory DESCRIPTION "The CLNP Address for a local router (ISs) to which the BIS may deliver an inbound packet whose destination lies within the BIS's routing domain." ::= { idrpIntraIsEntry 4 } idrpExternalBisNeighborTable OBJECT-TYPE SYNTAX SEQUENCE OF IDRPExternalBisNeighborEntry Expiration Date December 1992 FORMFEED[Page 14] RFC DRAFT June 1992 ACCESS not-accessible STATUS mandatory DESCRIPTION "A Table of Network Addresses which identify the BISs in adjacent routing domains which are reachable via a single subnetwork hop - that is on the same subnet." ::= {idrp 4} idrpExternalBisNeighborEntry OBJECT-TYPE SYNTAX IDRPExternalBisNeighborEntry ACCESS not-accesible STATUS mandatory DESCRIPTION "A Network Address of a BIS in adjacent routing domains which are reachable via a single subnetwork hop - that is on the same subnet." INDEX { idrpExternalBisIndex } ::= { idrpExternalBisNeighborEntry 1} IDRPExternalBisNeighborEntry :: = SEQUENCE { idrpExternalBisIndex INTEGER, idrpExternalBisNeighborRouterID INTEGER, idrpExternalBisNeighborIpAddress IpAddress, idrpExternalBisNeighborNet clnpAddress } idrpExternalBISIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Index into the idrpExternalBisNeighbor table for SNMP table walking." ::= { idrpExternalBisNieghborEntry 1 } idrpExternalBisRouterID OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory Expiration Date December 1992 FORMFEED[Page 15] RFC DRAFT June 1992 DESCRIPTION "Index to Internal BIS router table for each remote Internal BIS router." ::= { idrpExternalBisNeighborEntry 2 } idrpExternalBisNeighborIPAddress OBJECT-TYPE SYNTAX IPAddress ACCESS read-only STATUS mandatory DESCRIPTION "The IP Address of a BIS in adjacent routing domains which are reachable via a single subnetwork hop - that is on the same subnet." ::= { idrpExternalBisNeighborEntry 3 } idrpExternalBisNet OBJECT-TYPE SYNTAX clnpAddress ACCESS read-only STATUS mandatory DESCRIPTION "The CLNP Address for of a BIS in adjacent routing domains which are reachable via a single subnetwork hop - that is on the same subnet." ::= { idrpExternalBisNeighborEntry 4 } idrpInternalSystemsTable OBJECT-TYPE SYNTAX SEQUENCE OF IDRPInternalSystemsEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table of Network prefixes and Addresses which identify the systems in this routeing Domain which the BIS uses to construct the network layer reachability information." ::= {idrp 5} idrpInternalSystemsEntry OBJECT-TYPE SYNTAX IDRPInternalSystemsEntry ACCESS not-accesible STATUS mandatory DESCRIPTION "A table of Network prefixes and Addresses which identify the systems in this routeing Domain which the BIS uses to construct the network layer reachability information." Expiration Date December 1992 FORMFEED[Page 16] RFC DRAFT June 1992 INDEX { idrpInternalSystemSequenceID } ::= { idrpInternalSystemEntry 1} IDRPInternalSystemEntry :: = SEQUENCE { idrpInternalSystemSequenceID INTEGER, idrpInternalSystemProtocolType INTEGER, idrpInternalSystemProtocol OCTET STRING, idrpInternalSystemLength INTEGER, idrpInternalSystemPrefix OCTET STRING } idrpInternalSystemSequenceID OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Local ID and index for the list of the IDRP Internal Systems. " ::= {IDRPInternalSystemEntry 1} idrpInternalSystemProtocolType OBJECT-TYPE SYNTAX INTEGER { NLPID(1), Ethertype(2), LSAP(3) } ACCESS read-only STATUS mandatory DESCRIPTION "Identifier for the numbering scheme for the System Protocol type used in ISO IDRP specification. This Identifier allows multiple protocols within the ISO specification. The NLPID number scheme protocol type will be the only valid type for the IP and OSI IDRP." ::= { IDRPInternalSystemEntry 2 } idrpInternalSystemProtocol OBJECT-TYPE SYNTAX OCTET-STRING { IP ('CC'), CLNP ('??') Expiration Date December 1992 FORMFEED[Page 17] RFC DRAFT June 1992 } ACCESS read-only STATUS mandatory DESCRIPTION "The Protocol Identifier for the address type of the Internal System network layer reachability information. The only valid type for IDRP for IP is IP. The only valid types for Dual are IP and CLNP." ::= { IDRPInternalSystemEntry 3 } idrpInternalSystemLength OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Length of the InternalSystemPrefix in bits. The InternalSystemPrefix may be 1-32 bits for an IP address. The Supernetting Document [2] should be referred to for the concepts of IP prefixes. The length of the InternalSystems can be 0-160 bits for a CLNP address. " ::= { IDRPInternalSystemEntry 4 } idrpInternalSystemPrefix OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION "Sequence of Octets which encode the Internal System network Address Prefix. This sequence of octets may represent either IP address(es) for IDRP for IP, or either IP address(es) or CLNP Addresses for Dual IDRP. A Network Address Prefix may represent one network address or many network addresses or networks. For details on how to aggregate IP routes using an IP network address prefix, please refer to the RFC on IDRP for IP[x]. For details on how to aggreate OSI routes using OSI NET structure, please refer to the RFC on NSAP allocation[x]." :: = { IDRPInternalSystemEntry 5 } idrplocalRdi OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION "The Routing Domain Identifier for this routing Domain." Expiration Date December 1992 FORMFEED[Page 18] RFC DRAFT June 1992 ::= { idrp 6} --Note: for a routing domain with both IP and --OSI use the Routing Domain Identifier format in --IDRP for IP document [1]. idrpRdcConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF IDRPRdcConfigEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table of all of the Routing Confederations to which the RD of this BIS belongs and the nesting relationships that are in force between them. The nesting relationships are described as a sequence of sets of RDC Identifiers." ::= { idrp 7 } idrpRdcConfigTableEntry OBJECT-TYPE SYNTAX IdrpRdcConfigTableEntry ACCESS not-accessible STATUS mandatory DESCRIPTION " Information about a Routing Confederation to which the RD of this BIS belongs." INDEX { idrpRdcSetIndex } ::= { idrpRDCConfigTable 1 } IdrpRdcConfigTableEntry ::=SEQUENCE { idrpRdcSetIndex INTEGER, idrpRdcSetId INTEGER, idrpRdcSetMemberCount, INTEGER, idrpRdcMemberRdi1 OCTET-STRING, idrpRdcMemberRdi2 OCTET-STRING, idrpRdcMemberRdi3 OCTET-STRING, idrpRdcMemberRdi4 OCTET-STRING, idrpRdcMemberRdi5 OCTET-STRING } -- Editor's note: Expiration Date December 1992 FORMFEED[Page 19] RFC DRAFT June 1992 -- Help needed here. IDRP requires the -- nesting relationships are described as a -- sequence of sets of RDC Identifiers. -- ASN.1 format: -- Rdcgroup ::=SEQUENCE OF -- (Confed Rdcsetid, members SET of Rdi) --I have encoded around the SNMP limitations -- with Table Definition: -- -- Index SetId RDI1 RDI2 RDI3 RDI4 RD5 -- -- This table definitions is a major kludge, -- if you have more than 5 RDIs in your -- RDCs then, you must use a second row. -- What's the average RDC? idrpRdcSetIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Index into the IdrpRdcConfigTable for SNMP table walking so that a set of RDIs within a RDC set may span multiple table entries. This table definition is a redefining of ISO RdcGroup function into something the Simple Network Management Protocol (SNMP) can handle." ::= { IdrpRdcConfigTableEntry 1 } idrpRdcSetId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Identifer for Set of RDCs RD belongs to." ::= { IdrpRdcConfigTableEntry 2 } idrpRdcSetMemberCount OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Count of RDIs in the RDC member count. If this variable is set to zero, this line is a continuation line for an RDC set." ::= { IdrpRdcConfigTableEntry 3 } idrpRdcMemberRDI1 OBJECT-TYPE Expiration Date December 1992 FORMFEED[Page 20] RFC DRAFT June 1992 SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION " 1st RDI for this pariticular set of RDC that this BIS belongs to." ::= { IdrpRdcConfigTableEntry 4 } idrpRdcMemberRDI2 OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION " 2nd RDI for this pariticular set of RDC that this BIS belongs to." ::= { IdrpRdcConfigTableEntry 5 } idrpRdcMemberRDI3 OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION "Third RDI for this pariticular set of RDC that this BIS belongs to." ::= { IdrpRdcConfigTableEntry 6 } idrpRdcMemberRDI4 OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION " Fourth RDI for this pariticular set of RDC that this BIS belongs to." ::= { IdrpRdcConfigTableEntry 7 } idrpRdcMemberRDI5 OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION " Fifth RDI for this pariticular set of RDC that this BIS belongs to." ::= { IdrpRdcConfigTableEntry 8 } idrpLocalSnpaTable OBJECT-TYPE SYNTAX IdrpLocalSnpaEntry ACCESS read-only STATUS mandatory Expiration Date December 1992 FORMFEED[Page 21] RFC DRAFT June 1992 DESCRIPTION "Table of SNPAs of this BIS." ::= {idrp 7 } idrplocalSnpaEntry OBJECT-TYPE SYNTAX IdrpLocalSnpaEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Information about a SNPA on a BIS". INDEX { idrpIfIndex } ::= { idrpLocalSnapTable 1} IdrpLocalSnpaEntry SEQUENCE { idrpIfIndex INTEGER, idrpLocalSnpaAddress OCTET-STRING } idrpIfIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Identifier of the Interface to which the SNPA belongs. This Identifer should match the IfTable IfIndex value for the Interface." ::= { idrpLocalSnpaEntry 1 } idrpLocalSnpaAddress OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION " SNPA for this interface of this BIS." ::= { idrpLocalSnpaEntry 2 } idrpMultiExit OBJECT-TYPE SYNTAX INTEGER { true(1), false(2)} ACCESS read-write STATUS mandatory DESCRIPTION "The indication whether this BIS will use the MULTI_EXIT_DISC attribute to decide between otherwise identical routes. The multiExit parameter is used as the default value for the "multi_exit_disc" function in policy decisions. Expiration Date December 1992 FORMFEED[Page 22] RFC DRAFT June 1992 (ISO IDRP managed object: multiExit " ::== { idrp 8 } idrpRouteServer OBJECT-TYPE SYNTAX INTEGER { true(1), false(2)} ACCESS read-write STATUS mandatory DESCRIPTION "The indications whether is BIS may set the "IDRP_Server_Allowed" field in the NEXT_HOP attribute to FF(hex) for BIS to BIS UPDATE BISPDUs. If this variable is true then in accordance with local policy, the IDRP_Server_Allowed field may be set on some UPDATE BISPDUs that this BIS sends. If this attribute is set to false, then no UPDATE BISPDUs will be sent by this BIS with NEXT_HOP attributes containing an "IDRP_SERVER flag" equal to FF(hex). (ISO IDRP managed object routeServer)." ::== { idrp 9} idrpMaximumPduSize OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The maximum number of octets that this BIS is able to handle in an incoming BISPDU. (ISO IDRP managed object: maximumPDUsize)" ::== { idrp 10 } idrpHoldTime OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The maximum number of seconds that may elapse between the receipt of two successive BISPDUs of any of the following types: KEEPALIVE, UPDATE, RIB CHECKSUM PDUs or RIB REFRESH PDUs (ISO IDRP holdTime attribute.)" ::== { idrp 11 } idrpOustandingPDUs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION Expiration Date December 1992 FORMFEED[Page 23] RFC DRAFT June 1992 "The maximum number of BISPDUs that may be sent to this BIS without receiving an acknowledgement. (ISO IDRP oustandingPDUs attribute)." ::== { idrp 12 } idrpRetranmissionTime OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of seconds between KEEPALIVE messages if no other traffic is sent. (ISO IDRP retranmissionTime attribute.)" ::= { idrp 13 } idrpCloseWaitDelayPeriod OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of seconds the local system shall stay in the CLOSE-WAIT state prior to chaing to the CLOSED state. (ISO IDRP closeWaitDelayPeriod attribute)" ::= { idrp 14 } idrpRdTransitDelay OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The estimated average delay across a Routing Domain in units of 500ms. (ISO IDRP rdTransmitDealy attribute)" ::= { idrp 15 } idrpRdLRE OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The average error rate of a Routeing Domain in units of an integer which if divided by 2**32-1 will proviede the actual probablility of the error." (ISO IDRP rdLRE attribute)" ::= { idrp 16 } Expiration Date December 1992 FORMFEED[Page 24] RFC DRAFT June 1992 idrpLocExpense OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The monetary expense of transiting this Routeing Domain. The attribute contains an indication of cost and the units in which it is calculated. (ISO IDRP locExpense attribute.)" ::= { idrp 17 } idrpRibAttSetTable OBJECT-TYPE SYNTAX SEQUENCE OF IdrpRibAttSetEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The set of Rib Attributes supported by this BIS. (ISO IDRP ribAttsSet attribute)" ::= { idrp 18 } idrpRibAttsSetEntry OBJECT-TYPE SYNTAX IdrpRibAttsSetEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A Rib attribute supported by this BIS. (An element in the ISP IDRP ribAttsSet attribute.)" INDEX { idrpRibSetID } ::= { idrpRibAttsSetTable 1 } IdrpRibAttsSetEntry :: = SEQUENCE { idrpRibSetId INTEGER idrpRibSetCount INTEGER idrpRibAttributes SET OF { RibAttributeIdentifer INTEGER } } -- Help is needed her to turn complex -- ISO structure into SNMP compliant Expiration Date December 1992 FORMFEED[Page 25] RFC DRAFT June 1992 -- structure: -- -- ISO ASN.1 format for this is: -- RibAttsSet ::=SEQUENCE { confed Ribsetid, -- count Ribsetcount, -- attribs SET OF Ribattributes} -- Ribsetid ::=INTEGER(1..255) -- Ribsetcount ::=INGETER(0..255) -- RibAttributes ::=SEQUENCE{ -- attrib Ribattribute, -- value RibValue OPTIONAL} -- Ribattribute ::= ENUMERATED -- tRANSITDELAY (9), -- rESIDUALERROR (10), -- eXPENSE(11), -- sourceSpecificQOS(12), -- destinationSpecificQOS(13), -- sourceSpecificSecurity (17), -- destinationSpecificSecurity(18), -- capacity (19), -- priority (20)} -- -- Ribvalue ::=SEQUENCE {length Ribattlength, -- attr Ribattvalue } -- Ribattlength ::=INTEGER -- -- Ribattvalue ::= CHOICE { -- transitdelayvalue [0] IMPLICIT INTEGER, -- residualerrorvalue [1] IMPLICIT INTEGER, -- expensevalue [2] IMPLICIT INTEGER, -- sourcespecificqos [3] IMPLICIT INTEGER, -- destinationspecificqos [4] IMPLICIT INTEGER, -- sourcespecificsecurity [5] IMPLICIT INTEGER, -- destinationspecificsecurity [6] IMPLICIT INTEGER, -- capacityvalue [7] IMPLICIT INTEGER, -- priorityvalue [8] IMPLICIT INTEGER} -- -- Ribattqos ::=SEQUENCE { -- preflgth NSAPprefixLength, -- prefix NSAPprefix, -- qOSlgth QOSLength, -- qOSval QOSvalue -- metriclgth MetricLength -- metricval MetricValue } -- -- -- RibAttsec :: = SEQUENCE { -- preflgth NSAPprefixLength, -- prefix NSAPprefix, -- seclgth Securitylength, -- secval Securitylevel} -- -- Securitylength ::=INTEGER(0..255) -- Secuirtylevel ::=OCTET STRING(SIZE(1..255)) Expiration Date December 1992 FORMFEED[Page 26] RFC DRAFT June 1992 -- -- Current plan: -- Table 1 - idrpRibAttrSetEntry: -- idrpRibSetID idrpRibSetCount Continue-Ro 10RibAttributes -- (Integer) (Integer) 1-yes/0-no INTEGERs -- -- Table 2: Rib Attributes: -- RibAttributeID RibAttribute RibValuelength RIBValue -- INTEGER INTEGER INTEGER OCTET-STRING -- -- RibAttQOSID RibAttSECID -- INTEGER INTEGER -- (key to table3) (Key to Table 4) -- -- Table 3: RobAttQOS -- QOS-ID PrefixLength Prefix QOSlength QOS -- INTEGER INTEGER OCTET-STRING INTEGER OCTET-STRING -- MetricLength Metric -- INTEGER OCTET-STRING -- -- Table 4: RibAttrSecurity -- SEc-ID PrefixLength Prefix SECLength Security -- INTEGER INTEGER OCTET-STRING INTEGER OCTET-STRING -- idrpRibSetID OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Confederation Rib Attribute Set ID for this set of Rib attributes." ::= { idrpRibAttsSetEntry 1 } idrpRibSetCouunt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The RibSetCount indicates how many Rib Attribute values are listed in idrpRibAttributes attribute. " ::= { idrpRibATtsSetEntry 2 } --(More MIB variable definitions once the approach of the MIB --tables to represent the ISO definitions is approved.) idrpCapacity OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory Expiration Date December 1992 FORMFEED[Page 27] RFC DRAFT June 1992 DESCRIPTION "The traffic carrying capacity of this Routing Domain. (ISO IDRP cacpity attribute)" ::= { idrpCapacity 19 } --- --- --- IDRP BIS peer entries --- --- idrpAdjacentBisTable OBJECT-TYPE SYNTAX SEQUENCE OF IdrpAjacentBisEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The set of information about an adjacent BIS peer." ::={idrp 20} --internalBIS is GDMO entry but it --is a table. idrpAdjacentBisEntry OBJECT-TYPE SYNTAX IdrpAdjacnetBisEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Entry for in AdjacentBISTable for one adjacent BIS peer to this BIS." INDEX { idrpBISpeerID } ::= { idrpAdjacentBISTable 1} IdrAdjacentBISEntry:: = SEQUENCE { BisPeerID INTEGER, BISNet ClnpAddress, bisIPAddress IpAddress, bisRdi OCTET-STRING(length(1..20)) bisRdcId INTEGER, bisNegotatedVersion INTEGER, Expiration Date December 1992 FORMFEED[Page 28] RFC DRAFT June 1992 bisLocalSnpa OCTET-STRING, bisPeerSnpaTableId INTEGER, bisState INTEGER, bisLastSeqNoSent INTEGER, bisLastSeqNoRecv INTEGER, bisLastAckSent INTEGER, bisLastAckReceived INTEGER, bisUpdatesIn INTEGER, bisUpdatesOut INTEGER, totalBISPDUsIn INTEGER, keepAlivesSinceLastUpdate INTEGER bisPeerAdminStatus INTEGER } bisPeerID OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Table Index for the Management information about remote end of this BIS-BIS connection." ::= { idrpAdjacentBisEntry 1 } bisNet OBJECT-TYPE SYNTAX CLNPAddress ACCESS read-only STATUS mandatory DESCRIPTION "NET of the remote BIS with which this BIS is exchanging IDRP packets. (ISO bisNET attribute)" ::= { idrpAdjacentBisEntry 2 } bisIPAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "Ip Address of the remote BIS with which this Expiration Date December 1992 FORMFEED[Page 29] RFC DRAFT June 1992 BIS is exchanging IDRP packets. (No ISO attribute matches this.)" ::= { idrpAdjacentBisEntry 3 } bisRdi OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION "RDI of the remote BIS with which this BIS is exchanging IDRP packets. (ISO bisRDI attribute)" ::= { idrpAdjacentBisEntry 4 } bisRdcId OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION "Index into the BIS RDC Table which lists the RDCs a remote BIS is associated with. The entries in this table represent the RDC(s) the remote BIS belongs to in this BIS to BIS connection. (This plus table entries match the ISO bisRDC attribute)." ::= { idrpAdjacentBisEntry 5 } bisNegotatedVersion OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The negotiated version of IDRP protocol this BIS to BIs connection is using." ::= { idrpAdjacentBisEntry 6 } bisSnpaTableID OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Index into the idrpbisPeerSnpaTable which lists the SNPAs associated with with a router id. (This ID plus the idrpbisPeerSnpaTable entries associated with this ID represent the ISO entry bisPeerSNPAs.)" ::= { idrpAdjacentBisEntry 7 } bisLocalSnpa OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only Expiration Date December 1992 FORMFEED[Page 30] RFC DRAFT June 1992 STATUS mandatory DESCRIPTION "List the ID of the Local SNPA that should be the default for this BIS-BIS connection. (No ISO equivalent yet) " ::= { idrpAdjacentBisEntry 8 } bisLastSeqNoSent OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The last sequence nubmer sent to the remote BIS from this local BIS on this BIS to BIS connection. (ISO IDRP lastSeqNoSent attribute)." ::= { idrpAdjacentBisEntry 9 } bisLastSeqNoRecv OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The last sequence number received from the remote BIS by the local BIS on this BIS to BIS connection. (ISO IDRP lastSeqNoRecv attribute)" ::= { idrpAdjacentBisEntry 10 } bisLastAckSent OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of the last ack sent to the remote BIS by the local BIS on this BIS to BIS connection. (ISO IDRP lastAckSent attribute)" ::= { idrpAdjacentBisEntry 11 } bisLastAckRecv OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of the last ack received from the remote BIS by the local BIS on this BIS to BIS connection. (ISO IDRP lastAckRecv attribute)" ::= { idrpAdjacentBisEntry 12 } Expiration Date December 1992 FORMFEED[Page 31] RFC DRAFT June 1992 bisUpdatesIn OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of UPDATE BISPDUs received by this BIS on this BIS to BIS connection. (ISO IDRP updatesIn attribute)" ::= { idrpAdjacentBisEntry 13 } bisUpdatesOut OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of UPDATE BISPDUs sent by this BIS on this BIS to BIS connection. (ISO IDRP updatesOut attribute)" ::= { idrpAdjacentBisEntry 14 } bisTotalBISPDUsIn OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of BISPDUs received by this BIS on this BIS to BIS connection. (ISO IDRP totalBISPDUsIn attribute)" ::= { idrpAdjacentBisEntry 15 } bisTotalBISPDUsOut OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of BISPDUs received by this BIS on this BIS to BIS connection. (ISO IDRP totalBISPDUsOut attribute)" ::= { idrpAdjacentBisEntry 16 } BisKeepAlivesSinceLastUpdate OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of KEEPALIVE BISPDUs received by this BIS on this BIS to BIS connection since the last UPDATE BISODU. (ISO IDRP keepAlivesSinceLastUpdate attribute)" ::= { idrpAdjacentBisEntry 17 } Expiration Date December 1992 FORMFEED[Page 32] RFC DRAFT June 1992 ---Author's note: ---bisRDC table ---Table Format: --- (The description of this Table format will be added once --- some general help on the RDC problems. --- -- A tenative Table format might be: -- -- bisRdcIndex BisRdcRdi SetId RDI1 RDI2 RDI3 RDI4 RDI5 -- -- The bisRDC has RdcGroup ASN.1 definition of: --- SEQUENCE { confed Rdcsetid, members SET OF Rdi } --- ---The idrpRdcConfigTable entry also comes from the same --- RdcGroup. If this table looks good, please coment --- --- --bisPeerSnpaTable for all BIS peers -- (note this a kludge to get ISO bisPeerSNPAs into SNMP format) --Table format: -- --Index# BisRouterID SNPA1 SNPA2 SNPA3 SNPA4 SNPA5 bisPeerSnpaTable OBJECT-TYPE SYNTAX SEQUENCE OF BisPeerSnpaEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The Table of SNPA address per remote peer. (ISO IDRP attribute: bisPeerSNPAs)" ::={idrp 21} --bisPeerSNPA is ASN.1 SET OF but it --is a table, so it needs to be expanded --for SNMP bisPeerSnpaEntry OBJECT-TYPE SYNTAX BisPeerSnpaEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table entry to list the SNPAs per BIS peer. " INDEX { bisPeerSnpaIndex } ::= { bisPeerSnpaTable 1 } idrpInternalBisEntry :: = SEQUENCE { Expiration Date December 1992 FORMFEED[Page 33] RFC DRAFT June 1992 bisPeerSnpaIndex INTEGER, bisRouterId INTEGER, bisPeerSNPA1 OCTET-STRING, bisPeerSNPA1 OCTET-STRING, bisPeerSNPA2 OCTET-STRING, bisPeerSNPA3 OCTET-STRING, bisPeerSNPA4 OCTET-STRING, bisPeerSNPA5 OCTET-STRING } bisPeerSNPAIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Index into BisPeerSNPATable so SNMP can walk through table." ::= { bisPeeerSNPAEntry 1 } bisRouterId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "RouterID of bisPeer that SNPA table is for." ::= { bisPeerSNPAEntry 2 } bisPEERSNPA1 OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION "1st SNPA on this remote Bis Router." ::= { bisPeerSNPAEntry 3 } bisPEERSNPA2 OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION Expiration Date December 1992 FORMFEED[Page 34] RFC DRAFT June 1992 "1st SNPA on this remote Bis Router." ::= { bisPeerSNPAEntry 4 } bisPEERSNPA3 OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION "1st SNPA on this remote Bis Router." ::= { bisPeerSNPAEntry 5 } bisPEERSNPA4 OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION "1st SNPA on this remote Bis Router." ::= { bisPeerSNPAEntry 6 } bisPEERSNPA5 OBJECT-TYPE SYNTAX OCTET-STRING ACCESS read-only STATUS mandatory DESCRIPTION "1st SNPA on this remote Bis Router." ::= { bisPeerSNPAEntry 7 } ---- ---Actions bisPeerAdminStatus OBJECT-TYPE SYNTAX INTEGER {start(1), stop(0)} ACCESS read-write STATUS mandatory DESCRIPTION "The desired state of the idrp connection. A transition from 'stop' to 'start' will cause the idrp Start Event to be generated. A transition from 'start' to 'stop' will cause the idrp Stop Event to be generated. This parameter can be used to restart BGP peer connections. Care should be used in providing write access to this object without adequate authentication." ::= { bgpPeerEntry 17 } ---Traps -- IP only would leave the idrpRemoteNET as Null OCTET-STRING idrpErrorBISPDUsent TRAP-TYPE ENTERPRISE { idrp } Expiration Date December 1992 FORMFEED[Page 35] RFC DRAFT June 1992 VARIABLES { idrpRemoteBisID, idrpRemoteBisIpAddress, idrpRemoteBisNET, BispduErrorcode, BispduErrorSubCode, BISpduErrorInfo } DESCRIPTION "This trap is genererated when a BISPDU is received with an error in its format. (ISO NOTIFICIATION communicationAlarms notification with errorBISPDUsent text) [No BGP Trap equivalent]" ::= 1 idrpOpenBISpduRDCError TRAP-TYPE ENTERPRISE { idrp } VARIABLES { idrpRemoteBisID, idrpRemoteBisIpAddress, idrpRemoteBisNET, BispduErrorcode, idrpRdcConfigTableId, bisRDCTableId, } DESCRIPTION "This trap is generated when an OPEN BISPDU is received from another BIS in the same routeing domain, and the remote BIS is not a member of the identically same confederations as teh local BIS. (ISO NOTIFICIATION communicationAlarms notification with OpenBISpduRDCError text) [No BGP Trap equivalent]" ::=2 idrpCorruptAdjRIBIn TRAP-TYPE ENTERPRISE { idrp } VARIABLES { idrpRemoteBisID, idrpRemoteBisIpAddress, idrpRemoteBisNET, } DESCRIPTION "This trap is generated when the local BIS using a local method detects the the Adj-Rib has found an error. Al Adj-RIBs-In are being purged. (ISO NOTIFICIATION communicationAlarms notification with CorruptAdjRibIn text) [No BGP Trap equivalent]" ::=3 idrpPacketBomb TRAP-TYPE ENTERPRISE { idrp } Expiration Date December 1992 FORMFEED[Page 36] RFC DRAFT June 1992 VARIABLES { idrpRemoteBisID, idrpRemoteBisIpAddress, idrpRemoteBisNET, idrpRemoteBisRdi, idrpRemoteBisRdcConfigTableId, } DESCRIPTION "This trap is generated when the local BIS has been presented with a BISPDU whose source is not one of the BISs adjacent to the local BIS. Such BISPDUs are rejected by the local BIS. (ISO NOTIFICIATION communicationAlarms notification with PacketBomb text) [No BGP Trap equivalent]" ::= 4 6. IDRP for IP only MIB In the IDRP for IP only MIB, the IDRP loc-Rib and IDRP FIB will be defined. Because most of the idrp configuration information required for the local BIS or BIS Peers are common between the IDRP for IP and OSI IDRP, these definitions have been placed in the common MIB portion. An implementation of IDRP for IP, should leave the indicated ISO variables out. The table below gives a summary of these OSI variables. A dual IDRP implementations will just need to implement the full MIB described in Section 5.2. In addition, the IDRP for IP MIB must provide a means to read the IDRP routing tables. Editor's note: I need help defining what goes here The BGP MIB has the BGPRcvAttrTable. This Table gives the user a way to get via SNMP the BGP pathway information. The pathway information in the BGP table is: 1.) BGP Peer information Received From 2.) BGP Path Destination IP Address 3.) Origin of Path Info 4.) AS Path 5.) Next_HOP Expiration Date December 1992 FORMFEED[Page 37] RFC DRAFT June 1992 6.) Metric There are the following logical IDRP Information Bases: - Adj-Rib-In number: one per remote BIS peer index by: NET of adjacent BIS Rib-Attributes Route-ID contains: Path Attributes NLRI - loc-RIB number: one per local BIS index by: Rib-Atts contains: Path Attributes NLRI - Adj-Rib-Out number: one per remote BIS peer index by: NET of adjacent BIS Rib-Attributes Route-ID contains: Path Attributes NLRI - FIB number: one per local BIS index by: IP Address of next Hop BIS Output SNPA (interface) of local BIS Input SNPA (interface) of next hop BIS How the implementor turns these indications into code may affect how these logical tables turn into real tables. For the current time, only the loc-RIB and FIB will be encoded in the MIB. If sufficient needs for the Adj-Rib-In and Adj-Rib-Out will be encode. These local-RIB Reachability Table will have the following MIB components: Expiration Date December 1992 FORMFEED[Page 38] RFC DRAFT June 1992 1.) BisPeerID of Adjacent BIs 2.) RibAttributeType 3.) RibAttributeValue 4.) route-id 5.) IP NLRI - length of Prefix IP Prefix 5.) external-info 6.) rd_path Set or Sequence of RDIs with RDC markers needs to be encoded. 5.) Next_Hop_Table IP Address SNPA addresses for next hop 6.) DIST_LIST_INCL SET of RDIs 7.) DIST_LIST_EXCL SET of RDIs 8.) MULTI_EXIT_DISC value of MULTI_EXIT_DISC 9.) Local_PREF local preference value 10.) Hierarchial_Recording 11.) RD_HOP_COUNT The IDRP for FIB will contain the following MIB components: 1.)Rib Att Type (Default, delay, error, expense, sourceSpecificQOS, destinationSpecificQOS, SourceSpecificSecurity, DestinationSpecificSecurity) 2.) Rib Att Value 3.) IP NLRI - length of Prefix IP Prefix 4.) Output SNPA of local BIS 5.) Input SNPA of next hop BIS Expiration Date December 1992 FORMFEED[Page 39] RFC DRAFT June 1992 7.) Appendix 1 - IDRP for IP Only GDMO 8. Acknowledgements The IDRP for IP working group, and specifically the following individuals: Yakov Rekhter, IBM 9. References [1] ISO/IEC DIS 10747 - Information Processing Systems - Telecommunications and Information Exchange between Systems - Protocol for Exchange of Inter-domain Routeing Information among Intermediate Systems to Support Forwarding of ISO 8473 PDUs, 1992. [2] Hares, S; IDRP for IP; Internet Draft [3] Hares, S; IDRP Document Family ; Internet Draft [4] ISO 8473 - Information Processing Systems - Data Communications - Protocol for Providing the Connectionless-mode Network Service, 1988. [5] Rose M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based internets", RFC 1155, Performance Systems International, Hughes LAN Systems, May 1990. [6] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions", RFC 1212, Performance Systems International, Hughes LAN Systems, March 1991. [7] McCloghrie K., and M. Rose, "Management Information Base for Network Management of TCP/IP-based internets", RFC 1156, Hughes LAN Systems, Performance Systems International, May 1990. [8] McCloghrie K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets", RFC 1213, Performance Systems International, March 1991. [9] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", RFC 1157, SNMP Research, Performance Systems International, Performance Systems International, MIT Laboratory for Computer Science, May 1990. [10] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), Expiration Date December 1992 FORMFEED[Page 40] RFC DRAFT June 1992 International Organization for Standardization, International Standard 8824, December 1987. [11] Information processing systems - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Notation One (ASN.1), International Organization for Standardization, International Standard 8825, December 1987. [12] Rose, M., Editor, "A Convention for Defining Traps for use with the SNMP", RFC 1215, Performance Systems International, March 1991. 10. Security Considerations Security issues are not discussed in this memo. 11.) Author's addresses: Susan Hares MERIT Inc. 1071 Beal Avenue Ann Arbor, MI 48103-2112 phone: (313)936-2095 email: skh@merit.edu Expiration Date December 1992 FORMFEED[Page 41]