1. 66th IETF meeting, July 2006 Extensions to the OSPF Management Information Base in support of GMPLS Extensions to the OSPF Management Information Base in support of GMPLS draft-ietf-ccamp-gmpls-ospf-mib-00.txt Masanori Miyazawama-miyazawa@kddilabs.jp Tomohiro Otaniotani@kddilabs.jp Thomas D. Nadeautnadeau@cisco.com Kenji Kumakike-kumaki@kddi.com

2. 66th IETF meeting, July 2006 Summary of this draft This draft –describes the definition of MIB modules in order to manage OSPF routing information with TE extension in support of GMPLS as well as MPLS. –is expected to improve SPs’ network management system (NMS) of MPLS/GMPLS networks. Charter schedule –Mar 2007: Submit OSPF-TE/GMPLS MIB module for MIB doctor and IESG review. What are issues at this moment? –No definition of MPLS/GMPLS OSPF-TE object in the current OSPF MIB. Based on RFC3630, 4202 and 4203 –Difficulty and less efficiency to obtain such information using different interfaces at each network element.

3. 66th IETF meeting, July 2006 Definition of OSPF-TE MIB Currently included –ospfTeLsdbTable is basically used to indicate multiple sub-TLVs information of TE LSA defined in RFC3630. This is commonly utilized in MPLS and GMPLS. –ospfTeLocalIntIpAddrTable is identical to the Local interface IP address information in a sub-TLV for the Link- TLV. –ospfTeRemoteIntIpAddrTable is identical to the Remote interface IP address information in a sub-TLV of the Link-TLV. –ospfTeSwCapTable represents Interface Switching Capability Descriptor information. This is utilized only in GMPLS. –ospfTeSrlgTable contains the Sub-TLV information of Shared Risk Link Group (SRLG) information. Future consideration –ospfTeSupport: scalar is basically used to indicate TE capability of advertised routers. –ospfTeNonstdTLVTable: OCTET STRING Is utilized to represent additional (non-standard) TLVs

4. 66th IETF meeting, July 2006 OSPF-TE MIB tree +--ospfTeMIB(**) | +--ospfTeObjects(1) | | | +--ospfTeLsdbTable(1) | | | | | +--ospfTeLsdbEntry(1) | | | +--ospfTeLocalIntIpAddrTable(2) | | | | | +--ospfTeLocalIntIpAddrEntry(1) | | | +--ospfTeRemoteIntIpAddrTable(3) | | | | | +--ospfTeRemoteIntIpAddrEntry(1) | | | +--ospfTeSwCapTable(4) | | | | | +--ospfTeSwCapEntry(1) | | | +--ospfTeSrlgTable(5) | | | +--ospfTeSrlgEntry(1) | +--ospfTeConformance(2) | | | +--ospfTeCompliances(1) | | | | | +--ospfTeCompliances(1) | | +--udpMIBCompliance(1) | | | +--udpMIBCompliances(1) | | | +--ospfTeGroups(2) | | | | | +--ospfTeLsdbGroup(1) | | +--udpGroup(1) | | +--ospfTeLocalIntIpAddrGroup(2) | | +--ospfTeRemoteIntIpAddrGroup(3) | | +--ospfTeSwCapGroup(4) | | +--ospfTeSrlgGroup(5) | | | +--udpMIBGroups(2) | +--udpMIBConformance(2) ospfTeNonstdTLVTable ospfTeSupport

5. 66th IETF meeting, July 2006 Response to comments Scope of this I-D –OSPF-TE mib limits the support of OSPFv2 OSPF-TE is based on only OSPFv2. –OID is the form of “transmission xxx”, because GMPLS MIBs use the form of “Transmission xxx”. Need to update the description –Description of ospfTeLsdbTable Will be changed to includes “type-10 opaque LSP” –Description of InetAddressType, InetAddress We are considering to change to use “ipAdress” from those Otherwise, may be changed to include “support of only IPv4” Errors –Description of IMPORTS –Type of MAX-ACESS of ospfTeIntMtu Not read-write but read-only –Some typos…

6. 66th IETF meeting, July 2006 Next Step We will continuously keep updating the contents to meet requirements and feedbacks. We need more feedback in the mailing list.