1. Models to manage G.698.2 parameters draft-galikunze-ccamp-g-698-2-snmp-mib-11.txt Gabriele Galimberti Cisco Systems Ruediger KunzeDeutsche Telekom Lam, Hing-Kam Alcatel-Lucent Dharini Hiremagalur Juniper Networks Gert Grammel Juniper Networks John Drake Juniper Networks Luyuan Fang Microsoft Gary Ratterree Microsoft March 2015 IETF 92 - Dallas1

2. Current version of the draft - 11 Current version of the MIB is 11 not 10 Some changes got lost in version 10 Authors decided to re-submit the document including all the changes and comments from the past meetings Authors want to win the the highest draft number challenge, ;-) March 2015IETF 92 - Dallas2

3. Motivation & Problem statement ITU-T G.698.2 defines the Application Codes and their optical parameters to operate a DWDM system in a Black Link approach ITU-T G.694.1 providing the Lambda definition ITU-T G.872 and G.874.1 are considered as additional reference GOALS of the draft: Provide a standard to operate and manage optical interface parameters defined by ITU-T G.698.2 in a way to retrieve/set the ITU-T application code, the power and the frequency. Provide standard way to retrieve/set the optical parameters not included in the application code. Support EMS/NMS/SDN controllers to access the optical parameters Enable a common and simple way to share information on optical parameters across vendors and operators Allow Client and DWDM equipment to exchange information on DWDM i/f parameters 3 March 2015 IETF 92 - Dallas

4. Contents of the drafts 1.draft-galikunze-ccamp-g-698-2-snmp-mib-11.txt The Draft is and extension of the RFC3591 to support ITU-T G.698.2 and ITU-T G.694.1 Central frequency (see G.694.1 Table 1) Single-channel application identifiers (see G.698.2) Number of Single-channel application identifiers Supported Current Laser Output power Current Laser Input power Introducing theVendor Specific Application Identifier 4 March 2015 IETF 92 - Dallas

5. New Application Identifier Type added March 2105IETF 92- Dallas5 A.I. Type Vendor specific to extend the number of supported applications authors introduced a new Application Identifier Type A.I. type = PROPRIETARY, the first 6 Octets of the Application Identifier (PrintableString) must contain the Hexadecimal representation of an OUI (organizationally unique identifier) assigned to the vendor whose implementation generated the Application Identifier; the remaining octets of the field are not specified.

6. Changes from last meeting draft-galikunze-ccamp-g-698-2-snmp-mib Microsoft New co-author! Comments from Honolulu Added Vendor Specific Application Identifier Added text to describe the usage of the application code 6 March 2015 IETF 92 - Dallas

7. Next Steps Realign the Parameters to new ITU-T Rec. Keep the interactions to ITU-T alive to realign the draft to new Recommendation editions Add Flex Spectrum parameters / MIB Promote draft for working group adoption 7 March 2015 IETF 92 - Dallas