< draft-fioccola-ccamp-l1csm-yang-00.txt   draft-fioccola-ccamp-l1csm-yang-01.txt >
CCAMP Working Group G. Fioccola 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: April 27, 2018 Y. Lee Expires: September 5, 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
October 27, 2017 March 5, 2018
A Yang Data Model for L1 Connectivity Service Model (L1CSM) A Yang Data Model for L1 Connectivity Service Model (L1CSM)
draft-fioccola-ccamp-l1csm-yang-00 draft-fioccola-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 1, line 46 skipping to change at page 1, line 46
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on April 27, 2018. This Internet-Draft will expire on September 5, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 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 (http://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 to this document. Code Components extracted from this respect to this document. Code Components extracted from this
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
skipping to change at page 3, line 34 skipping to change at page 3, line 32
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].
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 11
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 8, line 4 skipping to change at page 8, line 4
+--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-ID /l1cs/access/uni-list/UNI-ID
+--rw subscriber-l1vc-ep-egress? -> +--rw subscriber-l1vc-ep-egress? ->
/l1cs/access/uni-list/UNI-ID /l1cs/access/uni-list/UNI-ID
+--rw client-protocol? identityref +--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 CoS_Name? string +--rw CoS_Name? string
+--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@2017-10-27.yang" <CODE BEGINS> file "ietf-l1csm@2018-03-05.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"; prefix "l1csm";
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
skipping to change at page 8, line 37 skipping to change at page 8, line 36
Editor: K. Lee (kwangkoog.lee@kt.com) Editor: K. Lee (kwangkoog.lee@kt.com)
Editor: Y. Lee (leeyoung@huawei.com) Editor: Y. Lee (leeyoung@huawei.com)
Editor: D. Dhody (dhruv.ietf@gmail.com) Editor: D. Dhody (dhruv.ietf@gmail.com)
Editor: O. Gonzalez de-Dios (oscar.gonzalezdedios@telefonica.com) Editor: O. Gonzalez de-Dios (oscar.gonzalezdedios@telefonica.com)
Editor: D. Ceccarelli (daniele.ceccarelli@ericsson.com)"; Editor: D. Ceccarelli (daniele.ceccarelli@ericsson.com)";
description description
"this module describes Layer 1 connectivity service model for "this module describes Layer 1 connectivity service model for
subscriber Layer 1 Connectivity Services and Attributes"; subscriber Layer 1 Connectivity Services and Attributes";
revision 2017-10-27 { revision 2018-03-05 {
description description
"Initial revision."; "Initial revision.";
reference "to add the draft name"; reference "to add the draft name";
} }
identity protocol-type { identity protocol-type {
description description
"base identity from which client protocol "base identity from which client protocol
type is derived."; type is derived.";
skipping to change at page 15, line 19 skipping to change at page 15, line 19
/* 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";
} }
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 protocol-type;
} }
description "Physical layer L1VC client description "Physical layer L1VC client
skipping to change at page 17, line 24 skipping to change at page 17, line 24
leaf CoS_Name { leaf CoS_Name {
type string; type string;
description "a Class of Service description "a Class of Service
Name used by the Subscriber L1VC End Point Class of Service Identifier Service Name used by the Subscriber L1VC End Point Class of Service Identifier Service
Attribute."; Attribute.";
} }
leaf performance-metric { leaf performance-metric {
type identityref { type identityref {
base performance-metriclist; base 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 20, line 12 skipping to change at page 20, line 9
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.
6. IANA Considerations 6. IANA Considerations
TDB This document registers the following namespace URIs in the IETF XML
registry [RFC3688]:
--------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:ietf-l1csm
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
--------------------------------------------------------------------
This document registers the following YANG modules in the YANG
Module
Names registry [RFC7950]:
--------------------------------------------------------------------
name: ietf-l1csm
namespace: urn:ietf:params:xml:ns:yang:ietf-l1csm
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",
Working Draft (WD) v0.09 December 13, 2017.
8.2. Informative References 8.2. Informative References
[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.
skipping to change at page 21, line 30 skipping to change at page 21, line 33
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
G. Fioccola G. Fioccola (Editor)
Telecom Italia Telecom Italia
Email: giuseppe.fioccola@telecomitalia.it Email: giuseppe.fioccola@telecomitalia.it
K. Lee K. Lee
KT KT
Email: kwangkoog.lee@kt.com Email: kwangkoog.lee@kt.com
Y. Lee Y. Lee (Editor)
Huawei Huawei
Email: leeyoung@huawei.com Email: leeyoung@huawei.com
D. Dhody D. Dhody
Huawei Huawei
Email: dhruv.ietf@gmail.com Email: dhruv.ietf@gmail.com
O. Gonzalez de Dios O. Gonzalez de Dios
Telefonica Telefonica
Email: oscar.gonzalezdedios@telefonica.com Email: oscar.gonzalezdedios@telefonica.com
 End of changes. 23 change blocks. 
32 lines changed or deleted 54 lines changed or added

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