MPLS Working Group                                               T. Saad
Internet-Draft                                                   K. Raza
Intended status: Standards Track                               R. Gandhi
Expires: September 22, November 12, 2016                             Cisco Systems Inc
                                                                  X. Liu
                                                                Ericsson
                                                               V. Beeram
                                                        Juniper Networks
                                                                 H. Shah
                                                                   Ciena
                                                              I. Bryskin
                                                                 X. Chen
                                                     Huawei Technologies
                                                                R. Jones
                                                                 Brocade
                                                                  B. Wen
                                                                 Comcast
                                                          March 21,
                                                            May 11, 2016

                 A YANG Data Model for MPLS Base and Static LSPs
                     draft-saad-mpls-static-yang-02
                     draft-saad-mpls-static-yang-03

Abstract

   This document contains a the specification of two YANG modules, for the MPLS
   base, and Static LSP Label
   Switched Paths (LSPs) YANG modules. model.  The MPLS base YANG module serves
   as a base framework model allows for configuring the
   provisioning of static LSP(s) on LER(s) and managing an MPLS switching
   subsystem. LSR(s) devices along a
   LSP path without the dependency on any signaling protocol.  The MPLS
   Static LSP module model augments the MPLS base YANG
   module model with specific data
   to configure and manage MPLS Static LSP(s).
   It is expected that other MPLS YANG modules for MPLS technology YANG
   modules (e.g.  MPLS LDP or MPLS RSVP-TE) will also augment the MPLS
   YANG base model.

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
   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 September 22, November 12, 2016.

Copyright Notice

   Copyright (c) 2016 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
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   3
       2.1.1.
     1.2.  MPLS Base Static LSPs Model Tree Diagram . . . . . . . . . . . . . . .   4
       2.1.2.
     1.3.  MPLS Static LSP Tree Diagram  . . . . . . . . . . . .   4
     2.2. YANG Modules  . . . . . . . . . . . . . . . . . . . . . .   6
       2.2.1.  MPLS Base Module . . . . . . . . . . . . . . . . . .   6
       2.2.2.  MPLS Static LSP YANG Module . . . . . . . . . . . . .   8
   3.   5
   2.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   4.  11
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   5.  11
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     5.1.  11
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     5.2.  11
     4.2.  Informative References  . . . . . . . . . . . . . . . . .  14  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15  12

1.  Introduction

   AAA

1.1.  Terminology

   In this document, the key words "MUST", "MUST NOT", "REQUIRED",
   "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",

   This document describes a YANG data model for configuring and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119
   [RFC2119].
   managing the Static LSPs feature.  The following terms are defined in [RFC6020]:

   o augment,

   o model allows the configuration data,

   o data model,

   o data node,

   o feature,

   o mandatory node,

   o module,

   o schema tree,

   o state data,

   o RPC operation.

2.  Introduction
   of LER and LSR devices with the necessary MPLS cross-connects or
   bindings to realize an end-to-end LSP service.

   A core routing data model static LSP is defined in
   [I-D.ietf-netmod-routing-cfg], established by manually specifying incoming and it proposes a basis for
   outgoing MPLS label(s) and necessary forwarding information on each
   of the
   development traversed Label Edge Router (LER) and Label Switched Router
   (LSR) devices (ingress, transit, or egress nodes) of data models for routing protocols.  The MPLS base
   model augments this the forwarding
   path.

   For example, on an ingress LER device, the model with additional data is used to associate
   a specific Forwarding Equivalence Class (FEC) of packets- e.g.
   matching a specific IP prefix in a Virtual Routing or Forwarding
   (VRF) instance- to an MPLS
   switching.  The interface data model is defined in [RFC7223] outgoing label imposition, next-hop(s) and
   respective outgoing interface(s) to forward the packet.  On an LSR
   device, the model is used for referencing interface from the MPLS base model.

   This document contains to create a specification of the following YANG modules:

   o  Module "ietf-mpls" provides base components of the MPLS data
      model.

   o  Module "ietf-mpls-static" binding that augments "ietf-mpls" swaps the incoming
   label with
      additional data specific to configuration an outgoing label and management of Static
      LSPs.

   Note, forwards the packet on one or
   multiple egress path(s).  On an egress LER, it is expected that other MPLS YANG models used to augment create a
   binding that decapsulates the
   "ietf-mpls" base model to define specific data to other incoming MPLS
   technologies (e.g. label and performs
   forwarding based on the inner MPLS LDP label (if present) or MPLS RSVP-TE).

2.1.  Overview IP
   forwarding in the packet.

   The MPLS base Static LSP YANG model is defined in module augments the "routing/routing-instance/
   routing- protocols/routing-protocol" path for the "rw" branch, "ietf-mpls-
   static" and augments path "routing-state/routing-instance/routing- protocols/
   routing-protocol" for the "ro" branch of the ietf-routing module. MPLS Base YANG model defined in module
   "ietf-mpls" in [I-D.saad-mpls-base-yang].  The approach described
   in [I-D.openconfig-netmod-opstate] is adopted to represent data
   pertaining to configuration intended, applied state and derived state
   data elements.  Each container in the model holds a "config" and
   "state" sub-container.  The "config" sub-container is used to
   represent the intended configurable parameters, and the state
   sub-container sub-
   container is used to represent both the applied configurable
   parameters and any derived state, such as counters or statistical
   information.

2.1.1.

1.1.  Terminology

   In this document, the key words "MUST", "MUST NOT", "REQUIRED",
   "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
   and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119
   [RFC2119].

   The following terms are defined in [RFC6020]:

   o augment,

   o configuration data,

   o data model,

   o data node,

   o feature,

   o mandatory node,

   o module,

   o schema tree,

   o state data,

   o RPC operation.

1.2.  MPLS Base Static LSPs Model Tree Diagram

   The MPLS base Static LSP tree diagram is shown in Figure 1.

   module: ietf-mpls
   augment /rt:routing:
      +--rw mpls
         +--rw interface* [name]
            +--rw name      if:interface-ref
            +--rw config
            |  +--rw enabled?   boolean
            +--ro state
               +--ro enabled?   boolean
   augment /rt:routing-state:
      +--ro mpls

                     Figure 1: MPLS Base tree diagram

2.1.2.  MPLS Static LSP Tree Diagram

   The MPLS Static LSP tree diagram is shown in Figure 2.

module: ietf-mpls ietf-mpls-static
   augment /rt:routing: /rt:routing/mpls:mpls:
      +--rw mpls static-lsps
         +--rw interface* static-lsp* [name]
      |
            +--rw name      if:interface-ref
      |  +--rw config
      |  |  +--rw enabled?   boolean
      |  +--ro state
      |     +--ro enabled?   boolean
      +--rw mpls-static:static-lsps
         +--rw mpls-static:static-lsp* [name]
            +--rw mpls-static:name      string
            +--rw mpls-static:config config
            |  +--rw mpls-static:in-segment in-segment
            |  |  +--rw (type)?
            |  |     +--:(ip-prefix)
            |  |     |  +--rw mpls-static:ip-prefix? ip-prefix?        inet:ip-prefix
            |  |     +--:(mpls-label)
            |  |        +--rw mpls-static:incoming-label?mpls:mpls-label
            |  +--rw mpls-static:operation?            enumeration
            |  +--rw (out-segment)?
            |     +--:(simple-path)
            |     |  +--rw mpls-static:next-hop?       inet:ip-address
            |     |  +--rw mpls-static:outgoing-label? incoming-label?   mpls:mpls-label
            |     |  +--rw mpls-static:outgoing-interface?
            |     +--:(path-list)
            |  +--rw mpls-static:paths* [path-index]
            |           +--rw mpls-static:path-index         uint32
            |           +--rw mpls-static:backup-path-index? uint32
            |           +--rw mpls-static:next-hop?  inet:ip-address
            |           +--rw mpls-static:outgoing-labels* [index]
            |           |  +--rw mpls-static:index    uint32
            |           |  +--rw mpls-static:label?   mpls:mpls-label
            |           +--rw mpls-static:outgoing-interface?
            |           +--rw mpls-static:loadshare? mpls:percent
            |           +--rw mpls-static:role? operation?            enumeration
            +--ro mpls-static:state
               +--ro mpls-static:in-segment
            |  +--ro (type)?
               |     +--:(ip-prefix)
               |     |  +--ro mpls-static:ip-prefix? inet:ip-prefix
               |     +--:(mpls-label)
               |        +--ro mpls-static:incoming-label?mpls:mpls-label
               +--ro mpls-static:operation?            enumeration
               +--ro  +--rw (out-segment)?
                  +--:(simple-path)
                  |  +--ro mpls-static:next-hop?       inet:ip-address
                  |  +--ro mpls-static:outgoing-label? mpls:mpls-label
                  |  +--ro mpls-static:outgoing-interface?
                  +--:(path-list)
                     +--ro mpls-static:paths* [path-index]
                        +--ro mpls-static:path-index            uint32
                        +--ro mpls-static:backup-path-index?    uint32
                        +--ro mpls-static:next-hop? inet:ip-address
                        +--ro mpls-static:outgoing-labels* [index]
                        |  +--ro mpls-static:index    uint32
                        |  +--ro mpls-static:label?   mpls:mpls-label
                        +--ro mpls-static:outgoing-interface?
                        +--ro mpls-static:loadshare? mpls:percent
                        +--ro mpls-static:role?      enumeration
augment /rt:routing-state:
   +--ro mpls

                  Figure 2: MPLS Static LSP tree diagram

2.2.  YANG Modules

2.2.1.  MPLS Base Module

   <CODE BEGINS>file "ietf-mpls@2016-03-21.yang"

   module ietf-mpls {

     namespace "urn:ietf:params:xml:ns:yang:ietf-mpls";

     prefix "mpls";

     import ietf-routing {
       prefix "rt";
     }

     import ietf-interfaces {
       prefix "if";
     }

     organization "TBD";

     contact "TBD";

     description
       "This YANG module defines the essential components for the
        management of the MPLS subsystem.";

     revision "2016-03-21" {
       description
         "Initial revision";
       reference "RFC 3031: A YANG Data Model for base MPLS";
     }

     typedef mpls-label {
       type uint32 {
         range "0..1048575";
       }
       description
         "The MPLS label range";
     }

     typedef percent {
       type uint16 {
         range "0 .. 100";
       }
       description "Percentage";
     }
     grouping interface-mpls {
       description "MPLS interface properties grouping";
       leaf enabled {
         type boolean;
         description
           "'true' if mpls encapsulation is enabled on the
            interface. 'false' if mpls encapsulation is enabled
            on the interface.";
       }
     }

     augment "/rt:routing" {
       description "MPLS augmentation.";
       container mpls {
         description
           "MPLS container, to be used as an augmentation target node
            other MPLS sub-features config, e.g. MPLS static LSP, MPLS
            LDP LSPs, and Trafic Engineering MPLS LSP Tunnels, etc.";

         list interface {
           key "name";
           description "List of MPLS interfaces";
           leaf name {
             type if:interface-ref;
             description
               "The name of a configured MPLS interface";
           }
           container config {
             description "Holds intended configuration";
             uses interface-mpls;
           }
           container
            |     +--:(simple-path)
            |     |  +--rw next-hop?             inet:ip-address
            |     |  +--rw outgoing-label?       mpls:mpls-label
            |     |  +--rw outgoing-interface?   if:interface-ref
            |     +--:(path-list)
            |        +--rw paths* [path-index]
            |           +--rw path-index            uint16
            |           +--rw backup-path-index?    uint16
            |           +--rw next-hop?             inet:ip-address
            |           +--rw outgoing-labels*      mpls:mpls-label
            |           +--rw outgoing-interface?   if:interface-ref
            |           +--rw loadshare?            uint16
            |           +--rw role?                 enumeration
            +--ro state {
             config false;
             description "Holds inuse configuration";
             uses interface-mpls;
           }
         }
       }
     }

     augment "/rt:routing-state" {
       description "MPLS augmentation.";
       container mpls {
         config false;
         description
           "MPLS container, to be used as an augmentation target node
            other MPLS sub-features state";
       }

     }
   }

   <CODE ENDS>
               +--ro in-segment
               |  +--ro (type)?
               |     +--:(ip-prefix)
               |     |  +--ro ip-prefix?        inet:ip-prefix
               |     +--:(mpls-label)
               |        +--ro incoming-label?   mpls:mpls-label
               +--ro operation?            enumeration
               +--ro (out-segment)?
                  +--:(simple-path)
                  |  +--ro next-hop?             inet:ip-address
                  |  +--ro outgoing-label?       mpls:mpls-label
                  |  +--ro outgoing-interface?   if:interface-ref
                  +--:(path-list)
                     +--ro paths* [path-index]
                        +--ro path-index            uint16
                        +--ro backup-path-index?    uint16
                        +--ro next-hop?             inet:ip-address
                        +--ro outgoing-labels*      mpls:mpls-label
                        +--ro outgoing-interface?   if:interface-ref
                        +--ro loadshare?            uint16
                        +--ro role?                 enumeration

                  Figure 3: 1: MPLS base YANG module

2.2.2. Static LSP tree diagram

1.3.  MPLS Static LSP YANG Module

 <CODE BEGINS>file "ietf-mpls-static@2016-03-21.yang" "ietf-mpls-static@2016-05-11.yang"

 module ietf-mpls-static {

   namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static";

   prefix "mpls-static";

   import ietf-mpls {
     prefix mpls;
   }

   import ietf-routing {
     prefix "rt";
   }

   import ietf-inet-types {
     prefix inet;
   }

   import ietf-interfaces {
     prefix "if";
   }

   organization "TBD"; "IETF MPLS Working Group";

   contact "TBD";
     "WG Web:   <http://tools.ietf.org/wg/mpls/>

      WG List:  <mailto:mpls@ietf.org>

      WG Chair: Loa Andersson
                <mailto:loa@pi.nu>

      WG Chair: Ross Callon
                <mailto:rcallon@juniper.net>

      WG Chair: George Swallow
                <mailto:swallow.ietf@gmail.com>

      Editor:   Tarek Saad
                <mailto:tsaad@cisco.com>

      Editor:   Kamran Raza
                <mailto:skraza@cisco.com>

      Editor:   Rakesh Gandhi
                <mailto:rgandhi@cisco.com>

      Editor:   Xufeng Liu
                <mailto: xufeng.liu.ietf@gmail.com>

      Editor:   Vishnu Pavan Beeram
                <mailto:vbeeram@juniper.net>

      Editor:   Himanshu Shah
                <mailto:hshah@ciena.com>

      Editor:   Igor Bryskin
                <mailto: Igor.Bryskin@huawei.com>

      Editor:   Xia Chen
                <mailto:jescia.chenxia@huawei.com>

      Editor:   Raqib Jones
                <mailto:raqib@Brocade.com>

      Editor:   Bin Wen
                <mailto:Bin_Wen@cable.comcast.com>";

   description
      "This YANG module augments the 'ietf-routing' module with basic
      configuration and operational state data for MPLS static";

   revision "2016-03-21" "2016-05-11" {
     description
         "Initial revision";
       "Latest revision:
         - Addressed MPLS-RT review comments";
     reference "RFC 3031: A YANG Data Model for Static MPLS Static"; LSPs";
   }

   grouping path-basic_config {
     description "common definitions for statics";

     leaf next-hop {
       type inet:ip-address;
       description "next hop IP address for the LSP";
     }

     leaf outgoing-label {
       type mpls:mpls-label;
       description
         "label value to push at the current hop for the
          LSP";
     }

     leaf outgoing-interface {
       type if:interface-ref;
       description
         "The outgoing interface";
     }

   }

   grouping path-properties_config {
     description
       "MPLS path properties";
     leaf path-index {
       type uint32; uint16;
       description
         "Path identifier";
     }

     leaf backup-path-index {
       type uint32;
       description
         "Backup path identifier";
     }

     leaf next-hop {
       type inet:ip-address;
       description
         "The address of the next-hop";
     }

       list

     leaf-list outgoing-labels {
         key index;
       type mpls:mpls-label;
       ordered-by user;
       description
         "The outgoing MPLS labels to impose";

         leaf index {
           type uint32;
           description
             "The index of the label, lower indices are closer to
              the top";
         }
         leaf label {
           type mpls:mpls-label;
           description
             "The MPLS label value";
         }
     }

     leaf outgoing-interface {
       type if:interface-ref;
       description
         "The outgoing interface";
     }

     leaf loadshare {
       type mpls:percent; uint16;
       description
           "The percentage of total
         "This value is used to compute a loadshare to perform un-equal
          load tto carry on balancing when multiple outgoing path(s) are specified. A
          share is computed as a ratio of this path"; number to the total under
          all configured path(s).";
     }

     leaf role {
       type enumeration {
         enum PRIMARY {
           description
             "Path as primary traffic carrying";
         }
         enum BACKUP {
           description
             "Path acts as backup";
         }
         enum PRIMARY_AND_BACKUP {
           description
             "Path acts as primary and backup simultaneously";
         }
       }
       description
         "The MPLS path role";
     }
   }

   grouping static-lsp_config {
     description "common definitions for static LSPs";

     container in-segment {
       description
         "MPLS incoming segment";
       choice type {
         description
           "Basic FEC choice";
         case ip-prefix {
           leaf ip-prefix {
             type inet:ip-prefix;
             description "An IP prefix";
           }
         }
         case mpls-label {
           leaf incoming-label {
             type mpls:mpls-label;
             description "label value on the incoming packet";
           }
         }
       }
     }

     leaf operation {
       type enumeration {
         enum impose-and-forward {
           description
             "Operation impose outgoing label(s) and forward to
              next-hop";
         }
         enum pop-and-forward {
           description
             "Operation pop outgoing incoming label and forward to next-hop";
         }
         enum pop-impose-and-forward {
           description
             "Operation pop incoming label, impose one or more
              outgoing label(s) and forward to next-hop";
         }
         enum swap-and-forward {
           description
             "Operation swap incoming label, with outgoing label and
              forward to next-hop";
         }
         enum pop-and-lookup {
           description
             "Operation pop incoming label and perform a lookup";
         }
       }
       description
         "The MPLS operation to be executed on the incoming packet";
     }

     choice out-segment {
       description "The MPLS out-segment type choice";
       case simple-path {
         uses path-basic_config;
       }
       case path-list {
         list paths {
           key path-index;
           description
             "The list of MPLS paths associated with the FEC";
           uses path-properties_config;
         }
       }
     }
   }

   grouping static-lsp {
     description "grouping for top level list of static LSPs";
     container config {
       description
         "Holds the intended configuration";
       uses static-lsp_config;
     }
     container state {
       config false;
       description
         "Holds the state and inuse configuration";
       uses static-lsp_config;
     }
   }

   augment "/rt:routing/mpls:mpls" {
     description "Augmentations for MPLS Static LSPs";
     container static-lsps {
       description
         "Statically configured LSPs, without dynamic signaling";
       list static-lsp {
         key name;
         description "list of defined static LSPs";

         leaf name {
           type string;
           description "name to identify the LSP";
         }
         uses static-lsp;
       }
     }
   }
 }

 <CODE ENDS>

                   Figure 4: 2: MPLS Static LSP YANG module

3.

2.  IANA Considerations

   This document registers the following URIs 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-mpls XML: N/A, the requested
   URI is an XML namespace.

   URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static XML: N/A, the
   requested URI is an XML namespace.

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

   name: ietf-mpls namespace: urn:ietf:params:xml:ns:yang:ietf-mpls
   prefix: ietf-mpls reference: RFC3031

   name: ietf-mpls-static namespace: urn:ietf:params:xml:ns:yang:ietf-
   mpls-static prefix: ietf-mpls-static reference: RFC3031

4.

3.  Security Considerations

   The YANG module defined in this memo is designed to be accessed via
   the NETCONF protocol [RFC6241].  The 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 means to restrict access for particular NETCONF
   users to a pre-configured subset of all available NETCONF protocol
   operations and content.

   There are a number of data nodes defined in the YANG module which are
   writable/creatable/deletable (i.e., config true, which is the
   default).  These data nodes may be considered sensitive or vulnerable
   in some network environments.  Write operations (e.g., <edit-config>)
   to these data nodes without proper protection can have a negative
   effect on network operations.

5.

4.  References

5.1.

4.1.  Normative References

   [I-D.ietf-netmod-routing-cfg]
              Lhotka, L.

   [I-D.saad-mpls-base-yang]
              Raza, K., Gandhi, R., Liu, X., Beeram, V., Saad, T., Chen,
              X., Jones, R., and A. Lindem, B. Wen, "A YANG Data Model for Routing
              Management", draft-ietf-netmod-routing-cfg-21 MPLS
              Base and Static LSPs", draft-saad-mpls-base-yang-00
              (work in progress), March November 2016.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
              RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              DOI 10.17487/RFC3688, January 2004,
              <http://www.rfc-editor.org/info/rfc3688>.

   [RFC6020]  Bjorklund, M., Ed., "YANG - A Data Modeling Language for
              the Network Configuration Protocol (NETCONF)", RFC 6020,
              DOI 10.17487/RFC6020, October 2010,
              <http://www.rfc-editor.org/info/rfc6020>.

   [RFC6241]  Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
              and A. Bierman, Ed., "Network Configuration Protocol
              (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
              <http://www.rfc-editor.org/info/rfc6241>.

   [RFC6242]  Wasserman, M., "Using the NETCONF Protocol over Secure
              Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
              <http://www.rfc-editor.org/info/rfc6242>.

   [RFC6536]  Bierman, A. and M. Bjorklund, "Network Configuration
              Protocol (NETCONF) Access Control Model", RFC 6536, DOI
              10.17487/RFC6536, March 2012,
              <http://www.rfc-editor.org/info/rfc6536>.

   [RFC7223]  Bjorklund, M., "A YANG Data Model for Interface
              Management", RFC 7223, DOI 10.17487/RFC7223, May 2014,
              <http://www.rfc-editor.org/info/rfc7223>.

5.2.

4.2.  Informative References

   [I-D.openconfig-netmod-opstate]
              Shakir, R., Shaikh, A., and M. Hines, "Consistent Modeling
              of Operational State Data in YANG", draft-openconfig-
              netmod-opstate-01 (work in progress), July 2015.

Authors' Addresses

   Tarek Saad
   Cisco Systems Inc

   Email: tsaad@cisco.com

   Kamran Raza
   Cisco Systems Inc

   Email: skraza@cisco.com

   Rakesh Gandhi
   Cisco Systems Inc

   Email: rgandhi@cisco.com
   Xufeng Liu
   Ericsson

   Email: xufeng.liu@ericsson.com xufeng.liu.ietf@gmail.com

   Vishnu Pavan Beeram
   Juniper Networks

   Email: vbeeram@juniper.net

   Himanshu Shah
   Ciena

   Email: tsaad@cisco.com hshah@ciena.com

   Igor Bryskin
   Huawei Technologies

   Email: Igor.Bryskin@huawei.com

   Xia Chen
   Huawei Technologies

   Email: jescia.chenxia@huawei.com

   Raqib Jones
   Brocade

   Email: raqib@Brocade.com

   Bin Wen
   Comcast

   Email: Bin_Wen@cable.comcast.com