draft-ietf-ccamp-l1csm-yang-00.txt   draft-ietf-ccamp-l1csm-yang-01.txt 
skipping to change at page 1, line 18 skipping to change at page 1, line 18
Huawei Huawei
O. Gonzalez de-Dios O. Gonzalez de-Dios
Telefonica Telefonica
D. Ceccarelli D. Ceccarelli
Ericsson Ericsson
April 25, 2018 April 25, 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-00 draft-ietf-ccamp-l1csm-yang-01
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 25 skipping to change at page 2, line 25
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
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. YANG Models....................................................8
5. Security Considerations.......................................19 4.1. YANG model for ietf-l1-service-types......................8
6. IANA Considerations...........................................20 4.2. YANG model for ietf-l1csm................................16
7. Acknowledgments...............................................20 5. Security Considerations.......................................20
8. References....................................................21 6. IANA Considerations...........................................21
8.1. Normative References.....................................21 7. Acknowledgments...............................................22
8.2. Informative References...................................21 8. References....................................................22
9. Contributors..................................................21 8.1. Normative References.....................................22
Authors' Addresses...............................................21 8.2. Informative References...................................22
9. Contributors..................................................22
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/Restconf interface.
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 model presented in Section 3 is consistent with [MEF-L1CS].
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 7, line 26 skipping to change at page 7, line 28
o Ellipsis ("...") stands for contents of subtrees that are not o Ellipsis ("...") stands for contents of subtrees that are not
shown. shown.
2. Definitions 2. Definitions
TDB TDB
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-ingress? -> +--rw subscriber-l1vc-ep-ingress? -> /l1cs/access/uni-list/UNI-
/l1cs/access/uni-list/UNI-ID ID
+--rw subscriber-l1vc-ep-egress? -> +--rw subscriber-l1vc-ep-egress? -> /l1cs/access/uni-list/UNI-
/l1cs/access/uni-list/UNI-ID ID
+--rw client-protocol? identityref +--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 CoS_Name? string
+--rw performance-metric? identityref
4. L1SM YANG Code
The YANG code is as follows: 4. YANG Models
<CODE BEGINS> file "ietf-l1csm@2018-03-05.yang" We have two YANG models described in this section.
module ietf-l1csm { The first model is ietf-l1-service-types that describes generic
yang-version 1.1; physical layer service attributes and performance-metric. (See
namespace "urn:ietf:params:xml:ns:yang:ietf-l1csm"; Section 4.1)
prefix "l1csm";
import ietf-yang-types { The second model is ietf-l1csm that describes L1 Connectivity
prefix "yang"; Service. (See Section 4.2)
}
organization 4.1. YANG model for ietf-l1-service-types
"Internet Engineering Task Force (IETF) CCAMP WG";
contact The YANG code is as follows:
"Editor: G. Fioccolla (giuseppe.fioccola@telecomitalia.it) <CODE BEGINS> file "ietf-l1-service-types@2018-04-11.yang"
Editor: K. Lee (kwangkoog.lee@kt.com)
Editor: Y. Lee (leeyoung@huawei.com)
Editor: D. Dhody (dhruv.ietf@gmail.com)
Editor: O. Gonzalez de-Dios (oscar.gonzalezdedios@telefonica.com)
Editor: D. Ceccarelli (daniele.ceccarelli@ericsson.com)";
description module ietf-l1-service-types {
"this module describes Layer 1 connectivity service model for namespace "urn:ietf:params:xml:ns:yang:ietf-l1-service-types";
subscriber Layer 1 Connectivity Services and Attributes"; prefix "l1-st";
revision 2018-03-05 { organization
description "IETF CCAMP Working Group";
"Initial revision."; contact
reference "to add the draft name"; "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. Gonzalez de-Dios(oscar.gonzalezdedios@telefonica.com)
Editor: D. Ceccarelli(daniele.ceccarelli@ericsson.com)";
identity protocol-type { description
description "This module defines L1 service types.";
"base identity from which client protocol
type is derived."; revision "2018-04-11" {
description
"Revision 0.1";
reference "TBD";
}
identity protocol-type {
description
"base identity from which client protocol type is derived.";
} }
identity aGigE { identity aGigE {
base protocol-type; base "protocol-type";
description description
"GigE protocol type"; "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 { identity STM-64 {
base protocol-type; base "protocol-type";
description description
"SDH STM-64 protocol type"; "SDH STM-64 protocol type";
} }
identity STM-256 { identity STM-256 {
base protocol-type; base "protocol-type";
description description
"SDH STM-256 protocol type"; "SDH STM-256 protocol type";
} }
identity OC-3 { identity OC-3 {
base protocol-type; base "protocol-type";
description description
"SONET OC-3 protocol type"; "SONET OC-3 protocol type";
} }
identity OC-12 { identity OC-12 {
base protocol-type; base "protocol-type";
description description
"SONET OC-12 protocol type"; "SONET OC-12 protocol type";
} }
identity OC-48 { identity OC-48 {
base protocol-type; base "protocol-type";
description description
"SONET OC-48 protocol type"; "SONET OC-48 protocol type";
} }
identity OC-192 { identity OC-192 {
base protocol-type; base "protocol-type";
description description
"SONET OC-192 protocol type"; "SONET OC-192 protocol type";
} }
identity OC-768 { identity OC-768 {
base protocol-type; base "protocol-type";
description description
"SONET OC-768 protocol type"; "SONET OC-768 protocol type";
} }
identity coding-func {
description identity coding-func {
"base identity from which coding func is description
derived."; "base identity from which coding func is derived.";
} }
identity a1000X-PCS-36 { identity a1000X-PCS-36 {
base coding-func; base "coding-func";
description description
"PCS clause 36 coding function that "PCS clause 36 coding function that
corresponds to 1000BASE-X"; corresponds to 1000BASE-X";
} }
identity a10GW-PCS-49-WIS-50 { identity a10GW-PCS-49-WIS-50 {
base coding-func; base "coding-func";
description description
"PCS clause 49 and WIS clause 50 coding func "PCS clause 49 and WIS clause 50 coding func
that corresponds to 10GBASE-W (WAN PHY)"; that corresponds to 10GBASE-W (WAN PHY)";
} }
identity a10GR-PCS-49 { identity a10GR-PCS-49 {
base coding-func; base "coding-func";
description description
"PCS clause 49 coding function that "PCS clause 49 coding function that
corresponds to 10GBASE-R (LAN PHY)"; corresponds to 10GBASE-R (LAN PHY)";
} }
identity a40GR-PCS-82 { identity a40GR-PCS-82 {
base coding-func; base "coding-func";
description description
"PCS clause 82 coding function that "PCS clause 82 coding function that
corresponds to 40GBASE-R"; corresponds to 40GBASE-R";
} }
identity a100GR-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 100GBASE-R";
} }
/* coding func needs to expand for Fiber Channel, SONET, SDH */ /* coding func needs to expand for Fiber Channel, SONET, SDH */
identity optical-interface-func { identity optical-interface-func {
description description
"base identity from which optical-interface- "base identity from which optical-interface-function is derived.";
function is derived."; }
}
identity SX-PMD-clause-38 { identity SX-PMD-clause-38 {
base optical-interface-func; base "optical-interface-func";
description description
"SX-PMD-clause-38 Optical Interface function "SX-PMD-clause-38 Optical Interface function
for 1000BASE-X PCS-36"; for 1000BASE-X PCS-36";
} }
identity LX-PMD-clause-38 { identity LX-PMD-clause-38 {
base optical-interface-func; base "optical-interface-func";
description description
"LX-PMD-clause-38 Optical Interface function "LX-PMD-clause-38 Optical Interface function
for 1000BASE-X PCS-36"; 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-36"; function for 1000BASE-X PCS-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-36"; function for 1000BASE-X PCS-36";
} }
identity LW-PMD-clause-52 { identity LW-PMD-clause-52 {
base optical-interface-func; base "optical-interface-func";
description description
"LW-PMD-clause-52 Optical Interface function "LW-PMD-clause-52 Optical Interface function
for 10GBASE-W PCS-49-WIS-50"; for 10GBASE-W PCS-49-WIS-50";
} }
identity EW-PMD-clause-52 { identity EW-PMD-clause-52 {
base optical-interface-func; base "optical-interface-func";
description description
"EW-PMD-clause-52 Optical Interface function "EW-PMD-clause-52 Optical Interface function
for 10GBASE-W PCS-49-WIS-50"; for 10GBASE-W PCS-49-WIS-50";
} }
identity LR-PMD-clause-52 { identity LR-PMD-clause-52 {
base optical-interface-func; base "optical-interface-func";
description description
"LR-PMD-clause-52 Optical Interface function "LR-PMD-clause-52 Optical Interface function
for 10GBASE-R PCS-49"; for 10GBASE-R PCS-49";
} }
identity ER-PMD-clause-52 { identity ER-PMD-clause-52 {
base optical-interface-func; base "optical-interface-func";
description description
"ER-PMD-clause-52 Optical Interface function "ER-PMD-clause-52 Optical Interface function
for 10GBASE-R PCS-49"; for 10GBASE-R PCS-49";
} }
identity LR4-PMD-clause-87 { identity LR4-PMD-clause-87 {
base optical-interface-func; base "optical-interface-func";
description description
"LR4-PMD-clause-87 Optical Interface function "LR4-PMD-clause-87 Optical Interface function
for 40GBASE-R PCS-82"; for 40GBASE-R PCS-82";
} }
identity ER4-PMD-clause-87 { identity ER4-PMD-clause-87 {
base optical-interface-func; base "optical-interface-func";
description description
"ER4-PMD-clause-87 Optical Interface function "ER4-PMD-clause-87 Optical Interface function
for 40GBASE-R PCS-82"; for 40GBASE-R PCS-82";
} }
identity FR-PMD-clause-89 { identity FR-PMD-clause-89 {
base optical-interface-func; base "optical-interface-func";
description description
"FR-PMD-clause-89 Optical Interface function "FR-PMD-clause-89 Optical Interface function
for 40GBASE-R PCS-82"; for 40GBASE-R PCS-82";
} }
identity LR4-PMD-clause-88 { identity LR4-PMD-clause-88 {
base optical-interface-func; base "optical-interface-func";
description description
"LR4-PMD-clause-88 Optical Interface function "LR4-PMD-clause-88 Optical Interface function
for 100GBASE-R PCS-82"; for 100GBASE-R PCS-82";
} }
identity ER4-PMD-clause-88 { identity ER4-PMD-clause-88 {
base optical-interface-func; base "optical-interface-func";
description description
"ER4-PMD-clause-88 Optical Interface function "ER4-PMD-clause-88 Optical Interface function
for 100GBASE-R PCS-82"; for 100GBASE-R PCS-82";
} }
/* optical interface func needs to expand for Fiber Channel, SONET /* optical interface func needs to expand for Fiber Channel, SONET
and SDH */ and SDH */
identity performance-metriclist { identity performance-metriclist {
description "list of performance metric"; description "list of performance metric";
} }
identity One-way-Delay { identity One-way-Delay {
base performance-metriclist; base "performance-metriclist";
description "one-way-delay"; description "one-way-delay";
} }
identity One-way-Errored-Second { identity One-way-Errored-Second {
base performance-metriclist; base "performance-metriclist";
description "one-way-errored-second"; 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 BEGINS>
4.2. YANG model for ietf-l1csm
The YANG code is as follows:
<CODE BEGINS> file "ietf-l1csm@2018-04-11.yang"
module ietf-l1csm {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-l1csm";
prefix "l1csm";
import ietf-yang-types {
prefix "yang";
}
import ietf-l1-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-04-11 {
description
"Initial revision.";
reference "to add the draft name";
}
grouping protocol-coding-optical_interface { grouping protocol-coding-optical_interface {
description description
"describes <p,c,o>"; "describes <p,c,o>";
leaf protocol { leaf protocol {
type identityref { type identityref {
base protocol-type; base "l1-st:protocol-type";
} }
description "Physical layer L1VC client
protocol service attribute"; description "List of physical layer L1VC
client protocol";
} }
leaf coding { leaf coding {
type identityref { type identityref {
base coding-func; base "l1-st:coding-func";
} }
description "coding function"; description "coding function";
} }
leaf optical_interface { leaf optical_interface {
type identityref { type identityref {
base optical-interface-func; base "l1-st:optical-interface-func";
} }
description "optical-interface-function"; description "optical-interface-function";
} }
} }
grouping uni-attributes { grouping uni-attributes {
description description
"uni-service-attributes"; "uni-service-attributes";
leaf UNI-ID { leaf UNI-ID {
type string; type string;
skipping to change at page 16, line 38 skipping to change at page 18, line 4
leaf UNI-ID { leaf UNI-ID {
type string; type string;
description "the UNI id of UNI description "the UNI id of UNI
Service Attributes"; Service Attributes";
} }
uses protocol-coding-optical_interface; uses protocol-coding-optical_interface;
} }
grouping subscriber-l1vc-sls-service-attribute { grouping subscriber-l1vc-sls-service-attribute {
description description
"The value of the Subscriber L1VC SLS "The value of the Subscriber L1VC SLS
(Service Level Specification) Service Attribute expressed in a 4-tuple of the (Service Level Specification) Service Attribute expressed in a 3-tuple of the
form."; form.";
leaf time-start { leaf time-start {
type yang:date-and-time; type yang:date-and-time;
description "a time that represent description "a time that represent
the date and time for the start of the SLS"; the date and time for the start of the SLS";
} }
leaf time-interval { leaf time-interval {
type int64; type int64;
units seconds; units seconds;
description "a time interval description "a time interval
(e.g., 1 month) that is used in conjunction wuth time-start to specify a (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 contiguous sequence of time intervals T for determining when performance
objectives are met."; objectives are met.";
} }
leaf CoS_Name {
type string;
description "a Class of Service
Name used by the Subscriber L1VC End Point Class of Service Identifier Service
Attribute.";
}
leaf performance-metric { leaf performance-metric {
type identityref { type identityref {
base performance-metriclist; base "l1-st:performance-"
+"metriclist";
} }
description "list of performance description "list of performance
metric"; metric";
} }
} }
grouping subscriber-l1vc-service-attributes { grouping subscriber-l1vc-service-attributes {
description description
"subscriber layer 1 connection service "subscriber layer 1 connection service
service level"; service level";
skipping to change at page 18, line 4 skipping to change at page 19, line 10
description "subscriber L1VC identifier"; description "subscriber L1VC identifier";
} }
leaf subscriber-l1vc-ep-ingress { leaf subscriber-l1vc-ep-ingress {
type leafref { type leafref {
path "/l1cs/access/uni-list/UNI-ID"; path "/l1cs/access/uni-list/UNI-ID";
} }
description "this is one end of subscriber L1VC end description "this is one end of subscriber L1VC end
point ID value = UNI-1"; point ID value = UNI-1";
} }
leaf subscriber-l1vc-ep-egress { leaf subscriber-l1vc-ep-egress {
type leafref { type leafref {
path "/l1cs/access/uni-list/UNI-ID"; path "/l1cs/access/uni-list/UNI-ID";
} }
description "this is the other end of subscriber description "this is the other end of subscriber
L1VC end point ID value = UNI-2"; L1VC end point ID value = UNI-2";
} }
leaf client-protocol {
type identityref {
base protocol-type;
}
description "One of Ethernet, Fiber Channel, SONET,
SDH";
}
uses subscriber-l1vc-sls-service-attribute; uses subscriber-l1vc-sls-service-attribute;
} }
grouping subscriber-attributes { grouping subscriber-attributes {
description description
"subscriber attributes"; "subscriber attributes";
uses subscriber-l1vc-service-attributes; uses subscriber-l1vc-service-attributes;
} }
skipping to change at page 20, line 18 skipping to change at page 21, line 20
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.
-------------------------------------------------------------------- --------------------------------------------------------------------
--------------------------------------------------------------------
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 This document registers the following YANG modules in the YANG
Module Module
Names registry [RFC7950]: Names registry [RFC7950]:
-------------------------------------------------------------------- --------------------------------------------------------------------
name: ietf-l1csm name: ietf-l1csm
namespace: urn:ietf:params:xml:ns:yang:ietf-l1csm namespace: urn:ietf:params:xml:ns:yang:ietf-l1csm
reference: RFC XXXX (TDB) reference: RFC XXXX (TDB)
-------------------------------------------------------------------- --------------------------------------------------------------------
--------------------------------------------------------------------
name: ietf-l1-service-types
namespace: urn:ietf:params:xml:ns:yang:ietf-l1-service-types
reference: RFC XXXX (TDB)
--------------------------------------------------------------------
7. Acknowledgments 7. Acknowledgments
The authors would like to thank Italo Busi for his helpful comments The authors would like to thank Italo Busi for his helpful comments
and valuable contributions. and valuable contributions.
8. References 8. References
8.1. Normative References 8.1. Normative References
[MEF-L1CS] "Subscriber Layer 1 Connectivity Service Attributes", [MEF-L1CS] "Subscriber Layer 1 Connectivity Service Attributes",
 End of changes. 80 change blocks. 
150 lines changed or deleted 203 lines changed or added

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