IDPR Working Group R.A. Woodburn, Editor Internet Draft SAIC March 1992 Definitions of Managed Objects for the Inter- Domain Policy Routing Protocol (Version 1) Status of this Memo This draft document will be submitted to the RFC editor as an experimental extension to the SNMP MIB. Distribution of this memo is unlimited. Please send comments to the IDPR Working Group (idpr-wg@bbn.com). Table of Contents Status of this Memo 1 Table of Contents 1 1. Abstract 2 2. Historical Perspective 2 3. Objects 3 3.1. Format of Definitions 4 4. Overview 4 4.1 Domain Structure 4 4.2 IDPR Functions 5 4.3 The IDPR MIB 8 5. Definitions 9 5.1 IDPR System Object Definitions 10 5.2 IDPR CMTP Object Definitions 11 5.3 IDPR VGP Object Definitions 14 5.4 IDPR RID Object Definitions 23 5.5 IDPR RTTREQ Object Definitions 29 5.6 IDPR PSP Object Definitions 30 5.7 IDPR Data Object Definitions 40 5.8 IDPR Address Mapping Table Object Definitions 42 5.9 Source Policy Table 46 5.10 Transit Policy Table 47 6. Acknowledgements 50 7. References 50 8. Editor's Address 51 IDPR WG Page 1 Internet Draft IDPR MIB March 1992 1. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Inter-Domain Policy Routing Protocol [10,11]. This memo does not specify a standard for the Internet community. However, after experimentation, if sufficient consensus is reached in the Internet community, then a subsequent revision of this document may be incorporated into the Internet-standard MIB. 2. Historical Perspective As reported in RFC 1052, IAB Recommendations for the Development of Internet Network Management Standards [1], a two-prong strategy for network management of TCP/IP-based internets was undertaken. In the short-term, the Simple Network Management Protocol (SNMP), defined in RFC 1067, was to be used to manage nodes in the Internet community. In the long-term, the use of the OSI network management framework was to be examined. Two documents were produced to define the management information: RFC 1065, which defined the Structure of Management Information (SMI), and RFC 1066, which defined the Management Information Base (MIB). Both of these documents were designed so as to be compatible with both the SNMP and the OSI network management framework. This strategy was quite successful in the short-term: Internet- based network management technology was fielded, by both the research and commercial communities, within a few months. As a result of this, portions of the Internet community became network manageable in a timely fashion. As reported in RFC 1109, Report of the Second Ad Hoc Network Management Review Group [2], the requirements of the SNMP and the OSI network management frameworks were more different than anticipated. As such, the requirement for compatibility between the SMI/MIB and both frameworks was suspended. This action permitted the operational network management framework, based on the SNMP, to respond to new operational needs in the Internet community by producing MIB-II. In May of 1990, the core documents were elevated to "Standard Protocols" with "Recommended" status. As such, the Internet- IDPR WG Page 2 Internet Draft IDPR MIB March 1992 standard network management framework consists of: Structure and Identification of Management Information for TCP/IP-based internets, RFC 1155 [3], which describes how managed objects contained in the MIB are defined; Management Information Base for Network Management of TCP/IP-based internets, which describes the managed objects contained in the MIB, RFC 1156 [4]; and, the Simple Network Management Protocol, RFC 1157 [5], which defines the protocol used to manage these objects. Consistent with the IAB directive to produce simple, workable systems in the short- term, the list of managed objects defined in the Internet- standard MIB was derived by taking only those elements which are considered essential. However, the SMI defined three extensibility mechanisms: one, the addition of new standard objects through the definitions of new versions of the MIB; two, the addition of widely-available but non-standard objects through the experimental subtree; and three, the addition of private objects through the enterprises subtree. Such additional objects can not only be used for vendor-specific elements, but also for experimentation as required to further the knowledge of which other objects are essential. This memo defines extensions to the MIB using the second method. It contains definitions of managed objects used for experimentation. After experimentation, if sufficient consensus is reached in the Internet community, then a subsequent revision of this memo may be placed in the Internet-standard MIB. 3. 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) [7] 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 [3] purposely restricts the ASN.1 constructs which may be used. These restrictions are explicitly made for simplicity. IDPR WG Page 3 Internet Draft IDPR MIB March 1992 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 [8], subject to the additional requirements imposed by the SNMP. 3.1. Format of Definitions Section 6 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 [9]. 4. Overview The Inter-Domain Policy Routing Protocol (IDPR) is a routing protocol for use between Administrative Domains. The objective of IDPR is to construct routes between source and destination administrative domains that provide user traffic with the service requested within the constraints stipulated by the domains transited. With IDPR, we introduce a new network-layer Internet protocol based on source-specified routing between administrative domains and a new Internet addressing structure based on an administrative domain hierarchy. However, for IDPR version 1, we recommend implementing a proper subset of the complete architecture proposed in [11]. The recommended subset provides the majority of the features of IDPR and comprises the virtual gateway protocol, the domain status distribution protocol, the route synthesis procedure, the path setup protocol, and the message forwarding procedure. 4.1 Domain Structure The IDPR architecture has been designed to accommodate an Internet with tens of thousands of administrative domains collectively containing hundreds of thousands of local networks. Inter-domain policy routes are constructed using information about the policy attributes of, and the connectivity between, administrative domains. The intra-domain details, gateways and networks traversed, of an inter-domain policy route are the IDPR WG Page 4 Internet Draft IDPR MIB March 1992 responsibility of intra-domain routing and are thus outside the scope of inter-domain routing. An Administrative Domain (AD) is a collection of contiguous networks managed by a single administrative authority that places policy restrictions on transit traffic, defines policy requirements for locally-generated traffic, and selects the intra-domain addressing schemes and routing procedures. Each administrative domain has a unique identity within the Internet. Virtual Gateways (VGs) are the only IDPR-recognized connecting points between adjacent administrative domains. Each virtual gateway is a collection of directly-connected policy gateways in two adjacent domains, whose existence has been sanctioned by the authorities in both domains. The domain authorities may agree to establish more than one virtual gateway between the two domains. For each such virtual gateway, the two authorities together assign a virtual gateway identifier, unique within the set of virtual gateways connecting the two domains. To produce a virtual gateway identifier unique within its domain, the domain authority concatenates the mutually assigned identifier together with the adjacent domain's identifier. Policy Gateways (PGs) are the physical gateways within a virtual gateway. Each policy gateway enforces policy restrictions on transit traffic as stipulated by the domain's administrative authority. A single policy gateway may belong to multiple virtual gateways. Within a domain, two policy gateways are neighbors if they are in different virtual gateways. Within a virtual gateway, two policy gateways are peers if they are in the same domain and are adjacent if they are in different domains. Adjacent policy gateways are directly connected if they are the only Internet-addressable entities attached to the connecting medium. Note that this definition implies that not only point- to-point links but also networks may serve as direct connections between adjacent policy gateways. The authority for a given domain assigns to each of its policy gateways an identifier, unique within that domain. 4.2 IDPR Functions Inter-domain policy routing comprises the following functions: 1. Collecting and distributing connectivity and policy information pertaining to transit domains. IDPR WG Page 5 Internet Draft IDPR MIB March 1992 2. Synthesizing and selecting policy routes based on the connectivity and policy information associated with the transit domains and on the service requirements associated with the source. 3. Setting up paths across the Internet, using the policy routes synthesized. 4. Forwarding messages across and between administrative domains along the established paths. 5. Maintaining databases of transit domain connectivity and policy, inter-domain policy routes, configured global information such as network- address/domain-identifier mappings, and configured local information such as the policy gateways within an administrative domain. As described in [11], a source domain controls synthesis and selection of policy routes to destination domains, while intermediate domains on a specific source-selected policy route determine whether or not the route is consistent with their transit policies. The route synthesis procedure uses domain status information in the form of advertised transit policies and adjacencies, to generate policy routes between source and destination domains. The source then selects policy routes from those provided by route synthesis, according to its own service requirements. Policy routes require a path setup procedure during which policy gateways in intermediate domains verify whether or not they will carry traffic travelling along the path, and contingent upon route acceptance, form an association between the path identifier and the previous and next policy gateways on the path. Following path setup, intermediate policy gateways use the path identifier carried in data messages to forward data traffic along the path. Several different entities are responsible for performing the IDPR functions. Policy gateways collect and distribute status information about their administrative domains, participate in path setup, and forward data messages along established paths. Path agents act on behalf of hosts to select policy routes and to set up and manage paths. Special-purpose servers maintain the routing databases which are distributed with partial redundancy throughout the Internet. Each special-purpose server within an administrative domain has a unique identifier, assigned by the IDPR WG Page 6 Internet Draft IDPR MIB March 1992 domain authority. Route servers are responsible for both the domain status (connectivity and policy) database and the route database. Also, route servers synthesize policy routes using domain status information and source traffic requirements. Name servers are responsible for the domain-name/network- address/domain-identifier database. Configuration servers are responsible for databases of configured information that apply to policy gateways, path agents, and route servers in the given administrative domain and inform these entities of configuration changes. Both route servers and name servers are organized hierarchically, where a server's position in the hierarchy determines the extent of its database. At the top are global servers that maintain information about all Internet domains; at the bottom are local servers that maintain information about a particular domain, its neighbors, and other frequently visited domains, this last type of information usually obtained from higher-level servers. Hierarchical database organization releases hosts and gateways from the burden of maintaining information about large portions of the Internet, most of which they will never use. In IDPR version 1, each policy gateway performs all IDPR functions, including those of the path agent and the special- purpose servers. Aggregating all routing functions into policy gateways simplifies implementation; one need only install IDPR protocols in policy gateways. Moreover, it simplifies communication between routing functions, as all functions reside within each policy gateway. We also note that IDPR version 1 supports only a flat route server hierarchy; each policy gateway contains a global route server. We are presently investigating approaches to making efficient use of hierarchically-organized routing information. Given the size of the current Internet (on the order of 100 administrative domains) and the type of policies supported in IDPR version 1 (access restrictions only), we believe that policy gateways have adequate processing and memory resources to synthesize policy routes and set up paths as well as to forward messages and participate in intra-domain routing. Meanwhile, we are developing autonomous route servers and configuration servers, separate from policy gateways, so that IDPR can accommodate larger numbers of administrative domains and policies in the future. IDPR WG Page 7 Internet Draft IDPR MIB March 1992 4.3 The IDPR MIB These objects are used to control and manage an IDPR [11] implementation. This MIB is broken into 10 sections. The first section describes system variables. The remaining sections describe tables and individual IDPR sub-protocols. IDPR WG Page 8 -- Internet Draft IDPR MIB March 1992 5. Definitions RFCxxxx-MIB DEFINITIONS ::= BEGIN IMPORTS experimental, IpAddress, Counter, TimeTicks FROM RFC1155-SMI OBJECT-TYPE FROM RFC-1212; -- This MIB module uses the extended OBJECT-TYPE macro as -- defined in [9] The following types are included for -- enhancing readability: -- The BitField type is an OCTET STRING of four octets. The -- first octet contains bit positions 0-7. The second -- octet contains bit positions 8-15. The third octet -- contains bit positions 16-23. The fourth octet contains -- bit positions 24-31. The values of the octets depend -- upon the bits that are set that are being represented. BitField ::= OCTET STRING (Size 4) idpr OBJECT IDENTIFIER ::= { experimental 28 } -- IDPR WG Page 9 -- Internet Draft IDPR MIB March 1992 -- 5.1 IDPR System Object Definitions idprsys OBJECT IDENTIFIER ::= { idpr 1 } idprAD OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The AD identifier for the entity" ::= { idprsys 1 } idprId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The identifier of the entity" ::= { idprsys 2 } idprType OBJECT-TYPE SYNTAX BitField ACCESS read-only STATUS mandatory DESCRIPTION "The entity type, RS, or PG, or both. Bit position 0 PG flag Bit position 1 RS flag" ::= { idprsys 3 } idprADRep OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The identifier of the AD Representative as viewed from this entity." ::= { idprsys 4 } -- IDPR WG Page 10 -- Internet Draft IDPR MIB March 1992 idprUpTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "The amount of time since IDPR was last initialized in TimeTicks." ::= { idprsys 5 } -- 5.2 IDPR CMTP Object Definitions idprcmtp OBJECT IDENTIFIER ::= { idpr 2 } idprcmtpVer OBJECT-TYPE SYNTAX BitField ACCESS read-only STATUS mandatory DESCRIPTION "The CMTP versions supported by this PG. Bit Position 0 == Version 1 Bit Position 1 == Version 2 ...and so on... Bit Position n == Version n+1 where n <= 31." ::= { idprcmtp 1 } idprcmtpIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of CMTP received by the entity." ::= { idprcmtp 2 } -- IDPR WG Page 11 -- Internet Draft IDPR MIB March 1992 idprcmtpOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of CMTP sent by the entity." ::= { idprcmtp 3 } idprcmtpRetries OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of CMTP retransmissions." ::= { idprcmtp 4 } idprcmtpAckIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of CMTP ACKs received." ::= { idprcmtp 5 } idprcmtpAckOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of CMTP ACKs sent." ::= { idprcmtp 6 } idprcmtpNakIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of CMTP NAKs received." ::= { idprcmtp 7 } -- IDPR WG Page 12 -- Internet Draft IDPR MIB March 1992 idprcmtpNakOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of CMTP NAKs." ::= { idprcmtp 8 } idprcmtpTimeouts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of CMTP Timeouts." ::= { idprcmtp 9 } idprcmtpUnkAuths OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of CMTP protocol messages received which contained an unrecognized authentication type." ::= { idprcmtp 10 } idprcmtpUnkProtos OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of CMTP protocol messages received which contained an invalid IDPR sub- protocol number." ::= { idprcmtp 11 } -- IDPR WG Page 13 -- Internet Draft IDPR MIB March 1992 idprcmtpBadAuths OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of CMTP protocol messages received for which authentication failed." ::= { idprcmtp 12 } idprcmtpBadLengths OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of CMTP protocol messages received which contained invalid length fields." ::= { idprcmtp 13 } idprcmtpBadTimes OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of CMTP protocol messages received which contained bad timestamps." ::= { idprcmtp 14 } -- 5.3 IDPR VGP Object Definitions idprvgp OBJECT IDENTIFIER ::= { idpr 3 } idprvgpPer OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The default value for the UpDown protocol interval (sec)." ::= { idprvgp 1 } -- IDPR WG Page 14 -- Internet Draft IDPR MIB March 1992 idprvgpPGInt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The retransmission interval in seconds for acknowledged VGP message types." ::= { idprvgp 2 } idprvgpPGRet OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of retransmissions to be sent for acknowledged VGP message types before timing them out" ::= { idprvgp 3 } idprvgpSTSInt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The delay in seconds from the time a VG representative receives a PG connect message until it issues a PG status message for that VG" ::= { idprvgp 4 } idprvgpUpDownIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Up/Down messages received." ::= { idprvgp 5 } -- IDPR WG Page 15 -- Internet Draft IDPR MIB March 1992 idprvgpUpDownOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Up/Down messages sent." ::= { idprvgp 6 } idprvgpPGConIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of PG Connect messages received." ::= { idprvgp 7 } idprvgpPGConOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of PG Connect messages sent." ::= { idprvgp 8 } idprvgpPGPlcyIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of PG Policy messages received." ::= { idprvgp 9 } idprvgpPGPlcyOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of PG Policy messages sent." ::= { idprvgp 10 } -- IDPR WG Page 16 -- Internet Draft IDPR MIB March 1992 idprvgpVGConIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of VG Connect messages received." ::= { idprvgp 11 } idprvgpVGConOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of VG Connect messages sent." ::= { idprvgp 12 } idprvgpVGPlcyIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of VG Policy messages received." ::= { idprvgp 13 } idprvgpVGPlcyOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of VG Policy messages sent." ::= { idprvgp 14 } idprvgpPGTab OBJECT-TYPE SYNTAX SEQUENCE OF IdprPGEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The table of other known Policy Gateways." ::= { idprvgp 15 } -- IDPR WG Page 17 -- Internet Draft IDPR MIB March 1992 idprPGEntry OBJECT-TYPE SYNTAX IdprPGEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Information for a single Pg." INDEX { idprPGAD, idprPGId } ::= { idprvgpPGTab 1 } IdprPGEntry ::= SEQUENCE { idprPGAD INTEGER, idprPGId INTEGER, idprPGFlags BitField, idprPGTrans Counter, idprPGUpDownPer INTEGER } idprPGAD OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The AD identifier for the PG." ::= { idprPGEntry 1 } idprPGId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The IDPR ID for the PG." ::= { idprPGEntry 2 } -- IDPR WG Page 18 -- Internet Draft IDPR MIB March 1992 idprPGFlags OBJECT-TYPE SYNTAX BitField ACCESS read-only STATUS mandatory DESCRIPTION "The type of entity and its status. Bit Position 0 == Status - A '1' in this bit position indicates the PG is UP, a '0' indicates that it is DOWN. Bit Position 1 == Peer - the entity is a peer PG Bit Position 2 == Neighbor - the entity is a neighbor PG Bit Position 3 == Adjacent - the entity is an adjacent PG" ::= { idprPGEntry 3 } idprPGTrans OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of times the PG has transitioned state." ::= { idprPGEntry 4 } idprPGUpDownPer OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The negotiated interval for Up/Down messages if any." ::= { idprPGEntry 5 } idprvgpVGTab OBJECT-TYPE SYNTAX SEQUENCE OF IdprVGEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The table of known VGs" ::= { idprvgp 16 } -- IDPR WG Page 19 -- Internet Draft IDPR MIB March 1992 idprVGEntry OBJECT-TYPE SYNTAX IdprVGEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Information for a single VG." INDEX { idprVGAdj, idprVGId } ::= { idprVGTab 1 } IdprVGEntry ::= SEQUENCE { idprVGAdj INTEGER, idprVGId INTEGER, idprVGFlags Counter, idprVGVGRep INTEGER } idprVGAdj OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The Adjacent AD of the VG." ::= { idprVGEntry 1 } idprVGId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The ID of the VG." ::= { idprVGEntry 2 } -- IDPR WG Page 20 -- Internet Draft IDPR MIB March 1992 idprVGFlags OBJECT-TYPE SYNTAX BitField ACCESS read-only STATUS mandatory DESCRIPTION "The status of the entity Bit Position 0 == Status - A '1' in this bit position indicates the PG is UP, a '0' indicates that it is DOWN." ::= { idprVGEntry 3 } idprVGVGRep OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The PG acting as the VG representative for the VG as seen by this PG." ::= { idprVGEntry 4 } idprvgpPGMap OBJECT-TYPE SYNTAX SEQUENCE OF IdprPGMapEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The Mapping of PGs to VGs" ::= { idprvgp 17 } idprPGMapEntry OBJECT-TYPE SYNTAX IdprPGMapEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Information for a single VG." INDEX { idprPGMapAD, idprPGMapId } ::= { idprvgpPGMap 1 } -- IDPR WG Page 21 -- Internet Draft IDPR MIB March 1992 IdprPGMapEntry ::= SEQUENCE { idprPGMapAD INTEGER, idprPGMapId INTEGER, idprPGMapAdj INTEGER, idprPGMapVG INTEGER } idprPGMapAD OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The AD of the PG." ::= { idprPGMapEntry 1 } idprPGMapId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The Id of the PG." ::= { idprPGMapEntry 2 } idprPGMapAdj OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The adjacent AD of the VG." ::= { idprPGMapEntry 3 } -- IDPR WG Page 22 -- Internet Draft IDPR MIB March 1992 idprPGMapVG OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The Id of the VG." ::= { idprPGMapEntry 4 } -- 5.4 IDPR RID Object Definitions idprrid OBJECT IDENTIFIER ::= { idpr 4 } idprridReqInt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The retransmission interval in seconds for update requests" ::= { idprrid 1 } idprridReqRet OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of retransmissions for update requests before timing out the request" ::= { idprrid 2 } idprridPer OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The interval in seconds between periodic configuration updates." ::= { idprrid 3 } -- IDPR WG Page 23 -- Internet Draft IDPR MIB March 1992 idprridInt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The retransmission interval in seconds for configuration and dynamic updates at the time they are sent." ::= { idprrid 4 } idprridRet OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of retransmissions for configuration and dynamic updates from the time of the first transmission until the update is timed out." ::= { idprrid 5 } idprridTimNew OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The maximum wait time in seconds before generating a 'correcting' update as a result of receiving an old update." ::= { idprrid 6 } idprridLif OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The lifetime of received updates in seconds." ::= { idprrid 7 } -- IDPR WG Page 24 -- Internet Draft IDPR MIB March 1992 idprridConfigIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Config updates received from the Entity." ::= { idprrid 8 } idprridConfigOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Config Updates sent to the Entity." ::= { idprrid 9 } idprridDynamicIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Dynamic Updates received from the Entity." ::= { idprrid 10 } idprridDynamicOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Dynamic Updates sent to the Entity." ::= { idprrid 11 } -- IDPR WG Page 25 -- Internet Draft IDPR MIB March 1992 idprridReqIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Requests received from the Entity." ::= { idprrid 12 } idprridReqOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Requests sent to the Entity." ::= { idprrid 13 } idprridRSTab OBJECT-TYPE SYNTAX SEQUENCE OF IdprRSEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The table of other known Route Servers." ::= { idprrid 14 } idprRSEntry OBJECT-TYPE SYNTAX IdprRSEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Information for a single RS." INDEX { idprRSAD, idprRSId } ::= { idprridRSTab 1 } -- IDPR WG Page 26 -- Internet Draft IDPR MIB March 1992 IdprRSEntry ::= SEQUENCE { idprRSAD INTEGER, idprRSId INTEGER, idprRSFlags BitField, idprRSLastSend TimeTicks, idprRSLastRecv TimeTicks } idprRSAD OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The AD identifier for the RS." ::= { idprRSEntry 1 } idprRSId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The identifier for the RS." ::= { idprRSEntry 2 } -- IDPR WG Page 27 -- Internet Draft IDPR MIB March 1992 idprRSFlags OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The send/advert status of RS. Bit Position 0 == Send - A '1' indicates that the RS is included in the list of RSs to which updates are sent. Bit Position 1 == Advert - A '1' indicates that the RS is included in the list of RSs which are advertised in updates from this AD." ::= { idprRSEntry 3 } idprRSLastSend OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "The last time an update was sent to this RS." ::= { idprRSEntry 4 } idprRSLastRecv OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "The last time an update was received from this RS." ::= { idprRSEntry 5 } -- IDPR WG Page 28 -- Internet Draft IDPR MIB March 1992 -- 5.5 IDPR RTTREQ Object Definitions idprrtreq OBJECT IDENTIFIER ::= { idpr 5 } idprrtreqReqIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Route Requests received." ::= { idprrtreq 1 } idprrtreqResps OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of positive Route Responses sent" ::= { idprrtreq 2 } idprrtreqNegResps OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of negative Route Responses sent" ::= { idprrtreq 3 } -- IDPR WG Page 29 -- Internet Draft IDPR MIB March 1992 -- 5.6 IDPR PSP Object Definitions idprpsp OBJECT IDENTIFIER ::= { idpr 6 } idprpspInt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The retransmission interval for setup messages in seconds" ::= { idprpsp 1 } idprpspRet OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of retransmissions for setup messages before they are timed out" ::= { idprpsp 2 } idprpspSetupIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Setup messages received from the PG." ::= { idprpsp 3 } idprpspSetupOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Setup messages sent to the PG." ::= { idprpsp 4 } -- IDPR WG Page 30 -- Internet Draft IDPR MIB March 1992 idprpspTeardownIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Teardown messages received from the PG." ::= { idprpsp 5 } idprpspTeardownOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Teardown messages sent to the PG." ::= { idprpsp 6 } idprpspRefuseIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Refuse messages received from the PG." ::= { idprpsp 7 } idprpspRefuseOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Refuse messages sent to the PG." ::= { idprpsp 8 } -- IDPR WG Page 31 -- Internet Draft IDPR MIB March 1992 idprpspAcceptIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Accept messages received from the PG." ::= { idprpsp 9 } idprpspAcceptOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Accept messages sent to the PG." ::= { idprpsp 10 } idprpspRepairIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Repair messages received." ::= { idprpsp 11 } idprpspRepairOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Repair messages sent." ::= { idprpsp 12 } idprpspErrorIns OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Error messages received from the PG." ::= { idprpsp 13 } -- IDPR WG Page 32 -- Internet Draft IDPR MIB March 1992 idprpspErrorOuts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Setup Error messages sent to the PG." ::= { idprpsp 14 } idprpspPathTab OBJECT-TYPE SYNTAX SEQUENCE OF IdprPathEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The table IDPR paths." ::= { idprpsp 15 } idprPathEntry OBJECT-TYPE SYNTAX IdprPathEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Information for a single IDPR path." INDEX { idprPathAD, idprPathEnt, idprPathId } ::= { idprpspPathTab 1 } -- IDPR WG Page 33 -- Internet Draft IDPR MIB March 1992 IdprPathEntry ::= SEQUENCE { idprPathAD INTEGER, idprPathEnt INTEGER, idprPathId INTEGER, idprPathDst INTEGER, idprPathNextAD INTEGER, idprPathNextEnt INTEGER, idprPathPrevAD INTEGER, idprPathPrevEnt INTEGER, idprPathNextVGAD INTEGER, idprPathNextVGId INTEGER, idprPathPrevVGAD INTEGER, idprPathPrevVGId INTEGER, idprPathState INTEGER, idprPathFlows INTEGER, idprPathMsgs Counter, idprPathMsgsMax INTEGER, idprPathBytes Counter, idprPathBytesMax INTEGER, idprPathExpire INTEGER, idprPathAuth INTEGER, idprPathVer BitField, idprPathTos OCTET STRING (Size 8), idprPathUCI -- IDPR WG Page 34 -- Internet Draft IDPR MIB March 1992 OCTET STRING (Size 8) } idprPathAD OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The Source AD for this path." ::= { idprPathEntry 1 } idprPathEnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The Source Entity identifier for this path." ::= { idprPathEntry 2 } idprPathId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The unique identifier for this path." ::= { idprPathEntry 3 } idprPathDst OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The final destination AD for this path." ::= { idprPathEntry 4 } -- IDPR WG Page 35 -- Internet Draft IDPR MIB March 1992 idprPathNextAD OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The AD of the next hop PG." ::= { idprPathEntry 5 } idprPathNextEnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The ID of the next hop PG." ::= { idprPathEntry 6 } idprPathPrevAD OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The AD of the prev hop PG." ::= { idprPathEntry 7 } idprPathPrevEnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The ID of the prev hop PG." ::= { idprPathEntry 8 } idprPathNextVGAD OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The AD of the next hop VG." ::= { idprPathEntry 9 } -- IDPR WG Page 36 -- Internet Draft IDPR MIB March 1992 idprPathNextVGId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The ID of the next hop VG." ::= { idprPathEntry 10 } idprPathPrevVGAD OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The AD of the prev hop VG." ::= { idprPathEntry 11 } idprPathPrevVGId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The ID of the prev hop VG." ::= { idprPathEntry 12 } idprPathState OBJECT-TYPE SYNTAX INTEGER { idle (1), -- the path is no longer being used start (2), -- a setup request has been received setup (3), -- a setup has been sent acceptwait (4), -- an ACK has been received active (5), -- the accept has been received dying (6) -- teardown has been received/sent } ACCESS read-only STATUS mandatory DESCRIPTION "The current state of the path.." ::= { idprPathEntry 13 } -- IDPR WG Page 37 -- Internet Draft IDPR MIB March 1992 idprPathFlows OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of data messages forwarded on this path." ::= { idprPathEntry 14 } idprPathMsgs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of data messages forwarded on this path." ::= { idprPathEntry 15 } idprPathMsgsMax OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The maximum allowable number of data messages forwarded on this path." ::= { idprPathEntry 16 } idprPathBytes OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of bytes of data forwarded on this path." ::= { idprPathEntry 17 } -- IDPR WG Page 38 -- Internet Draft IDPR MIB March 1992 idprPathBytesMax OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The maximum allowable number of bytes of data forwarded on this path." ::= { idprPathEntry 18 } idprPathExpire OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of seconds remaining before this path expires." ::= { idprPathEntry 19 } idprPathAuth OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The authentication used for this path." ::= { idprPathEntry 20 } idprPathVer OBJECT-TYPE SYNTAX BitField ACCESS read-only STATUS mandatory DESCRIPTION "The version of the encapsulation protocol expected for this path. Bit Position 0 == Version 1 Bit Position 1 == Version 2 ...and so on... Bit Position n == Version n+1 where n <= 31." ::= { idprPathEntry 21 } -- IDPR WG Page 39 -- Internet Draft IDPR MIB March 1992 idprPathTos OBJECT-TYPE SYNTAX OCTET STRING (Size 8) ACCESS read-only STATUS mandatory DESCRIPTION "The type of services associated with this path. Each octet in the string represents a different type of service supported." ::= { idprPathEntry 22 } idprPathUCI OBJECT-TYPE SYNTAX OCTET STRING (Size 8) ACCESS read-only STATUS mandatory DESCRIPTION "The User Class Identifiers associated with this path. Each octet of the string represents a different supported UCI." ::= { idprPathEntry 23 } -- 5.7 IDPR Data Object Definitions idprdata OBJECT IDENTIFIER ::= { idpr 7 } idprdataVer OBJECT-TYPE SYNTAX BitField ACCESS read-only STATUS mandatory DESCRIPTION "The versions of the encapsulation protocol supported by this PG. Bit Position 0 == Version 1 Bit Position 1 == Version 2 ...and so on... Bit Position n == Version n+1 where n <= 31." ::= { idprdata 1 } -- IDPR WG Page 40 -- Internet Draft IDPR MIB March 1992 idprdataErrs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of messages received which could not be processed." ::= { idprdata 2 } idprdataUnkPaths OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total number of Data messages received by this entity which referenced and unknown path." ::= { idprdata 3 } idprdataUnkProtos OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Data packets received which had an invalid protocol field." ::= { idprdata 4 } idprdataBadLengths OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of Data packets received which had an invalid length field." ::= { idprdata 5 } -- IDPR WG Page 41 -- Internet Draft IDPR MIB March 1992 idprdataBadAuths OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of data packets received which failed authentication." ::= { idprdata 6 } -- 5.8 IDPR Address Mapping Table Object Definitions idpraddr OBJECT IDENTIFIER ::= { idpr 8 } idpraddrTab OBJECT-TYPE SYNTAX SEQUENCE OF IdprAddrEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The address mapping table from source and destination addresses to a particular IDPR path." ::= { idpraddr 1 } idprAddrEntry OBJECT-TYPE SYNTAX IdprAddrEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Information for a single IDPR Address Map." INDEX { idpraddrSrc, idpraddrDst, idpraddrTos, idpraddrProto, idpraddrSrcPort, idpraddrDstPort} ::= { idprPathTable 1 } -- IDPR WG Page 42 -- Internet Draft IDPR MIB March 1992 IdprAddrEntry ::= SEQUENCE { idpraddrSrc IpAddress, idpraddrDst IpAddress, idpraddrSrcMask IpAddress, idpraddrDstMask IpAddress, idpraddrTos INTEGER, idpraddrProto INTEGER, idpraddrSrcPort INTEGER, idpraddrDstPort INTEGER, idpraddrPathAD INTEGER, idpraddrPathEnt INTEGER, idpraddrPathId INTEGER, idpraddrState INTEGER } idpraddrSrc OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "The source address for the mapping." ::= { idpraddrEntry 1 } idpraddrDst OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "The destination address for the mapping" ::= { idpraddrEntry 2 } -- IDPR WG Page 43 -- Internet Draft IDPR MIB March 1992 idpraddrSrcMask OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "The source address mask for the mapping." ::= { idpraddrEntry 3} idpraddrDstMask OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "The destination address mask for the mapping." ::= { idpraddrEntry 4 } idpraddrTos OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The TOS for the mapping." ::= { idpraddrEntry 5} idpraddrProto OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The IP protocol for the mapping." ::= { idpraddrEntry 6 } idpraddrSrcPort OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The higher layer protocol source port for the mapping." ::= { idpraddrEntry 7 } -- IDPR WG Page 44 -- Internet Draft IDPR MIB March 1992 idpraddrDstPort OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The higher layer protocol destination port for the mapping." ::= { idpraddrEntry 8 } idpraddrPathAD OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The AD of the path this mapping uses." ::= { idpraddrEntry 9 } idpraddrPathEnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The entity for the path this mapping uses." ::= { idpraddrEntry 10 } idpraddrPathId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The unique Id for the path this mapping uses." ::= { idpraddrEntry 11 } -- IDPR WG Page 45 -- Internet Draft IDPR MIB March 1992 idpraddrState OBJECT-TYPE SYNTAX INTEGER { idle (1), -- no request pending, no path assigned waiting (2), -- request pending, no path assigned active (3) -- path assigned } ACCESS read-only STATUS mandatory DESCRIPTION "The state of this mapping." ::= { idpraddrEntry 12 } -- 5.9 Source Policy Table idprsrcplcy OBJECT IDENTIFIER ::= { idpr 9 } idprsrcplcyTab OBJECT-TYPE SYNTAX SEQUENCE OF IdprSrcPlcyEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table of Source Policies for this AD." ::= { idprsrcplcy 1 } idprSrcPlcyEntry OBJECT-TYPE SYNTAX IdprSrcPlcyEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table entry for Source Policies for this AD." INDEX { idprSrcPlcyId } ::= { idprsrcplcyTab 1 } IdprSrcPlcyEntry ::= SEQUENCE { idprSrcPlcyId INTEGER, idprSrcPlcyInfo OPAQUE } -- IDPR WG Page 46 -- Internet Draft IDPR MIB March 1992 idprSrcPlcyId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The identifier of the source policy." ::= { idprSrcPlcyEntry 1 } idprSrcPlcyInfo OBJECT-TYPE SYNTAX OPAQUE ACCESS read-only STATUS mandatory DESCRIPTION "The identifier of the source policy." ::= { idprSrcPlcyEntry 2 } -- 5.10 Transit Policy Table idprtrnplcy OBJECT IDENTIFIER ::= { idpr 10 } idprtrnplcyTab OBJECT-TYPE SYNTAX SEQUENCE OF IdprTrnPlcyEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table of Transit Policies for this AD." ::= { idprtrnplcy 1 } idprTrnPlcyEntry OBJECT-TYPE SYNTAX IdprTrnPlcyEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table Entry for Transit Policies for this AD." INDEX { idprTrnPlcyAD, idprTrnPlcyId } ::= { idprtrnplcyTab 1 } -- IDPR WG Page 47 -- Internet Draft IDPR MIB March 1992 IdprTrnPlcyEntry ::= SEQUENCE { idprTrnPlcyAD INTEGER, idprTrnPlcyEnt INTEGER, idprTrnPlcyId INTEGER, idprTrnPlcyInfo OPAQUE } idprTrnPlcyAD OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The AD from which the policy was reported." ::= { idprTrnPlcyEntry 1 } idprTrnPlcyEnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The Entity from which the policy was reported." ::= { idprTrnPlcyEntry 2 } idprTrnPlcyId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The identifier of the source policy." ::= { idprTrnPlcyEntry 3 } -- IDPR WG Page 48 -- Internet Draft IDPR MIB March 1992 idprTrnPlcyInfo OBJECT-TYPE SYNTAX OPAQUE ACCESS read-only STATUS mandatory DESCRIPTION "The identifier of the source policy." ::= { idprTrnPlcyEntry 4 } END -- IDPR WG Page 49 Internet Draft IDPR MIB March 1992 6. Acknowledgements We would like to acknowledge the assistance of all the members of the IDPR Working Group and particularly the following individuals : Ken Carlberg, SAIC Mark Sleeper, Sparta Martha Steenstrup, BBN 7. References [1] V. Cerf, IAB Recommendations for the Development of Internet Network Management Standards, Internet Working Group Request for Comments 1052. Network Information Center, SRI International, Menlo Park, California, April 1988. [2] V. Cerf, Report of the Second Ad Hoc Network Management Review Group, Internet Working Group Request for Comments 1109. Network Information Center, SRI International, Menlo Park, California, August 1989. [3] M.T. Rose and K. McCloghrie, Structure and Identification of Management Information for TCP/IP-based internets, Internet Working Group Request for Comments 1155. Network Information Center, SRI International, Menlo Park, California, May 1990. [4] K. McCloghrie and M.T. Rose, Management Information Base for Network Management of TCP/IP-based internets, Internet Working Group Request for Comments 1156. Network Information Center, SRI International, Menlo Park, California, May 1990. [5] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin, Simple Network Management Protocol, Internet Working Group Request for Comments 1157. Network Information Center, SRI International, Menlo Park, California, May 1990. [6] M.T. Rose (editor), Management Information Base for Network Management of TCP/IP-based internets, Internet Working Group Request for Comments 1158, Network Information Center, SRI International, Menlo Park, California, May 1990. [7] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation IDPR WG Page 50 Internet Draft IDPR MIB March 1992 One (ASN.1), International Organization for Standardization. International Standard 8824, December 1987. [8] 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. [9] M.T. Rose, K. McCloghrie (editors), Towards Concise MIB Definitions, Internet Working Group Request for Comments 1212, Network Information Center, SRI International, Menlo Park, California, September 1990. [10] M. Lepp and M. Steenstrup, An Architecture for Inter-Domain Policy Routing, Internet Draft, July 1990. [11] ORWG, Inter-Domain Policy Routing Protocol Specification and Usage, Internet Draft, July 1991. 8. Editor's Address IDPR Working Group c/o Robert A. Woodburn SAIC CSEIC 8619 Westwood Center Drive Vienna, VA 22182 (703) 734-9000 or (703) 448-0210 EMAIL: idpr-wg@bbn.com or woody@cseic.saic.com IDPR WG Page 51