draft-ietf-ccamp-l1csm-yang-06.txt   draft-ietf-ccamp-l1csm-yang-07.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: January 17, 2019 Y. Lee (Ed.) Expires: March 1, 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
July 17, 2018 August 30, 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-06 draft-ietf-ccamp-l1csm-yang-07
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). This YANG model is NMDA-compliant. Service Model (L1CSM). This YANG model is NMDA-compliant.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted 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 January 17, 2019. This Internet-Draft will expire on March 1 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 27 skipping to change at page 2, line 27
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 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. JSON Example..................................................19 5. JSON Example..................................................20
6. Security Considerations.......................................20 6. Security Considerations.......................................21
7. IANA Considerations...........................................21 7. IANA Considerations...........................................22
8. Acknowledgments...............................................22 8. Acknowledgments...............................................23
9. References....................................................23 9. References....................................................24
9.1. Normative References.....................................23 9.1. Normative References.....................................24
9.2. Informative References...................................23 9.2. Informative References...................................24
10. Contributors.................................................24 10. Contributors.................................................25
Authors' Addresses...............................................24 Authors' Addresses...............................................25
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 [RFC8341] or a RESTCONF [RFC8040] controller via a NETCONF [RFC8341] or a RESTCONF [RFC8040]
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 4, line 39 skipping to change at page 4, line 39
: | | : : | | :
: |<-Provider network->| : : |<-Provider network->| :
Customer Customer Customer Customer
Interface Interface Interface Interface
Figure 1: L1VPN SDN Controller/EMS/NMS-Based Service Model: External Customer Figure 1: L1VPN SDN Controller/EMS/NMS-Based Service Model: External Customer
With this scenario, the customer service orchestrator interfaces With this scenario, the customer service orchestrator interfaces
with the network SDN controller of the provider using Customer with the network SDN controller of the provider using Customer
Service Model as defined in [Service-Yang]. Service Model as defined in [RFC8309].
Figure 2 depicts another deployment scenario for internal customer Figure 2 depicts another deployment scenario for internal customer
(e.g., higher-layer service management department(s)) interfacing (e.g., higher-layer service management department(s)) interfacing
the layer 1 transport network department. With this scenario, a the layer 1 transport network department. With this scenario, a
multi-service backbone is characterized such that each service multi-service backbone is characterized such that each service
department of a provider (e.g., L2/3 services) that receives the department of a provider (e.g., L2/3 services) that receives the
same provider's L1VPN service provides a different kind of higher- same provider's L1VPN service provides a different kind of higher-
layer service. The customer receiving the L1VPN service (i.e., each layer service. The customer receiving the L1VPN service (i.e., each
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
skipping to change at page 7, line 15 skipping to change at page 7, line 15
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 | [RFC XXXX] | | l1csm | ietf-l1cms | [RFC XXXX] |
| l1-st | ietf-l1-mef-service-types | [RFC XXXX] | | l1-st | ietf-l1-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 Note: The RFC Editor will replace XXXX with the number assigned to
the RFC once this draft becomes an RFC. the RFC once this draft becomes an RFC.
2. Definitions 2. Definitions
skipping to change at page 8, line 25 skipping to change at page 8, line 25
+--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? Int32 +--rw time-interval? Int32
+--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-07-05" <CODE BEGINS> file "ietf-l1csm@2018-08-30.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";
} }
import ietf-l1-mef-service-types { import ietf-l1-service-types {
prefix "l1-st"; prefix "l1-st";
} }
organization organization
"Internet Engineering Task Force (IETF) CCAMP WG"; "Internet Engineering Task Force (IETF) CCAMP WG";
contact contact
"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 L1 connectivity service based on MEF 63:
model for subscriber Layer 1 Connectivity Services Subscriber Layer 1 Service Attribute Technical Specification.
and Attributes. Refer to 'MEF x.y.x Technical Specification Refer to MEF 63 for all terms and the original references
Working Draft v0.09 5, December 13, 2017' for all terms and used in the module.
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-05" { revision "2018-08-30" {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A Yang Data Model for L1 Connectivity reference "RFC XXXX: A Yang Data Model for L1 Connectivity
Service Model (L1CSM)"; Service Model (L1CSM)";
// Note: The RFC Editor will replace XXXX with the number // Note: The RFC Editor will replace XXXX with the number
// assigned to the RFC once this draft becomes an RFC. // assigned to the RFC once this draft becomes an RFC.
} }
grouping protocol-coding-optical_interface { grouping protocol-coding-optical_interface {
description description
"describes <p,c,o> where p:protocol type; c:coding "describes <p,c,o> where p:protocol type; c:coding
skipping to change at page 12, line 36 skipping to change at page 13, line 4
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-07-05" <CODE BEGINS> file "ietf-l1-service-types@2018-08-30.yang"
module ietf-l1-mef-service-types { module ietf-l1-service-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-l1-mef-service-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-l1-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: G. Fioccolla(giuseppe.fioccola@telecomitalia.it)
Editor: Y. Lee (leeyoung@huawei.com) Editor: K. Lee (kwangkoog.lee@kt.com)
Editor: D. Dhody (dhruv.ietf@gmail.com) Editor: Y. Lee (leeyoung@huawei.com)
Editor: O. G. de-Dios(oscar.gonzalezdedios@telefonica.com) Editor: D. Dhody (dhruv.ietf@gmail.com)
Editor: D. Ceccarelli(daniele.ceccarelli@ericsson.com)"; Editor: O. G. de-Dios(oscar.gonzalezdedios@telefonica.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 63:
subscriber Layer 1 Connectivity Service Attribute. Refer to Subscriber Layer 1 Service Attribute Technical Specification.
'MEF x.y.x Technical Specification Working Draft v0.09 5, Refer to MEF 63 for all terms and the original references
December 13, 2017' for all terms and the original references used in the module. As for the protocol-type, refer also to
used in the module. the client-type in G.709.
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-05" { revision "2018-08-30" {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A Yang Data Model for L1 Connectivity reference "RFC XXXX: A Yang Data Model for L1 Connectivity
Service Model (L1CSM)"; Service Model (L1CSM)";
// Note: The RFC Editor will replace XXXX with the number // Note: The RFC Editor will replace XXXX with the number
// assigned to the RFC once this draft becomes an RFC. // assigned to the RFC once this draft becomes an RFC.
}
identity protocol-type {
description
"base identity from which client protocol type is derived.";
} }
identity aGigE { identity protocol-type {
base "protocol-type"; description
description "base identity from which client protocol type is derived.";
"GigE protocol type"; }
}
identity a10GigE_WAN { identity ETH-1GbE {
base "protocol-type"; base "protocol-type";
description description
"10GigE-WAN protocol type"; "GigE protocol type";
} reference "MEF63 & G.709";
}
identity a10GigE_LAN { identity ETH-10GbE-WAN {
base "protocol-type"; base "protocol-type";
description description
"10GigE-LAN protocol type"; "10GigE-WAN protocol type";
} reference "MEF63 & G.709";
}
identity a40GigE { identity ETH-10GbE-LAN {
base "protocol-type"; base "protocol-type";
description description
"40GigE protocol type"; "10GigE-LAN protocol type";
} reference "MEF63 & G.709";
}
identity a100GigE { identity ETH-40GbE {
base "protocol-type"; base "protocol-type";
description description
"100GigE protocol type"; "40GigE protocol type";
} reference "MEF63 & G.709";
}
identity FC-100 { identity ETH-100GbE {
base "protocol-type"; base "protocol-type";
description description
"Fiber Channel - 100 protocol type"; "100GigE protocol type";
} reference "MEF63 & G.709";
}
identity FC-200 { identity FC-100 {
base "protocol-type"; base "protocol-type";
description description
"Fiber Channel - 200 protocol type"; "Fiber Channel - 100 protocol type";
} reference "MEF63 & G.709";
identity FC-400 { }
base "protocol-type";
description
"Fiber Channel - 400 protocol type";
}
identity FC-800 { identity FC-200 {
base "protocol-type"; base "protocol-type";
description description
"Fiber Channel - 800 protocol type"; "Fiber Channel - 200 protocol type";
} reference "MEF63 & G.709";
}
identity FC-1200 { identity FC-400 {
base "protocol-type"; base "protocol-type";
description description
"Fiber Channel - 1200 protocol type"; "Fiber Channel - 400 protocol type";
reference "MEF63 & G.709";
}
} identity FC-800 {
base "protocol-type";
description
"Fiber Channel - 800 protocol type";
reference "MEF63 & G.709";
}
identity FC-1600 { identity FC-1200 {
base "protocol-type"; base "protocol-type";
description description
"Fiber Channel - 1600 protocol type"; "Fiber Channel - 1200 protocol type";
} reference "MEF63 & G.709";
}
identity FC-3200 { identity FC-1600 {
base "protocol-type"; base "protocol-type";
description description
"Fiber Channel - 3200 protocol type"; "Fiber Channel - 1600 protocol type";
} reference "MEF63 & G.709";
}
identity STM-1 { identity FC-3200 {
base "protocol-type"; base "protocol-type";
description description
"SDH STM-1 protocol type"; "Fiber Channel - 3200 protocol type";
} reference "MEF63 & G.709";
}
identity STM-4 { identity STM-1 {
base "protocol-type"; base "protocol-type";
description description
"SDH STM-4 protocol type"; "SDH STM-1 protocol type";
} reference "MEF63 & G.709";
identity STM-16 { }
base "protocol-type";
description
"SDH STM-16 protocol type";
}
identity STM-64 { identity STM-4 {
base "protocol-type"; base "protocol-type";
description description
"SDH STM-64 protocol type"; "SDH STM-4 protocol type";
} reference "MEF63 & G.709";
}
identity STM-256 { identity STM-16 {
base "protocol-type"; base "protocol-type";
description description
"SDH STM-256 protocol type"; "SDH STM-16 protocol type";
} reference "MEF63 & G.709";
}
identity OC-3 { identity STM-64 {
base "protocol-type"; base "protocol-type";
description description
"SONET OC-3 protocol type"; "SDH STM-64 protocol type";
} reference "MEF63 & G.709";
identity OC-12 { }
base "protocol-type";
description
"SONET OC-12 protocol type";
}
identity OC-48 { identity STM-256 {
base "protocol-type"; base "protocol-type";
description description
"SONET OC-48 protocol type"; "SDH STM-256 protocol type";
} reference "MEF63 & G.709";
}
identity OC-192 { identity OC-3 {
base "protocol-type"; base "protocol-type";
description description
"SONET OC-192 protocol type"; "SONET OC-3 protocol type";
} reference "MEF63 & G.709";
}
identity OC-768 { identity OC-12 {
base "protocol-type"; base "protocol-type";
description description
"SONET OC-768 protocol type"; "SONET OC-12 protocol type";
} reference "MEF63 & G.709";
}
identity OC-48 {
base "protocol-type";
description
"SONET OC-48 protocol type";
reference "MEF63 & G.709";
}
identity OC-192 {
base "protocol-type";
description
"SONET OC-192 protocol type";
reference "MEF63 & G.709";
}
identity OC-768 {
base "protocol-type";
description
"SONET OC-768 protocol type";
reference "MEF63 & G.709";
}
identity coding-func { identity coding-func {
description description
"base identity from which coding func is derived."; "base identity from which coding func is derived.";
} }
identity a1000X-PCS-36 { identity ETH-1000X-PCS-36 {
base "coding-func"; base "coding-func";
description description
"PCS clause 36 coding function that corresponds to 1000BASE-X"; "PCS clause 36 coding function that corresponds to 1000BASE-X";
} }
identity a10GW-PCS-49-WIS-50 { identity ETH-10GW-PCS-49-WIS-50 {
base "coding-func"; base "coding-func";
description description
"PCS clause 49 and WIS clause 50 coding func that corresponds to "PCS clause 49 and WIS clause 50 coding func that corresponds to 10GBASE-W
10GBASE-W (WAN PHY)"; (WAN PHY)";
} }
identity a10GR-PCS-49 { identity ETH-10GR-PCS-49 {
base "coding-func"; base "coding-func";
description description
"PCS clause 49 coding function that corresponds to 10GBASE-R (LAN "PCS clause 49 coding function that corresponds to 10GBASE-R (LAN PHY)";
PHY)"; }
}
identity a40GR-PCS-82 {
base "coding-func";
description
"PCS clause 82 coding function that corresponds to 40GBASE-R";
}
identity a100GR-PCS-82 { identity ETH-40GR-PCS-82 {
base "coding-func"; base "coding-func";
description description
"PCS clause 82 coding function that corresponds to 100GBASE-R"; "PCS clause 82 coding function that corresponds to 40GBASE-R";
} }
/* coding func needs to expand for Fiber Channel, SONET, SDH */ identity ETH-100GR-PCS-82 {
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 { identity optical-interface-func {
description description
"base identity from which optical-interface-function is derived."; "base identity from which optical-interface-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 for 1000BASE-X PCS-36"; "SX-PMD-clause-38 Optical Interface function 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 for 1000BASE-X PCS-36"; "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 function for 1000BASE-X PCS- "LX10-PMD-clause-59 Optical Interface 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 function for 1000BASE-X PCS- "BX10-PMD-clause-59 Optical Interface function for 1000BASE-X PCS-36";
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 for 10GBASE-W PCS-49- "LW-PMD-clause-52 Optical Interface function for 10GBASE-W PCS-49-WIS-50";
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 for 10GBASE-W PCS-49- "EW-PMD-clause-52 Optical Interface function for 10GBASE-W PCS-49-WIS-50";
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 for 10GBASE-R PCS-49"; "LR-PMD-clause-52 Optical Interface function 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 for 10GBASE-R PCS-49"; "ER-PMD-clause-52 Optical Interface function 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 for 40GBASE-R PCS-82"; "LR4-PMD-clause-87 Optical Interface function 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 for 40GBASE-R PCS-82"; "ER4-PMD-clause-87 Optical Interface function 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 for 40GBASE-R PCS-82"; "FR-PMD-clause-89 Optical Interface function 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 for 100GBASE-R PCS- "LR4-PMD-clause-88 Optical Interface function for 100GBASE-R PCS-82";
82"; }
}
identity ER4-PMD-clause-88 {
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 and SDH */ identity ER4-PMD-clause-88 {
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 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 ENDS> <CODE ENDS>
5. JSON Example 5. JSON Example
This section provides a JSON example of the YANG module described in This section provides a JSON example of the YANG module described in
Section 4. Section 4.
{ {
"l1cs": { "l1cs": {
"access": { "access": {
"uni-list": [ "uni-list": [
{ {
"UNI-ID": "MTL-HQ-Node3-Slot2-Port1", "UNI-ID": "MTL-HQ-Node3-Slot2-Port1",
"protocol": "a10GigE_LAN ", "protocol": "ETH-10GigE_LAN ",
"coding": "a10GR-PCS-49 ", "coding": "ETH-10GR-PCS-49 ",
"optical_interface": "LR-PMD-clause-52 " "optical_interface": "LR-PMD-clause-52 "
}, },
{ {
"UNI-ID": "MTL-STL-Node5-Slot4-Port3", "UNI-ID": "MTL-STL-Node5-Slot4-Port3",
"protocol": "a10GigE_LAN ", "protocol": "ETH-10GigE_LAN ",
"coding": "a10GR-PCS-49 ", "coding": "ETH-10GR-PCS-49 ",
"optical_interface": "ER-PMD-clause-52 " "optical_interface": "ER-PMD-clause-52 "
} }
] ]
}, },
"service": { "service": {
"service-list": [ "service-list": [
{ {
"subscriber-l1vc-id": "Sub-L1VC-1867-LT-MEGAMART", "subscriber-l1vc-id": "Sub-L1VC-1867-LT-MEGAMART",
"service-config": { "service-config": {
"subscriber-l1vc-id": "Sub-L1VC-1867-LT-MEGAMART", "subscriber-l1vc-id": "Sub-L1VC-1867-LT-MEGAMART",
skipping to change at page 22, line 4 skipping to change at page 22, line 32
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-mef-service-types URI: urn:ietf:params:xml:ns:yang:ietf-l1-service-types
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.
-------------------------------------------------------------------- --------------------------------------------------------------------
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-mef-service-types name: ietf-l1-service-types
namespace: urn:ietf:params:xml:ns:yang:ietf-l1-mef-service-types namespace: urn:ietf:params:xml:ns:yang:ietf-l1-service-types
reference: RFC XXXX (TDB) reference: RFC XXXX (TDB)
-------------------------------------------------------------------- --------------------------------------------------------------------
8. Acknowledgments 8. Acknowledgments
The authors would like to thank Tom Petch and Italo Busi for their The authors would like to thank Tom Petch and Italo Busi for their
helpful comments and valuable contributions. helpful comments and valuable contributions.
9. References 9. References
9.1. Normative References 9.1. Normative References
[MEF-L1CS] "Subscriber Layer 1 Connectivity Service Attributes", [MEF63] "Subscriber Layer 1 Service Attributes", Technical
Working Draft (WD) v0.09 December 13, 2017. Specification, MEF 63, August 2018.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. October 2010.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
skipping to change at page 23, line 46 skipping to change at page 24, line 46
Access Control Model", RFC 8341, March 2018. Access Control Model", RFC 8341, March 2018.
9.2. Informative References 9.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- [RFC8309] Q. Wu, W. Liu and A. Farrel, "Service Models Explained",
opsawg-service-model-explained, Work in progress. RFC 8309, January 2018.
[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,
[G.709] ITU-T Recommendation G.709/Y.1331, Interfaces for the
optical transport network, Corrigendum 1, August 2017.
10. Contributors 10. 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. 75 change blocks. 
296 lines changed or deleted 320 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/