draft-ietf-ccamp-l1csm-yang-09.txt   draft-ietf-ccamp-l1csm-yang-10.txt 
CCAMP Working Group G. Fioccola (Ed.)
Telecom Italia
Internet Draft K. Lee
Intended Status: Standard Track Korea Telecom
Expires: September 6, 2019 Y. Lee (Ed.)
D. Dhody
Huawei
O. Gonzalez de-Dios
Telefonica
D. Ceccarelli
Ericsson
March 6, 2019 CCAMP Working Group Y. Lee
Internet-Draft SKKU
A YANG Data Model for L1 Connectivity Service Model (L1CSM) Intended status: Standards Track K. Lee
Expires: March 12, 2020 Korea Telecom
H. Zheng
D. Dhody
Huawei Technologies
O. Gonzalez de Dios
Telefonica
D. Ceccarelli
Ericsson
September 9, 2019
draft-ietf-ccamp-l1csm-yang-09 A YANG Data Model for L1 Connectivity Service Model (L1CSM)
draft-ietf-ccamp-l1csm-yang-10
Abstract Abstract
This document provides a YANG data model for Layer 1 Connectivity This document provides a YANG data model for Layer 1 Connectivity
Service Model (L1CSM). The intent of this document is to provide a Service Model (L1CSM). The intent of this document is to provide a
transport service model exploiting YANG data model, which can be Layer 1 service model exploiting YANG data model, which can be
utilized by a client network controller to initiate a service utilized by a customer network controller to initiate a service
request connectivity request as well as retrieving service states request connectivity as well as retrieving service states toward a
toward a transport network controller communicating with the client Layer 1 network controller communicating with its customer network
controller. This YANG model is NMDA-compliant. controller. This YANG model is NMDA-compliant.
Status of this Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted in full conformance with the
the provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at https://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."
The list of current Internet-Drafts can be accessed at Internet-Drafts are draft documents valid for a maximum of six months
http://www.ietf.org/ietf/1id-abstracts.txt 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."
The list of Internet-Draft Shadow Directories can be accessed at This Internet-Draft will expire on March 12, 2020.
http://www.ietf.org/shadow.html
This Internet-Draft will expire on September 6, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with respect
respect to this document. Code Components extracted from this to this document. Code Components extracted from this document must
document must include Simplified BSD License text as described in include Simplified BSD License text as described in Section 4.e of
Section 4.e of the Trust Legal Provisions and are provided without the Trust Legal Provisions and are provided without warranty as
warranty as described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Deployment Scenarios......................................3 1.1. Deployment Scenarios . . . . . . . . . . . . . . . . . . 3
1.2. Terminology...............................................6 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6
1.3. Tree diagram..............................................6 1.3. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 6
1.4. Prefixes in Data Node Names...............................6 1.4. Prefixes in Data Node Names . . . . . . . . . . . . . . . 6
2. Definitions....................................................7 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. L1SM YANG Model (Tree Structure)...............................7 3. L1CSM YANG Model (Tree Structure) . . . . . . . . . . . . . . 7
4. L1SM YANG Code.................................................8 4. L1CSM YANG Code . . . . . . . . . . . . . . . . . . . . . . . 8
5. JSON Example..................................................21 5. JSON Example . . . . . . . . . . . . . . . . . . . . . . . . 12
6. Security Considerations.......................................22 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14
7. IANA Considerations...........................................23 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
8. Acknowledgments...............................................24 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
9. References....................................................25 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References.....................................25 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.2. Informative References...................................25 10.1. Normative References . . . . . . . . . . . . . . . . . . 15
10. Contributors.................................................26 10.2. Informative References . . . . . . . . . . . . . . . . . 16
Authors' Addresses...............................................26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
This document provides a YANG data model for L1VPN Connectivity This document provides a YANG data model for L1VPN Connectivity
Service Model (L1CSM) which can be classified as Network Service Service Model (L1CSM) which can be classified as Network Service YANG
YANG module per [RFC8199]. The intent of this document is to provide module per [RFC8199]. The intent of this document is to provide a
a transport service model exploiting YANG data model, which can be transport service model exploiting YANG data model, which can be
utilized by a client network controller to initiate a service utilized by a client network controller to initiate a service request
request connectivity request as well as retrieving service states connectivity request as well as retrieving service states toward a
toward a transport network controller communicating with the client transport network controller communicating with the client controller
controller via a NETCONF [RFC8341] or a RESTCONF [RFC8040] via a NETCONF [RFC8341] or a RESTCONF [RFC8040] interface.
interface.
[RFC4847] provides a framework and service level requirements for [RFC4847] provides a framework and service level requirements for
Layer 1 Virtual Private Networks (L1VPNs). It classifies service Layer 1 Virtual Private Networks (L1VPNs). It classifies service
models as management-based service model, signaling-based service models as management-based service model, signaling-based service
model (Basic Mode) and signaling and routing service model (Enhanced model (Basic Mode) and signaling and routing service model (Enhanced
Mode). Mode).
In the management-based service model, customer management systems In the management-based service model, customer management systems
and provider management systems communicate with each other. and provider management systems communicate with each other.
Customer management systems access provider management systems to Customer management systems access provider management systems to
request layer 1 connection setup/deletion between a pair of CEs. request layer 1 connection setup/deletion between a pair of CEs.
Customer management systems may obtain additional information, such Customer management systems may obtain additional information, such
as resource availability information and monitoring information, as resource availability information and monitoring information, from
from provider management systems. There is no control message provider management systems. There is no control message exchange
exchange between a CE and PE. between a CE and PE.
In the signaling-based service model (Basic Model), the CE-PE In the signaling-based service model (Basic Model), the CE-PE
interface's functional repertoire is limited to path setup signaling interface's functional repertoire is limited to path setup signaling
only. In the Signaling and routing service model (Enhanced Mode), only. In the Signaling and routing service model (Enhanced Mode),
the CE-PE interface provides the signaling capabilities as in the the CE-PE interface provides the signaling capabilities as in the
Basic Mode, plus permits limited exchange of information between the Basic Mode, plus permits limited exchange of information between the
control planes of the provider and the customer to help such control planes of the provider and the customer to help such
functions as discovery of customer network routing information functions as discovery of customer network routing information (i.e.,
(i.e., reachability or TE information in remote customer sites), or reachability or TE information in remote customer sites), or
parameters of the part of the provider's network dedicated to the parameters of the part of the provider's network dedicated to the
customer. customer.
The primary focus of this document is to describe L1CS YANG model The primary focus of this document is to describe L1CS YANG model
required for the instantiation of point-to-point L1VPN service. A required for the instantiation of point-to-point L1VPN service. A
L1VPN is a service offered by a core layer 1 network to provide L1VPN is a service offered by a core layer 1 network to provide layer
layer 1 connectivity between two or more customer sites where the 1 connectivity between two or more customer sites where the customer
customer has some control over the establishment and type of the has some control over the establishment and type of the connectivity.
connectivity.
The data model presented in Section 3 is in consistent with [MEF63]. The data model presented in Section 3 is in consistent with [MEF63].
The data model includes configuration and state data according to The data model includes configuration and state data according to the
the new Network Management Datastore Architecture [RFC8342]. new Network Management Datastore Architecture [RFC8342].
1.1. Deployment Scenarios 1.1. Deployment Scenarios
Figure 1 depicts a deployment scenario of the L1VPN SDN control- Figure 1 depicts a deployment scenario of the L1VPN SDN control-based
based service model for an external customer instantiating L1 point- service model for an external customer instantiating L1 point-to-
to-point connectivity to the provider. point connectivity to the provider.
+------------+ +------------+
| Customer | | Customer |
| Service | | Service |
|Orchestrator| |Orchestrator|
+------------+ +------------+
| |
.. .. .. .. ..|.. .. .. .. .. .. . .. .. .. .. ..|.. .. .. .. .. ..
: | : : | :
: +--------------------+ : : +--------------------+ :
: | | : : | | :
: | +----------+ | : : | +----------+ | :
: | | Network | | : : | | Network | | :
: | | SDN | | : : | | SDN | | :
: | |Controller| | : : | |Controller| | :
: | |/NMS/EMS | | : : | |/NMS/EMS | | :
: | +----------+ | : : | +----------+ | :
: | | : : | | :
: | | : : | | :
skipping to change at page 4, line 35 skipping to change at page 4, line 35
+----+ : +----+ +----+ +----+ : +----+ +----+ : +----+ +----+ +----+ : +----+
: | | : : | | :
: | | : : | | :
: +--------------------+ : : +--------------------+ :
: | | : : | | :
: |<-Provider network->| : : |<-Provider network->| :
Customer Customer Customer Customer
Interface Interface Interface Interface
Figure 1: L1VPN SDN Controller/EMS/NMS-Based Service Model: Figure 1: L1VPN SDN Controller/EMS/NMS-Based Service Model: External
External Customer Customer
With this scenario, the customer service orchestrator interfaces With this scenario, the customer service orchestrator interfaces with
with the network SDN controller of the provider using Customer the network SDN controller of the provider using Customer Service
Service Model as defined in [RFC8309]. Model as defined in [RFC8309].
Figure 2 depicts another deployment scenario for internal customer Figure 2 depicts another deployment scenario for internal customer
(e.g., higher-layer service management department(s)) interfacing (e.g., higher-layer service management department(s)) interfacing the
the layer 1 transport network department. With this scenario, a layer 1 transport network department. With this scenario, a multi-
multi-service backbone is characterized such that each service service backbone is characterized such that each service department
department of a provider (e.g., L2/3 services) that receives the of a provider (e.g., L2/3 services) that receives the same provider's
same provider's L1VPN service provides a different kind of higher- L1VPN service provides a different kind of higher-layer service. The
layer service. The customer receiving the L1VPN service (i.e., each customer receiving the L1VPN service (i.e., each service department)
service department) can offer its own services, whose payloads can can offer its own services, whose payloads can be any layer (e.g.,
be any layer (e.g., ATM, IP, TDM). The layer 1 transport network and ATM, IP, TDM). The layer 1 transport network and each service
each service network belong to the same organization, but may be network belong to the same organization, but may be managed
managed separately. The Service SDN Controller is the separately. The Service SDN Controller is the control/management
control/management entity owned by higher-layer service department entity owned by higher-layer service department (e.g., L2/3 VPN)
(e.g., L2/3 VPN) whereas the Network SDN Controller is the whereas the Network SDN Controller is the control/management entity
control/management entity responsible for Layer 1 connectivity responsible for Layer 1 connectivity service. The CEs in Figure 2
service. The CE's in Figure 2 are L2/3 devices that interface with are L2/3 devices that interface with L1 PE devices.
L1 PE devices.
+----------+ +----------+
| Service | | Service |
| SDN | | SDN |
|Controller| |Controller|
|/EMS/NMS | |/EMS/NMS |
| for L2/3 | | for L2/3 |
+----------+ +----------+
| |
| |
| |
+--------------------+ +--------------------+
| | | |
| +----------+ | | +----------+ |
| | Network | | | | Network | |
| | SDN | | | | SDN | |
| |Controller| | | |Controller| |
| |/EMS/NMS | | | |/EMS/NMS | |
| | for L1VPN| | | | for L1VPN| |
| +----------+ | | +----------+ |
| | | |
skipping to change at page 5, line 45 skipping to change at page 5, line 43
| CE |--------| PE |----| P |----| PE |------| CE | | CE |--------| PE |----| P |----| PE |------| CE |
+----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+
| | | | | | | |
| | | | | | | |
| +--------------------+ | | +--------------------+ |
| | | | | | | |
| |<------------------>| | | |<------------------>| |
| Provider Network | | Provider Network |
| For Layer 1 | | For Layer 1 |
|<------------------------------------------>| |<------------------------------------------>|
Provider Network for L2/3 Provider Network for L2/3
Figure 2: L1VPN SDN Controller/EMS/NMS-Based Service Model: Figure 2: L1VPN SDN Controller/EMS/NMS-Based Service Model: Internal
Internal Customer Customer
The benefit is that the same layer 1 transport network resources are The benefit is that the same layer 1 transport network resources are
shared by multiple services. A large capacity backbone network shared by multiple services. A large capacity backbone network (data
(data plane) can be built economically by having the resources plane) can be built economically by having the resources shared by
shared by multiple services usually with flexibility to modify multiple services usually with flexibility to modify topologies,
topologies, while separating the control functions for each service while separating the control functions for each service department.
department. Thus, each customer can select a specific set of Thus, each customer can select a specific set of features that are
features that are needed to provide their own service [RFC4847]. needed to provide their own service [RFC4847].
1.2. Terminology 1.2. Terminology
Refer to [RFC4847] and [RFC5253] for the key terms used in this Refer to [RFC4847] and [RFC5253] for the key terms used in this
document. document.
The following terms are defined in [RFC7950] and are not redefined The following terms are defined in [RFC7950] and are not redefined
here: here:
o client o client
o server o server
o augment o augment
o data model o data model
o data node o data node
The following terms are defined in [RFC6241] and are not redefined The following terms are defined in [RFC6241] and are not redefined
here: here:
o configuration data o configuration data
o state data o state data
The terminology for describing YANG data models is found in The terminology for describing YANG data models is found in
[RFC7950]. [RFC7950].
1.3. Tree diagram 1.3. Tree Diagram
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
chapter 3 of this this document. The meaning of the symbols in Section 3 of this this document. The meaning of the symbols in these
these diagrams is defined in [RFC8340]. diagrams is defined in [RFC8340].
1.4. Prefixes in Data Node Names 1.4. Prefixes in Data Node Names
In this document, names of data nodes and other data model objects In this document, names of data nodes and other data model objects
are prefixed using the standard prefix associated with the are prefixed using the standard prefix associated with the
corresponding YANG imported modules, as shown in Table 1. corresponding YANG imported modules. The module ietf-layer1-types
specified in [I-D.ietf-ccamp-layer1-types] and ietf-yang-types
+---------+------------------------------+-----------------+ specified in [RFC6991] are imported in this module.
| Prefix | YANG module | Reference |
+---------+------------------------------+-----------------+
| l1csm | ietf-l1cms | [RFC XXXX] |
| l1-st | ietf-l1-service-types | [RFC XXXX] |
| yang | ietf-yang-types | [RFC6991] |
+---------+------------------------------+-----------------+
Table 1: Prefixes and corresponding YANG modules +-------------+-------------------+------------------------------+
| Prefix | YANG module | Reference |
+-------------+-------------------+------------------------------+
| l1csm | ietf-l1csm | [RFC XXXX] |
| layer1-types|ietf-layer1-types | [I-D.ietf-ccamp-layer1-types]|
| yang | ietf-yang-types | [RFC6991] |
+-------------+-------------------+------------------------------+
Note: The RFC Editor will replace XXXX with the number assigned to Note: The RFC Editor will replace XXXX with the number assigned to
the RFC once this draft becomes an RFC. the RFC once this draft becomes an RFC.
2. Definitions 2. Definitions
L1VC Layer 1 Virtual Connection
SLS Service Level Specification
UNI User Network Interface L1VC Layer 1 Virtual Connection
PE Provider Edge SLS Service Level Specification
CE Customer Edge UNI User Network Interface
EP End Point PE Provider Edge
P Protocol CE Customer Edge
C Coding EP End Point
O Optical Interface P Protocol
3. L1SM YANG Model (Tree Structure) C Coding
module: ietf-l1csm O Optical Interface
+--rw l1-connectivity
+--rw access
| +--rw unis
| +--rw uni* [id]
| +--rw id string
| +--rw protocol? identityref
| +--rw coding? identityref
| +--rw optical-interface? identityref
+--rw services
+--rw service* [service-id]
+--rw service-id string
+--rw endpoint-1
| +--rw id string
| +--rw uni -> /l1-connectivity/access/unis/uni/id
+--rw endpoint-2
| +--rw id string
| +--rw uni -> /l1-connectivity/access/unis/uni/id
+--rw start-time? yang:date-and-time
+--rw time-interval? int32
+--rw performance-metric* identityref
4. L1SM YANG Code 3. L1CSM YANG Model (Tree Structure)
module: ietf-l1csm
+--rw l1-connectivity
+--rw access
| +--rw unis
| +--rw uni* [id]
| +--rw id string
| +--rw protocol? identityref
| +--rw coding? identityref
| +--rw optical-interface? identityref
+--rw services
+--rw service* [service-id]
+--rw service-id string
+--rw endpoint-1
| +--rw id string
| +--rw uni -> /l1-connectivity/access/unis/uni/id
+--rw endpoint-2
| +--rw id string
| +--rw uni -> /l1-connectivity/access/unis/uni/id
+--rw start-time? yang:date-and-time
+--rw time-interval? int32
+--rw performance-metric* identityref
The YANG code is as follows: 4. L1CSM YANG Code
<CODE BEGINS> file "ietf-l1csm@2018-09-12.yang" <CODE BEGINS>file "ietf-l1csms@2019-09-09.yang"
module ietf-l1csm {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-l1csm";
prefix "l1csm";
module ietf-l1csm { import ietf-yang-types {
yang-version 1.1; prefix "yang";
namespace "urn:ietf:params:xml:ns:yang:ietf-l1csm"; }
prefix "l1csm"; import ietf-layer1-types {
import ietf-yang-types { prefix "layer1-types";
prefix "yang"; }
reference "RFC 6991 - Common YANG Data Types";
}
import ietf-l1-service-types { organization
prefix "l1-st"; "Internet Engineering Task Force (IETF) CCAMP WG";
reference "RFC XXXX - A YANG Data Model for L1 Connectivity
Service Model (L1CSM)";
}
organization contact
"Internet Engineering Task Force (IETF) CCAMP WG";
contact "Editor: Y. Lee (younglee_tx@gmail.com)
Editor: K. Lee (kwangkoog.lee@kt.com)
Editor: H. Zheng (zhenghaomian@huawei.com)
Editor: D. Dhody (dhruv.ietf@gmail.com)
Editor: O. G. de-Dios (oscar.gonzalezdedios@telefonica.com)
Editor: D. Ceccarelli (daniele.ceccarelli@ericsson.com)";
"Editor: G. Fioccolla (giuseppe.fioccola@telecomitalia.it) description
Editor: K. Lee (kwangkoog.lee@kt.com) "This module describes L1 connectivity service based on MEF 63:
Editor: Y. Lee (leeyoung@huawei.com) Subscriber Layer 1 Service Attribute Technical Specification.
Editor: D. Dhody (dhruv.ietf@gmail.com) Refer to MEF 63 for all terms and the original references
Editor: O. G. de-Dios (oscar.gonzalezdedios@telefonica.com) used in the module.
Editor: D. Ceccarelli (daniele.ceccarelli@ericsson.com)";
description Copyright (c) 2019 IETF Trust and the persons identified as
"This module describes L1 connectivity service based on MEF 63: authors of the code. All rights reserved.
Subscriber Layer 1 Service Attribute Technical Specification. Redistribution and use in source and binary forms, with or
Refer to MEF 63 for all terms and the original references without modification, is permitted pursuant to, and subject
used in the module. 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).
Copyright (c) 2018 IETF Trust and the persons identified as This version of this YANG module is part of RFC XXXX; see
authors of the code. All rights reserved. the RFC itself for full legal notices.";
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).
This version of this YANG module is part of RFC XXXX; see revision "2019-09-09" {
the RFC itself for full legal notices."; description "Initial revision.";
reference "RFC XXXX: A Yang Data Model for L1 Connectivity
Service Model (L1CSM)";
// Note: The RFC Editor will replace XXXX with the number
// assigned to the RFC once this draft becomes an RFC.
}
revision "2018-09-12" { grouping protocol-coding-optical-interface {
description "Initial revision."; description
reference "RFC XXXX: A YANG Data Model for L1 Connectivity "describes <p,c,o> where p:protocol type; c:coding
Service Model (L1CSM)"; function; o:optical interface function";
// Note: The RFC Editor will replace XXXX with the number reference "MEF 63";
// assigned to the RFC once this draft becomes an RFC. leaf protocol {
} type identityref {
base "layer1-types:client-signal";
}
description
"List of physical layer L1VC client protocol";
grouping protocol-coding-optical-interface {
description
"describes <p,c,o> where p:protocol type; c:coding
function; o:optical interface function";
reference "MEF 63";
leaf protocol {
type identityref {
base "l1-st:protocol-type";
} }
description leaf coding {
"List of physical layer L1VC clientprotocol"; type identityref {
base "layer1-types:coding-func";
} }
leaf coding { description "coding function";
type identityref { }
base "l1-st:coding-func";
}
description "coding function";
}
leaf optical-interface {
type identityref {
base "l1-st:optical-interface-func";
}
description "optical-interface-function";
}
}
grouping subscriber-l1vc-sls-service-attribute {
description
"The value of the Subscriber L1VC SLS (Service Level
Specification) Service Attribute";
reference "MEF 63";
leaf start-time {
type yang:date-and-time;
description "a time that represent the date and time
for the start of the SLS";
}
leaf time-interval {
type int32;
units seconds;
description "a time interval (e.g., 2,419,200 seconds
which is 28 days) that is used in
conjunction wuth time-start to specify a
contiguous sequence of time intervals T for
determining when performance objectives are
met.";
}
leaf-list performance-metric { leaf optical-interface {
type identityref { type identityref {
base "l1-st:performance-metric"; base "layer1-types:optical-interface-func";
}
description "optical-interface-function";
} }
description "list of performance metric";
}
} }
grouping subscriber-l1vc-endpoint-attributes { grouping subscriber-l1vc-sls-service-attribute {
description description
"subscriber layer 1 connection endpoint attributes"; "The value of the Subscriber L1VC SLS (Service Level
reference "MEF 63"; Specification) Service Attribute";
reference "MEF 63";
container endpoint-1 { leaf start-time {
description "One end of UNI id's - string and id"; type yang:date-and-time;
leaf id { description "a time that represent the date and time
type string; for the start of the SLS";
mandatory true;
description "subscriber end point ID of one end";
} }
leaf uni { leaf time-interval {
type leafref { type int32;
path "/l1-connectivity/access/unis/uni/id"; units seconds;
} description "a time interval (e.g., 2,419,200 seconds
mandatory true; which is 28 days) that is used in
description "this is one end of subscriber L1VC end point conjunction wuth time-start to specify a
ID value = UNI-1"; contiguous sequence of time intervals T for
} determining when performance objectives are
} met.";
container endpoint-2 {
description "One end of UNI id's - string and id";
leaf id {
type string;
mandatory true;
description "subscriber end point ID of the other end";
} }
leaf uni { leaf-list performance-metric {
type leafref { type identityref {
path "/l1-connectivity/access/unis/uni/id"; base "layer1-types:service-performance-metric";
} }
mandatory true; description "list of service performance metric.";
description
"this is one other end of subscriber L1VC end point
ID value = UNI-2";
} }
}
}
container l1-connectivity { }
description
"serves as a top-level container for a list of layer 1
connection services (l1cs)";
container access {
description "UNI configurations for access networks";
container unis {
description "the list of UNI's to be configured";
list uni {
key "id";
description "UNI identifier";
leaf id {
type string;
description "the UNI id of UNI Service Attributes";
} grouping subscriber-l1vc-endpoint-attributes {
description
"subscriber layer 1 connection endpoint attributes";
reference "MEF 63";
container endpoint-1 {
description "One end of UNI id's - string and id";
leaf id {
type string;
mandatory true;
description "subscriber end point ID of one end";
}
uses protocol-coding-optical-interface; leaf uni {
type leafref {
path "/l1-connectivity/access/unis/uni/id";
}
mandatory true;
description "this is one end of subscriber L1VC end point
ID value = UNI-1";
} }
} }
} container endpoint-2 {
description "One end of UNI id's - string and id";
container services { leaf id {
description "L1VC services"; type string;
list service { mandatory true;
key "service-id"; description "subscriber end point ID of the other end";
description }
"an unique identifier of a subscriber L1VC service";
leaf service-id {
type string;
mandatory true;
description "a unique service identifier for
subscriber L1VC.";
}
uses subscriber-l1vc-endpoint-attributes;
uses subscriber-l1vc-sls-service-attribute;
}//end of service list
} //end of service container
}//service top container
}
<CODE ENDS>
<CODE BEGINS> file "ietf-l1-service-types@2018-09-12.yang"
module ietf-l1-service-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-l1-service-types";
prefix "l1-st";
organization
"IETF CCAMP Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/ccamp/>
WG List: <mailto:ccamp@ietf.org>
Editor: G. Fioccolla(giuseppe.fioccola@telecomitalia.it)
Editor: K. Lee (kwangkoog.lee@kt.com)
Editor: Y. Lee (leeyoung@huawei.com)
Editor: D. Dhody (dhruv.ietf@gmail.com)
Editor: O. G. de-Dios(oscar.gonzalezdedios@telefonica.com)
Editor: D. Ceccarelli(daniele.ceccarelli@ericsson.com)";
description
"This module defines L1 service types based on MEF 63:
Subscriber Layer 1 Service Attribute Technical Specification.
Refer to MEF 63 for all terms and the original references
used in the module. As for the protocol-type, refer also to
the client-type in G.709.
Copyright (c) 2018 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).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
revision "2018-09-12" { leaf uni {
description "Initial revision."; type leafref {
reference "RFC XXXX: A Yang Data Model for L1 Connectivity path "/l1-connectivity/access/unis/uni/id";
Service Model (L1CSM)"; }
// Note: The RFC Editor will replace XXXX with the number mandatory true;
// assigned to the RFC once this draft becomes an RFC. description
"this is one other end of subscriber L1VC end point
ID value = UNI-2";
}
} }
}
identity protocol-type { container l1-connectivity {
description
"base identity from which client protocol type is derived.";
}
identity ETH-1GbE {
base "protocol-type";
description
"Gigabit Ethernet protocol type";
reference "MEF63 & G.709";
}
identity ETH-10GbE-WAN {
base "protocol-type";
description
"10 Gigabit Ethernet-WAN protocol type";
reference "MEF63 & G.709";
}
identity ETH-10GbE-LAN {
base "protocol-type";
description
"10 Gigabit Ethernet-LAN protocol type";
reference "MEF63 & G.709";
}
identity ETH-40GbE {
base "protocol-type";
description
"40 Gigabit Ethernet protocol type";
reference "MEF63 & G.709";
}
identity ETH-100GbE {
base "protocol-type";
description
"100 Gigabit Ethernet protocol type";
reference "MEF63 & G.709";
}
identity FC-100 {
base "protocol-type";
description
"Fiber Channel - 100 protocol type";
reference "MEF63 & G.709";
}
identity FC-200 {
base "protocol-type";
description
"Fiber Channel - 200 protocol type";
reference "MEF63 & G.709";
}
identity FC-400 {
base "protocol-type";
description
"Fiber Channel - 400 protocol type";
reference "MEF63 & G.709";
}
identity FC-800 {
base "protocol-type";
description
"Fiber Channel - 800 protocol type";
reference "MEF63 & G.709";
}
identity FC-1200 {
base "protocol-type";
description
"Fiber Channel - 1200 protocol type";
reference "MEF63 & G.709";
}
identity FC-1600 {
base "protocol-type";
description
"Fiber Channel - 1600 protocol type";
reference "MEF63 & G.709";
}
identity FC-3200 {
base "protocol-type";
description
"Fiber Channel - 3200 protocol type";
reference "MEF63 & G.709";
}
identity STM-1 {
base "protocol-type";
description
"SDH STM-1 protocol type";
reference "MEF63 & G.709";
}
identity STM-4 {
base "protocol-type";
description
"SDH STM-4 protocol type";
reference "MEF63 & G.709";
}
identity STM-16 {
base "protocol-type";
description
"SDH STM-16 protocol type";
reference "MEF63 & G.709";
}
identity STM-64 {
base "protocol-type";
description
"SDH STM-64 protocol type";
reference "MEF63 & G.709";
}
identity STM-256 {
base "protocol-type";
description
"SDH STM-256 protocol type";
reference "MEF63 & G.709";
}
identity OC-3 {
base "protocol-type";
description
"SONET OC-3 protocol type";
reference "MEF63 & G.709";
}
identity OC-12 {
base "protocol-type";
description
"SONET OC-12 protocol type";
reference "MEF63 & G.709";
}
identity OC-48 {
base "protocol-type";
description
"SONET OC-48 protocol type";
reference "MEF63 & G.709";
}
identity OC-192 {
base "protocol-type";
description
"SONET OC-192 protocol type";
reference "MEF63 & G.709";
}
identity OC-768 {
base "protocol-type";
description
"SONET OC-768 protocol type";
reference "MEF63 & G.709";
}
identity coding-func {
description
"base identity from which coding func is derived.";
}
identity ETH-1000X-PCS-36 {
base "coding-func";
description
"PCS clause 36 coding function that corresponds to
1000BASE-X";
reference "MEF63 & IEEE802.3";
}
identity ETH-10GW-PCS-49-WIS-50 {
base "coding-func";
description
"PCS clause 49 and WIS clause 50 coding func that
corresponds to 10GBASE-W (WAN PHY)";
reference "MEF63 & IEEE802.3";
}
identity ETH-10GR-PCS-49 {
base "coding-func";
description
"PCS clause 49 coding function that corresponds to
10GBASE-R (LAN PHY)";
reference "MEF63 & IEEE802.3";
}
identity ETH-40GR-PCS-82 {
base "coding-func";
description
"PCS clause 82 coding function that corresponds to
40GBASE-R";
reference "MEF63 & IEEE802.3";
}
identity ETH-100GR-PCS-82 {
base "coding-func";
description
"PCS clause 82 coding function that corresponds to
100GBASE-R";
reference "MEF63 & IEEE802.3";
}
/* coding func needs to expand for Fiber Channel, SONET, SDH */
identity optical-interface-func {
description description
"base identity from which optical-interface-function is "serves as a top-level container for a list of layer 1
derived."; connection services (l1cs)";
}
identity SX-PMD-clause-38 {
base "optical-interface-func";
description
"SX-PMD-clause-38 Optical Interface function for
1000BASE-X PCS-36";
reference "MEF63 & IEEE802.3";
}
identity LX-PMD-clause-38 {
base "optical-interface-func";
description
"LX-PMD-clause-38 Optical Interface function for
1000BASE-X PCS-36";
reference "MEF63 & IEEE802.3";
}
identity LX10-PMD-clause-59 {
base "optical-interface-func";
description
"LX10-PMD-clause-59 Optical Interface function for
1000BASE-X PCS-36";
reference "MEF63 & IEEE802.3";
}
identity BX10-PMD-clause-59 {
base "optical-interface-func";
description
"BX10-PMD-clause-59 Optical Interface function for
1000BASE-X PCS-36";
reference "MEF63 & IEEE802.3";
}
identity LW-PMD-clause-52 {
base "optical-interface-func";
description
"LW-PMD-clause-52 Optical Interface function for
10GBASE-W PCS-49-WIS-50";
reference "MEF63 & IEEE802.3";
}
identity EW-PMD-clause-52 {
base "optical-interface-func";
description
"EW-PMD-clause-52 Optical Interface function for
10GBASE-W PCS-49-WIS-50";
reference "MEF63 & IEEE802.3";
}
identity LR-PMD-clause-52 {
base "optical-interface-func";
description
"LR-PMD-clause-52 Optical Interface function for
10GBASE-R PCS-49";
reference "MEF63 & IEEE802.3";
}
identity ER-PMD-clause-52 {
base "optical-interface-func";
description
"ER-PMD-clause-52 Optical Interface function for
10GBASE-R PCS-49";
reference "MEF63 & IEEE802.3";
}
identity LR4-PMD-clause-87 {
base "optical-interface-func";
description
"LR4-PMD-clause-87 Optical Interface function for
40GBASE-R PCS-82";
reference "MEF63 & IEEE802.3";
}
identity ER4-PMD-clause-87 {
base "optical-interface-func";
description
"ER4-PMD-clause-87 Optical Interface function for
40GBASE-R PCS-82";
reference "MEF63 & IEEE802.3";
}
identity FR-PMD-clause-89 {
base "optical-interface-func";
description
"FR-PMD-clause-89 Optical Interface function for
40GBASE-R PCS-82";
reference "MEF63 & IEEE802.3";
}
identity LR4-PMD-clause-88 {
base "optical-interface-func";
description
"LR4-PMD-clause-88 Optical Interface function for
100GBASE-R PCS-82";
reference "MEF63 & IEEE802.3";
}
identity ER4-PMD-clause-88 {
base "optical-interface-func";
description
"ER4-PMD-clause-88 Optical Interface function for
100GBASE-R PCS-82";
reference "MEF63 & IEEE802.3";
}
/* optical interface func needs to expand for Fiber Channel,
SONET and SDH */
identity performance-metric { container access {
description "list of performance metric"; description "UNI configurations for access networks";
}
identity One-way-Delay { container unis {
base "performance-metric"; description "the list of UNI's to be configured";
description "one-way-delay"; list uni {
} key "id";
description "UNI identifier";
leaf id {
type string;
description "the UNI id of UNI Service Attributes";
}
identity One-way-Errored-Second { uses protocol-coding-optical-interface;
base "performance-metric"; }
description "one-way-errored-second"; }
} }
identity One-way-Severely-Errored-Second { container services {
base "performance-metric"; description "L1VC services";
description "one-way-severely-errored-second"; list service {
} key "service-id";
description
"an unique identifier of a subscriber L1VC service";
identity One-way-Unavailable-Second { leaf service-id {
base "performance-metric"; type string;
description "one-way-unavailable-second"; mandatory true;
} description "a unique service identifier for
subscriber L1VC.";
}
identity One-way-Availability { uses subscriber-l1vc-endpoint-attributes;
base "performance-metric"; uses subscriber-l1vc-sls-service-attribute;
description "one-way-availability";
}
} }//end of service list
} //end of service container
}//service top container
}
<CODE ENDS> <CODE ENDS>
5. JSON Example 5. JSON Example
This section provides a JSON example of the YANG module described in This section provides a JSON example of the YANG module described in
Section 4. This example configures one L1VC service with two UNIs Section 4. This example configures one L1VC service with two UNIs
that describe the UNI endpoints. The service is configured with the that describe the UNI endpoints. The service is configured with the
starting time to be 06:06:09 on 2018-09-13 for the service life time starting time to be 06:06:09 on 2018-09-13 for the service life time
of 2419200 seconds (which is corresponds to 28 days). In addition, of 2419200 seconds (which is corresponds to 28 days). In addition,
the service is configured to collect one performance metric, One- the service is configured to collect one performance metric, One-way-
way-Delay. Delay.
{ {
"l1-connectivity": { "l1-connectivity": {
"access": { "access": {
"unis": { "unis": {
"uni": [ "uni": [
{ {
"id": "MTL-HQ-Node3-Slot2-Port1", "id": "MTL-HQ-Node3-Slot2-Port1",
"protocol": "ETH-10GigE_LAN ", "protocol": "ETH-10GigE_LAN ",
"coding": "ETH-10GR-PCS-49 ", "coding": "ETH-10GR-PCS-49 ",
"optical_interface": "LR-PMD-clause-52 " "optical_interface": "LR-PMD-clause-52 "
}, },
skipping to change at page 22, line 18 skipping to change at page 14, line 5
"uni": "MTL-STL-Node5-Slot4-Port3" "uni": "MTL-STL-Node5-Slot4-Port3"
}, },
"start-time": "2018-09-13T06:06:09Z", "start-time": "2018-09-13T06:06:09Z",
"time-interval": 2419200, "time-interval": 2419200,
"performance-metric": "One-way-Delay " "performance-metric": "One-way-Delay "
} }
] ]
}, },
} }
6. Security Considerations 6. Security Considerations
The configuration, state, and action data defined in this document The YANG module specified in this document defines a schema for data
are designed to be accessed via a management protocol with a secure that is designed to be accessed via network management protocols such
transport layer, such as NETCONF [RFC6241] or RESTCONF [RFC8040]. as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
The lowest NETCONF layer is the secure transport layer, and the is the secure transport layer, and the mandatory-to-implement secure
mandatory-to-implement secure transport is Secure Shell (SSH) transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
[RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory- is HTTPS, and the mandatory-to-implement secure transport is TLS
to-implement secure transport is TLS [RFC8446]. [RFC8446].
The NETCONF access control model [RFC8341] provides the means to The NETCONF access control model [RFC8341] provides the means to
restrict access for particular NETCONF users to a preconfigured restrict access for particular NETCONF or RESTCONF users to a
subset of all available NETCONF protocol operations and content. preconfigured subset of all available NETCONF or RESTCONF protocol
operations and content.
A number of configuration data nodes defined in this document are A number of configuration data nodes defined in this document are
writable/deletable (i.e., "config true") These data nodes may be writable/deletable (i.e., "config true") These data nodes may be
considered sensitive or vulnerable in some network environments. considered sensitive or vulnerable in some network environments.
These are the subtrees and data nodes and their These are the subtrees and data nodes and their sensitivity/
sensitivity/vulnerability: vulnerability:
unis: unis:
- id
- id
Service: Service:
- service-id
- endpoint-1
- endpoint-2
- start-time
- time-interval
- performance-metric
7. IANA Considerations - service-id
This document registers the following namespace URIs in the IETF XML - endpoint-1
registry [RFC3688]:
-------------------------------------------------------------------- - endpoint-2
URI: urn:ietf:params:xml:ns:yang:ietf-l1csm
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
--------------------------------------------------------------------
-------------------------------------------------------------------- - start-time
URI: urn:ietf:params:xml:ns:yang:ietf-l1-service-types
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
--------------------------------------------------------------------
This document registers the following YANG modules in the YANG - time-interval
Module
Names registry [RFC6020]: - performance-metric
-------------------------------------------------------------------- The security considerations spelled out in the YANG 1.1 specification
name: ietf-l1csm [RFC7950] apply for this document as well.
namespace: urn:ietf:params:xml:ns:yang:ietf-l1csm
reference: RFC XXXX (TDB)
--------------------------------------------------------------------
-------------------------------------------------------------------- 7. IANA Considerations
name: ietf-l1-service-types
namespace: urn:ietf:params:xml:ns:yang:ietf-l1-service-types
reference: RFC XXXX (TDB)
--------------------------------------------------------------------
8. Acknowledgments It is proposed that IANA should assign new URIs from the "IETF XML
Registry" [RFC3688] as follows:
The authors would like to thank Tom Petch and Italo Busi for their URI: urn:ietf:params:xml:ns:yang:ietf-l1csm
helpful comments and valuable contributions and Robert Wilton for Registrant Contact: The IESG
his YANG doctor's review that improved the model significantly. XML: N/A; the requested URI is an XML namespace.
9. References This document registers following YANG modules in the YANG Module
Names registry [RFC7950].
9.1. Normative References name: ietf-l1csm
namespace: urn:ietf:params:xml:ns:yang:ietf-l1csm
prefix: l1csm
reference: RFC XXXX
[MEF63] "Subscriber Layer 1 Service Attributes", Technical 8. Acknowledgements
Specification, MEF 63, August 2018.
[RFC8446] Dierks, T. and E. Rescorla, "The Transport Layer Security The authors would like to thank Tom Petch for his helpful comments
(TLS) Protocol Version 1.3", RFC 8446, August 2018. and valuable contributions and Robert Wilton for his review that
improved the model significantly.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 9. Contributors
the Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., Italo Busi
and A. Bierman, Ed., "Network Configuration Protocol Huawei Technologies
(NETCONF)", RFC 6241, June 2011. Email: Italo.Busi@huawei.com
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Giuseppe Fioccola
Shell (SSH)", RFC 6242, June 2011. Huawei Technologies
Email: giuseppe.fioccola@huawei.com
[RFC6991] J. Schoenwaelder, Ed., "Common YANG Data Types", RFC 6991, 10. References
July 2013.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 10.1. Normative References
RFC 7950, August 2016.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [MEF63] Metro Ethernet Forum, "Subscriber Layer1 Service
Protocol", RFC 8040, January 2017. Attributes Technical Specification", MEF 63, August 2018.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
Access Control Model", RFC 8341, March 2018. DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
9.2. Informative References [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,
<https://www.rfc-editor.org/info/rfc6241>.
[RFC3688] M. Mealling, "The IETF XML Registry", RFC 3688, January [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
2004. Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>.
[RFC4847] T. Takeda (Editor), "Framework and Requirements for Layer [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
1 Virtual Private Networks", RFC 4847, April 2007. RFC 6991, DOI 10.17487/RFC6991, July 2013,
<https://www.rfc-editor.org/info/rfc6991>.
[RFC5253] T. Takeda, "Applicability Statement for Layer 1 Virtual [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
Private Network (L1VPN) Basic Mode", RFC 5253, July 2008. RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>.
[RFC8199] D. Bogdanovic, B. Claise, and C. Moberg, "YANG Module [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Classification", RFC 8199, July 2017. Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>.
[RFC8309] Q. Wu, W. Liu and A. Farrel, "Service Models Explained", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
RFC 8309, January 2018. BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>.
[RFC8340] M. Bjorklund and L. Berger, Ed., "YANG Tree Diagrams", RFC [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
8340, March 2018. Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, March 2018, (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
[G.709] ITU-T Recommendation G.709/Y.1331, Interfaces for the [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
optical transport network, Corrigendum 1, August 2017. Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>.
[IEEE802.3] IEEE Std 802.3, IEEE Standard for Ethernet, 2015. 10.2. Informative References
10. Contributors [I-D.ietf-ccamp-layer1-types]
Zheng, H. and I. Busi, "A YANG Data Model for Layer 1
Types", draft-ietf-ccamp-layer1-types-01 (work in
progress), July 2019.
Contributor's Addresses [RFC4847] Takeda, T., Ed., "Framework and Requirements for Layer 1
Virtual Private Networks", RFC 4847, DOI 10.17487/RFC4847,
April 2007, <https://www.rfc-editor.org/info/rfc4847>.
I. Busi [RFC5253] Takeda, T., Ed., "Applicability Statement for Layer 1
Huawei Virtual Private Network (L1VPN) Basic Mode", RFC 5253,
Email: Italo.Busi@huawei.com DOI 10.17487/RFC5253, July 2008,
<https://www.rfc-editor.org/info/rfc5253>.
[RFC8199] Bogdanovic, D., Claise, B., and C. Moberg, "YANG Module
Classification", RFC 8199, DOI 10.17487/RFC8199, July
2017, <https://www.rfc-editor.org/info/rfc8199>.
[RFC8309] Wu, Q., Liu, W., and A. Farrel, "Service Models
Explained", RFC 8309, DOI 10.17487/RFC8309, January 2018,
<https://www.rfc-editor.org/info/rfc8309>.
Authors' Addresses Authors' Addresses
G. Fioccola (Editor) Young Lee
Telecom Italia SKKU
Email: giuseppe.fioccola@telecomitalia.it Sung Kyun Kwan University
Seoul
South Korea
Email: younglee.tx@gmail.com
KwangKoog Lee
Korea Telecom
South Korea
K. Lee
KT
Email: kwangkoog.lee@kt.com Email: kwangkoog.lee@kt.com
Y. Lee (Editor) Haomian Zheng
Huawei Huawei Technologies
Email: leeyoung@huawei.com H1-1-A043S Huawei Industrial Base, Songshanhu
Dongguan, Guangdong 523808
China
Email: zhenghaomian@huawei.com
Dhruv Dhody
Huawei Technologies
India
D. Dhody
Huawei
Email: dhruv.ietf@gmail.com Email: dhruv.ietf@gmail.com
O. Gonzalez de Dios Oscar Gonzalez de Dios
Telefonica Telefonica
Email: oscar.gonzalezdedios@telefonica.com Email: oscar.gonzalezdedios@telefonica.com
D. Ceccarelli Daniele Ceccarelli
Ericsson Ericsson
Email: daniele.ceccarelli@ericsson.com Email: daniele.ceccarelli@ericsson.com
 End of changes. 142 change blocks. 
865 lines changed or deleted 469 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/