1. 67th IETF meeting, Nov. 2006 Traffic Engineering Database Management Information Base in support of GMPLS Traffic Engineering Database Management Information Base in support of GMPLS draft-ietf-ccamp-gmpls-ospf-mib-01.txt Masanori Miyazawama-miyazawa@kddilabs.jp Tomohiro Otaniotani@kddilabs.jp Thomas D. Nadeautnadeau@cisco.com Kenji Kumakike-kumaki@kddi.com

2. 67th IETF meeting, Nov. 2006 Summary of this draft This draft –describes the definition of MIB modules in order to manage TE Database information 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 TE database information object commonly utilized for IGP. Based on RFC3630, 4202 and 4203 –Difficulty and less efficiency to obtain such information using different interfaces at each network element.

3. 67th IETF meeting, Nov. 2006 Changes in this draft The title(!) is changed –from “OSPF-TE MIB” to “Traffic Engineering Database Management Information Base in support of GMPLS” The scope is a bit modified –from OSPF-TE MIB to TE database information objects commonly utilized for IGP. OSPF, ISIS, and etc. New objects are introduced –to support common TE database for different IGP. Mailing list comments –Description of InetAddressType, InetAddress considered to change to use “ipAdress” from those Otherwise, may be changed to include “support of only IPv4” –SYNTAX of teLinkProtectionType From “INTEGER” to “BIT” To support a bit vector in RFC4203 –SYNTAX of “Bandwidth” From “Unsigned 32” to “OCTET STRING SIZE (4)” To support 4 octets by IEEE floating point format –MAX-ACCESS of teIntMtu From read-write to read-only

4. 67th IETF meeting, Nov. 2006 Definition of TED MIB Currently included –teTEDTable is basically used to indicate TED information of OSPF, that of ISIS, locally Configured one or others. –teLocalIntIpAddrTable is identical to the Local interface IP address information in a sub-TLV for the Link-TLV. –teRemoteIntIpAddrTable is identical to the Remote interface IP address information in a sub-TLV of the Link-TLV. –teSwCapTable represents Interface Switching Capability Descriptor information. This is utilized only in GMPLS. –teSrlgTable contains the Sub-TLV information of Shared Risk Link Group (SRLG) information. –(Future: ospfTeNonstdTLVTable: OCTET STRING) Is utilized to represent additional (non-standard) TLVs

5. 67th IETF meeting, Nov. 2006 TED MIB tree +--teMIB(**) | +--teObjects(1) | | | +--teTEDTable(1) | | | | | +--teTEDEntry(1) | | | +--teLsdbTable(2) | | | | | +--teLsdbEntry(1) | | | +--teLocalIntIpAddrTable(3) | | | | | +--teLocalIntIpAddrEntry(1) | | | +--teRemoteIntIpAddrTable(4) | | | | | +--teRemoteIntIpAddrEntry(1) | | | +--teSwCapTable(5) | | | | | +--teSwCapEntry(1) | | | +--teSrlgTable(6) | | | +--teSrlgEntry(1) | +--teConformance(2) | | | +--teCompliances(1) | | | | | +--teCompliances(1) | | +--udpMIBCompliance(1) | | | +--udpMIBCompliances(2) | | | +--teGroups(3) | | | | | +--teLsdbGroup(1) | | +--udpGroup(2) | | +--teLocalIntIpAddrGroup(3) | | +--teRemoteIntIpAddrGroup(4) | | +--teSwCapGroup(5) | | +--teSrlgGroup(6) | | | +--udpMIBGroups(4) | +--udpMIBConformance(3)

6. 67th IETF meeting, Nov. 2006 Next Step We will continuously keep updating the contents especially in the case of ISIS. –More work to stabilize the draft. We need more feedback in the mailing list.