Network Working Group E. Stephan Internet-Draft France Telecom Intended status: Best Current October 15, 2006 Practice Expires: April 18, 2007 Definitions of Managed Objects for Path Computation Element Discovery Protocol draft-stephan-pce-disc-mib-00 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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 and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on April 18, 2007. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing Path Computation Elements Discovery. Stephan Expires April 18, 2007 [Page 1]
Internet-Draft PCE-DISC-STD-MIB October 2006 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 6.1. The Discovery objects . . . . . . . . . . . . . . . . . . 4 6.2. General PCEs capabilities objects . . . . . . . . . . . . 5 6.3. PCEs Computation options objects . . . . . . . . . . . . . 5 6.4. The Notification Group . . . . . . . . . . . . . . . . . . 5 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 7.1. Relationship to IGP MIB modules . . . . . . . . . . . . . 6 7.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 6 8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6 9. Security Considerations . . . . . . . . . . . . . . . . . . . 20 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 11.1. Normative References . . . . . . . . . . . . . . . . . . . 21 11.2. Informative References . . . . . . . . . . . . . . . . . . 21 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . . 22 Appendix B. Editing MIB module in XML . . . . . . . . . . . . . . 22 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 23 Intellectual Property and Copyright Statements . . . . . . . . . . 24 Stephan Expires April 18, 2007 [Page 2]
Internet-Draft PCE-DISC-STD-MIB October 2006 1. Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing Path Computation Elements Discovery. 2. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 3. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL", when they appear in this document, are to be interpreted as described in BCP 14, RFC 2119 [RFC2119]. 4. Terminology The terminology used in this document is built on notions introduced and discussed in PCE WG documents. The reader should be familiar with these documents Domain: any collection of network elements within a common sphere of address management or path computational responsibility. IGP Area: OSPF Area or ISIS level. PCC: Stephan Expires April 18, 2007 [Page 3]
Internet-Draft PCE-DISC-STD-MIB October 2006 Path Computation Client: any client application requesting a path computation to be performed by a Path Computation Element. PCE: Path Computation Element: an entity (component, application, or network node) that is capable of computing a network path or route based on a network graph, and applying computational constraints. 5. Overview [RFC4655], describes the architecture for a PCE-based path computation model for MPLS and GMPLS TE LSPs. The architecture allows the separation of PCE from PCC. It requires that a PCC be aware of the location of one or more PCEs. This relies on a communication protocol between PCC and PCE for automatic and dynamic PCE discovery. [RFC4674] defines the mechanism and the information of PCE discovery. [I-D.ietf-pce-disco-proto-igp] declines theses components for PCCs participating to an IGP routing domain: o The discovery mechanism relies on IGP (OSPF, ISIS) routing protocols; o It defines the information elements a PCE participating in the IGP advertises in IGP extensions. The section "6.10.2.1. PCC MIB module " of [RFC4674] identifies the information to be disclosed on the management interface of the PCC. The current MIB module defines the corresponding objects. 6. Structure of the MIB Module Objects in this MIB module are arranged into groups. Each group is organized as a set of related objects. The overall structure and assignment of objects to their groups, and the intended purpose of each group, is shown below. 6.1. The Discovery objects These objects provide PCE discovery information and discovery activities. It includes: - A control to disable the automatic discovery mechanism; - The number of known PCEs; Stephan Expires April 18, 2007 [Page 4]
Internet-Draft PCE-DISC-STD-MIB October 2006 - The number of discovered PCEs; - The set of known PCEs. pceDiscoveryTable gives discovery information per PCE: - Addresses, discovery Mechanism type; - Discovery time, last activity time; - congestion and congestion duration; pceDiscoveryActTable gives discovery activity per PCE: * discovery protocol activity: these objects will define the average and maximum rates of arrival, departure and modification of PCE discovery to enable effective analysis of the operation of the protocols. * these objects will report on the operation of the discovery protocol by counting the number of unacceptable and incomprehensible information exchanges. 6.2. General PCEs capabilities objects These objects provides general information per PCE regarding PCE- PATHSCOPE, PCE-DOMAINS and PCE-DEST-DOMAINS CapPathScopeTable defines PCE computation capabilities and PCE preferences per kind of routing domain. CapDomainTable defines domains for which a PCE has topology visibility and can compute paths. CapDestDomainTable defines domains toward which a PCE can compute path. 6.3. PCEs Computation options objects These objects provides information per PCE regarding GENERAL-CAP and PATH-COMP-CAP. 6.4. The Notification Group This group will define notifications when thresholds (e.g. on the maximum rate of change, on the number of unacceptable messages) are crossed, or when important events occur (e.g. the number of discovered PCEs decreases to zero). 7. Relationship to Other MIB Modules Stephan Expires April 18, 2007 [Page 5]
Internet-Draft PCE-DISC-STD-MIB October 2006 7.1. Relationship to IGP MIB modules PCE Discovery relies on existing protocols which have specialized MIB objects to monitor protocol activities. Consequently this document considers that the monitoring of the undelying protocol in out of the scope of the current MIB module. 7.2. MIB modules required for IMPORTS The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB [RFC2863] and also REFERENCEs document RFC0768 [RFC0768] 8. Definitions PCE-DISC-STD-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Unsigned32, Gauge32, Integer32, IpAddress, experimental FROM SNMPv2-SMI RowStatus, TEXTUAL-CONVENTION, TimeStamp, TruthValue FROM SNMPv2-TC Ipv6Address FROM IPV6-TC MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF AddressFamilyNumbers FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB IANAipRouteProtocol FROM IANA-RTPROTO-MIB; pceDiscStdMIB MODULE-IDENTITY LAST-UPDATED "200610150000Z" -- October 15, 2006 ORGANIZATION "Path Computation Element (PCE) Working Group" CONTACT-INFO " Stephan Emile France Telecom DR&D Email: emile.stephan@orange-ft.com Stephan Expires April 18, 2007 [Page 6]
Internet-Draft PCE-DISC-STD-MIB October 2006 Email comments directly to the PCE WG Mailing List at pce@ietf.org WG-URL: http://www.ietf.org/html.charters/pce-charter.html " DESCRIPTION "This MIB module defines a collection of objects for managing Path Computation Elements (PCEs) Discovery." ::= { experimental 10000 } -- Temporary node ( for smilint) -- Textual Conventions used in this MIB module -- -- Defined in PCE TC STD MIB -- Currently duplicated for Smilint PceRoutingDomainID ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "" SYNTAX OCTET STRING (SIZE (0..20)) -- Notification -- pceDiscNotifications OBJECT IDENTIFIER ::= { pceDiscStdMIB 0 } -- empty for now pceDiscMIBObjects OBJECT IDENTIFIER ::= { pceDiscStdMIB 1 } pceDiscoveryObjects OBJECT IDENTIFIER ::= { pceDiscMIBObjects 1 } pceDiscoveryAdminStatus OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Setting this object to disabled(2) disables the discovery of PCEs. Once disabled, The discovery must be explicitly enabled to restore discovery of PCEs. Setting this object to enabled(1) enables the discovery of PCEs." ::= { pceDiscoveryObjects 1 } pceDiscoveryKnowPCEs OBJECT-TYPE SYNTAX Counter32 Stephan Expires April 18, 2007 [Page 7]
Internet-Draft PCE-DISC-STD-MIB October 2006 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of PCEs the PCC is potentially in relation with. This includes PCE manually declared and active PCEs" ::= { pceDiscoveryObjects 2 } pceDiscoveryActivePCEs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of active PCEs. The detection of the activity a a PCE depends on the nature discovery mechanism. PCE discovered using PCED information received: The relation between the PCC and a PCE is active while the PCE discovery protocol maintains a communication between the PCC and this PCE. PCE Manually declared: The relation between the PCC and a PCE is active and the discovery mechanism is implementation specific; " ::= { pceDiscoveryObjects 3 } pceDiscoveryTable OBJECT-TYPE SYNTAX SEQUENCE OF PceDiscoveryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the PCEs discovered." ::= { pceDiscoveryObjects 4 } pceDiscoveryEntry OBJECT-TYPE SYNTAX PceDiscoveryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing general information of each PCE discovered." INDEX { pceDiscoveryIndex } ::= { pceDiscoveryTable 1 } PceDiscoveryEntry ::= SEQUENCE { pceDiscoveryIndex Integer32, pceDiscoveryMechanism IANAipRouteProtocol, Stephan Expires April 18, 2007 [Page 8]
Internet-Draft PCE-DISC-STD-MIB October 2006 pceDiscoveryIPv4Address IpAddress, pceDiscoveryIPv6Address Ipv6Address, pceDiscoveryTime TimeStamp, pceDiscoveryLastUpdated TimeStamp, pceDiscoveryCongestion TruthValue, pceDiscoveryCongestionDuration Unsigned32 } pceDiscoveryIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object identifies locally the PCE for which this entry contains information." ::= { pceDiscoveryEntry 1 } pceDiscoveryMechanism OBJECT-TYPE SYNTAX IANAipRouteProtocol MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies the type of discovery mechanism used to discover the PCE. The discovery mechanisms covered by PCE WG at the time of the specification are : other (1), --not specified local (2), -- local interface isIs (9), -- Dual IS-IS ospf (13), -- Open Shortest Path First bgp (14), -- Border Gateway Protocol It does not preclude the usage of another routing protocol numbered by this IANAipRouteProtocol " ::= { pceDiscoveryEntry 2 } pceDiscoveryIPv4Address OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "This object is the IP address to be used to reach the PCE. It corresponds to the PCED PCE-ADDRESS. . A value of 0.0.0.0 indicates the absence of this address." ::= { pceDiscoveryEntry 3 } pceDiscoveryIPv6Address OBJECT-TYPE Stephan Expires April 18, 2007 [Page 9]
Internet-Draft PCE-DISC-STD-MIB October 2006 SYNTAX Ipv6Address MAX-ACCESS read-only STATUS current DESCRIPTION "This object is the IPv6 address to be used to reach the PCE. It corresponds to the PCED PCE-ADDRESS. A value of ::0 indicates the absence of this address." ::= { pceDiscoveryEntry 4 } pceDiscoveryTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time this entry was created. local entry: the value of sysUpTime at the time the PCC restarted." ::= { pceDiscoveryEntry 5 } pceDiscoveryLastUpdated OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time this entry was last updated. Static entry: if the entry values keep unchanged since the re- initialization of the PCC then this object contains a zero value." ::= { pceDiscoveryEntry 6 } pceDiscoveryCongestion OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates whether a PCE experiences a processing congestion state or not. " ::= { pceDiscoveryEntry 7 } pceDiscoveryCongestionDuration OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION Stephan Expires April 18, 2007 [Page 10]
Internet-Draft PCE-DISC-STD-MIB October 2006 "This object specifies, in seconds, the congestion duration. When the value of pceDiscoveryCongestion is 'false' then this objet MUST be to '0'" ::= { pceDiscoveryEntry 8 } pceDiscCapabilityObjects OBJECT IDENTIFIER ::= { pceDiscMIBObjects 2 } -- -- PCE-PATHSCOPE informations elements -- pceDiscCapPathScopeTable OBJECT-TYPE SYNTAX SEQUENCE OF PceDiscCapPathScopeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the capacity of the PCEs discovered." ::= { pceDiscCapabilityObjects 1 } pceDiscCapPathScopeEntry OBJECT-TYPE SYNTAX PceDiscCapPathScopeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the capacity of each PCE discovered." INDEX { pceDiscoveryIndex } ::= { pceDiscCapPathScopeTable 1 } PceDiscCapPathScopeEntry ::= SEQUENCE { pceDiscCapPathScopeIntraArea TruthValue, pceDiscCapPathScopeInterArea TruthValue, pceDiscCapPathScopeDefInterArea TruthValue, pceDiscCapPathScopeInterAS TruthValue, pceDiscCapPathScopeDefInterAS TruthValue, pceDiscCapPathScopeInterLayer TruthValue, pceDiscCapPathScopePrefIntraArea Integer32, pceDiscCapPathScopePrefInterArea Integer32, pceDiscCapPathScopePrefInterAS Integer32, pceDiscCapPathScopePrefIntLayer Integer32 } pceDiscCapPathScopeIntraArea OBJECT-TYPE SYNTAX TruthValue Stephan Expires April 18, 2007 [Page 11]
Internet-Draft PCE-DISC-STD-MIB October 2006 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates whether the PCE supports the L option of the PATH- SCOPE sub TLV: The value is 'true' if the PCE can compute intra-area path." ::= { pceDiscCapPathScopeEntry 1 } pceDiscCapPathScopeInterArea OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates whether the PCE supports the R option of the PATH- SCOPE sub TLV: The value is 'true' if the PCE can act as PCE for inter-area TE LSPs computation." ::= { pceDiscCapPathScopeEntry 2 } pceDiscCapPathScopeDefInterArea OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates whether the PCE supports the Rd option of the PATH- SCOPE sub TLV: The value is 'true' if the PCE can act as a default PCE for inter-area TE LSPs computation." ::= { pceDiscCapPathScopeEntry 3 } pceDiscCapPathScopeInterAS OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates whether the PCE supports the S option of the PATH- SCOPE sub TLV: The value is 'true' if the PCE can act as PCE for inter-AS TE LSPs computation." ::= { pceDiscCapPathScopeEntry 4 } pceDiscCapPathScopeDefInterAS OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION Stephan Expires April 18, 2007 [Page 12]
Internet-Draft PCE-DISC-STD-MIB October 2006 "Indicates whether the PCE supports the Sd option of the PATH- SCOPE sub TLV: The value is 'true' if the PCE can act as a default PCE for inter-AS TE LSPs computation." ::= { pceDiscCapPathScopeEntry 5 } pceDiscCapPathScopeInterLayer OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates whether the PCE supports the Y option of the PATH- SCOPE sub TLV: The value is 'true' if the PCE can compute or take part into the computation of paths across layers." ::= { pceDiscCapPathScopeEntry 6} pceDiscCapPathScopePrefIntraArea OBJECT-TYPE SYNTAX Integer32 (0..7) MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the level of preference of the option of computation 'L' compared to other computation options: A value of 7 reflects the highest preference. When the value of PceDiscCapCompIntraArea is 'false' then this objet MUST be to '0'." ::= { pceDiscCapPathScopeEntry 7} pceDiscCapPathScopePrefInterArea OBJECT-TYPE SYNTAX Integer32 (0..7) MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the level of preference of the option of computation 'R' compared to other computation options: A value of 7 reflects the highest preference. When the value of PceDiscCapCompInterArea is 'false' then this objet MUST be to '0'." ::= { pceDiscCapPathScopeEntry 8} pceDiscCapPathScopePrefInterAS OBJECT-TYPE SYNTAX Integer32 (0..7) MAX-ACCESS read-only STATUS current DESCRIPTION Stephan Expires April 18, 2007 [Page 13]
Internet-Draft PCE-DISC-STD-MIB October 2006 "Indicates the level of preference of the option of computation 'S' compared to other computation options: A value of 7 reflects the highest preference. When the value of PceDiscCapCompInterAS is 'false' then this objet MUST be to '0'." ::= { pceDiscCapPathScopeEntry 9} pceDiscCapPathScopePrefIntLayer OBJECT-TYPE SYNTAX Integer32 (0..7) MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the level of preference of the option of computation 'Y' compared to other computation options: A value of 7 reflects the highest preference. When the value of PceDiscCapCompInterLayer is 'false' then this objet MUST be to '0'." ::= { pceDiscCapPathScopeEntry 10} -- -- PCE-DOMAINS information elements -- pceDiscCapDomainTable OBJECT-TYPE SYNTAX SEQUENCE OF PceDiscCapDomainEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the set of domains where the PCE has topology visibility and can compute paths." ::= { pceDiscCapabilityObjects 2 } pceDiscCapDomainEntry OBJECT-TYPE SYNTAX PceDiscCapDomainEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the domains of each PCE discovered." INDEX { pceDiscoveryIndex, pceDiscCapDomainIndex } ::= { pceDiscCapDomainTable 1 } PceDiscCapDomainEntry ::= SEQUENCE { pceDiscCapDomainIndex Integer32, pceDiscCapDomainIDType AddressFamilyNumbers, Stephan Expires April 18, 2007 [Page 14]
Internet-Draft PCE-DISC-STD-MIB October 2006 pceDiscCapDomainID PceRoutingDomainID } pceDiscCapDomainIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object identifies locally a domain for which the PCE identified by pceDiscoveryIndex has topology visibility and can compute paths." ::= { pceDiscCapDomainEntry 1 } pceDiscCapDomainIDType OBJECT-TYPE SYNTAX AddressFamilyNumbers MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies the type of the domainID of a PCE- DOMAIN SUB TLV. Acceptable types are : ipV4(1) and ipV6(2) for an OSPF area ID; nsap(3) for and ISIS area ID; asNumber(18) for an BGP AS number" ::= { pceDiscCapDomainEntry 2 } pceDiscCapDomainID OBJECT-TYPE SYNTAX PceRoutingDomainID MAX-ACCESS read-only STATUS current DESCRIPTION "The ID (area,AS) of the routing domain for which this entry contains information." ::= { pceDiscCapDomainEntry 3 } -- -- PCE-DEST-DOMAINS information elements -- pceDiscCapDestDomainTable OBJECT-TYPE SYNTAX SEQUENCE OF PceDiscCapDestDomainEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION Stephan Expires April 18, 2007 [Page 15]
Internet-Draft PCE-DISC-STD-MIB October 2006 "Information describing the set of destination domains toward which a PCE can compute path." ::= { pceDiscCapabilityObjects 3 } pceDiscCapDestDomainEntry OBJECT-TYPE SYNTAX PceDiscCapDestDomainEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the destination domains of each PCE." INDEX { pceDiscoveryIndex, pceDiscCapDestDomainIndex } ::= { pceDiscCapDestDomainTable 1 } PceDiscCapDestDomainEntry ::= SEQUENCE { pceDiscCapDestDomainIndex Integer32, pceDiscCapDestDomainIDType AddressFamilyNumbers, pceDiscCapDestDomainID PceRoutingDomainID } pceDiscCapDestDomainIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object identifies locally a destination domain toward which a PCE identified by pceDiscoveryIndex can compute path." ::= { pceDiscCapDestDomainEntry 1 } pceDiscCapDestDomainIDType OBJECT-TYPE SYNTAX AddressFamilyNumbers MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies the type of the routing domain. Acceptable types are : ipV4(1) and ipV6(2) for an OSPF area ID; nsap(3) for and ISIS area ID; asNumber(18) for an BGP AS number" ::= { pceDiscCapDestDomainEntry 2 } pceDiscCapDestDomainID OBJECT-TYPE SYNTAX PceRoutingDomainID MAX-ACCESS read-only STATUS current DESCRIPTION "The ID (area,AS) of the routing domain for which this entry contains information." ::= { pceDiscCapDestDomainEntry 3 } Stephan Expires April 18, 2007 [Page 16]
Internet-Draft PCE-DISC-STD-MIB October 2006 pceDiscComputationOptionsObjects OBJECT IDENTIFIER ::= { pceDiscMIBObjects 3 } -- GENERAL-CAP and PATH-COMP-CAP pceDiscComputationOptionsTable OBJECT-TYPE SYNTAX SEQUENCE OF PceDiscComputationOptionsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing options supported by each PCE." ::= { pceDiscComputationOptionsObjects 1 } pceDiscComputationOptionsEntry OBJECT-TYPE SYNTAX PceDiscComputationOptionsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the activity of the discovery mechanism of a PCE discovered. " INDEX { pceDiscoveryIndex } ::= { pceDiscComputationOptionsTable 1 } PceDiscComputationOptionsEntry ::= SEQUENCE { pceDiscCompOptionsRpriority INTEGER, pceDiscCompOptionsMmessages INTEGER } pceDiscCompOptionsRpriority OBJECT-TYPE SYNTAX INTEGER { supported(1), notSupported(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The PCE identified by pceDiscoveryIndex supports for Request prioritization if the value of this object is supported(1)." ::= { pceDiscComputationOptionsEntry 1 } pceDiscCompOptionsMmessages OBJECT-TYPE SYNTAX INTEGER { supported(1), Stephan Expires April 18, 2007 [Page 17]
Internet-Draft PCE-DISC-STD-MIB October 2006 notSupported(2) } MAX-ACCESS read-only STATUS current DESCRIPTION " If the value of this object is supported(1), then the PCE identified by pceDiscoveryIndex supports for multiple messages within the same request message." ::= { pceDiscComputationOptionsEntry 2 } -- Activity objects pceDiscActivityObjects OBJECT IDENTIFIER ::= { pceDiscMIBObjects 4 } pceDiscActivityTable OBJECT-TYPE SYNTAX SEQUENCE OF PceDiscActivityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing for each PCE the activity of the discovery mechanism." ::= { pceDiscActivityObjects 1 } pceDiscActivityEntry OBJECT-TYPE SYNTAX PceDiscActivityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the activity of the discovery mechanism of a PCE discovered. " INDEX { pceDiscoveryIndex } ::= { pceDiscActivityTable 1 } PceDiscActivityEntry ::= SEQUENCE { pceDiscActivityTlvsRecv Integer32, pceDiscActivityErroredTlvsRecv Integer32 } pceDiscActivityTlvsRecv OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object counts the number of TLV received since the discovery of the PCE." ::= { pceDiscActivityEntry 1 } Stephan Expires April 18, 2007 [Page 18]
Internet-Draft PCE-DISC-STD-MIB October 2006 pceDiscActivityErroredTlvsRecv OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object counts the number of Errored TVL received since the discovery of the PCE." ::= { pceDiscActivityEntry 2 } -- -- PCE DISC agents conformance statement -- pceDiscConformance OBJECT IDENTIFIER ::= { pceDiscStdMIB 2 } pceDiscGroups OBJECT IDENTIFIER ::= { pceDiscConformance 1 } pceDiscCompliances OBJECT IDENTIFIER ::= { pceDiscConformance 2 } -- PCE DISC agent compliance statements pceDiscGeneralPceInformation MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement only general information monitoring as proposed in the 2nd S. of the section 6.1 of [RFC4674]." MODULE -- -- objets of pceDiscoveryTable -- objects of pceDiscPathScopeTable -- ::= { pceDiscCompliances 1 } pceDiscDetailledPceInformation MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement detailled monitoring as proposed in the 3rd S. of the section 6.1 of [RFC4674]." MODULE -- -- objets of pceDiscoveryTable; Stephan Expires April 18, 2007 [Page 19]
Internet-Draft PCE-DISC-STD-MIB October 2006 -- objects of pceDiscPathScopeTable; -- objects of pceDiscDomainTable; -- objects of pceDiscDestDomainTable -- ::= { pceDiscCompliances 2 } END 9. Security Considerations There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability: o on/off of discovery : Unauthorized changes to pceDiscoveryAdminStatus could result in a temporary interruption of the discovery ; Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability: o IP addresses of PCE. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate Stephan Expires April 18, 2007 [Page 20]
Internet-Draft PCE-DISC-STD-MIB October 2006 rights to indeed GET or SET (change/create/delete) them. 10. IANA Considerations . 11. References 11.1. Normative References [I-D.ietf-pce-disco-proto-igp] Roux, J., "IGP protocol extensions for Path Computation Element (PCE) Discovery", draft-ietf-pce-disco-proto-igp-02 (work in progress), June 2006. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC4674] Le Roux, J., "Requirements for Path Computation Element (PCE) Discovery", RFC 4674, October 2006. 11.2. Informative References [I-D.harrington-text-mib-doc-template] Harrington, D., "A Template for Documents Containing a MIB Module", draft-harrington-text-mib-doc-template-00 (work in progress), June 2006. [I-D.harrington-xml2rfc-mib-doc-template] Harrington, D., "An XML2RFC Template for Documents Containing a MIB Module", draft-harrington-xml2rfc-mib-doc-template-00 (work in progress), June 2006. Stephan Expires April 18, 2007 [Page 21]
Internet-Draft PCE-DISC-STD-MIB October 2006 [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August 1980. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFC3418] Presuhn, R., "Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3418, December 2002. [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation Element (PCE)-Based Architecture", RFC 4655, August 2006. Appendix A. Open Issues This list of open issues should be cleared and removed before this document hits the IESG. Appendix B. Editing MIB module in XML This section must be removed before this document hits the IESG. This section is not related to PCE WG. It focuses on MIB document editing, and XML editing of MIB module using xxe pluging and xml2rfc. Prior to the edition of the document the author initiated a discussion with the Rfc-editor regarding the way to write SMI definition in XML. This discussion has 2 results: 1. This document use some material from "MIB Module Document Text Template" [I-D.harrington-text-mib-doc-template].; 2. Regarding xml2rfc usage, currently MIB modules are writen in raw text encapsulated in XML <figure> and <artwork> tokens. So the editor must take care of all formating aspecs such as the length of each line, bullet tabulation... This is against the spirit of xml2rfc and of XML. So I writen this MIB module using XML <list> tokens to let xml2rfc deals with the formating of the document. The results are excellent: 1. The text version of this MIB module does not differ from a mib module handcrafted; 2. smilint does not detect any difference; Stephan Expires April 18, 2007 [Page 22]
Internet-Draft PCE-DISC-STD-MIB October 2006 3. The editong with xxe is user friendly; 3. Conclusion: 1. Writing MIB module in XML is the right direction. 2. MIB module editing will be very fast if we define a set of XML templates for SMI objects definition. These definitions should be added to"MIB Module Document Template" [I-D.harrington-xml2rfc-mib-doc-template]. Following are some comments related to "MIB Module Document Text Template" [I-D.harrington-text-mib-doc-template] : 1. It should help to determine which SNMP and SMI rfc are normative or informative. Author's Address Stephan Emile France Telecom Division R&D 2 avenue Pierre Marzin Lannion, F-22307 Fax: +33 2 96 05 18 52 Email: emile.stephan@orange-ft.com Stephan Expires April 18, 2007 [Page 23]
Internet-Draft PCE-DISC-STD-MIB October 2006 Full Copyright Statement Copyright (C) The Internet Society (2006). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Stephan Expires April 18, 2007 [Page 24]