Network Working Group E. Stephan Internet-Draft France Telecom Expires: December 12, 2006 June 10, 2006 Definitions of Managed Objects for Path Computation Element Discovery Protocol (PCEDP) inside a Path Computation Client (PCC) draft-stephan-pce-pcedp-pcc-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 December 12, 2006. 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 (PCEs) Discovery Protocol inside a Path Computation Client (PCC) application. Stephan Expires December 12, 2006 [Page 1] Internet-Draft PCEDP PCC MIB June 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. Textual Conventions . . . . . . . . . . . . . . . . . . . 5 6.2. The PCEs Discovery Group . . . . . . . . . . . . . . . . . 5 6.3. The PCEs capabilities Group . . . . . . . . . . . . . . . 5 6.4. The PCEs activities Group . . . . . . . . . . . . . . . . 5 6.5. 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 . . . . . . . . . . . . . . . . . . . 10 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 11.1. Normative References . . . . . . . . . . . . . . . . . . . 11 11.2. Informative References . . . . . . . . . . . . . . . . . . 11 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . . 12 A.1. pcedpPccPceDiscoveryTable . . . . . . . . . . . . . . . . 12 Appendix B. MIB module document template usage . . . . . . . . . 12 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14 Intellectual Property and Copyright Statements . . . . . . . . . . 15 Stephan Expires December 12, 2006 [Page 2] Internet-Draft PCEDP PCC MIB June 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 (PCEs) Discovery Protocol inside a Path Computation Client (PCC) application. 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 Terminology used in this document. 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: 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. Stephan Expires December 12, 2006 [Page 3] Internet-Draft PCEDP PCC MIB June 2006 5. Overview [I-D.ietf-pce-architecture], 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. [I-D.ietf-pce-discovery-reqs] 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) advertisements; 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 [I-D.ietf-pce-discovery- reqs] identifies the information to be disclosed on the management interface of the PCC. The current MIB module defines the corresponding objects. It provides a PCE the capability to advertise several types of informations: o its location; o information useful for PCE selection; o information useful to satisfy dynamic PCE discovery; o PCE processing congestion state; o 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. The MIB module that will run on PCCs MUST include at least: - A control to disable automatic discovery by the PCC; - The set of known PCEs; - The number of known PCEs, and the number of discovered PCEs. For each PCE reported in the MIB module, the following information MUST be available: - Information advertised by the PCE (i.e., discovered information); - Information locally configured about the PCE; - The time since the PCE was discovered; - The time since any change to the discovered information for the PCE; Note that when a Stephan Expires December 12, 2006 [Page 4] Internet-Draft PCEDP PCC MIB June 2006 PCE is no longer alive (see section 6.4), it SHOULD no longer be reported in the PCC MIB module. The MIB module SHOULD also provide the average and maximum rates of arrival, departure and modification of PCE discovery to enable effective analysis of the operation of the protocols. Further, the MIB module SHOULD report on the operation of the discovery protocol by counting the number of unacceptable and incomprehensible information exchanges. The PCC MIB module SHOULD also be used to provide 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). 6.1. Textual Conventions 6.2. The PCEs Discovery Group This group provides general PCEs information such as their location, domains supported and inter-domain functions. 6.3. The PCEs capabilities Group This group provides detailed PCEs information. It is not part of PCE discovery. This comprises any or all information about PCE path computation capabilities and alternate PCEs. 6.4. The PCEs activities Group This group provides PCEs activity information. It defines the average and maximum rates of arrival, departure and modification of PCE discovery to enable effective analysis of the operation of the protocols. Its report on the operation of the discovery protocol by counting the number of unacceptable and incomprehensible information exchanges. 6.5. The Notification Group This group defines 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 December 12, 2006 [Page 5] Internet-Draft PCEDP PCC MIB June 2006 7.1. Relationship to IGP MIB modules PCEDP 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 PCEDP-PCC-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Unsigned32, Gauge32, Integer32, IpAddress, experimental FROM SNMPv2-SMI RowStatus, TEXTUAL-CONVENTION, TimeStamp FROM SNMPv2-TC Ipv6Address FROM IPV6-TC MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF; pcedpPccMIB MODULE-IDENTITY LAST-UPDATED "200606150000Z" -- June 15, 2006 ORGANIZATION "PCE Working Group" CONTACT-INFO "WG-email: pce@ietf.org WG-URL: http://www.ietf.org/html.charters/pce-charter.html TODO: This section has to be completed with chairs and authors addresses " DESCRIPTION "This MIB module defines a collection of objects for managing Path Computation Elements (PCEs) Discovery Protocol inside a Path Computation Client (PCC) application." ::= { experimental 10000 } -- Temporary node ( for smilint) Stephan Expires December 12, 2006 [Page 6] Internet-Draft PCEDP PCC MIB June 2006 -- Textual Conventions used in this MIB module -- -- empty for now -- Notification -- pcedpPccNotifications OBJECT IDENTIFIER ::= { pcedpPccMIB 0 } -- empty for now pcedpPccMIBObjects OBJECT IDENTIFIER ::= { pcedpPccMIB 1 } pcedpPccDiscoveryGroup OBJECT IDENTIFIER ::= { pcedpPccMIBObjects 1 } pcedpPccPceDiscoveryAdminStatus 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." ::= { pcedpPccDiscoveryGroup 1 } pcedpPccPceDiscoveryTable OBJECT-TYPE SYNTAX SEQUENCE OF PcedpPccPceDiscoveryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the PCEs discovered by the PCC." ::= { pcedpPccDiscoveryGroup 2 } pcedpPccPceDiscoveryEntry OBJECT-TYPE SYNTAX PcedpPccPceDiscoveryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the general information of each PCE discovered by the PCC." INDEX { pcedpPccPceIndex } ::= { pcedpPccPceDiscoveryTable 1 } PcedpPccPceDiscoveryEntry ::= SEQUENCE { Stephan Expires December 12, 2006 [Page 7] Internet-Draft PCEDP PCC MIB June 2006 pcedpPccPceIndex Integer32, pcedpPccPceIPv4Address IpAddress, pcedpPccPceIPv6Address Ipv6Address, pcedpPccPceTimeDiscovered TimeStamp, pcedpPccPceLastUpdated TimeStamp } pcedpPccPceIndex 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." ::= { pcedpPccPceDiscoveryEntry 1 } pcedpPccPceIPv4Address OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address to be used to reach the PCE. A value of 0.0.0.0 indicates the absence of this address." ::= { pcedpPccPceDiscoveryEntry 2 } pcedpPccPceIPv6Address OBJECT-TYPE SYNTAX Ipv6Address MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address to be used to reach the PCE. A value of ::0 indicates the absence of this address." ::= { pcedpPccPceDiscoveryEntry 3 } pcedpPccPceTimeDiscovered OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time this entry was created. Static entry: the value of sysUpTime at the time PCC restarted." ::= { pcedpPccPceDiscoveryEntry 4 } pcedpPccPceLastUpdated OBJECT-TYPE SYNTAX TimeStamp Stephan Expires December 12, 2006 [Page 8] Internet-Draft PCEDP PCC MIB June 2006 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." ::= { pcedpPccPceDiscoveryEntry 5 } -- pcedpPccPceDomains -- Table to be defined -- pcedpPccPceDestDomains -- table to be defined pcedpPccPcesCapabilityGroup OBJECT IDENTIFIER ::= { pcedpPccMIBObjects 2 } -- empty for now: TODO pcedpPccPcesActivityGroup OBJECT IDENTIFIER ::= { pcedpPccMIBObjects 3 } -- empty for now: TODO -- -- PCC agents conformance statement -- pcedpPccConformance OBJECT IDENTIFIER ::= { pcedpPccMIB 2 } pcedpPccGroups OBJECT IDENTIFIER ::= { pcedpPccConformance 1 } pcedpPccCompliances OBJECT IDENTIFIER ::= { pcedpPccConformance 2 } -- PCC agent compliance statements pcedpPccGeneralPceInformation MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that monitors only general information as proposed in the 2nd S. of the section 6.1 of [I-D.ietf-pce-discovery-reqs]." Stephan Expires December 12, 2006 [Page 9] Internet-Draft PCEDP PCC MIB June 2006 MODULE ::= { pcedpPccCompliances 1 } pcedpPccDetailledPceInformation 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 [I-D.ietf-pce-discovery-reqs]." MODULE ::= { pcedpPccCompliances 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 cedpPccPceDiscoveryAdminStatus 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). Stephan Expires December 12, 2006 [Page 10] Internet-Draft PCEDP PCC MIB June 2006 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 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-01 (work in progress), March 2006. [I-D.ietf-pce-discovery-reqs] Roux, J., "Requirements for Path Computation Element (PCE) Discovery", draft-ietf-pce-discovery-reqs-05 (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. 11.2. Informative References [I-D.harrington-text-mib-doc-template] Harrington, D., "A Template for Documents Containing a MIB Stephan Expires December 12, 2006 [Page 11] Internet-Draft PCEDP PCC MIB June 2006 Module", draft-harrington-text-mib-doc-template-00 (work in progress), June 2006. [I-D.ietf-pce-architecture] Farrel, A., "A Path Computation Element (PCE) Based Architecture", draft-ietf-pce-architecture-05 (work in progress), April 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. Appendix A. Open Issues This list of open issues should be cleared and removed before this document hits the IESG. A.1. pcedpPccPceDiscoveryTable 1. Is the activation/desactivation of discovery allowed when an agent complies to pcedpPccGeneralPceInformationOnlyCompliance ? 2. What happen when cedpPccPceDiscoveryAdminStatus is set to disabled ? Do we delete all PCEs discovered dynamically ? 3. pcedpPccPceDomains & pcedpPccPceDestDomains: Do we need separate tables ? 4. Do we need a type of entry static/dynamic ? Appendix B. MIB module document template usage This section must be removed before this document hits the IESG. This section has nothing todo with PCE WG but with MIB document editing, MIB module editing, Bill Fenner xxe pluging and xml2rfc. Prior to the edition of the document the author iniitaited a discussion with the Rfc-editor regarding the way to write SMI Stephan Expires December 12, 2006 [Page 12] Internet-Draft PCEDP PCC MIB June 2006 definition in XML. This discussion has 2 results: 1. This document use parts of the "MIB Module Document Template" [I-D.harrington-text-mib-doc-template] edited by David Harrington; 2. Regarding xml2rfc usage, currently MIB objets are writen in raw text encapsulated in XML
and tokens. this is against the spirit of xml2rfc because the editor must take of the formating of the text. So I writen the objects definition using XML tokens to let xml2rfc deals with the formating of the document. Note that it does not affect the .txt version of the draft. Following are comments related to The MIB module template the author collected during the editing: 1. The MIB module template should help to determine which SNMP and SMI rfc are normative or informative. 2. Stephan Expires December 12, 2006 [Page 13] Internet-Draft PCEDP PCC MIB June 2006 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@francetelecom.com Stephan Expires December 12, 2006 [Page 14] Internet-Draft PCEDP PCC MIB June 2006 Intellectual Property Statement 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. Disclaimer of Validity 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. 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. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Stephan Expires December 12, 2006 [Page 15]