Internet Engineering Task Force                        G.Galimberti, Ed.
Internet-Draft                                                     Cisco
Intended status: Standards Track                            R.Kunze, Ed.
Expires: April 27, 2015                                 Deutsche Telekom
                                                             K. Lam, Ed.
                                                          Alcatel-Lucent
                                                     D. Hiremagalur, Ed.
                                                          G.Grammel, Ed.
                                                                 Juniper
                                                        October 24, 2014


  A YANG model to manage the optical interface parameters of "G.698.2
                  single channel" in DWDM applications
                  draft-dharini-netmod-g-698-2-yang-01

Abstract

   This memo defines a yang model that translates the SNMP mib module
   defined in draft-galikunze-ccamp-g-698-2-snmp-mib for managing single
   channel optical interface parameters of DWDM applications, using the
   approach specified in G.698.2.  This model is to support the optical
   parameters specified in ITU-T G.698.2 [ITU.G698.2] and application
   identifiers specified in ITU-T G.874.1 [ITU.G874.1] .  Note that
   G.874.1 encompasses vendor-specific codes, which if used would make
   the interface a single vendor IaDI and could still be managed.

   The Yang model defined in this memo can be used for Optical
   Parameters monitoring and/or configuration of the endpoints of the
   multi-vendor IaDI based on the Black Link approach.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any



G.Galimberti, et al.     Expires April 27, 2015                 [Page 1]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 27, 2015.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The Internet-Standard Management Framework  . . . . . . . . .   4
   3.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Optical Parameters Description  . . . . . . . . . . . . .   5
       4.1.1.  Rs-Ss Configuration . . . . . . . . . . . . . . . . .   6
       4.1.2.  Table of Application Codes  . . . . . . . . . . . . .   7
       4.1.3.  Table of Vendor Application Codes . . . . . . . . . .   7
     4.2.  Optical Interface for G.698.2 . . . . . . . . . . . . . .   8
   5.  Structure of the Yang Module  . . . . . . . . . . . . . . . .   9
   6.  Yang Module . . . . . . . . . . . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   9.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  16
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  17
     10.2.  Informative References . . . . . . . . . . . . . . . . .  19
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .  19
   Appendix B.  Open Issues  . . . . . . . . . . . . . . . . . . . .  19
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  19

1.  Introduction

   This memo defines a yang model that translates the SNMP mib module
   defined in draft-galikunze-ccamp-g-698-2-snmp-mib for managing single
   channel optical interface parameters of DWDM applications, using the



G.Galimberti, et al.     Expires April 27, 2015                 [Page 2]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


   approach specified in G.698.2.  This model is to support the optical
   parameters specified in ITU-T G.698.2 [ITU.G698.2] and application
   identifiers specified in ITU-T G.874.1 [ITU.G874.1] . Note that
   G.874.1 encompasses vendor-specific codes, which if used would make
   the interface a single vendor IaDI and could still be managed.`

   The Black Link approach allows supporting an optical transmitter/
   receiver pair of one vendor to inject an optical tributary signal and
   run it over an optical network composed of amplifiers, filters, add-
   drop multiplexers from a different vendor.  In the OTN architecture,
   the 'black-link' represents a pre-certified network media channel
   conforming to G.698.2 specifications at the S and R reference points.

   [Editor's note: In G.698.2 this corresponds to the optical path from
   point S to R; network media channel is also used and explained in
   draft-ietf-ccamp-flexi-grid-fwk-02]

   Management will be performed at the edges of the network media
   channel (i.e., at the transmitters and receivers attached to the S
   and R reference points respectively) for the relevant parameters
   specified in G.698.2 [ITU.G698.2], G.798 [ITU.G798], G.874
   [ITU.G874], and the performance parameters specified in G.7710/Y.1701
   [ITU-T G.7710] and G.874.1 [ITU.G874.1].

   G.698.2 [ITU.G698.2] is primarily intended for metro applications
   that include optical amplifiers.  Applications are defined in G.698.2
   [ITU.G698.2] using optical interface parameters at the single-channel
   connection points between optical transmitters and the optical
   multiplexer, as well as between optical receivers and the optical
   demultiplexer in the DWDM system.  This Recommendation uses a
   methodology which does not explicitly specify the details of the
   optical network between reference point Ss and Rs, e.g., the passive
   and active elements or details of the design.  The Recommendation
   currently includes unidirectional DWDM applications at 2.5 and 10
   Gbit/s (with 100 GHz and 50 GHz channel frequency spacing).  Work is
   still under way for 40 and 100 Gbit/s interfaces.  There is
   possibility for extensions to a lower channel frequency spacing.
   This document specifically refers to the "application code" defined
   in the G.698.2 [ITU.G698.2] and included in the Application
   Identifier defined in G.874.1 [ITU.G874.1] and G.872 [ITU.G872], plus
   a few optical parameters not included in the G.698.2 application code
   specification.

   This draft refers and supports the draft-kunze-g-698-2-management-
   control-framework

   The building of a yang model describing the optical parameters
   defined in G.698.2 [ITU.G698.2], and reflected in G.874.1



G.Galimberti, et al.     Expires April 27, 2015                 [Page 3]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


   [ITU.G874.1], allows the different vendors and operator to retrieve,
   provision and exchange information across the G.698.2 multi-vendor
   IaDI in a standardized way.

   The Yang Model, reporting the Optical parameters and their values,
   characterizes the features and the performances of the optical
   components and allow a reliable black link design in case of multi
   vendor optical networks.

   Although RFC 3591 [RFC3591], which draft-galikunze-ccamp-g-698-2-
   snmp-mib is extending, describes and defines the SNMP MIB of a number
   of key optical parameters, alarms and Performance Monitoring, as this
   RFC is over a decade old, it is primarily pre-OTN, and a more
   complete and up-to-date description of optical parameters and
   processes can be found in the relevant ITU-T Recommendations.  The
   same considerations can be applied to the RFC 4054 [RFC4054].

2.  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].

   This memo specifies a Yang model for optical interfaces.

3.  Conventions

   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 [RFC2119] In
   the description of OIDs the convention: Set (S) Get (G) and Trap (T)
   conventions will describe the action allowed by the parameter.

4.  Overview

















G.Galimberti, et al.     Expires April 27, 2015                 [Page 4]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


   Figure 1 shows a set of reference points, for the linear "black link"
   approach, for single-channel connection (Ss and Rs) between
   transmitters (Tx) and receivers (Rx).  Here the DWDM network elements
   include an OM and an OD (which are used as a pair with the opposing
   element), one or more optical amplifiers and may also include one or
   more OADMs.


             +-------------------------------------------------+
         Ss  |              DWDM Network Elements              | Rs
    +---+ |  |  | \                                       / |  |  | +--+
    Tx L1----|->|   \    +------+            +------+   /   |--|-->Rx L1
    +---+    |  |    |   |      |  +------+  |      |  |    |  |    +--+
    +---+    |  |    |   |      |  |      |  |      |  |    |  |    +--+
    Tx L2----|->| OM |-->|------|->| OADM |--|------|->| OD |--|-->Rx L2
    +---+    |  |    |   |      |  |      |  |      |  |    |  |    +--+
    +---+    |  |    |   |      |  +------+  |      |  |    |  |    +--+
    Tx L3----|->|   /    | DWDM |    |  ^    | DWDM |   \   |--|-->Rx L3
    +---+    |  | /      | Link +----|--|----+ Link |     \ |  |    +--+
             +-----------+           |  |           +----------+
                                  +--+  +--+
                                  |        |
                               Rs v        | Ss
                               +-----+  +-----+
                               |RxLx |  |TxLx |
                               +-----+  +-----+
      Ss = reference point at the DWDM network element tributary output
      Rs = reference point at the DWDM network element tributary input
      Lx = Lambda x
      OM = Optical Mux
      OD = Optical Demux
      OADM = Optical Add Drop Mux


   from Fig. 5.1/G.698.2

                   Figure 1: Linear Black Link approach

   G.698.2 [ITU.G698.2] defines also Ring "Black Link" approach
   configurations [Fig. 5.2/G.698.2] and Linear "black link" approach
   for Bidirectional applications[Fig. 5.3/G.698.2]

4.1.  Optical Parameters Description

   The G.698.2 pre-certified network media channels are managed at the
   edges, i.e. at the transmitters (Tx) and receivers (Rx) attached to
   the S and R reference points respectively.  The set of parameters




G.Galimberti, et al.     Expires April 27, 2015                 [Page 5]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


   that could be managed are specified in G.698.2 [ITU.G698.2] section
   5.3 referring the "application code" notation

   The definitions of the optical parameters are provided below to
   increase the readability of the document, where the definition is
   ended by (R) the parameter can be retrieve with a read, when (W) it
   can be provisioned by a write, (R,W) can be either read or written.

4.1.1.  Rs-Ss Configuration

   The Rs-Ss configuration table allows configuration of Wavelength,
   Power and Application codes as described in [ITU.G698.2] and G.694.1
   [ITU.G694.1]
   This parameter report the current Transceiver Output power, it can be
   either a setting and measured value (G, S).

   Wavelength Value (see G.694.1 Table 1):
      This parameter indicates the wavelength value that Ss and Rs will
      be set to work (in THz).  See the details in Section 6/G.694.1 (G,
      S).

   Number of Vendor Transceiver Class Supported
      This parameter indicates the number of Vendor Transceiver codes
      supported by this interface (G).

   Single-channel application codes(see G.698.2):
      This parameter indicates the transceiver application code at Ss
      and Rs as defined in [ITU.G698.2] Chapter 5.4 - this parameter can
      be called Optical Interface Identifier OII as per [draft-
      martinelli-wson-interface-class](G).

   Number of Single-channel application codes Supported
      This parameter indicates the number of Single-channel application
      codes supported by this interface (G).

   Current Laser Output power:
      This parameter report the current Transceiver Output power, it can
      be either a setting and measured value (G, S).

   Current Laser Input power:
      This parameter report the current Transceiver Input power (G).










G.Galimberti, et al.     Expires April 27, 2015                 [Page 6]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


   +---------------------------------------------+---------+-----------+
   | PARAMETERS                                  | Get/Set | Reference |
   +---------------------------------------------+---------+-----------+
   | Wavelength Value                            |   G,S   |  G.694.1  |
   |                                             |         |    S.6    |
   | Vendor Transceiver Class                    |    G    |    N.A.   |
   | Number of Vendor Transceiver Class          |    G    |    N.A.   |
   | Supported                                   |         |           |
   | Single-channel application codes            |    G    |  G.698.2  |
   |                                             |         |   S.5.3   |
   | Number of Single-channel application codes  |    G    |    N.A.   |
   | Supported                                   |         |           |
   | Current Output Power                        |   G,S   |    N.A.   |
   | Current Input Power                         |    G    |    N.A.   |
   +---------------------------------------------+---------+-----------+

                       Table 1: Rs-Ss Configuration

4.1.2.  Table of Application Codes

   This table has a list of Application codes supported by this
   interface at point R are defined in G.698.2.

     Application code Identifier:
         The Identifier for the Application code.

     Application code:
      This is the application code that is defined in G.698.2.


4.1.3.  Table of Vendor Application Codes

   This table has a list of Application codes supported by this
   interface at point R are defined in G.698.2.

   Vendor Transceiver Class Identifier::
      The Identifier for the vendor transceiver class.

   Vendor Transceiver Class:
      Other than specifying all the Transceiver parameter, it might be
      convenient for the vendors to summarize a set of parameters in a
      single proprietary parameter: the Class of transceiver.  The
      Transceiver classification will be based on the Vendor Name and
      the main TX and RX parameters (i.e.  Trunk Mode, Framing, Bit
      rate, Trunk Type, Channel Band, Channel Grid, Modulation Format,
      Channel Modulation Format, FEC Coding, Electrical Signal Framing
      at Tx, Minimum maximum Chromatic Dispersion (CD) at Rx, Maximum
      Polarization Mode Dispersion (PMD) at Rx, Maximum differential



G.Galimberti, et al.     Expires April 27, 2015                 [Page 7]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


      group delay at Rx, Loopbacks, TDC, Pre-FEC BER, Q-factor,
      Q-margin,etc.).  If this parameter is used, the vendor will be
      responsible to specify the Class contents and values.  The Vendor
      can publish the parameters of its Classes or declare to be
      compatible with published Classes.(G) Optional for compliance.
      (not mentioned in G.698.2)

4.2.  Optical Interface for G.698.2

   The ietf-opt-if-g698-2 is an augment to the ietf-interface.  It
   allows the user to set the application code/vedor transceiver class/
   wavelength and the output power.  The module can also be used to get
   the list of supported application codes/ transceiver class and also
   the wavelength/output power/input power of the interface.





































G.Galimberti, et al.     Expires April 27, 2015                 [Page 8]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


       module: ietf-opt-if-g698-2
       augment /ietf-interfaces
           +.... rw optIfOChRsSs
              +... rw ifCurrentApplicationCode
              |     + .... rw  applicationCodeId
              |     + .... rw  applicationCode
              +... rw ifCurrentVendorTransceiverClass
              |     + .... rw  vendorTransceiverClassId
              |     + .... rw  vendorTransceiverClass
              +... r  ifSupportedApplicationCodes
              |     + .... r  numberApplicationCodesSupported
              |     + .... r  applicationCodesList * [applicationCodeId]
              |          | + .... r  applicationCodeId
              |          | + .... r  applicationCode
              +... r  ifSupportedVendorTransceiverClasses
              |     + .... r  numberVendorTransceiverClassesSupported
              |     + .... r  vendorTransceiverClassList *
                                            [vendorTransceiverClassId]
              |          | + .... r  vendorTransceiverClassId
              |          | + .... r  vendorTransceiverClass
              +... rw  wavelength
              +... rw  optIfOChOutputPower
              |     + .... rw   outputPower
              |     + .... r    inputPower

      notifications:
     +---n optIfOChWavelengthChange
     |  +--ro if-name?      leafref
     |  +--ro wavelength
     |     +--ro wavelength?   uint32
     +---n optIfOChApplicationCodeChange
     |  +--ro if-name?              leafref
     |  +--ro newApplicationCode
     |     +--ro applicationCodeId?   uint8
     |     +--ro applicationCode?     string
     +---n optIfOChVendorTransceiverCodeChange
        +--ro if-name?                     leafref
        +--ro newVendorTransceiverClass
           +--ro vendorTransceiverClassId?   uint8
           +--ro vendorTransceiverClass?     string


5.  Structure of the Yang Module

   ietf-opt-if-g698-2 is a top level model for the support of this
   feature.





G.Galimberti, et al.     Expires April 27, 2015                 [Page 9]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


6.  Yang Module

   The ietf-opt-if-g698-2 is defined as an extension to ietf interfaces.



   module ietf-opt-if-g698-2 {
        namespace "urn:ietf:params:xml:ns:yang:ietf-opt-if";
        prefix ietf-opt-if-g698-2

        import ietf-interfaces {
          prefix if;
        }

        import ietf-yang-types {
          prefix yang;
        }
        organization
          "IETF NETMOD (NETCONF Data Modelling Language) Working Group";

        contact
          "WG Web:   <http://tools.ietf.org/wg/netmod/>
           WG List:  <mailto:netmod@ietf.org>

           WG Chair: Thomas Nadeau
                     <mailto:tnadeau@lucidvision.com>

           WG Chair: Juergen Schoenwaelder
                     <mailto:j.schoenwaelder@jacobs-university.de>

           Editor:   Dharini Hiremagalur
                     <mailto:dharinih@juniper.net>";

        description
          "This module contains a collection of YANG definitions for
           configuring Optical interfaces.

           Copyright (c) 2013 IETF Trust and the persons identified as
           authors of the code.  All rights reserved.

           Redistribution and use in source and binary forms, with or
           without modification, is permitted pursuant to, and subject
           to the license terms contained in, the Simplified BSD License
           set forth in Section 4.c of the IETF Trust's Legal Provisions
           Relating to IETF Documents
           (http://trustee.ietf.org/license-info).

           revision 2014-10-25 {



G.Galimberti, et al.     Expires April 27, 2015                [Page 10]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


              description
                  "Initial revision.";
              reference
                  "RFC XXXX: A YANG Data Model for Optical Management of
                    an Interface for g.698.2 support";
           }
           revision 2014-02-14 {
              description
                 "Revision 1.0";
           }









































G.Galimberti, et al.     Expires April 27, 2015                [Page 11]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


      grouping optIfOChVendorTransceiverClass {
          description " A unique Vendor transceiver class supported by
                        this interface";
          leaf vendorTransceiverClassId {
                   description
                       "Id for the Vendor transceiver class";
                   type uint8 {
                       range "1..255";
                   }
          }
          leaf vendorTransceiverClass {
              type string {
                   length "1..256";
              }
              description "This defines the transceiver class that
                      is/should be used by this interface.
                      Vendors can summarize a set of parameters in a
                      single proprietary parameter: the Class of
                      transceiver. The Transceiver classification will
                      be based on the Vendor Name and the main TX and RX
                      parameters i.e.  Trunk Mode, Framing, Bit rate,
                      Trunk Type etc).";
            }

      }

      grouping vendorTransceiverClassList {
          description " List of vendor transceiver codes group"
          leaf numberVendorTransceiverClassSupported {
              type uint32;
              description " Number of Vendor classes supported by this
                            interface";
          }
          list vendorTransceiverClassList {
              key "vendorTransceiverClassId";
              uses optIfOCh-VendorTransceiverClass;
          }
       }





      grouping optIfOChApplicationCode  {
             description " Application code entity"
             leaf applicationCodeId {
                  description
                      " Id for the Application code";



G.Galimberti, et al.     Expires April 27, 2015                [Page 12]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


                  type uint8 {
                      range "1..255";
                  }
              }
              leaf applicationCode {
                  description "This parameter indicates the transceiver
                     application code at Ss and Rs as defined in
                     [ITU.G698.2] Chapter 5.3, that is/should be used by
                     this interface.
                     The optIfOChApplicationsCodeList has all the
                     application codes supported by this interface. ";
                  }
                  type string {
                      length "1..256";
                  }
              }
      }


      grouping optIfOChApplicationCodeList {
          description " List of Application codes group"
          leaf numberApplicationCodesSupported {
              type uint32;
              description " Number of Application codes supported by
                            this interface";
          }
          list applicationCodeList {
              key "applicationCodeId";
              uses   optIfApplicationCode;
          }
      }


     grouping optIfOChPower {
         leaf outputPower {
            type int32;
            units ".01dbm"
            description " The output power for this interface in .01
                          dbm "
         }

         leaf inputPower {
             type int32;
             units ".01dbm";
             description " The current input power of this interface";
          }
     }




G.Galimberti, et al.     Expires April 27, 2015                [Page 13]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


     grouping optIfOChWavelength {
          leaf wavelengthn {
              type uint32;
              description " This parameter indicate minimum wavelength
              spectrum - n, in a definite wavelength Band (L, C and S)
              as represented in[RFC6205] by the formula -
              Wavelength (nm ) = 1471nm + n* Channel Spacing
                                                (converted to nm)
              Eg - Channel Spacing in nm
              'Wavelength (nm ) = 1471nm + n* 20nm  (20nm is the
                spacing for CWDM)' ";

            }
     }

      notification optIfOChWavelengthChange {
         leaf "if-name" {
             type leafref {
                 path "/if:interface/name";
             }
         }
         container wavelength {
             uses optIfOChWavelength;
         }
      }

      notification optIfOChApplicationCodeChange {
         leaf "if-name" {
             type leafref {
                 path "/if:interface/name";
             }
         }
         container newApplicationCode {
             uses optIfApplicationCode;
         }
      }


      notification optIfOChVendorTransceiverCodeChange {
         leaf "if-name" {
             type leafref {
                 path "/if:interface/name";
             }
         }
         container newVendorTransceiverClass {
            uses optIfVendorTransceiverClass;
        }
      }



G.Galimberti, et al.     Expires April 27, 2015                [Page 14]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


      augment "/if:interfaces/if:interface" {

         container optIfOChRsSs {
           description " RsSs path configuration for an interface";

            container ifCurrentApplicationCode {
               uses optIfOChApplicationCode;
            }

            container ifCurrentVendorTransceiverClass {
                uses optIfOChVendorTransceiverClasses;
            }

            container ifSupportedApplicationCodes {
                uses optIfOChApplicationCodesList;
            }

            container ifSupportedVendorTransceiverClass {
                uses optIfOChVendorTransceiverClassList;
            }

            uses optIfOChPower;

            uses optIfOChWavelength;

         }
      }
}



7.  Security Considerations

   The YANG module defined in this memo is designed to be accessed via
   the NETCONF protocol [RFC6241]. he lowest NETCONF layer is the secure
   transport layer and the mandatory-to-implement secure transport is
   SSH [RFC6242].  The NETCONF access control model [RFC6536] provides
   the means to restrict access for particular NETCONF users to a pre-
   configured subset of all available NETCONF protocol operation and
   content.

8.  IANA Considerations

   This document registers a URI in the IETF XML registry [RFC3688].
   Following the format in [RFC3688], the following registration is
   requested to be made:

   URI: urn:ietf:params:xml:ns:yang:ietf-interfaces:ietf-opt-if-g698-2



G.Galimberti, et al.     Expires April 27, 2015                [Page 15]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


   Registrant Contact: The IESG.

   XML: N/A, the requested URI is an XML namespace.

   This document registers a YANG module in the YANG Module Names
   registry [RFC6020].

   This document registers a YANG module in the YANG Module Names
   registry [RFC6020].

   prefix: ietf-opt-if-g698-2 reference: RFC XXXX

9.  Contributors

               Dean Bogdanovic
                 Juniper Networks
                 Westford
                 U.S.A.
                 email deanb@juniper.net

               Bernd Zeuner
                 Deutsche Telekom
                 Darmstadt
                 Germany
                 email B.Zeuner@telekom.de

               Arnold Mattheus
                 Deutsche Telekom
                 Darmstadt
                 Germany
                 email a.mattheus@telekom.de

               Manuel Paul
                 Deutsche Telekom
                 Berlin
                 Germany
                 email Manuel.Paul@telekom.de

               Walid Wakim
                 Cisco
                 9501 Technology Blvd
                 ROSEMONT, ILLINOIS 60018
                 UNITED STATES
                 email wwakim@cisco.com







G.Galimberti, et al.     Expires April 27, 2015                [Page 16]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


10.  References

10.1.  Normative References

   [RFC2863]  McCloghrie, K. and F. Kastenholz, "The Interfaces Group
              MIB", RFC 2863, June 2000.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2578]  McCloghrie, K., Ed., Perkins, D., Ed., and J.
              Schoenwaelder, Ed., "Structure of Management Information
              Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.

   [RFC2579]  McCloghrie, K., Ed., Perkins, D., Ed., and J.
              Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
              58, RFC 2579, April 1999.

   [RFC2580]  McCloghrie, K., Perkins, D., and J. Schoenwaelder,
              "Conformance Statements for SMIv2", STD 58, RFC 2580,
              April 1999.

   [RFC3591]  Lam, H-K., Stewart, M., and A. Huynh, "Definitions of
              Managed Objects for the Optical Interface Type", RFC 3591,
              September 2003.

   [RFC6205]  Otani, T. and D. Li, "Generalized Labels for Lambda-
              Switch-Capable (LSC) Label Switching Routers", RFC 6205,
              March 2011.

   [ITU.G698.2]
              International Telecommunications Union, "Amplified
              multichannel dense wavelength division multiplexing
              applications with single channel optical interfaces",
              ITU-T Recommendation G.698.2, November 2009.

   [ITU.G709]
              International Telecommunications Union, "Interface for the
              Optical Transport Network (OTN)", ITU-T Recommendation
              G.709, March 2003.

   [ITU.G872]
              International Telecommunications Union, "Architecture of
              optical transport networks", ITU-T Recommendation G.872,
              November 2001.






G.Galimberti, et al.     Expires April 27, 2015                [Page 17]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


   [ITU.G798]
              International Telecommunications Union, "Characteristics
              of optical transport network hierarchy equipment
              functional blocks", ITU-T Recommendation G.798, October
              2010.

   [ITU.G874]
              International Telecommunications Union, "Management
              aspects of optical transport network elements", ITU-T
              Recommendation G.874, July 2010.

   [ITU.G874.1]
              International Telecommunications Union, "Optical transport
              network (OTN): Protocol-neutral management information
              model for the network element view", ITU-T Recommendation
              G.874.1, January 2002.

   [ITU.G959.1]
              International Telecommunications Union, "Optical transport
              network physical layer interfaces", ITU-T Recommendation
              G.959.1, November 2009.

   [ITU.G826]
              International Telecommunications Union, "End-to-end error
              performance parameters and objectives for international,
              constant bit-rate digital paths and connections", ITU-T
              Recommendation G.826, November 2009.

   [ITU.G8201]
              International Telecommunications Union, "Error performance
              parameters and objectives for multi-operator international
              paths within the Optical Transport Network (OTN)", ITU-T
              Recommendation G.8201, April 2011.

   [ITU.G694.1]
              International Telecommunications Union, "Spectral grids
              for WDM applications: DWDM frequency grid", ITU-T
              Recommendation G.694.1, June 2002.

   [ITU.G7710]
              International Telecommunications Union, "Common equipment
              management function requirements", ITU-T Recommendation
              G.7710, May 2008.








G.Galimberti, et al.     Expires April 27, 2015                [Page 18]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


10.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.

   [RFC2629]  Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
              June 1999.

   [RFC4181]  Heard, C., "Guidelines for Authors and Reviewers of MIB
              Documents", BCP 111, RFC 4181, September 2005.

   [I-D.kunze-g-698-2-management-control-framework]
              Kunze, R., "A framework for Management and Control of
              optical interfaces supporting G.698.2", draft-kunze-
              g-698-2-management-control-framework-00 (work in
              progress), July 2011.

   [RFC4054]  Strand, J. and A. Chiu, "Impairments and Other Constraints
              on Optical Layer Routing", RFC 4054, May 2005.

Appendix A.  Change Log

   This optional section should be removed before the internet draft is
   submitted to the IESG for publication as an RFC.

   Note to RFC Editor: please remove this appendix before publication as
   an RFC.

Appendix B.  Open Issues

   Note to RFC Editor: please remove this appendix before publication as
   an RFC.

Authors' Addresses

   Gabriele Galimberti (editor)
   Cisco
   Via Philips,12
   20052 - Monza
   Italy

   Phone: +390392091462
   Email: ggalimbe@cisco.com







G.Galimberti, et al.     Expires April 27, 2015                [Page 19]


Internet-Draft    draft-dharini-netmod-g-698-2-yang-01      October 2014


   Ruediger Kunze (editor)
   Deutsche Telekom
   Dddd, xx
   Berlin
   Germany

   Phone: +49xxxxxxxxxx
   Email: RKunze@telekom.de


   Kam Lam (editor)
   Alcatel-Lucent
   USA

   Phone: +1 732 331 3476
   Email: kam.lam@alcatel-lucent.com


   Dharini Hiremagalur (editor)
   Juniper
   1194 N Mathilda Avenue
   Sunnyvale - 94089 California
   USA

   Phone: +1408
   Email: dharinih@juniper.net


   Gert Grammel (editor)
   Juniper
   1194 N Mathilda Avenue
   Sunnyvale - 94089 California
   USA

   Phone: +1408
   Email: ggrammel@juniper.net















G.Galimberti, et al.     Expires April 27, 2015                [Page 20]