Internet Draft A S Kiran Koushik Expires: August 2007 Cisco Systems, Inc. E. Stephan France Telecom PCE communication protocol(PCEP) Management Information Base draft-kkoushik-pce-pcep-mib-00.txt 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. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract This memo defines an experimental portion of the Management Information Base for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling of Path Computation Element communication Protocol (PCEP) for communications between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between two PCEs. Table of Contents Abstract............................................................1 1 Introduction...................................................2 PCE Working Group Expires August 2007 [Page 1] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 2 Terminology....................................................3 3 The Internet-Standard Management Framework.....................3 4 PCEP MIB modules Architecture..................................3 4.1 Relations to other MIB modules.................................3 5 Example of the PCEP MIB modules usage .........................3 6 Object definitions.............................................3 6.1 PCE-PCEP-DRAFT-MIB.............................................4 7 Security considerations.......................................16 8 IANA Considerations...........................................16 9 References....................................................16 9.1 Normative References..........................................16 9.2 Informative References........................................17 10 Acknowledgement ..............................................17 11 Author's Addresses............................................17 12 Intellectual Property Notice..................................17 13 Full Copyright Statement......................................18 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 defines a MIB module that can be used to manage Path Computation Element communication Protocol (PCEP) for communications between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between two PCEs. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [BCP14]. 2 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. PCE Working Group Expires August 2007 [Page 2] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 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. 3 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]. 4. PCEP MIB Module Architecture The PCEP MIB will contain the following information: a. PCEP client configuration and status. b. PCEP peer configuration and information. c. PCEP session configuration and information. d. Notifications to indicate PCEP session changes. 4.1. Relations to other MIB modules TBD 5 Example of the PCEP MIB module usage TBD 6 Object definitions PCE Working Group Expires August 2007 [Page 3] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 6.1 PCE-PCEP-DRAFT-MIB This MIB module makes references to the following documents. [RFC2578], [RFC2579], [RFC2580], [RFC2571], [RFC3411], [RFC2863], [RFC4001], [RFC4265] and [RFC3813]. PCE-PCEP-DRAFT-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Unsigned32, Gauge32, Integer32, IpAddress, experimental FROM SNMPv2-SMI RowStatus, TimeInterval, TruthValue, TimeStamp, StorageType,TEXTUAL-CONVENTION FROM SNMPv2-TC -- [RFC2579] InetAddressPrefixLength, InetAddressType, InetAddress, InetPortNumber FROM INET-ADDRESS-MIB -- [RFC3291] MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF; pcePcepDraftMIB MODULE-IDENTITY LAST-UPDATED "200702200000Z" --February 20, 2007 ORGANIZATION "Path Computation Element (PCE) Working Group" CONTACT-INFO " A S Kiran Koushik Cisco Systems Inc. Stephan Emile France Telecom DR&D Email: kkoushik@cisco.com Email: emile.stephan@orange-ft.com 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 PCE communication protocol(PCEP)." ::= { experimental 9999 } -- -- Textual Conventions used in this MIB module -- PCE Working Group Expires August 2007 [Page 4] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 PcePcepIdentifier ::= TEXTUAL-CONVENTION DISPLAY-HINT "1d.1d.1d.1d:1d:1d" STATUS current DESCRIPTION "The LDP identifier is a six octet quantity which is used to identify a PCE client." SYNTAX OCTET STRING (SIZE (6)) -- Notifications -- pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepDraftMIB 0 } pcePcepMIBObjects OBJECT IDENTIFIER ::= { pcePcepDraftMIB 1 } pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepDraftMIB 2 } pcePcepClientObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 1 } -- -- PCE Client Objects -- pcePcepClientLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time of the most recent addition or deletion of an entry to/from the pcePcepClientTable/pcePcepClientStatsTable, or the most recent change in value of any objects in the pcePcepClientTable. If no such changes have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value." ::= { pcePcepClientObjects 1 } pcePcepClientIndexNext OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains an appropriate value to be used for pcePcepClientIndex when creating entries in the pcePcepClientTable. The value 0 indicates that no unassigned entries are PCE Working Group Expires August 2007 [Page 5] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 available." ::= { pcePcepClientObjects 2 } pcePcepClientTable OBJECT-TYPE SYNTAX SEQUENCE OF PcePcepClientEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains information about the Path Computation Element(PCE)." ::= { pcePcepClientObjects 3 } pcePcepClientEntry OBJECT-TYPE SYNTAX PcePcepClientEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents a PCE. An entry can be created by a network administrator or by an SNMP agent as instructed by PCEP." INDEX { pcePcepClientPcepId, pcePcepClientIndex } ::= { pcePcepClientTable 1 } PcePcepClientEntry ::= SEQUENCE { pcePcepClientPcepId PcePcepIdentifier, pcePcepClientIndex Unsigned32, pcePcepClientAdminStatus INTEGER, pcePcepClientOperStatus INTEGER, pcePcepClientTcpPort InetPortNumber, pcePcepClientKeepAliveHoldTimer Unsigned32, pcePcepClientStorageType StorageType, pcePcepClientRowStatus RowStatus } pcePcepClientPcepId OBJECT-TYPE SYNTAX PcePcepIdentifier MAX-ACCESS not-accessible STATUS current DESCRIPTION "The PCE identifier." ::= { pcePcepClientEntry 1 } pcePcepClientIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "This index is used to uniquely identify the PCE client. PCE Working Group Expires August 2007 [Page 6] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 Before creating a row in this table, the 'pcePcepClientIndexNext' object should be retrieved. That value should be used for the value of this index when creating a row in this table. NOTE: if a value of zero (0) is retrieved, that indicates that no rows can be created in this table at this time." ::= { pcePcepClientEntry 2 } pcePcepClientAdminStatus OBJECT-TYPE SYNTAX INTEGER { enable(1), disable(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The administrative status of this PCE Client. If this object is changed from 'enable' to 'disable' and this entity has already attempted to establish contact with a Peer, then all contact with that Peer is lost and all information from that Peer needs to be removed from the MIB. (This implies that the network management subsystem should clean up any related entry in the pcePcepPeerTable. This further implies that a 'tear-down' for that session is issued and the session and all information related to that session cease to exist). At this point the operator is able to change values which are related to this entity. When the admin status is set back to 'enable', then this Entity will attempt to establish a new session with the Peer." DEFVAL { enable } ::= { pcePcepClientEntry 4 } pcePcepClientOperStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), enabled(2), disabled(3) } MAX-ACCESS read-only STATUS current DESCRIPTION PCE Working Group Expires August 2007 [Page 7] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 "The operational status of this PCE client. The value of unknown(1) indicates that the operational status cannot be determined at this time. The value of unknown should be a transient condition before changing to enabled(2) or disabled(3)." ::= { pcePcepClientEntry 5 } pcePcepClientTcpPort OBJECT-TYPE SYNTAX InetPortNumber MAX-ACCESS read-create STATUS current DESCRIPTION "The TCP Port for PCEP. The default value is the well-known value of this port." -- To be assigned by IANA ::= { pcePcepClientEntry 6 } pcePcepClientKeepAliveHoldTimer OBJECT-TYPE SYNTAX Unsigned32 (1..65535) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The 16-bit integer value which is the proposed keep alive hold timer for this PCE client." ::= { pcePcepClientEntry 7 } pcePcepClientStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row." DEFVAL{ nonVolatile } ::= { pcePcepClientEntry 8 } pcePcepClientRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row. All writable PCE Working Group Expires August 2007 [Page 8] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 objects in this row may be modified at any time, however, as described in detail in the section entitled, 'Changing Values After Session Establishment', and again described in the DESCRIPTION clause of the pcePcepClientAdminStatus object, if a session has been initiated with a Peer, changing objects in this table will wreak havoc with the session and interrupt traffic. To repeat again: the recommended procedure is to set the pcePcepClientAdminStatus to down, thereby explicitly causing a session to be torn down. Then, change objects in this entry, then set the pcePcepClientAdminStatus to enable, which enables a new session to be initiated." ::= { pcePcepClientEntry 9 } -- -- The PCEP Client Statistics Table -- TBD -- -- -- The PCEP Peer Table -- pcePcepSessionObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 3 } pcePcepPeerLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time of the most recent addition or deletion to/from the pcePcepPeerTable/pcePcepSessionTable." ::= { pcePcepSessionObjects 1 } pcePcepPeerTable OBJECT-TYPE SYNTAX SEQUENCE OF PcePcepPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about PCEP peers known by Entities in the pcePcepClientTable. The information in this table is based on information from the Client-Peer interaction during session initialization but is not appropriate for the pcePcepSessionTable, because objects in this PCE Working Group Expires August 2007 [Page 9] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 table may or may not be used in session establishment." ::= { pcePcepSessionObjects 2 } pcePcepPeerEntry OBJECT-TYPE SYNTAX PcePcepPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a single Peer which is related to a Session. This table is augmented by the pcePcepSessionTable." INDEX { pcePcepClientPcepId, pcePcepClientIndex, pcePcepPeerPcepId } ::= { pcePcepPeerTable 1 } PcePcepPeerEntry ::= SEQUENCE { pcePcepPeerPcepId PcePcepIdentifier, pcePcepPeerTransportAddrType InetAddressType, pcePcepPeerTransportAddr InetAddress } pcePcepPeerPcepId OBJECT-TYPE SYNTAX PcePcepIdentifier MAX-ACCESS not-accessible STATUS current DESCRIPTION "The PCEP identifier of this PCE Peer." ::= { pcePcepPeerEntry 1 } pcePcepPeerTransportAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The type of the Internet address for the pcePcepPeerTransportAddr object. The PCEP specification describes this as being either an IPv4 Transport Address or IPv6 Transport This object specifies how the value of the pcePcepPeerTransportAddr object should be interpreted." ::= { pcePcepPeerEntry 2 } pcePcepPeerTransportAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only PCE Working Group Expires August 2007 [Page 10] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 STATUS current DESCRIPTION "The Internet address advertised by the peer. The type of this address is specified by the value of the pcePcepPeerTransportAddrType object." ::= { pcePcepPeerEntry 3 } -- -- The PCEP Sessions Table -- pcePcepSessionTable OBJECT-TYPE SYNTAX SEQUENCE OF PcePcepSessionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of Sessions between the PCE Clients and PCE Peers. This table AUGMENTS the pcePcepPeerTable. Each row in this table represents a single session." ::= { pcePcepSessionObjects 3 } pcePcepSessionEntry OBJECT-TYPE SYNTAX PcePcepSessionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents information on a single session between an PCE Client and PCE Peer. The information contained in a row is read-only." AUGMENTS { pcePcepPeerEntry } ::= { pcePcepSessionTable 1 } PcePcepSessionEntry ::= SEQUENCE { pcePcepSessionStateLastChange TimeStamp, pcePcepSessionState INTEGER, pcePcepSessionKeepAliveHoldTimeRem TimeInterval, pcePcepSessionKeepAliveTime Unsigned32, pcePcepSessionDiscontinuityTime TimeStamp } pcePcepSessionStateLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current PCE Working Group Expires August 2007 [Page 11] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 DESCRIPTION "The value of sysUpTime at the time this Session entered its current state as denoted by the pcePcepSessionState object." ::= { pcePcepSessionEntry 1 } pcePcepSessionState OBJECT-TYPE SYNTAX INTEGER { sessionUp(1), keepWait(2), openWait(3), tcpPending(4), idle(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "The current state of the session, all of the states 1 to 5 are based on the state machine for session negotiation behavior." ::= { pcePcepSessionEntry 2 } pcePcepSessionKeepAliveHoldTimeRem OBJECT-TYPE SYNTAX TimeInterval MAX-ACCESS read-only STATUS current DESCRIPTION "The keep alive hold time remaining for this session." ::= { pcePcepSessionEntry 3 } pcePcepSessionKeepAliveTime OBJECT-TYPE SYNTAX Unsigned32 (1..65535) UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The negotiated KeepAlive Time which represents the amount of seconds between keep alive messages. The pcePcepClientKeepAliveHoldTimer related to this Session is the value that was proposed as the KeepAlive Time for this session. This value is negotiated during session initialization between PCE Working Group Expires August 2007 [Page 12] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 the entity's proposed value (i.e., the value configured in pcePcepClientKeepAliveHoldTimer) and the peer's proposed KeepAlive Hold Timer value. This value is the smaller of the two proposed values." ::= { pcePcepSessionEntry 4 } pcePcepSessionDiscontinuityTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime on the most recent occasion at which any one or more of this session's counters suffered a discontinuity. The relevant counters are the specific instances associated with this session of any Counter32 object contained in the pcePcepSessionStatsTable. The initial value of this object is the value of sysUpTime when the entry was created in this table. Also, a command generator can distinguish when a session between a given Entity and Peer goes away and a new session is established. This value would change and thus indicate to the command generator that this is a different session." ::= { pcePcepSessionEntry 5 } -- -- The PCEP Session Statistics Table -- TBD -- --- --- Notifications --- pcePcepSessionUp NOTIFICATION-TYPE OBJECTS { pcePcepSessionState, pcePcepSessionDiscontinuityTime } STATUS current DESCRIPTION "If this notification is sent when the PCE Working Group Expires August 2007 [Page 13] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 value of 'pcePcepSessionState' enters the 'sessionUp(1)' state." ::= { pcePcepNotifications 1 } pcePcepSessionDown NOTIFICATION-TYPE OBJECTS { pcePcepSessionState, pcePcepSessionDiscontinuityTime } STATUS current DESCRIPTION "This notification is sent when the value of 'pcePcepSessionState' leaves the 'sessionUp(1)' state." ::= { pcePcepNotifications 2 } --**************************************************************** -- Module Conformance Statement --**************************************************************** pcePcepGroups OBJECT IDENTIFIER ::= { pcePcepConformance 1 } pcePcepCompliances OBJECT IDENTIFIER ::= { pcePcepConformance 2 } -- -- Full Compliance -- pcePcepModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The Module is implemented with support for read-create and read-write. In other words, both monitoring and configuration are available when using this MODULE-COMPLIANCE." MODULE -- this module MANDATORY-GROUPS { pcePcepGeneralGroup, pcePcepNotificationsGroup } ::= { pcePcepCompliances 1 } -- PCE Working Group Expires August 2007 [Page 14] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 -- Read-Only Compliance -- pcePcepModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The Module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE." MODULE -- this module MANDATORY-GROUPS { pcePcepGeneralGroup, pcePcepNotificationsGroup } ::= { pcePcepCompliances 2 } -- units of conformance pcePcepGeneralGroup OBJECT-GROUP OBJECTS { pcePcepClientLastChange, pcePcepClientIndexNext, pcePcepClientAdminStatus, pcePcepClientOperStatus, pcePcepClientTcpPort, pcePcepClientKeepAliveHoldTimer, pcePcepClientStorageType, pcePcepClientRowStatus, pcePcepPeerLastChange, pcePcepPeerTransportAddrType, pcePcepPeerTransportAddr, pcePcepSessionStateLastChange, pcePcepSessionState, pcePcepSessionKeepAliveHoldTimeRem, pcePcepSessionKeepAliveTime, pcePcepSessionDiscontinuityTime } STATUS current DESCRIPTION "Objects that apply to all PCEP MIB implementations." ::= { pcePcepGroups 1 } pcePcepNotificationsGroup NOTIFICATION-GROUP NOTIFICATIONS { pcePcepSessionUp, pcePcepSessionDown } PCE Working Group Expires August 2007 [Page 15] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 STATUS current DESCRIPTION "The notifications for a PCEP MIB implementation." ::= { pcePcepGroups 2 } END 7. Security Considerations These MIB modules can be used for configuration of certain objects, and anything that can be configured can be incorrectly configured, with potentially disastrous results. There are a number of management objects defined in these MIB modules 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: 8. IANA Considerations -- (Note to RFC-Editor:) -- We request that you assign contiguous RFC numbers to the -- IANA is requested to root MIB objects in the MIB module -- contained in this document under the transmission subtree. -- 9. References 9.1 Normative References [PCEP] Path Computation Element (PCE) communication Protocol (PCEP), JP. Vasseur, JL. Le Roux [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements PCE Working Group Expires August 2007 [Page 16] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 for SMIv2", STD 58, RFC 2580, April 1999. 9.2. Informative References [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002. 10. Acknowledgement 11. Authors' Addresses A S Kiran Koushik Cisco Systems Inc. Email: kkoushik@cisco.com Stephan Emile France Telecom 2 avenue Pierre Marzin Lannion, F-22307 Email: emile.stephan@orange-ftgroup.com 12. Intellectual Property Notice 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. PCE Working Group Expires August 2007 [Page 17] draft-kkoushik-pce-pcep-mib-00 PCE-PCEP-MIB Feb 22, 2007 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, THE IETF TRUST 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. 13. Full Copyright Statement Copyright (C) The IETF Trust (2007). Copyright (C) The Internet Society (2007). 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. PCE Working Group Expires August 2007 [Page 18]