draft-ietf-ccamp-l1csm-yang-03.txt   draft-ietf-ccamp-l1csm-yang-04.txt 
CCAMP Working Group G. Fioccola (Ed.) CCAMP Working Group G. Fioccola (Ed.)
Telecom Italia Telecom Italia
Internet Draft K. Lee Internet Draft K. Lee
Intended Status: Standard Track Korea Telecom Intended Status: Standard Track Korea Telecom
Expires: December 20, 2018 Y. Lee (Ed.) Expires: December 22, 2018 Y. Lee (Ed.)
D. Dhody D. Dhody
Huawei Huawei
O. Gonzalez de-Dios O. Gonzalez de-Dios
Telefonica Telefonica
D. Ceccarelli D. Ceccarelli
Ericsson Ericsson
June 20, 2018 June 22, 2018
A Yang Data Model for L1 Connectivity Service Model (L1CSM) A Yang Data Model for L1 Connectivity Service Model (L1CSM)
draft-ietf-ccamp-l1csm-yang-03 draft-ietf-ccamp-l1csm-yang-04
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). Service Model (L1CSM).
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the provisions of BCP 78 and BCP 79.
skipping to change at page 2, line 23 skipping to change at page 2, line 23
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as 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...............................7
2. Definitions....................................................7 2. Definitions....................................................7
3. L1SM YANG Model (Tree Structure)...............................7 3. L1SM YANG Model (Tree Structure)...............................7
4. L1SM YANG Code.................................................8 4. L1SM YANG Code.................................................8
5. Security Considerations.......................................21 5. Security Considerations.......................................20
6. IANA Considerations...........................................21 6. IANA Considerations...........................................20
7. Acknowledgments...............................................22 7. Acknowledgments...............................................21
8. References....................................................23 8. References....................................................22
8.1. Normative References.....................................23 8.1. Normative References.....................................22
8.2. Informative References...................................23 8.2. Informative References...................................22
9. Contributors..................................................23 9. Contributors..................................................22
Authors' Addresses...............................................23 Authors' Addresses...............................................22
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). 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 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 connectivity request as well as retrieving service states request connectivity request as well as retrieving service states
toward a transport network controller communicating with the client toward a transport network controller communicating with the client
controller via a Netconf/Restconf interface. controller via a Netconf[RFC6020] 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
skipping to change at page 3, line 32 skipping to change at page 3, line 34
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 1 connectivity between two or more customer sites where the layer 1 connectivity between two or more customer sites where the
customer has some control over the establishment and type of the customer has some control over the establishment and type of the
connectivity. connectivity.
The model presented in Section 3 is in consistent with [MEF-L1CS]. The data model presented in Section 3 is in consistent with [MEF-
L1CS]. The data model includes configuration and state data
according to the 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 service model for an external customer instantiating L1 point- based service model for an external customer instantiating L1 point-
to-point connectivity to the provider. to-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 5, line 11 skipping to change at page 5, line 17
service department) can offer its own services, whose payloads can service department) can offer its own services, whose payloads can
be any layer (e.g., ATM, IP, TDM). The layer 1 transport network and be any layer (e.g., ATM, IP, TDM). The layer 1 transport network and
each service network belong to the same organization, but may be each service network belong to the same organization, but may be
managed separately. The Service SDN Controller is the managed separately. The Service SDN Controller is the
control/management entity owned by higher-layer service department control/management entity owned by higher-layer service department
(e.g., L2/3 VPN) whereas the Network SDN Controller is the (e.g., L2/3 VPN) whereas the Network SDN Controller is the
control/management entity responsible for Layer 1 connectivity control/management entity responsible for Layer 1 connectivity
service. The CE's in Figure 2 are L2/3 devices that interface with service. The CE's in Figure 2 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 42 skipping to change at page 5, line 48
+----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+
| 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: Internal Customer Figure 2: L1VPN SDN Controller/EMS/NMS-Based Service Model: Internal 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 plane) can be built economically by having the resources (data plane) can be built economically by having the resources
shared by multiple services usually with flexibility to modify shared by multiple services usually with flexibility to modify
topologies, while separating the control functions for each service topologies, while separating the control functions for each service
department. Thus, each customer can select a specific set of department. Thus, each customer can select a specific set of
features that are needed to provide their own service [RFC4847]. features that are needed to provide their own service [RFC4847].
1.2. Terminology 1.2. Terminology
skipping to change at page 6, line 42 skipping to change at page 6, line 45
o data model o data model
o data node o data node
The terminology for describing YANG data models is found in The terminology for describing YANG data models is found in
[RFC6020]. [RFC6020].
1.3. Tree diagram 1.3. Tree diagram
A simplified graphical representation of the data model is presented A simplified graphical representation of the data model is used in
in Section x. chapter 3 of this this document. The meaning of the symbols in
these diagrams is defined in [RFC8340].
The meaning of the symbols in these diagrams is as follows: 1.4. Prefixes in Data Node Names
o Brackets "[" and "]" enclose list keys. In this document, names of data nodes and other data model objects
are prefixed using the standard prefix associated with the
corresponding YANG imported modules, as shown in Table 1.
o Curly braces "{" and "}" contain names of optional features that +---------+------------------------------+-----------------+
make the corresponding node conditional. | Prefix | YANG module | Reference |
+---------+------------------------------+-----------------+
| l1csm | ietf-l1cms | [This I-D] |
| l1-st | ietf-l1-mef-service-types | [This I-D] |
| yang | ietf-yang-types | [RFC6991] |
+---------+------------------------------+-----------------+
o Abbreviations before data node names: "rw" means configuration Table 1: Prefixes and corresponding YANG modules
(read-write), and "ro" state data (read-only).
o Symbols after data node names: "?" means an optional node and "*" 2. Definitions
denotes a "list" or "leaf-list".
o Parentheses enclose choice and case nodes, and case nodes are also L1VC Layer 1 Virtual Connection
marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not SLS Service Level Specification
shown.
2. Definitions UNI User Network Interface
TDB PE Provider Edge
CE Customer Edge
EP End Point
P Protocol
C Coding
O Optical Interface
3. L1SM YANG Model (Tree Structure) 3. L1SM YANG Model (Tree Structure)
module: ietf-l1csm module: ietf-l1csm
+--rw l1cs +--rw l1cs
+--rw access +--rw access
| +--rw uni-list* [UNI-ID] | +--rw uni-list* [UNI-ID]
| +--rw UNI-ID string | +--rw UNI-ID string
| +--rw protocol? identityref | +--rw protocol? identityref
| +--rw coding? identityref | +--rw coding? identityref
| +--rw optical_interface? identityref | +--rw optical_interface? identityref
+--rw service +--rw service
+--rw service-list* [subscriber-l1vc-id] +--rw service-list* [subscriber-l1vc-id]
+--rw subscriber-l1vc-id string +--rw subscriber-l1vc-id string
+--rw service-config +--rw service-config
+--rw subscriber-l1vc-id? string +--rw subscriber-l1vc-id? string
+--rw subscriber-l1vc-ep-id-1? string +--rw subscriber-l1vc-ep-id-1? string
+--rw subscriber-l1vc-ep-id-2? string +--rw subscriber-l1vc-ep-id-2? string
+--rw subscriber-l1vc-ep-UNI-1? -> /l1cs/access/uni- +--rw subscriber-l1vc-ep-UNI-1? -> /l1cs/access/uni-list/UNI-ID
list/UNI-ID +--rw subscriber-l1vc-ep-UNI-2? -> /l1cs/access/uni-list/UNI-ID
+--rw subscriber-l1vc-ep-UNI-2? -> /l1cs/access/uni-
list/UNI-ID
+--rw time-start? yang:date-and-time +--rw time-start? yang:date-and-time
+--rw time-interval? int64 +--rw time-interval? int64
+--rw performance-metric? identityref +--rw performance-metric? Identityref
4. L1SM YANG Code 4. L1SM YANG Code
The YANG code is as follows: The YANG code is as follows:
<CODE BEGINS> file "ietf-l1csm@2018-06-20.yang" <CODE BEGINS> file "ietf-l1csm@2018-06-20.yang"
module ietf-l1csm { module ietf-l1csm {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-l1csm"; namespace "urn:ietf:params:xml:ns:yang:ietf-l1csm";
prefix "l1csm";
import ietf-yang-types {
prefix "yang";
}
import ietf-l1-mef-service-types {
prefix "l1-st";
}
organization
"Internet Engineering Task Force (IETF) CCAMP WG";
contact
"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. Gonzalez de-Dio(oscar.gonzalezdedios@telefonica.com)
Editor: D. Ceccarelli (daniele.ceccarelli@ericsson.com)";
description
"this module describes Layer 1 connectivity service
model for subscriber Layer 1 Connectivity Services
and Attributes";
revision 2018-06-20 {
description
"updated version to incorporate MEF
comments";
reference "to add the draft name";
}
revision 2018-04-11 {
description
"Initial revision.";
reference "to add the draft name";
}
grouping protocol-coding-optical_interface {
description
"describes <p,c,o>";
leaf protocol {
type identityref {
base "l1-st:protocol-type";
}
description "List of physical layer L1VC prefix "l1csm";
client protocol"; import ietf-yang-types {
} prefix "yang";
}
leaf coding { import ietf-l1-mef-service-types {
type identityref { prefix "l1-st";
base "l1-st:coding-func"; }
}
description "coding function"; organization
} "Internet Engineering Task Force (IETF) CCAMP WG";
leaf optical_interface { contact
type identityref {
base "l1-st:optical-interface-func";
}
description "optical-interface-function"; "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)";
grouping uni-attributes { description
description "this module describes Layer 1 connectivity service
"uni-service-attributes"; model for subscriber Layer 1 Connectivity Services
and Attributes.
leaf UNI-ID { Copyright (c) 2018 IETF Trust and the persons identified as
type string; authors of the code. All rights reserved.
description "the UNI id of UNI Redistribution and use in source and binary forms, with or
Service Attributes"; 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).
uses protocol-coding-optical_interface; This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
} revision 2018-06-20 {
description
"updated version to incorporate MEF comments";
reference "to add the draft name";
}
grouping subscriber-l1vc-sls-service-attribute { revision 2018-04-11 {
description description
"The value of the Subscriber L1VC SLS "Initial revision.";
(Service Level Specification) Service Attribute expressed in a 3-tuple of the reference "to add the draft name";
form."; }
leaf time-start { grouping protocol-coding-optical_interface {
type yang:date-and-time; description
description "a time that represent "describes <p,c,o>";
the date and time for the start of the SLS"; leaf protocol {
} type identityref {
base "l1-st:protocol-type";
}
description
"List of physical layer L1VC clientprotocol";
}
leaf coding {
type identityref {
base "l1-st:coding-func";
}
description "coding function";
}
leaf optical_interface {
type identityref {
base "l1-st:optical-interface-func";
}
leaf time-interval { description "optical-interface-function";
type int64; }
units seconds; }
description "a time interval
(e.g., 1 month) 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 performance-metric { grouping uni-attributes {
type identityref { description
base "l1-st:performance-" "uni-service-attributes";
+"metriclist";
}
description "list of performance leaf UNI-ID {
metric"; type string;
} description "the UNI id of UNI Service Attributes";
} }
grouping subscriber-l1vc-service-attributes { uses protocol-coding-optical_interface;
description }
"subscriber layer 1 connection service
service level";
leaf subscriber-l1vc-id {
type string;
description "subscriber L1VC identifier";
}
leaf subscriber-l1vc-ep-id-1 { grouping subscriber-l1vc-sls-service-attribute {
type string; description
description "subscriber end point ID"; "The value of the Subscriber L1VC SLS (Service Level
} Specification) Service Attribute expressed in a 3-tuple
of the form.";
leaf subscriber-l1vc-ep-id-2 { leaf time-start {
type string; type yang:date-and-time;
description "subscriber end point ID"; description "a time that represent the date and time
} for the start of the SLS";
}
leaf subscriber-l1vc-ep-UNI-1 { leaf time-interval {
type leafref { type int64;
path "/l1cs/access/uni-list/UNI-ID"; units seconds;
} description "a time interval (e.g., 1 month) that is used
description "this is one end of subscriber L1VC end in conjunction wuth time-start to specify a
point ID value = UNI-1"; contiguous sequence of time intervals T for
} determining when performance objectives are
met.";
}
leaf subscriber-l1vc-ep-UNI-2 { leaf performance-metric {
type leafref { type identityref {
path "/l1cs/access/uni-list/UNI-ID"; base "l1-st:performance-metriclist";
} }
description "this is the other end of subscriber description "list of performance metric";
L1VC end point ID value = UNI-2"; }
} }
grouping subscriber-l1vc-service-attributes {
description
"subscriber layer 1 connection service service level";
uses subscriber-l1vc-sls-service-attribute; leaf subscriber-l1vc-id {
} type string;
description "subscriber L1VC identifier";
}
grouping subscriber-attributes { leaf subscriber-l1vc-ep-id-1 {
description type string;
"subscriber attributes"; description "subscriber end point ID";
}
uses subscriber-l1vc-service-attributes; leaf subscriber-l1vc-ep-id-2 {
type string;
description "subscriber end point ID";
}
} leaf subscriber-l1vc-ep-UNI-1 {
type leafref {
path "/l1cs/access/uni-list/UNI-ID";
}
description "this is one end of subscriber L1VC end point
ID value = UNI-1";
}
container l1cs { leaf subscriber-l1vc-ep-UNI-2 {
description type leafref {
"serves as a top-level container for a list of layer 1 path "/l1cs/access/uni-list/UNI-ID";
connection services (l1cs)"; }
description "this is the other end of subscriber L1VC end
point ID value = UNI-2";
}
container access { uses subscriber-l1vc-sls-service-attribute;
description "UNI configurations"; }
list uni-list { grouping subscriber-attributes {
key "UNI-ID"; description
description "uni identifier"; "subscriber attributes";
uses uni-attributes {
description "UNI attributes
information";
}
}
} uses subscriber-l1vc-service-attributes;
}
container service { container l1cs {
description "L1VC service"; description
list service-list { "serves as a top-level container for a list of layer 1
key "subscriber-l1vc-id"; connection services (l1cs)";
description
"an unique identifier of a service";
leaf subscriber-l1vc-id { container access {
type string; description "UNI configurations";
description "a unique service identifier for
L1VC.";
}
container service-config {
description "service-config container";
uses subscriber-attributes; list uni-list {
key "UNI-ID";
description "uni identifier";
uses uni-attributes {
description "UNI attributes information";
}
}
}
}//end of service-config container service {
}//end of service list description "L1VC service";
} //end of service container list service-list {
key "subscriber-l1vc-id";
description
"an unique identifier of a service";
}//service top container leaf subscriber-l1vc-id {
type string;
description "a unique service identifier for
L1VC.";
}
container service-config {
description "service-config container";
uses subscriber-attributes;
}//end of service-config
}//end of service list
} //end of service container
}//service top container
} }
<CODE ENDS> <CODE ENDS>
<CODE BEGINS> file "ietf-l1-mef-service-types@2018-06-20.yang" <CODE BEGINS> file "ietf-l1-mef-service-types@2018-06-20.yang"
module ietf-l1-mef-service-types { module ietf-l1-mef-service-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-l1-mef-service-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-l1-mef-service-types";
prefix "l1-st"; prefix "l1-st";
organization organization
"IETF CCAMP Working Group"; "IETF CCAMP Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/ccamp/> "WG Web: <http://tools.ietf.org/wg/ccamp/>
WG List: <mailto:ccamp@ietf.org> 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)";
Editor: G. Fioccolla(giuseppe.fioccola@telecomitalia.it) description
Editor: K. Lee (kwangkoog.lee@kt.com) "This module defines L1 service types based on MEF
Editor: Y. Lee (leeyoung@huawei.com) subscriber Layer 1 Connectivity Service Attribute.
Editor: D. Dhody (dhruv.ietf@gmail.com)
Editor: O. Gonzalez de-Dios(oscar.gonzalezdedios@telefonica.com)
Editor: D. Ceccarelli(daniele.ceccarelli@ericsson.com)";
description Copyright (c) 2018 IETF Trust and the persons identified as
"This module defines L1 service types based on MEF subscriber Layer 1 authors of the code. All rights reserved.
Connectivity Service Attribute."; 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 "2018-06-20" { This version of this YANG module is part of RFC XXXX; see
description the RFC itself for full legal notices.";
"Revision 0.2";
reference "TBD";
}
revision "2018-04-11" { revision "2018-06-20" {
description description
"Revision 0.1"; "Revision 0.2";
reference "TBD"; reference "TBD";
}
revision "2018-04-11" {
description
"Revision 0.1";
reference "TBD";
}
identity protocol-type {
description
"base identity from which client protocol type is derived.";
} }
identity protocol-type { identity aGigE {
base "protocol-type";
description description
"base identity from which client protocol type is derived."; "GigE protocol type";
} }
identity aGigE {
base "protocol-type";
description
"GigE protocol type";
}
identity a10GigE_WAN { identity a10GigE_WAN {
base "protocol-type"; base "protocol-type";
description description
"10GigE-WAN protocol type"; "10GigE-WAN protocol type";
} }
identity a10GigE_LAN { identity a10GigE_LAN {
base "protocol-type"; base "protocol-type";
description description
"10GigE-LAN protocol type"; "10GigE-LAN protocol type";
} }
identity a40GigE { identity a40GigE {
base "protocol-type"; base "protocol-type";
description description
"40GigE protocol type"; "40GigE protocol type";
} }
identity a100GigE { identity a100GigE {
base "protocol-type"; base "protocol-type";
description description
"100GigE protocol type"; "100GigE protocol type";
} }
identity FC-100 { identity FC-100 {
base "protocol-type"; base "protocol-type";
description description
"Fiber Channel - 100 protocol type"; "Fiber Channel - 100 protocol type";
} }
identity FC-200 { identity FC-200 {
base "protocol-type"; base "protocol-type";
description description
"Fiber Channel - 200 protocol type"; "Fiber Channel - 200 protocol type";
} }
identity FC-400 { identity FC-400 {
base "protocol-type"; base "protocol-type";
description description
"Fiber Channel - 400 protocol type"; "Fiber Channel - 400 protocol type";
} }
identity FC-800 { identity FC-800 {
base "protocol-type"; base "protocol-type";
description description
"Fiber Channel - 800 protocol type"; "Fiber Channel - 800 protocol type";
} }
identity FC-1200 { identity FC-1200 {
base "protocol-type"; base "protocol-type";
description description
"Fiber Channel - 1200 protocol type"; "Fiber Channel - 1200 protocol type";
} }
identity FC-1600 { identity FC-1600 {
base "protocol-type"; base "protocol-type";
description description
"Fiber Channel - 1600 protocol type"; "Fiber Channel - 1600 protocol type";
} }
identity FC-3200 { identity FC-3200 {
base "protocol-type"; base "protocol-type";
description description
"Fiber Channel - 3200 protocol type"; "Fiber Channel - 3200 protocol type";
} }
identity STM-1 { identity STM-1 {
base "protocol-type"; base "protocol-type";
description description
"SDH STM-1 protocol type"; "SDH STM-1 protocol type";
} }
identity STM-4 { identity STM-4 {
base "protocol-type"; base "protocol-type";
description description
"SDH STM-4 protocol type"; "SDH STM-4 protocol type";
} }
identity STM-16 { identity STM-16 {
base "protocol-type"; base "protocol-type";
description description
"SDH STM-16 protocol type"; "SDH STM-16 protocol type";
}
} identity STM-64 {
base "protocol-type";
description
"SDH STM-64 protocol type";
}
identity STM-64 { identity STM-256 {
base "protocol-type"; base "protocol-type";
description description
"SDH STM-64 protocol type"; "SDH STM-256 protocol type";
} }
identity STM-256 { identity OC-3 {
base "protocol-type"; base "protocol-type";
description description
"SDH STM-256 protocol type"; "SONET OC-3 protocol type";
} }
identity OC-3 { identity OC-12 {
base "protocol-type"; base "protocol-type";
description description
"SONET OC-3 protocol type"; "SONET OC-12 protocol type";
} }
identity OC-12 { identity OC-48 {
base "protocol-type"; base "protocol-type";
description description
"SONET OC-12 protocol type"; "SONET OC-48 protocol type";
} }
identity OC-48 { identity OC-192 {
base "protocol-type"; base "protocol-type";
description description
"SONET OC-48 protocol type"; "SONET OC-192 protocol type";
} }
identity OC-192 { identity OC-768 {
base "protocol-type"; base "protocol-type";
description description
"SONET OC-192 protocol type"; "SONET OC-768 protocol type";
} }
identity OC-768 { identity coding-func {
base "protocol-type"; description
description "base identity from which coding func is derived.";
"SONET OC-768 protocol type"; }
}
identity coding-func { identity a1000X-PCS-36 {
base "coding-func";
description description
"base identity from which coding func is derived."; "PCS clause 36 coding function that corresponds to 1000BASE-X";
} }
identity a1000X-PCS-36 { identity a10GW-PCS-49-WIS-50 {
base "coding-func"; base "coding-func";
description description
"PCS clause 36 coding function that "PCS clause 49 and WIS clause 50 coding func that corresponds to
corresponds to 1000BASE-X"; 10GBASE-W (WAN PHY)";
} }
identity a10GW-PCS-49-WIS-50 { identity a10GR-PCS-49 {
base "coding-func"; base "coding-func";
description description
"PCS clause 49 and WIS clause 50 coding func "PCS clause 49 coding function that corresponds to 10GBASE-R (LAN
that corresponds to 10GBASE-W (WAN PHY)"; PHY)";
} }
identity a10GR-PCS-49 { identity a40GR-PCS-82 {
base "coding-func"; base "coding-func";
description description
"PCS clause 49 coding function that "PCS clause 82 coding function that corresponds to 40GBASE-R";
corresponds to 10GBASE-R (LAN PHY)"; }
}
identity a40GR-PCS-82 { identity a100GR-PCS-82 {
base "coding-func"; base "coding-func";
description description
"PCS clause 82 coding function that "PCS clause 82 coding function that corresponds to 100GBASE-R";
corresponds to 40GBASE-R"; }
}
identity a100GR-PCS-82 { /* coding func needs to expand for Fiber Channel, SONET, SDH */
base "coding-func";
description
"PCS clause 82 coding function that
corresponds to 100GBASE-R";
}
/* coding func needs to expand for Fiber Channel, SONET, SDH */ identity optical-interface-func {
description
"base identity from which optical-interface-function is derived.";
}
identity optical-interface-func { identity SX-PMD-clause-38 {
base "optical-interface-func";
description description
"base identity from which optical-interface-function is derived."; "SX-PMD-clause-38 Optical Interface function for 1000BASE-X PCS-36";
} }
identity SX-PMD-clause-38 { identity LX-PMD-clause-38 {
base "optical-interface-func"; base "optical-interface-func";
description description
"SX-PMD-clause-38 Optical Interface function "LX-PMD-clause-38 Optical Interface function for 1000BASE-X PCS-36";
for 1000BASE-X PCS-36"; }
}
identity LX-PMD-clause-38 {
base "optical-interface-func";
description
"LX-PMD-clause-38 Optical Interface function
for 1000BASE-X PCS-36";
}
identity LX10-PMD-clause-59 { identity LX10-PMD-clause-59 {
base "optical-interface-func"; base "optical-interface-func";
description description
"LX10-PMD-clause-59 Optical Interface "LX10-PMD-clause-59 Optical Interface function for 1000BASE-X PCS-
function for 1000BASE-X PCS-36"; 36";
} }
identity BX10-PMD-clause-59 { identity BX10-PMD-clause-59 {
base "optical-interface-func"; base "optical-interface-func";
description description
"BX10-PMD-clause-59 Optical Interface "BX10-PMD-clause-59 Optical Interface function for 1000BASE-X PCS-
function for 1000BASE-X PCS-36"; 36";
} }
identity LW-PMD-clause-52 {
base "optical-interface-func";
description
"LW-PMD-clause-52 Optical Interface function for 10GBASE-W PCS-49-
WIS-50";
}
identity LW-PMD-clause-52 { identity EW-PMD-clause-52 {
base "optical-interface-func"; base "optical-interface-func";
description description
"LW-PMD-clause-52 Optical Interface function "EW-PMD-clause-52 Optical Interface function for 10GBASE-W PCS-49-
for 10GBASE-W PCS-49-WIS-50"; WIS-50";
} }
identity EW-PMD-clause-52 { identity LR-PMD-clause-52 {
base "optical-interface-func"; base "optical-interface-func";
description description
"EW-PMD-clause-52 Optical Interface function "LR-PMD-clause-52 Optical Interface function for 10GBASE-R PCS-49";
for 10GBASE-W PCS-49-WIS-50"; }
}
identity LR-PMD-clause-52 { identity ER-PMD-clause-52 {
base "optical-interface-func"; base "optical-interface-func";
description description
"LR-PMD-clause-52 Optical Interface function "ER-PMD-clause-52 Optical Interface function for 10GBASE-R PCS-49";
for 10GBASE-R PCS-49"; }
}
identity ER-PMD-clause-52 { identity LR4-PMD-clause-87 {
base "optical-interface-func"; base "optical-interface-func";
description description
"ER-PMD-clause-52 Optical Interface function "LR4-PMD-clause-87 Optical Interface function for 40GBASE-R PCS-82";
for 10GBASE-R PCS-49"; }
}
identity LR4-PMD-clause-87 { identity ER4-PMD-clause-87 {
base "optical-interface-func"; base "optical-interface-func";
description description
"LR4-PMD-clause-87 Optical Interface function "ER4-PMD-clause-87 Optical Interface function for 40GBASE-R PCS-82";
for 40GBASE-R PCS-82"; }
}
identity ER4-PMD-clause-87 { identity FR-PMD-clause-89 {
base "optical-interface-func"; base "optical-interface-func";
description description
"ER4-PMD-clause-87 Optical Interface function "FR-PMD-clause-89 Optical Interface function for 40GBASE-R PCS-82";
for 40GBASE-R PCS-82"; }
}
identity FR-PMD-clause-89 { identity LR4-PMD-clause-88 {
base "optical-interface-func"; base "optical-interface-func";
description description
"FR-PMD-clause-89 Optical Interface function "LR4-PMD-clause-88 Optical Interface function for 100GBASE-R PCS-
for 40GBASE-R PCS-82"; 82";
} }
identity LR4-PMD-clause-88 { identity ER4-PMD-clause-88 {
base "optical-interface-func"; base "optical-interface-func";
description description
"LR4-PMD-clause-88 Optical Interface function "ER4-PMD-clause-88 Optical Interface function for 100GBASE-R PCS-
for 100GBASE-R PCS-82"; 82";
} }
identity ER4-PMD-clause-88 { /* optical interface func needs to expand for Fiber Channel, SONET and SDH */
base "optical-interface-func";
description
"ER4-PMD-clause-88 Optical Interface function
for 100GBASE-R PCS-82";
}
/* optical interface func needs to expand for Fiber Channel, SONET identity performance-metriclist {
and SDH */ description "list of performance metric";
}
identity performance-metriclist { identity One-way-Delay {
description "list of performance metric"; base "performance-metriclist";
description "one-way-delay";
} }
identity One-way-Delay { identity One-way-Errored-Second {
base "performance-metriclist"; base "performance-metriclist";
description "one-way-delay"; description "one-way-errored-second";
} }
identity One-way-Errored-Second {
base "performance-metriclist";
description "one-way-errored-second";
}
identity One-way-Severely-Errored-Second { identity One-way-Severely-Errored-Second {
base "performance-metriclist"; base "performance-metriclist";
description "one-way-severely-errored-second"; description "one-way-severely-errored-second";
} }
identity One-way-Unavailable-Second { identity One-way-Unavailable-Second {
base "performance-metriclist"; base "performance-metriclist";
description "one-way-unavailable-second"; description "one-way-unavailable-second";
} }
identity One-way-Availability { identity One-way-Availability {
base "performance-metriclist"; base "performance-metriclist";
description "one-way-availability"; description "one-way-availability";
} }
} }
<CODE ENDS> <CODE ENDS>
5. Security Considerations 5. Security Considerations
The configuration, state, and action data defined in this document The configuration, state, and action data defined in this document
are designed to be accessed via a management protocol with a secure are designed to be accessed via a management protocol with a secure
transport layer, such as NETCONF [RFC6241]. The NETCONF access transport layer, such as NETCONF [RFC6241]. The NETCONF access
control model [RFC6536] provides the means to restrict access for control model [RFC6536] provides the means to restrict access for
particular NETCONF users to a preconfigured subset of all available particular NETCONF users to a preconfigured subset of all available
NETCONF protocol operations and content. NETCONF 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
sensitivity/vulnerability:
Service-Config:
- subscriber-l1vc-id
- subscriber-l1vc-ep-id-1
- subscriber-l1vc-ep-id-2
- subscriber-l1vc-ep-UNI-1
- subscriber-l1vc-ep-UNI-2
- time-start
- time-interval
- performance-metric
6. IANA Considerations 6. IANA Considerations
This document registers the following namespace URIs in the IETF XML This document registers the following namespace URIs in the IETF XML
registry [RFC3688]: registry [RFC3688]:
-------------------------------------------------------------------- --------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:ietf-l1csm URI: urn:ietf:params:xml:ns:yang:ietf-l1csm
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
-------------------------------------------------------------------- --------------------------------------------------------------------
skipping to change at page 23, line 23 skipping to change at page 22, line 23
[RFC4847] T. Takeda (Editor), "Framework and Requirements for Layer [RFC4847] T. Takeda (Editor), "Framework and Requirements for Layer
1 Virtual Private Networks", RFC 4847, April 2007. 1 Virtual Private Networks", RFC 4847, April 2007.
[RFC5253] T. Takeda, "Applicability Statement for Layer 1 Virtual [RFC5253] T. Takeda, "Applicability Statement for Layer 1 Virtual
Private Network (L1VPN) Basic Mode", RFC 5253, July 2008. Private Network (L1VPN) Basic Mode", RFC 5253, July 2008.
[Service-Yang] Q. Wu, et al, "Service Models Explained", draft-wu- [Service-Yang] Q. Wu, et al, "Service Models Explained", draft-wu-
opsawg-service-model-explained, Work in progress. opsawg-service-model-explained, Work in progress.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, March 2018,
[RFC6991] J. Schoenwaelder, Ed., "Common YANG Data Types", RFC 6991,
July 2013.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010.
9. Contributors 9. Contributors
Contributor's Addresses Contributor's Addresses
I. Busi I. Busi
Huawei Huawei
Email: Italo.Busi@huawei.com Email: Italo.Busi@huawei.com
Authors' Addresses Authors' Addresses
 End of changes. 117 change blocks. 
501 lines changed or deleted 533 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/