draft-ietf-ccamp-layer1-types-03.txt   draft-ietf-ccamp-layer1-types-04.txt 
CCAMP Working Group H. Zheng CCAMP Working Group H. Zheng
Internet-Draft I. Busi Internet-Draft I. Busi
Intended status: Standards Track Huawei Technologies Intended status: Standards Track Huawei Technologies
Expires: May 4, 2020 November 1, 2019 Expires: June 7, 2020 December 5, 2019
A YANG Data Model for Layer 1 Types A YANG Data Model for Layer 1 Types
draft-ietf-ccamp-layer1-types-03 draft-ietf-ccamp-layer1-types-04
Abstract Abstract
This document defines a collection of common data types and groupings This document defines a collection of common data types and groupings
in YANG data modeling language for layer 1 networks. These derived in YANG data modeling language for layer 1 networks. These derived
common types and groupings are intended to be imported by modules common types and groupings are intended to be imported by modules
that specifies the OTN networks, including the topology, tunnel, that specifies the OTN networks, including the topology, tunnel,
client signal adaptation and service. client signal adaptation and service.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 4, 2020. This Internet-Draft will expire on June 7, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 2, line 16 skipping to change at page 2, line 16
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology and Notations . . . . . . . . . . . . . . . . . . 2 2. Terminology and Notations . . . . . . . . . . . . . . . . . . 2
3. Prefix in Data Node Names . . . . . . . . . . . . . . . . . . 3 3. Prefix in Data Node Names . . . . . . . . . . . . . . . . . . 3
4. Layer 1 Types Overview . . . . . . . . . . . . . . . . . . . 3 4. Layer 1 Types Overview . . . . . . . . . . . . . . . . . . . 3
4.1. Relationship with other Modules . . . . . . . . . . . . . 3 4.1. Relationship with other Modules . . . . . . . . . . . . . 3
4.2. Content in Layer 1 Type Module . . . . . . . . . . . . . 3 4.2. Content in Layer 1 Type Module . . . . . . . . . . . . . 3
4.3. Usage of groupings in Layer1-types . . . . . . . . . . . 5 4.3. Usage of groupings in Layer1-types . . . . . . . . . . . 5
5. YANG Code for Layer1 Types . . . . . . . . . . . . . . . . . 6 5. YANG Code for Layer1 Types . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 20 6. Security Considerations . . . . . . . . . . . . . . . . . . . 20
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 21 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 21
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
10.1. Normative References . . . . . . . . . . . . . . . . . . 22 10.1. Normative References . . . . . . . . . . . . . . . . . . 22
10.2. Informative References . . . . . . . . . . . . . . . . . 23 10.2. Informative References . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25
1. Introduction 1. Introduction
This document introduces a collection of common data types which This document introduces a collection of common data types which
would be used in Layer 1 networks. The derived types and groupings would be used in Layer 1 networks. The derived types and groupings
are designed to be the common types applicable for modeling Traffic are designed to be the common types applicable for modeling Traffic
Engineering (TE) features for Layer 1 optical networks. Engineering (TE) features for Layer 1 networks.
Typical L1 network, the Optical Transport Networking, was specified Typical Layer 1 network, the Optical Transport Networking, was
in [RFC7062]. Corresponding routing and signaling protocol have been specified in [RFC7062]. Corresponding routing and signaling protocol
specified in [RFC7138] and [RFC7139]. The types and groupings have been specified in [RFC7138] and [RFC7139]. The types and
defined in this document is consistent to these document, and will be groupings defined in this document is consistent to these document,
imported in other Layer 1 data models, including but not restrictive and will be imported in other Layer 1 data models, including but not
to, [I-D.ietf-ccamp-otn-topo-yang], [I-D.ietf-ccamp-otn-tunnel-model] restrictive to, [I-D.ietf-ccamp-otn-topo-yang],
and [I-D.ietf-ccamp-l1csm-yang]. [I-D.ietf-ccamp-otn-tunnel-model] and [I-D.ietf-ccamp-l1csm-yang].
The data model in this draft has only types defined including The data model in this draft has only types defined including
groupings, typedef and identities. There is no need to include groupings, typedef and identities. There is no need to include
configuration and state data according to the new Network Management configuration and state data according to the new Network Management
Datastore Architecture [RFC8342]. The content in this draft is in Datastore Architecture [RFC8342]. The content in this draft is in
consistent with [MEF63]. consistent with other specifications, including [MEF63] for Layer 1
service attributes, [ITU-Tg709] and [ITU-Tgsup43] for OTN data plane
definitions.
2. Terminology and Notations 2. Terminology and Notations
Refer to [RFC7062] for the key terms used in this document, and the Refer to [RFC7062] for the key terms used in this document, and the
terminology for describing YANG data models can be found in terminology for describing YANG data models can be found in
[RFC7950]. [RFC7950].
3. Prefix in Data Node Names 3. Prefix 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
skipping to change at page 3, line 44 skipping to change at page 3, line 44
tributary-slot-granularity: tributary-slot-granularity:
This is to define the granularity of the server layer ODU Link (HO This is to define the granularity of the server layer ODU Link (HO
ODUk or ODUCn) supporting a client layer ODU LSP (LO ODUj or ODUk, ODUk or ODUCn) supporting a client layer ODU LSP (LO ODUj or ODUk,
respectively). Three granularities, 1.25G/2.5G/5G, have been respectively). Three granularities, 1.25G/2.5G/5G, have been
specified. specified.
odu-type: odu-type:
This is to specify the type of ODUk LSP. This is to specify the type of ODUk LSP, including the types
specified in [RFC7139] and [RFC7963].
client-signal: client-signal:
This is to specify the client signal types of OTN networks. The This is to specify the client signal types of OTN networks. The
initial input was the G-PID specified in [RFC7139]. Identities about initial input was the G-PID specified in [RFC7139]. Identities about
a few categories of client signal types, including ETH, STM-n, OC and a few categories of client signal types, including ETH, STM-n, OC and
Fiber Channel have been specified. Fiber Channel have been specified.
otn-label-range-type: otn-label-range-type:
The label range type of OTN has two different representations, The label range type of OTN has two different representations,
tributary slots (TS) and tributary port number (TPN), according to tributary slots (TS) and tributary port number (TPN), according to
[RFC7139]. Respective representation is specified under this same [RFC7139]. Respective representation is specified under this same
base type. base type.
otn-link-bandwidth: otn-link-bandwidth:
This grouping defines the link bandwidth information and could be This grouping defines the link bandwidth information and could be
used in OTN topology model for bandwidth representation. All the used in OTN topology model for bandwidth representation. All the
bandwidth related sections in generic topology module, ietf-te- bandwidth related sections in generic module,
topology, need to be augmented with this grouping for the usage of [I-D.ietf-teas-yang-te-types], need to be augmented with this
Layer 1. grouping for the usage of Layer 1.
otn-path-bandwidth: otn-path-bandwidth:
This grouping defines the path bandwidth information and could be This grouping defines the path bandwidth information and could be
used in OTN topology model for bandwidth representation. All the used in OTN topology model for bandwidth representation. All the
bandwidth related sections in generic topology module, ietf-te- bandwidth related sections in generic module,
topology, need to be augmented with this grouping for the usage of [I-D.ietf-teas-yang-te-types], need to be augmented with this
Layer 1. This grouping is also applicable to set up the OTN tunnel. grouping for the usage of Layer 1. This grouping is also applicable
to set up the OTN tunnel.
otn-label-restriction and otn-label-step: otn-label-range-info and otn-label-step:
These groupings are used for the augmentation of OTN label in a These groupings are used for the augmentation of OTN label in a
specific way. specific way.
otn-label-start-end and otn-label-hop: otn-label-start-end and otn-label-hop:
These groupings are used for the augmentation of label for OTN link These groupings are used for the augmentation of label for OTN link
and path respectively. and path respectively.
optical-interface-func: optical-interface-func:
skipping to change at page 5, line 28 skipping to change at page 5, line 28
are numbered from 1 to 4095, although the actual maximum values are numbered from 1 to 4095, although the actual maximum values
depend on the type of server layer ODU. For example, a server layer depend on the type of server layer ODU. For example, a server layer
ODU4 provides 80 time slots (numbered from 1 to 80) and the TPN ODU4 provides 80 time slots (numbered from 1 to 80) and the TPN
values can be any number from 1 to 80. values can be any number from 1 to 80.
The OTN Label Range represents the values for the TPN and TS that are The OTN Label Range represents the values for the TPN and TS that are
available for ODUk LSPs to be setup over a given OTN Link. available for ODUk LSPs to be setup over a given OTN Link.
The OTN Label Range is defined by the label-restriction list, defined The OTN Label Range is defined by the label-restriction list, defined
in [I-D.ietf-teas-yang-te-types], which, for OTN, should be augmented in [I-D.ietf-teas-yang-te-types], which, for OTN, should be augmented
using the otn-label-restriction grouping. using the otn-label-range-info grouping.
Each entry in the label-restriction list represents either the range Each entry in the label-restriction list represents either the range
of the available TPN values or the range of the available TS values: of the available TPN values or the range of the available TS values:
the range-type attribute defines the type of range for each entry of the range-type attribute in the otn-label-range-info grouping defines
the list. the type of range for each entry of the list.
Each entry of the label-restriction list, as defined in Each entry of the label-restriction list, as defined in
[I-D.ietf-teas-yang-te-types], defines a label-start, a label-end, a [I-D.ietf-teas-yang-te-types], defines a label-start, a label-end, a
label-step and a range-bitmap. The label-start and label-end label-step and a range-bitmap. The label-start and label-end
definitions for OTN should be augmented using the otn-link-label definitions for OTN should be augmented using the otn-label-start-end
grouping. The label-step definition for OTN should be augmented grouping. The label-step definition for OTN should be augmented
using the otn-label-step grouping. It is expected that the otn- using the otn-label-step grouping. It is expected that the otn-
label-step will always be equal to its default value (i.e., 1). label-step will always be equal to its default value (i.e., 1).
As described in [RFC7139], in some cases, the TPN assignment rules is As described in [RFC7139], in some cases, the TPN assignment rules is
flexible (e.g., ODU4 Link) while in other cases the TPN assignment flexible (e.g., ODU4 Link) while in other cases the TPN assignment
rules are fixed (e.g., ODU1 Link). In the latter case, only the TS rules are fixed (e.g., ODU1 Link). In the former case, both TPN and
range is reported: not reporting the TPN range means that the TPN TS ranges are reported, while in the latter case, the TPN range is
shall be set equal to the TS number assigned to the ODUk LSP. not reported to indicate that the TPN shall be set equal to the TS
number assigned to the ODUk LSP.
As described in [RFC7139], in some cases, the TPN assignment rules As described in [RFC7139], in some cases, the TPN assignment rules
depends on the TS Granularity (e.g., ODU2 or ODU3 Links). Different depends on the TS Granularity (e.g., ODU2 or ODU3 Links). Different
entries in the label-restriction list will report different TPN entries in the label-restriction list will report different TPN
ranges for each TS granularity supported by the link, as indicated by ranges for each TS granularity supported by the link, as indicated by
the tsg attribute. the tsg attribute in the otn-label-range-info grouping.
As described in [RFC7139], in some cases, the TPN ranges are As described in [RFC7139], in some cases, the TPN ranges are
different for different types of ODUk LSPs. For example, on an ODU2 different for different types of ODUk LSPs. For example, on an ODU2
Link with 1,25G TS granularity, there is TPN range 1-4 for ODU1 and Link with 1,25G TS granularity, there is TPN range 1-4 for ODU1 and
another TPN range 1-8 in common for ODU0 and ODUflex. Different another TPN range 1-8 in common for ODU0 and ODUflex. Different
entries in the label-restriction list will report different TPN entries in the label-restriction list will report different TPN
ranges for different set of ODUk types, as indicated by the odu-type- ranges for different set of ODUk types, as indicated by the odu-type-
list . list in the otn-label-range-info grouping.
5. YANG Code for Layer1 Types 5. YANG Code for Layer1 Types
<CODE BEGINS>file "ietf-layer1-types@2019-11-01.yang" <CODE BEGINS>file "ietf-layer1-types@2019-12-05.yang"
module ietf-layer1-types { module ietf-layer1-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-layer1-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-layer1-types";
prefix "layer1-types"; prefix "layer1-types";
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: Haomian Zheng Editor: Haomian Zheng
<mailto:zhenghaomian@huawei.com> <mailto:zhenghaomian@huawei.com>
Editor: Italo Busi Editor: Italo Busi
<mailto:Italo.Busi@huawei.com>"; <mailto:Italo.Busi@huawei.com>";
description description
"This module defines Layer 1 types. The model fully conforms "This module defines Layer 1 types. The model fully conforms
to the Network Management Datastore Architecture (NMDA). to the Network Management Datastore Architecture (NMDA).
Copyright (c) 2018 IETF Trust and the persons Copyright (c) 2019 IETF Trust and the persons
identified as authors of the code. All rights reserved. identified as 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 License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://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 "2019-11-01" { revision "2019-12-05" {
description description
"Initial Version"; "Initial Version";
reference reference
"RFC XXXX: A YANG Data Model for Layer 1 Types"; "RFC XXXX: A YANG Data Model for Layer 1 Types";
// RFC Ed.: replace XXXX with actual RFC number, update date // RFC Ed.: replace XXXX with actual RFC number, update date
// information and remove this note // information and remove this note
} }
identity tributary-slot-granularity { identity tributary-slot-granularity {
description description
skipping to change at page 7, line 46 skipping to change at page 7, line 46
} }
identity odu-type { identity odu-type {
description description
"Base identity for protocol framing used by tributary signals."; "Base identity for protocol framing used by tributary signals.";
} }
identity ODU0 { identity ODU0 {
base odu-type; base odu-type;
description description
"ODU0 protocol (1.24G), RFC7139/ITU-T G.709, as standard track."; "ODU0 protocol (1.24G), RFC7139/ITU-T G.709, which is
categorized as standards track .";
} }
identity ODU1 { identity ODU1 {
base odu-type; base odu-type;
description description
"ODU1 protocol (2.49G), RFC7139/ITU-T G.709, as standard track."; "ODU1 protocol (2.49G), RFC7139/ITU-T G.709, which is
categorized as standards track .";
} }
identity ODU1e { identity ODU1e {
base odu-type; base odu-type;
description description
"ODU1e protocol (10.35G), RFC7963/ITU-T G.sup43, as informational."; "ODU1e protocol (10.35G), RFC7963/ITU-T G.sup43, which is
categorized as informational.";
} }
identity ODU2 { identity ODU2 {
base odu-type; base odu-type;
description description
"ODU2 protocol (10.03G), RFC7139/ITU-T G.709, as standard track."; "ODU2 protocol (10.03G), RFC7139/ITU-T G.709, which is
categorized as standards track .";
} }
identity ODU2e { identity ODU2e {
base odu-type; base odu-type;
description description
"ODU2e protocol (10.39G), RFC7139/ITU-T G.709, as standard track."; "ODU2e protocol (10.39G), RFC7139/ITU-T G.709, which is
categorized as standards track .";
} }
identity ODU3 { identity ODU3 {
base odu-type; base odu-type;
description description
"ODU3 protocol (40.31G), RFC7139/ITU-T G.709, as standard track."; "ODU3 protocol (40.31G), RFC7139/ITU-T G.709, which is
categorized as standards track .";
} }
identity ODU3e1 { identity ODU3e1 {
base odu-type; base odu-type;
description description
"ODU3e1 protocol (41.77G), RFC7963/ITU-T G.sup43, as informational."; "ODU3e1 protocol (41.77G), RFC7963/ITU-T G.sup43, which is
categorized as informational.";
} }
identity ODU3e2 { identity ODU3e2 {
base odu-type; base odu-type;
description description
"ODU3e2 protocol (41.78G), RFC7963/ITU-T G.sup43, as informational."; "ODU3e2 protocol (41.78G), RFC7963/ITU-T G.sup43, which is
categorized as informational.";
} }
identity ODU4 { identity ODU4 {
base odu-type; base odu-type;
description description
"ODU4 protocol (104.79G), RFC7139/ITU-T G.709, as standard track."; "ODU4 protocol (104.79G), RFC7139/ITU-T G.709, which is
categorized as standards track .";
} }
identity ODUFlex-cbr { identity ODUFlex-cbr {
base odu-type; base odu-type;
description description
"ODU Flex CBR protocol for transporting constant bit rate "ODU Flex CBR protocol for transporting constant bit rate
signal"; signal";
} }
identity ODUFlex-gfp { identity ODUFlex-gfp {
skipping to change at page 13, line 11 skipping to change at page 13, line 20
} }
leaf number { leaf number {
type uint16; type uint16;
description "Number of ODUs"; description "Number of ODUs";
} }
} }
} }
grouping otn-path-bandwidth { grouping otn-path-bandwidth {
description description
"path bandwidth attributes for OTN"; "path bandwidth attributes for OTN";
leaf odu-type { leaf odu-type {
type identityref { type identityref {
base layer1-types:odu-type; base layer1-types:odu-type;
} }
description "ODU type"; description "ODU type";
} }
} }
grouping otn-label-range-info { grouping otn-label-range-info {
description "label range information for OTN"; description "label range information for OTN";
skipping to change at page 13, line 33 skipping to change at page 13, line 42
type identityref { type identityref {
base layer1-types:otn-label-range-type; base layer1-types:otn-label-range-type;
} }
description "type for range"; description "type for range";
} }
leaf tsg { leaf tsg {
type identityref { type identityref {
base layer1-types:tributary-slot-granularity; base layer1-types:tributary-slot-granularity;
} }
description description
"Tributary slot granularity."; "Tributary slot granularity.";
reference reference
"G.709/Y.1331, February 2016: Interfaces for the "G.709/Y.1331, February 2016: Interfaces for the
Optical Transport Network (OTN)"; Optical Transport Network (OTN)";
} }
leaf-list odu-type-list { leaf-list odu-type-list {
type identityref { type identityref {
base odu-type; base odu-type;
} }
description description
"List of ODU types to which the label range applies. "List of ODU types to which the label range applies.
Empty odu-type-list means all the ODU types are applicable
per label range. "; Empty odu-type-list means all the ODU types are applicable
per label range. ";
} }
leaf priority { leaf priority {
type uint8; type uint8;
description "priority."; description "priority.";
} }
} }
grouping otn-label-start-end { grouping otn-label-start-end {
description description
"The OTN label-start or label-end used to specify an OTN label range."; "The OTN label-start or label-end used to specify an OTN label
range.";
choice otn-label-type { choice otn-label-type {
description description
"OTN label range type, either TPN range or TS range"; "OTN label range type, either TPN range or TS range";
case tributary-port { case tributary-port {
leaf tpn { leaf tpn {
type uint16 { type uint16 {
range "1..4095"; range "1..4095";
} }
description description
"Tributary Port Number. Applicable in case of mux services."; "Tributary Port Number applicable in case of mux services.";
reference reference
"RFC7139: GMPLS Signaling Extensions for Control of Evolving "RFC7139: GMPLS Signaling Extensions for Control of Evolving
G.709 Optical Transport Networks."; G.709 Optical Transport Networks.";
} }
} }
case tributary-slot { case tributary-slot {
leaf ts { leaf ts {
type uint16 { type uint16 {
range "1..4095"; range "1..4095";
} }
description description
"Tributary Slot Number. Applicable in case of mux services."; "Tributary Slot Number applicable in case of mux services.";
reference reference
"RFC7139: GMPLS Signaling Extensions for Control of Evolving "RFC7139: GMPLS Signaling Extensions for Control of Evolving
G.709 Optical Transport Networks."; G.709 Optical Transport Networks.";
} }
} }
} }
} }
grouping otn-label-hop { grouping otn-label-hop {
description "label information for OTN, for label-hop"; description "label information for OTN, for label-hop";
skipping to change at page 14, line 42 skipping to change at page 15, line 4
} }
} }
} }
} }
grouping otn-label-hop { grouping otn-label-hop {
description "label information for OTN, for label-hop"; description "label information for OTN, for label-hop";
leaf tpn { leaf tpn {
type uint16 { type uint16 {
range "1..4095"; range "1..4095";
} }
description description
"Tributary Port Number. Applicable in case of mux services."; "Tributary Port Number applicable in case of mux services.";
reference reference
"RFC7139: GMPLS Signaling Extensions for Control of Evolving "RFC7139: GMPLS Signaling Extensions for Control of Evolving
G.709 Optical Transport Networks."; G.709 Optical Transport Networks.";
} }
leaf tsg { leaf tsg {
type identityref { type identityref {
base layer1-types:tributary-slot-granularity; base layer1-types:tributary-slot-granularity;
} }
description "Tributary slot granularity."; description "Tributary slot granularity.";
reference reference
"G.709/Y.1331, February 2016: Interfaces for the "G.709/Y.1331, February 2016: Interfaces for the
Optical Transport Network (OTN)"; Optical Transport Network (OTN)";
} }
leaf ts-list { leaf ts-list {
type string { type string {
pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?" pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?"
+ "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)"; + "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)";
skipping to change at page 16, line 23 skipping to change at page 16, line 33
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 ETH-1000X-PCS-36 { identity ETH-1000X-PCS-36 {
base "coding-func"; base "coding-func";
description description
"PCS clause 36 coding function that corresponds to "PCS clause 36 coding function that corresponds to
1000BASE-X"; 1000BASE-X";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
identity ETH-10GW-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 "PCS clause 49 and WIS clause 50 coding func that
corresponds to 10GBASE-W (WAN PHY)"; corresponds to 10GBASE-W (WAN PHY)";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
identity ETH-10GR-PCS-49 { identity ETH-10GR-PCS-49 {
base "coding-func"; base "coding-func";
description description
"PCS clause 49 coding function that corresponds to "PCS clause 49 coding function that corresponds to
10GBASE-R (LAN PHY)"; 10GBASE-R (LAN PHY)";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
identity ETH-40GR-PCS-82 { identity ETH-40GR-PCS-82 {
base "coding-func"; base "coding-func";
description description
"PCS clause 82 coding function that corresponds to "PCS clause 82 coding function that corresponds to
40GBASE-R"; 40GBASE-R";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
identity ETH-100GR-PCS-82 { identity ETH-100GR-PCS-82 {
base "coding-func"; base "coding-func";
description description
"PCS clause 82 coding function that corresponds to "PCS clause 82 coding function that corresponds to
100GBASE-R"; 100GBASE-R";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
identity optical-interface-func { identity optical-interface-func {
description description
"base identity from which optical-interface-function is "base identity from which optical-interface-function is
derived."; 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 "SX-PMD-clause-38 Optical Interface function for
1000BASE-X PCS-36"; 1000BASE-X PCS-36";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
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 "LX-PMD-clause-38 Optical Interface function for
1000BASE-X PCS-36"; 1000BASE-X PCS-36";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
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 "LX10-PMD-clause-59 Optical Interface function for
1000BASE-X PCS-36"; 1000BASE-X PCS-36";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
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 "BX10-PMD-clause-59 Optical Interface function for
1000BASE-X PCS-36"; 1000BASE-X PCS-36";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
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 "LW-PMD-clause-52 Optical Interface function for
10GBASE-W PCS-49-WIS-50"; 10GBASE-W PCS-49-WIS-50";
reference "MEF63: Subscriber Layer 1 Service Attributes";
reference "MEF63 & IEEE802.3";
} }
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 "EW-PMD-clause-52 Optical Interface function for
10GBASE-W PCS-49-WIS-50"; 10GBASE-W PCS-49-WIS-50";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
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 "LR-PMD-clause-52 Optical Interface function for
10GBASE-R PCS-49"; 10GBASE-R PCS-49";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
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 "ER-PMD-clause-52 Optical Interface function for
10GBASE-R PCS-49"; 10GBASE-R PCS-49";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
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 "LR4-PMD-clause-87 Optical Interface function for
40GBASE-R PCS-82"; 40GBASE-R PCS-82";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
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 "ER4-PMD-clause-87 Optical Interface function for
40GBASE-R PCS-82"; 40GBASE-R PCS-82";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
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 "FR-PMD-clause-89 Optical Interface function for
40GBASE-R PCS-82"; 40GBASE-R PCS-82";
reference "MEF63: Subscriber Layer 1 Service Attributes";
reference "MEF63 & IEEE802.3";
} }
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 "LR4-PMD-clause-88 Optical Interface function for
100GBASE-R PCS-82"; 100GBASE-R PCS-82";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
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 for "ER4-PMD-clause-88 Optical Interface function for
100GBASE-R PCS-82"; 100GBASE-R PCS-82";
reference "MEF63 & IEEE802.3"; reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
identity service-performance-metric { identity service-performance-metric {
description description
"list of service-specific performance metric"; "list of service-specific performance metric";
} }
identity One-way-Delay { identity One-way-Delay {
base "service-performance-metric"; base "service-performance-metric";
description "one-way-delay"; description "one-way-delay";
reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
identity One-way-Errored-Second { identity One-way-Errored-Second {
base "service-performance-metric"; base "service-performance-metric";
description "one-way-errored-second"; description "one-way-errored-second";
reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
identity One-way-Severely-Errored-Second { identity One-way-Severely-Errored-Second {
base "service-performance-metric"; base "service-performance-metric";
description "one-way-severely-errored-second"; description "one-way-severely-errored-second";
reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
identity One-way-Unavailable-Second { identity One-way-Unavailable-Second {
base "service-performance-metric"; base "service-performance-metric";
description "one-way-unavailable-second"; description "one-way-unavailable-second";
reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
identity One-way-Availability { identity One-way-Availability {
base "service-performance-metric"; base "service-performance-metric";
description "one-way-availability"; description "one-way-availability";
reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
identity network-performance-metric { identity network-performance-metric {
description "list of network-specific performance metric"; description "list of network-specific performance metric";
reference "MEF63: Subscriber Layer 1 Service Attributes";
} }
} }
<CODE ENDS> <CODE ENDS>
6. Security Considerations 6. Security Considerations
The YANG module specified in this document defines a schema for data The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocols such that is designed to be accessed via network management protocols such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
skipping to change at page 21, line 15 skipping to change at page 21, line 30
This document registers following YANG modules in the YANG Module This document registers following YANG modules in the YANG Module
Names registry [RFC7950]. Names registry [RFC7950].
name: ietf-layer1-types name: ietf-layer1-types
namespace: urn:ietf:params:xml:ns:yang:ietf-otn-types namespace: urn:ietf:params:xml:ns:yang:ietf-otn-types
prefix: layer1-types prefix: layer1-types
reference: RFC XXXX reference: RFC XXXX
8. Acknowledgements 8. Acknowledgements
TBD. The authors and the working group give their sincere thanks for
Robert Wilton for the YANG doctor review, and Tom Petch for his
comments during the model and document development.
9. Contributors 9. Contributors
Dieter Beller Dieter Beller
Nokia Nokia
Email: dieter.beller@nokia.com Email: dieter.beller@nokia.com
Sergio Belotti Sergio Belotti
Nokia Nokia
Email: sergio.belotti@nokia.com Email: sergio.belotti@nokia.com
Yanlei Zheng Yanlei Zheng
China Unicom China Unicom
Email: zhengyl@dimpt.com Email: zhengyanlei@chinaunicom.cn
Aihua Guo Aihua Guo
Huawei Technologies Futurewei Technologies
Email: aihuaguo@huawei.com Email: aihuaguo@futurewei.com
Young Lee Young Lee
Huawei Technologies Sung Kyun Kwan University
Email: leeyoung@huawei.com Email: younglee.tx@gmail.com
Lei Wang Lei Wang
China Mobile China Mobile
Email: wangleiyj@chinamobile.com Email: wangleiyj@chinamobile.com
Oscar Gonzalez de Dios Oscar Gonzalez de Dios
Telefonica Telefonica
Email: oscar.gonzalezdedios@telefonica.com Email: oscar.gonzalezdedios@telefonica.com
Xufeng Liu Xufeng Liu
skipping to change at page 22, line 4 skipping to change at page 22, line 23
China Mobile China Mobile
Email: wangleiyj@chinamobile.com Email: wangleiyj@chinamobile.com
Oscar Gonzalez de Dios Oscar Gonzalez de Dios
Telefonica Telefonica
Email: oscar.gonzalezdedios@telefonica.com Email: oscar.gonzalezdedios@telefonica.com
Xufeng Liu Xufeng Liu
Volta Networks Volta Networks
Email: xufeng.liu.ietf@gmail.com Email: xufeng.liu.ietf@gmail.com
Yunbin Xu Yunbin Xu
CAICT CAICT
Email: xuyunbin@ritt.com Email: xuyunbin@caict.ac.cn
Anurag Sharma Anurag Sharma
Google Google
Email: ansha@google.com Email: ansha@google.com
Rajan Rao Rajan Rao
Infinera Infinera
Email: rrao@infinera.com Email: rrao@infinera.com
Victor Lopez Victor Lopez
skipping to change at page 22, line 31 skipping to change at page 22, line 51
China Mobile China Mobile
Email: liyunbo@chinamobile.com Email: liyunbo@chinamobile.com
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.ietf-teas-yang-te-types] [I-D.ietf-teas-yang-te-types]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"Traffic Engineering Common YANG Types", draft-ietf-teas- "Traffic Engineering Common YANG Types", draft-ietf-teas-
yang-te-types-11 (work in progress), October 2019. yang-te-types-13 (work in progress), November 2019.
[ITU-Tg709]
International Telecommunication Union, "Interfaces for the
optical transport network", ITU-T G.709, June 2016.
[ITU-Tgsup43]
International Telecommunication Union, "Transport of IEEE
10GBASE-R in optical transport networks (OTN)",
ITU-T G.sup43, February 2011.
[MEF63] Metro Ethernet Forum, "Subscriber Layer1 Service [MEF63] Metro Ethernet Forum, "Subscriber Layer1 Service
Attributes Technical Specification", MEF 63, August 2018. Attributes Technical Specification", MEF 63, August 2018.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[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 15 skipping to change at page 23, line 40
[RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D., [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D.,
and K. Pithewan, "GMPLS Signaling Extensions for Control and K. Pithewan, "GMPLS Signaling Extensions for Control
of Evolving G.709 Optical Transport Networks", RFC 7139, of Evolving G.709 Optical Transport Networks", RFC 7139,
DOI 10.17487/RFC7139, March 2014, DOI 10.17487/RFC7139, March 2014,
<https://www.rfc-editor.org/info/rfc7139>. <https://www.rfc-editor.org/info/rfc7139>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC7963] Ali, Z., Bonfanti, A., Hartley, M., and F. Zhang, "RSVP-TE
Extension for Additional Signal Types in G.709 Optical
Transport Networks (OTNs)", RFC 7963,
DOI 10.17487/RFC7963, August 2016,
<https://www.rfc-editor.org/info/rfc7963>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341, Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018, DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>. <https://www.rfc-editor.org/info/rfc8341>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
skipping to change at page 23, line 42 skipping to change at page 24, line 28
10.2. Informative References 10.2. Informative References
[I-D.ietf-ccamp-l1csm-yang] [I-D.ietf-ccamp-l1csm-yang]
Lee, Y., Lee, K., Zheng, H., Dhody, D., Dios, O., and D. Lee, Y., Lee, K., Zheng, H., Dhody, D., Dios, O., and D.
Ceccarelli, "A YANG Data Model for L1 Connectivity Service Ceccarelli, "A YANG Data Model for L1 Connectivity Service
Model (L1CSM)", draft-ietf-ccamp-l1csm-yang-10 (work in Model (L1CSM)", draft-ietf-ccamp-l1csm-yang-10 (work in
progress), September 2019. progress), September 2019.
[I-D.ietf-ccamp-otn-topo-yang] [I-D.ietf-ccamp-otn-topo-yang]
Zheng, H., Guo, A., Busi, I., Sharma, A., Liu, X., Zheng, H., Busi, I., Liu, X., Belotti, S., and O. Dios, "A
Belotti, S., Xu, Y., Wang, L., and O. Dios, "A YANG Data YANG Data Model for Optical Transport Network Topology",
Model for Optical Transport Network Topology", draft-ietf- draft-ietf-ccamp-otn-topo-yang-09 (work in progress),
ccamp-otn-topo-yang-08 (work in progress), September 2019. November 2019.
[I-D.ietf-ccamp-otn-tunnel-model] [I-D.ietf-ccamp-otn-tunnel-model]
Zheng, H., Busi, I., Belotti, S., Lopezalvarez, V., and Y. Zheng, H., Busi, I., Belotti, S., Lopezalvarez, V., and Y.
Xu, "OTN Tunnel YANG Model", draft-ietf-ccamp-otn-tunnel- Xu, "OTN Tunnel YANG Model", draft-ietf-ccamp-otn-tunnel-
model-08 (work in progress), October 2019. model-09 (work in progress), November 2019.
[RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D. [RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D.
Ceccarelli, "Framework for GMPLS and PCE Control of G.709 Ceccarelli, "Framework for GMPLS and PCE Control of G.709
Optical Transport Networks", RFC 7062, Optical Transport Networks", RFC 7062,
DOI 10.17487/RFC7062, November 2013, DOI 10.17487/RFC7062, November 2013,
<https://www.rfc-editor.org/info/rfc7062>. <https://www.rfc-editor.org/info/rfc7062>.
[RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and
J. Drake, "Traffic Engineering Extensions to OSPF for J. Drake, "Traffic Engineering Extensions to OSPF for
GMPLS Control of Evolving G.709 Optical Transport GMPLS Control of Evolving G.709 Optical Transport
 End of changes. 77 change blocks. 
90 lines changed or deleted 129 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/