draft-ietf-ccamp-layer1-types-01.txt   draft-ietf-ccamp-layer1-types-02.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: January 9, 2020 July 8, 2019 Expires: March 12, 2020 September 9, 2019
A YANG Data Model for Layer 1 Types A YANG Data Model for Layer 1 Types
draft-ietf-ccamp-layer1-types-01 draft-ietf-ccamp-layer1-types-02
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 January 9, 2020. This Internet-Draft will expire on March 12, 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 13 skipping to change at page 2, line 13
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
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
5. OTN Tunnel YANG Code . . . . . . . . . . . . . . . . . . . . 5 5. YANG Code for Layer1 Types . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 18 6. Security Considerations . . . . . . . . . . . . . . . . . . . 19
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
10.1. Normative References . . . . . . . . . . . . . . . . . . 20 10.1. Normative References . . . . . . . . . . . . . . . . . . 21
10.2. Informative References . . . . . . . . . . . . . . . . . 21 10.2. Informative References . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
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 optical networks.
Typical L1 network, the Optical Transport Networking, was specified Typical L1 network, the Optical Transport Networking, was specified
in [RFC7062]. Corresponding routing and signaling protocol have been in [RFC7062]. Corresponding routing and signaling protocol have been
skipping to change at page 5, line 5 skipping to change at page 5, line 5
The optical interface function is specified in [MEF63]. This The optical interface function is specified in [MEF63]. This
grouping describes the functionality which encodes bits for grouping describes the functionality which encodes bits for
transmission and the corresponding decode upon reception. transmission and the corresponding decode upon reception.
service-performance-metric: service-performance-metric:
The service performance metric is a quantitative characterization of The service performance metric is a quantitative characterization of
Layer 1 characteristic information delivery quality experienced by Layer 1 characteristic information delivery quality experienced by
the Layer 1 subscriber. the Layer 1 subscriber.
5. OTN Tunnel YANG Code 5. YANG Code for Layer1 Types
<CODE BEGINS>file "ietf-layer1-types@2019-07-08.yang" <CODE BEGINS>file "ietf-layer1-types@2019-09-09.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."; "This module defines Layer 1 types.";
revision "2019-07-07" { revision "2019-09-09" {
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 6, line 22 skipping to change at page 6, line 22
} }
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, standard track."; "ODU0 protocol (1.24G), RFC7139/ITU-T G.709, as standard track.";
} }
identity ODU1 { identity ODU1 {
base odu-type; base odu-type;
description description
"ODU1 protocol (2.49G), RFC7139/ITU-T G.709, standard track."; "ODU1 protocol (2.49G), RFC7139/ITU-T G.709, as standard track.";
} }
identity ODU1e { identity ODU1e {
base odu-type; base odu-type;
description description
"ODU1e protocol (10.35G), RFC7963/ITU-T G.sup43, informational."; "ODU1e protocol (10.35G), RFC7963/ITU-T G.sup43, as informational.";
} }
identity ODU2 { identity ODU2 {
base odu-type; base odu-type;
description description
"ODU2 protocol (10.03G), RFC7139/ITU-T G.709, standard track."; "ODU2 protocol (10.03G), RFC7139/ITU-T G.709, as standard track.";
} }
identity ODU2e { identity ODU2e {
base odu-type; base odu-type;
description description
"ODU2e protocol (10.39G), RFC7139/ITU-T G.709, standard track."; "ODU2e protocol (10.39G), RFC7139/ITU-T G.709, as standard track.";
} }
identity ODU3 { identity ODU3 {
base odu-type; base odu-type;
description description
"ODU3 protocol (40.31G), RFC7139/ITU-T G.709, standard track."; "ODU3 protocol (40.31G), RFC7139/ITU-T G.709, as standard track.";
} }
identity ODU3e1 { identity ODU3e1 {
base odu-type; base odu-type;
description description
"ODU3e1 protocol (41.77G), RFC7963/ITU-T G.sup43, informational."; "ODU3e1 protocol (41.77G), RFC7963/ITU-T G.sup43, as informational.";
} }
identity ODU3e2 { identity ODU3e2 {
base odu-type; base odu-type;
description description
"ODU3e2 protocol (41.78G), RFC7963/ITU-T G.sup43, informational."; "ODU3e2 protocol (41.78G), RFC7963/ITU-T G.sup43, as informational.";
} }
identity ODU4 { identity ODU4 {
base odu-type; base odu-type;
description description
"ODU4 protocol (104.79G), RFC7139/ITU-T G.709, standard track."; "ODU4 protocol (104.79G), RFC7139/ITU-T G.709, as standard 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 12, line 44 skipping to change at page 12, line 44
description "link label information for OTN, for label-start/end"; description "link label information for OTN, for label-start/end";
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 for 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 for 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.";
} }
} }
} }
} }
// Editor Notes: following groupings are used in both otn topology // Editor Notes: following groupings are used in both otn topology
// and tunnel model, so suggest to be kept in the types. // and tunnel model, so suggest to be kept in the types.
skipping to change at page 14, line 43 skipping to change at page 14, line 43
Tributary Slot Number."; Tributary Slot Number.";
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.";
} }
} }
} }
} }
// Editor Notes: to be reviewed for the following coding functions. // Editor Notes: to be reviewed for the following coding functions.
identity coding-func {
description
"base identity from which coding func is derived.";
}
identity ETH-1000X-PCS-36 {
base "coding-func";
description
"PCS clause 36 coding function that corresponds to
1000BASE-X";
reference "MEF63 & IEEE802.3";
}
identity ETH-10GW-PCS-49-WIS-50 {
base "coding-func";
description
"PCS clause 49 and WIS clause 50 coding func that
corresponds to 10GBASE-W (WAN PHY)";
reference "MEF63 & IEEE802.3";
}
identity ETH-10GR-PCS-49 {
base "coding-func";
description
"PCS clause 49 coding function that corresponds to
10GBASE-R (LAN PHY)";
reference "MEF63 & IEEE802.3";
}
identity ETH-40GR-PCS-82 {
base "coding-func";
description
"PCS clause 82 coding function that corresponds to
40GBASE-R";
reference "MEF63 & IEEE802.3";
}
identity ETH-100GR-PCS-82 {
base "coding-func";
description
"PCS clause 82 coding function that corresponds to
100GBASE-R";
reference "MEF63 & IEEE802.3";
}
/* 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 "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
skipping to change at page 20, line 23 skipping to change at page 21, line 29
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-10 (work in progress), July 2019. yang-te-types-10 (work in progress), July 2019.
[MEF63] M, EF., "Subscriber Layer1 Service Attributes Technical [MEF63] Metro Ethernet Forum, "Subscriber Layer1 Service
Specification", MEF63 , 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
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
skipping to change at page 21, line 36 skipping to change at page 22, line 44
[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., Guo, A., Busi, I., Sharma, A., Liu, X.,
Belotti, S., Xu, Y., Wang, L., and O. Dios, "A YANG Data Belotti, S., Xu, Y., Wang, L., and O. Dios, "A YANG Data
Model for Optical Transport Network Topology", draft-ietf- Model for Optical Transport Network Topology", draft-ietf-
ccamp-otn-topo-yang-07 (work in progress), July 2019. ccamp-otn-topo-yang-07 (work in progress), July 2019.
[I-D.ietf-ccamp-otn-tunnel-model] [I-D.ietf-ccamp-otn-tunnel-model]
Zheng, H., Guo, A., Busi, I., Sharma, A., Rao, R., Zheng, H., Guo, A., Busi, I., Sharma, A., Rao, R.,
Belotti, S., Lopezalvarez, V., Li, Y., and Y. Xu, "OTN Belotti, S., Lopezalvarez, V., Li, Y., and Y. Xu, "OTN
Tunnel YANG Model", draft-ietf-ccamp-otn-tunnel-model-06 Tunnel YANG Model", draft-ietf-ccamp-otn-tunnel-model-07
(work in progress), February 2019. (work in progress), July 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. 21 change blocks. 
30 lines changed or deleted 78 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/