PCEP MIB Module draft-ietf-pce-pcep-mib-01.txt Kiran Koushik(Cisco Systems) Dan King(Old dog consulting) Quintin Zhao(Huawei) Emile Stephan(France Telecom) March 2010 77th IETF@Anaheim

Overview 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. The present architecture has support for the following: pcePcepClientTable: Contains information about a PCEP client(PCE or PCC) pcePcepPeerTable: Information about PCEP peers known by Entities in the pcePcepClientTable pcePcepSessionTable: A table of Sessions between PCEP clients pcePcepSessionUp & pcePcepSessionDown : Notifications to indicate PCEP session up/down March 2010 77th IETF@Anaheim

Changes and Progress Changes from -00- ietf draft include support for the following in the MIB : Whether the PCEP speaker should initiate the PCEP session or wait for initiation by the peer, A set of PCEP policies including the type of operations allowed for the PCEP peer (e.g., diverse path computation, synchronization, etc.), A scalar object restricting the set of PCEP peers that can initiate a PCEP session with the PCEP speaker (e.g., list of authorized PCEP peers, all PCEP peers in the area, all PCEP peers in the AS). Moved Abstract according to new best practices. New Copyright notices (Dec 2009) Updated Security text Updated IANA text                                                                                                Updated References Added new authors/contributors Various minor formatting updates March 2010 77th IETF@Anaheim 3

Represent previous/ongoing path computation requests. Open Issues Represent previous/ongoing path computation requests. Represent information regarding stateful PCE (section 6.8 RFC 4655) Security: We still need to document our read-write and/or read-create objects in the Security section. We should describe their specific sensitivity or vulnerabilities. IANA:  Planning for one PCE entry under mib-2. That way all of the PCE modules become children of this PCE entry. March 2010 77th IETF@Anaheim 4

Next Steps: Implementations: It would be good to know if any vendor has/is implementing and what percentage of the document/functionality has been implemented. Outstanding sections: We still need text for 4.1. Relations to other MIB modules and 5.  Example of the PCEP MIB module usage. March 2010 77th IETF@Anaheim 5