draft-ietf-ccamp-l1csm-yang-04.txt   draft-ietf-ccamp-l1csm-yang-05.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 22, 2018 Y. Lee (Ed.) Expires: January 3, 2019 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 22, 2018 July 2, 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-04 draft-ietf-ccamp-l1csm-yang-05
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 October 25, 2018. This Internet-Draft will expire on January 3, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
skipping to change at page 2, line 28 skipping to change at page 2, line 28
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 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.......................................20 5. Security Considerations.......................................20
6. IANA Considerations...........................................20 6. IANA Considerations...........................................21
7. Acknowledgments...............................................21 7. Acknowledgments...............................................22
8. References....................................................22 8. References....................................................23
8.1. Normative References.....................................22 8.1. Normative References.....................................23
8.2. Informative References...................................22 8.2. Informative References...................................23
9. Contributors..................................................22 9. Contributors..................................................24
Authors' Addresses...............................................22 Authors' Addresses...............................................24
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[RFC6020] interface. controller via a NETCONF [RFC8341] 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 4, line 11 skipping to change at page 4, line 11
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 48 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
skipping to change at page 7, line 14 skipping to change at page 7, line 14
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, as shown in Table 1.
+---------+------------------------------+-----------------+ +---------+------------------------------+-----------------+
| Prefix | YANG module | Reference | | Prefix | YANG module | Reference |
+---------+------------------------------+-----------------+ +---------+------------------------------+-----------------+
| l1csm | ietf-l1cms | [This I-D] | | l1csm | ietf-l1cms | [RFC XXXX] |
| l1-st | ietf-l1-mef-service-types | [This I-D] | | l1-st | ietf-l1-mef-service-types | [RFC XXXX] |
| yang | ietf-yang-types | [RFC6991] | | yang | ietf-yang-types | [RFC6991] |
+---------+------------------------------+-----------------+ +---------+------------------------------+-----------------+
Table 1: Prefixes and corresponding YANG modules Table 1: Prefixes and corresponding YANG modules
Note: The RFC Editor will replace XXXX with the number assigned to
the RFC once this draft becomes an RFC.
2. Definitions 2. Definitions
L1VC Layer 1 Virtual Connection L1VC Layer 1 Virtual Connection
SLS Service Level Specification SLS Service Level Specification
UNI User Network Interface UNI User Network Interface
PE Provider Edge PE Provider Edge
skipping to change at page 8, line 17 skipping to change at page 8, line 18
+--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-list/UNI-ID +--rw subscriber-l1vc-ep-UNI-1? -> /l1cs/access/uni-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? int16
+--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-07-02.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 9, line 8 skipping to change at page 9, line 9
"Editor: G. Fioccolla (giuseppe.fioccola@telecomitalia.it) "Editor: G. Fioccolla (giuseppe.fioccola@telecomitalia.it)
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. G. de-Dios (oscar.gonzalezdedios@telefonica.com) Editor: O. G. 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 "this module describes Layer 1 connectivity service
model for subscriber Layer 1 Connectivity Services model for subscriber Layer 1 Connectivity Services
and Attributes. and Attributes. Refer to 'MEF x.y.x Technical Specification
Working Draft v0.09 5, December 13, 2017' for all terms and
the original references used in the module.
Copyright (c) 2018 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision 2018-06-20 { revision 2018-07-02 {
description
"updated version to incorporate MEF comments";
reference "to add the draft name";
}
revision 2018-06-20 {
description description
"updated version to incorporate MEF comments"; "updated version to incorporate MEF comments";
reference "to add the draft name"; reference "to add the draft name";
} }
revision 2018-04-11 { revision 2018-04-11 {
description description
"Initial revision."; "Initial revision.";
reference "to add the draft name"; 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> where p:protocol type; c:coding
function; o:optical interface function";
leaf protocol { leaf protocol {
type identityref { type identityref {
base "l1-st:protocol-type"; base "l1-st:protocol-type";
} }
description description
"List of physical layer L1VC clientprotocol"; "List of physical layer L1VC clientprotocol";
} }
leaf coding { leaf coding {
type identityref { type identityref {
base "l1-st:coding-func"; base "l1-st:coding-func";
} }
description "coding function"; description "coding function";
} }
leaf optical_interface { leaf optical_interface {
type identityref { type identityref {
base "l1-st: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;
description "the UNI id of UNI Service Attributes"; description "the UNI id of UNI 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 (Service Level "The value of the Subscriber L1VC SLS (Service Level
Specification) Service Attribute expressed in a 3-tuple Specification) Service Attribute expressed in a 3-tuple
of the form."; <p,c,o> of the form.";
leaf time-start { leaf time-start {
type yang:date-and-time; type yang:date-and-time;
description "a time that represent the date and time description "a time that represent the date and time
for the start of the SLS"; for the start of the SLS";
} }
leaf time-interval { leaf time-interval {
type int64; type int16;
units seconds; units seconds;
description "a time interval (e.g., 1 month) that is used description "a time interval (e.g., 2,419,200 seconds
in conjunction wuth time-start to specify a which is 28 days) that is used in
contiguous sequence of time intervals T for conjunction wuth time-start to specify a
determining when performance objectives are contiguous sequence of time intervals T for
met."; determining when performance objectives are
met.";
} }
leaf performance-metric { leaf performance-metric {
type identityref { type identityref {
base "l1-st:performance-metriclist"; base "l1-st:performance-metriclist";
} }
description "list of performance metric"; description "list of performance metric";
} }
} }
grouping subscriber-l1vc-service-attributes { grouping subscriber-l1vc-service-attributes {
description description
"subscriber layer 1 connection service service level"; "subscriber layer 1 connection service service level";
leaf subscriber-l1vc-id { leaf subscriber-l1vc-id {
type string; type string;
description "subscriber L1VC identifier"; description "subscriber L1VC identifier";
} }
leaf subscriber-l1vc-ep-id-1 { leaf subscriber-l1vc-ep-id-1 {
skipping to change at page 11, line 15 skipping to change at page 11, line 27
description description
"subscriber layer 1 connection service service level"; "subscriber layer 1 connection service service level";
leaf subscriber-l1vc-id { leaf subscriber-l1vc-id {
type string; type string;
description "subscriber L1VC identifier"; description "subscriber L1VC identifier";
} }
leaf subscriber-l1vc-ep-id-1 { leaf subscriber-l1vc-ep-id-1 {
type string; type string;
description "subscriber end point ID"; description "subscriber end point ID of one end";
} }
leaf subscriber-l1vc-ep-id-2 { leaf subscriber-l1vc-ep-id-2 {
type string; type string;
description "subscriber end point ID"; description "subscriber end point ID of the other end";
} }
leaf subscriber-l1vc-ep-UNI-1 { leaf subscriber-l1vc-ep-UNI-1 {
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 point description "this is one end of subscriber L1VC end point
ID value = UNI-1"; ID value = UNI-1";
} }
skipping to change at page 12, line 34 skipping to change at page 12, line 44
leaf subscriber-l1vc-id { leaf subscriber-l1vc-id {
type string; type string;
description "a unique service identifier for description "a unique service identifier for
L1VC."; L1VC.";
} }
container service-config { container service-config {
description "service-config container"; description "service-config container";
uses subscriber-attributes; uses subscriber-attributes;
}//end of service-config }//end of service-config
}//end of service list }//end of service list
} //end of service container } //end of service container
}//service top 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-7-02.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>
skipping to change at page 13, line 4 skipping to change at page 13, line 14
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: G. Fioccolla(giuseppe.fioccola@telecomitalia.it)
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. G. de-Dios(oscar.gonzalezdedios@telefonica.com) Editor: O. G. de-Dios(oscar.gonzalezdedios@telefonica.com)
Editor: D. Ceccarelli(daniele.ceccarelli@ericsson.com)"; Editor: D. Ceccarelli(daniele.ceccarelli@ericsson.com)";
description description
"This module defines L1 service types based on MEF "This module defines L1 service types based on MEF
subscriber Layer 1 Connectivity Service Attribute. subscriber Layer 1 Connectivity Service Attribute. Refer to
'MEF x.y.x Technical Specification Working Draft v0.09 5,
December 13, 2017' for all terms and the original references
used in the module.
Copyright (c) 2018 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision "2018-07-02" {
description
"Revision 0.2";
reference "TBD";
}
revision "2018-06-20" { revision "2018-06-20" {
description description
"Revision 0.2"; "Revision 0.2";
reference "TBD"; reference "TBD";
} }
revision "2018-04-11" { revision "2018-04-11" {
description description
"Revision 0.1"; "Revision 0.1";
reference "TBD"; reference "TBD";
} }
identity protocol-type { identity protocol-type {
description description
skipping to change at page 20, line 9 skipping to change at page 20, line 25
} }
} }
<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] or RESTCONF [RFC8040].
control model [RFC6536] provides the means to restrict access for The lowest NETCONF layer is the secure transport layer, and the
particular NETCONF users to a preconfigured subset of all available mandatory-to-implement secure transport is Secure Shell (SSH)
NETCONF protocol operations and content. [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-
to-implement secure transport is TLS [RFC5246].
The NETCONF access control model [RFC8341] provides the means to
restrict access for particular NETCONF users to a preconfigured
subset of all available 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 These are the subtrees and data nodes and their
sensitivity/vulnerability: sensitivity/vulnerability:
Service-Config: Service-Config:
- subscriber-l1vc-id - subscriber-l1vc-id
skipping to change at page 21, line 26 skipping to change at page 22, line 7
-------------------------------------------------------------------- --------------------------------------------------------------------
-------------------------------------------------------------------- --------------------------------------------------------------------
name: ietf-l1-mef-service-types name: 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
reference: RFC XXXX (TDB) 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 Tom Petch and Italo Busi for their
and valuable contributions. helpful comments 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",
Working Draft (WD) v0.09 December 13, 2017. Working Draft (WD) v0.09 December 13, 2017.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, June 2011.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, June 2011.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, August 2016.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, January 2017.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", RFC 8341, March 2018.
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.
[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, March 2018,
[RFC6991] J. Schoenwaelder, Ed., "Common YANG Data Types", RFC 6991, [RFC6991] J. Schoenwaelder, Ed., "Common YANG Data Types", RFC 6991,
July 2013. 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. 32 change blocks. 
45 lines changed or deleted 94 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/