< draft-ietf-ccamp-layer1-types-12.txt   draft-ietf-ccamp-layer1-types-13.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: 8 September 2022 7 March 2022 Expires: 10 October 2022 8 April 2022
A YANG Data Model for Layer 1 Types A YANG Data Model for Layer 1 Types
draft-ietf-ccamp-layer1-types-12 draft-ietf-ccamp-layer1-types-13
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 the YANG data modeling language for use with layer 1 networks. in the YANG data modeling language for use with layer 1 networks.
These derived common types and groupings are intended to be imported These derived common types and groupings are intended to be imported
by modules that specify OTN networks, such as topology, tunnel, by modules that specify OTN networks, such as 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 8 September 2022. This Internet-Draft will expire on 10 October 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 17 skipping to change at page 2, line 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology and Notations . . . . . . . . . . . . . . . . . . 3 2. Terminology and Notations . . . . . . . . . . . . . . . . . . 3
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. OTN Label and Label Range . . . . . . . . . . . . . . . . 6 4.3. OTN Label and Label Range . . . . . . . . . . . . . . . . 6
4.4. ODUflex . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.4. ODUflex . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.4.1. Resizable ODUflex . . . . . . . . . . . . . . . . . . 10 4.4.1. Resizable ODUflex . . . . . . . . . . . . . . . . . . 10
5. YANG Code for Layer1 Types . . . . . . . . . . . . . . . . . 10 5. YANG Code for Layer1 Types . . . . . . . . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 35 6. Security Considerations . . . . . . . . . . . . . . . . . . . 36
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 36 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 36 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 37
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 37
10.1. Normative References . . . . . . . . . . . . . . . . . . 37 10.1. Normative References . . . . . . . . . . . . . . . . . . 37
10.2. Informative References . . . . . . . . . . . . . . . . . 39 10.2. Informative References . . . . . . . . . . . . . . . . . 39
Appendix A. Examples of OTN Label Ranges . . . . . . . . . . . . 40 Appendix A. Examples of OTN Label Ranges . . . . . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 47
1. Introduction 1. Introduction
This document specifies common data types for use in YANG [RFC7950] This document specifies common data types, groupings and identities
data models of Layer 1 networks. The derived types and groupings are for use in YANG [RFC7950] data models of Layer 1 networks. The
types applicable to modeling Traffic Engineering (TE) for Layer 1 derived types and groupings are types applicable to modeling Traffic
networks. Engineering (TE) for Layer 1 networks.
The Optical Transport Networking, a typical Layer 1 network, is The Optical Transport Networking, a typical Layer 1 network, is
specified in [RFC7062]. The corresponding routing and signaling specified in [RFC7062]. The corresponding routing and signaling
protocol are specified in [RFC7138] and [RFC7139]. The types and protocol are specified in [RFC7138] and [RFC7139]. The types and
groupings defined in this document are consistent to those documents, groupings defined in this document are consistent to those documents,
and can be imported into other Layer 1 data models, including but not and can be imported into other Layer 1 data models, including but not
limited to, [I-D.ietf-ccamp-otn-topo-yang], limited to, [I-D.ietf-ccamp-otn-topo-yang],
[I-D.ietf-ccamp-otn-tunnel-model], [I-D.ietf-ccamp-otn-tunnel-model],
[I-D.ietf-ccamp-client-signal-yang] and [I-D.ietf-ccamp-l1csm-yang]. [I-D.ietf-ccamp-client-signal-yang] and [I-D.ietf-ccamp-l1csm-yang].
The data model in this draft only defines groupings, typedef and The document is consistent with other specifications, including
identities. There is no configuration or state data as specified in [MEF63] for Layer 1 service attributes, [ITU-Tg709] and [ITU-Tgsup43]
the Network Management Datastore Architecture [RFC8342]. The for OTN data plane definitions.
document is consistent with other specifications, including [MEF63]
for Layer 1 service attributes, [ITU-Tg709] and [ITU-Tgsup43] for OTN The YANG data model in this document only defines groupings, typedef
data plane definitions. and identities and it does not define any configuration or state
data, as specified in the Network Management Datastore Architecture
defined in [RFC8342].
2. Terminology and Notations 2. Terminology and Notations
Refer to [RFC7062] for the key terms used in this document. The Refer to [RFC7062] for the key terms used in this document. 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
are prefixed using the standard prefix associated with the are prefixed using the standard prefix associated with the
corresponding YANG imported modules. corresponding YANG imported modules, as shown in table 1.
+-------------+---------------------------+----------------------+ +-------------+---------------------------+----------------------+
| Prefix | YANG module | Reference | | Prefix | YANG module | Reference |
+-------------+---------------------------+----------------------+ +-------------+---------------------------+----------------------+
| l1-types | ietf-layer1-types | This Document | | l1-types | ietf-layer1-types | This Document |
+-------------+---------------------------+----------------------+ +-------------+---------------------------+----------------------+
Table 1: Prefixes and Corresponding YANG Modules
RFC Editor Note: Please replace XXXX with the number assigned to the
RFC once this draft becomes an RFC.
4. Layer 1 Types Overview 4. Layer 1 Types Overview
4.1. Relationship with other Modules 4.1. Relationship with other Modules
This document defines one YANG module for common Layer 1 types. The This document defines one YANG module for common Layer 1 types. The
aim is to specify common Layer 1 TE types (i.e. typedef, identity, aim is to specify common Layer 1 TE types (i.e. typedef, identity,
grouping) that can be imported by layer 1 specific technology, for grouping) that can be imported by layer 1 specific technology, for
example OTN, in its technology-specific modules, such as topology and example OTN, in its technology-specific modules, such as topology and
tunnels. It is worth noting that the generic traffic-engineering tunnels. It is worth noting that the generic traffic-engineering
skipping to change at page 4, line 5 skipping to change at page 4, line 5
while the OTN-specific attributes, such as odu-type, are specified in while the OTN-specific attributes, such as odu-type, are specified in
ietf-layer1-types in this document. ietf-layer1-types in this document.
4.2. Content in Layer 1 Type Module 4.2. Content in Layer 1 Type Module
The module ietf-layer1-types contains the following YANG reusable The module ietf-layer1-types contains the following YANG reusable
types and groupings: types and groupings:
tributary-slot-granularity: tributary-slot-granularity:
This specifies the granularity of the server layer ODU Link (HO ODUk This specifies the granularity of the time slots used by the server
or ODUCn) supporting a client layer ODU LSP (LO ODUj or ODUk, layer ODU Link (HO ODUk or ODUCn) when supporting client layer ODU
respectively). Three granularities, 1.25G/2.5G/5G, have been LSPs (LO ODUj or ODUk, respectively). Three granularities,
specified. 1.25G/2.5G/5G, have been specified.
odu-type: odu-type:
This specifies the type of ODUk LSP, including the types specified in This specifies the type of ODUk LSP, including the types specified in
[RFC7139] and [RFC7963]. [RFC7139] and [RFC7963].
client-signal: client-signal:
This specifies the client signal types of OTN networks. The initial This specifies the client signal types of OTN networks. The initial
input was the G-PID specified in [RFC7139]. Identities for some of input was the G-PID specified in [RFC7139]. Identities for some of
skipping to change at page 10, line 40 skipping to change at page 10, line 40
These two identities are used to identify whether an ODUflex(GFP,n,k) These two identities are used to identify whether an ODUflex(GFP,n,k)
LSP does or does support the [ITU-Tg7044] hitless resizing LSP does or does support the [ITU-Tg7044] hitless resizing
procedures. They also identify whether an OTN link only supports the procedures. They also identify whether an OTN link only supports the
setup of non-resizable ODUflex LSPs or also supports the setup of setup of non-resizable ODUflex LSPs or also supports the setup of
resizable ODUflex(GFP,n,k) LSP but with different capabilities (e.g., resizable ODUflex(GFP,n,k) LSP but with different capabilities (e.g.,
a lower number of LSPs). a lower number of LSPs).
5. YANG Code for Layer1 Types 5. YANG Code for Layer1 Types
<CODE BEGINS> <CODE BEGINS>
file "ietf-layer1-types@2021-02-19.yang" file "ietf-layer1-types@2022-04-07.yang"
module ietf-layer1-types { module ietf-layer1-types {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-layer1-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-layer1-types";
prefix "l1-types"; prefix "l1-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>
skipping to change at page 11, line 13 skipping to change at page 11, line 13
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) 2021 IETF Trust and the persons Copyright (c) 2022 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 "2021-02-19" { revision "2022-04-07" {
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 Editor: replace XXXX with actual RFC number, update date // RFC Editor: replace XXXX with actual RFC number, update date
// information and remove this note // information and remove this note
} }
/* /*
* Typedefs
*/
typedef otn-tpn {
type uint16 {
range "1..4095";
}
description
"Tributary Port Number for OTN. ";
reference
"RFC7139: GMPLS Signaling Extensions for Control of Evolving
G.709 Optical Transport Networks.";
}
typedef otn-ts {
type uint16 {
range "1..4095";
}
description
"Tributary Slot for OTN. ";
reference
"RFC7139: GMPLS Signaling Extensions for Control of Evolving
G.709 Optical Transport Networks.";
}
typedef otn-label-range-type {
type enumeration {
enum trib-slot {
description
"Defines a range of OTN tributary slots. ";
}
enum trib-port {
description
"Defines a range of OTN tributary ports. ";
}
}
description
"Defines the type of OTN label range: TS or TPN. ";
}
typedef gfp-k {
type enumeration {
enum 2 {
description
"The ODU2.ts rate (1,249,177.230 kbit/s) is used
to compute the rate of an ODUflex(GFP,n,2). ";
}
enum 3 {
description
"The ODU3.ts rate (1,254,470.354 kbit/s) is used
to compute the rate of an ODUflex(GFP,n,3). ";
}
enum 4 {
description
"The ODU4.ts rate (1,301,467.133 kbit/s) is used
to compute the rate of an ODUflex(GFP,n,4). ";
}
}
description
"The ODUk.ts used to compute the rate of an ODUflex(GFP,n,k)";
reference
"ITU-T G.709 v6.0 (06/2020), Table 7-8 and L.7: Interfaces for
the Optical Transport Network (OTN)";
}
typedef flexe-client-rate {
type union {
type uint16;
type enumeration {
enum "10G" {
description
"Represents a 10G FlexE Client signal (s=2)";
}
enum "40G" {
description
"Represents a 40G FlexE Client signal (s=8)";
}
}
}
description
"The FlexE Client signal rate (s x 5,156,250.000 kbit/s)
used to compute the rate of an ODUflex(IMP, s).
Valid values for s are s=2 (10G), s=4 (40G) and
s=5 x n (n x 25G).
In the first two cases an enumeration value
(either 10G or 40G) is used, while in the latter case
the value of n is used";
reference
"ITU-T G.709 v6.0 (06/2020), Table 7-2: Interfaces for the
Optical Transport Network (OTN)";
}
/*
* Identities * Identities
*/ */
identity tributary-slot-granularity { identity tributary-slot-granularity {
description description
"Tributary slot granularity"; "Tributary slot granularity";
reference reference
"ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical "ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical
Transport Network (OTN)"; Transport Network (OTN)";
} }
skipping to change at page 28, line 48 skipping to change at page 27, line 4
} }
identity ER4-PMD-100G { identity ER4-PMD-100G {
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 reference
"MEF63: Subscriber Layer 1 Service Attributes"; "MEF63: Subscriber Layer 1 Service Attributes";
} }
/*
* Typedefs
*/
typedef otn-tpn {
type uint16 {
range "1..4095";
}
description
"Tributary Port Number for OTN. ";
reference
"RFC7139: GMPLS Signaling Extensions for Control of Evolving
G.709 Optical Transport Networks.";
}
typedef otn-ts {
type uint16 {
range "1..4095";
}
description
"Tributary Slot for OTN. ";
reference
"RFC7139: GMPLS Signaling Extensions for Control of Evolving
G.709 Optical Transport Networks.";
}
typedef otn-label-range-type {
type enumeration {
enum trib-slot {
description
"Defines a range of OTN tributary slots. ";
}
enum trib-port {
description
"Defines a range of OTN tributary ports. ";
}
}
description
"Defines the type of OTN label range: TS or TPN. ";
}
typedef gfp-k {
type enumeration {
enum 2 {
description
"The ODU2.ts rate (1,249,177.230 kbit/s) is used
to compute the rate of an ODUflex(GFP,n,2). ";
}
enum 3 {
description
"The ODU3.ts rate (1,254,470.354 kbit/s) is used
to compute the rate of an ODUflex(GFP,n,3). ";
}
enum 4 {
description
"The ODU4.ts rate (1,301,467.133 kbit/s) is used
to compute the rate of an ODUflex(GFP,n,4). ";
}
}
description
"The ODUk.ts used to compute the rate of an ODUflex(GFP,n,k)";
reference
"ITU-T G.709 v6.0 (06/2020), Table 7-8 and L.7: Interfaces for
the Optical Transport Network (OTN)";
}
typedef flexe-client-rate {
type union {
type uint16;
type enumeration {
enum "10G" {
description
"Represents a 10G FlexE Client signal (s=2)";
}
enum "40G" {
description
"Represents a 40G FlexE Client signal (s=8)";
}
}
}
description
"The FlexE Client signal rate (s x 5,156,250.000 kbit/s)
used to compute the rate of an ODUflex(IMP, s).
Valid values for s are s=2 (10G), s=4 (40G) and
s=5 x n (n x 25G).
In the first two cases an enumeration value
(either 10G or 40G) is used, while in the latter case
the value of n is used";
reference
"ITU-T G.709 v6.0 (06/2020), Table 7-2: Interfaces for the
Optical Transport Network (OTN)";
}
/* /*
* Groupings * Groupings
*/ */
grouping otn-link-bandwidth { grouping otn-link-bandwidth {
description description
"Bandwidth attributes for OTN links"; "Bandwidth attributes for OTN links";
list odulist { container otn {
key "odu-type";
description description
"OTN bandwidth definition"; "Bandwidth attributes for OTN links";
leaf odu-type { list odulist {
type identityref { key "odu-type";
base odu-type; description
"OTN bandwidth definition";
leaf odu-type {
type identityref {
base odu-type;
}
description "ODU type";
}
leaf number {
type uint16;
description "Number of ODUs";
} }
description "ODU type";
}
leaf number {
type uint16;
description "Number of ODUs";
} }
} }
} }
grouping otn-path-bandwidth { grouping otn-path-bandwidth {
description description
"Bandwidth attributes for OTN paths."; "Bandwidth attributes for OTN paths.";
container otn { container otn {
description description
"Bandwidth attributes for OTN paths."; "Bandwidth attributes for OTN paths.";
skipping to change at page 31, line 37 skipping to change at page 31, line 41
grouping otn-label-range-info { grouping otn-label-range-info {
description description
"Label range information for OTN. "Label range information for OTN.
This grouping should be used together with the This grouping should be used together with the
otn-label-start-end and otn-label-step groupings to provide otn-label-start-end and otn-label-step groupings to provide
OTN technology-specific label information to the models which OTN technology-specific label information to the models which
use the label-restriction-info grouping defined in the module use the label-restriction-info grouping defined in the module
ietf-te-types."; ietf-te-types.";
leaf range-type { container otn-label-range {
type otn-label-range-type;
description "The type of range (e.g., TPN or TS)
to which the label range applies";
}
leaf tsg {
type identityref {
base tributary-slot-granularity;
}
description description
"Tributary slot granularity (TSG) to which the label range "Label range information for OTN.";
applies. leaf range-type {
type otn-label-range-type;
description "The type of range (e.g., TPN or TS)
to which the label range applies";
}
leaf tsg {
type identityref {
base tributary-slot-granularity;
This leaf shall be present when the range-type is TS. }
description
"Tributary slot granularity (TSG) to which the label range
applies.
This leaf can be omitted when mapping an ODUk over an OTUk This leaf shall be present when the range-type is TS.
Link. In this case the range-type is tpn, with only one
entry (ODUk), and the tpn range has only one value (1)."; This leaf can be omitted when mapping an ODUk over an OTUk
reference Link. In this case the range-type is tpn, with only one
"ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical entry (ODUk), and the tpn range has only one value (1).";
Transport Network (OTN)"; reference
} "ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical
leaf-list odu-type-list { Transport Network (OTN)";
type identityref {
base odu-type;
} }
description leaf-list odu-type-list {
"List of ODU types to which the label range applies. type identityref {
base odu-type;
}
description
"List of ODU types to which the label range applies.
An Empty odu-type-list means that the label range An Empty odu-type-list means that the label range
applies to all the supported ODU types."; applies to all the supported ODU types.";
} }
leaf priority { leaf priority {
type uint8; type uint8;
description description
"Priority in Interface Switching Capability "Priority in Interface Switching Capability
Descriptor (ISCD)."; Descriptor (ISCD).";
reference reference
"RFC4203: OSPF Extensions in Support of Generalized "RFC4203: OSPF Extensions in Support of Generalized
Multi-Protocol Label Switching (GMPLS)"; Multi-Protocol Label Switching (GMPLS)";
}
} }
} }
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 "The OTN label-start or label-end used to specify an OTN label
range. range.
This grouping is dependent on the range-type defined in the This grouping is dependent on the range-type defined in the
otn-label-range-info grouping. otn-label-range-info grouping.
This grouping should be used together with the This grouping should be used together with the
otn-label-range-info and otn-label-step groupings to provide otn-label-range-info and otn-label-step groupings to provide
OTN technology-specific label information to the models which OTN technology-specific label information to the models which
use the label-restriction-info grouping defined in the module use the label-restriction-info grouping defined in the module
ietf-te-types."; ietf-te-types.";
choice range-type { container otn {
description description
"OTN label range type, either TPN range or TS range"; "Label start or label end for OTN.";
case trib-port { choice range-type {
leaf otn-tpn { description
when "../../../range-type = 'trib-port'" { "OTN label range type, either TPN range or TS range";
case trib-port {
leaf tpn {
when "../../../../otn-label-range/range-type =
'trib-port'" {
description
"Valid only when range-type represented by
trib-port";
}
type otn-tpn;
description description
"Valid only when range-type represented by trib-port"; "Tributary Port Number (TPN).";
reference
"RFC7139: GMPLS Signaling Extensions for Control of
Evolving G.709 Optical Transport Networks.";
} }
type otn-tpn;
description
"Tributary Port Number.";
reference
"RFC7139: GMPLS Signaling Extensions for Control of
Evolving G.709 Optical Transport Networks.";
} }
} case trib-slot {
case trib-slot { leaf ts {
leaf otn-ts { when "../../../../otn-label-range/range-type =
when "../../../range-type = 'trib-slot'" { 'trib-slot'" {
description
"Valid only when range-type represented by
trib-slot";
}
type otn-ts;
description description
"Valid only when range-type represented by trib-slot"; "Tributary Slot (TS) number.";
reference
"RFC7139: GMPLS Signaling Extensions for Control of
Evolving G.709 Optical Transport Networks";
} }
type otn-ts;
description
"Tributary Slot Number.";
reference
"RFC7139: GMPLS Signaling Extensions for Control of
Evolving G.709 Optical Transport Networks";
} }
} }
} }
} }
grouping otn-label-hop { grouping otn-label-hop {
description "OTN Label"; description "OTN Label";
reference reference
"RFC7139, section 6: GMPLS Signaling Extensions for Control of "RFC7139, section 6: GMPLS Signaling Extensions for Control of
Evolving G.709 Optical Transport Networks"; Evolving G.709 Optical Transport Networks";
leaf otn-tpn {
type otn-tpn; container otn {
description description
"Tributary Port Number."; "Label hop for OTN.";
reference leaf tpn {
"RFC7139: GMPLS Signaling Extensions for Control of Evolving type otn-tpn;
G.709 Optical Transport Networks."; description
} "Tributary Port Number (TPN).";
leaf tsg { reference
type identityref { "RFC7139: GMPLS Signaling Extensions for Control of
base tributary-slot-granularity; Evolving G.709 Optical Transport Networks.";
} }
description "Tributary slot granularity."; leaf tsg {
reference type identityref {
"ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical base tributary-slot-granularity;
Transport Network (OTN)";
}
leaf ts-list {
type string {
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})?)*)";
} }
description description "Tributary Slot Granularity (TSG).";
"A list of available tributary slots ranging reference
between 1 and 4095. If multiple values or "ITU-T G.709 v6.0 (06/2020): Interfaces for the Optical
ranges are given, they all must be disjoint Transport Network (OTN)";
and must be in ascending order. }
For example 1-20,25,50-1000."; leaf ts-list {
reference type string {
"RFC 7139: GMPLS Signaling Extensions for Control pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?"
of Evolving G.709 Optical Transport Networks"; + "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)";
}
description
"A list of available Tributary Slots (TS) ranging
between 1 and 4095. If multiple values or
ranges are given, they all must be disjoint
and must be in ascending order.
For example 1-20,25,50-1000.";
reference
"RFC 7139: GMPLS Signaling Extensions for Control
of Evolving G.709 Optical Transport Networks";
}
} }
} }
grouping otn-label-step { grouping otn-label-step {
description description
"Label step for OTN. "Label step for OTN.
This grouping is dependent on the range-type defined in the This grouping is dependent on the range-type defined in the
otn-label-range-info grouping. otn-label-range-info grouping.
This grouping should be used together with the This grouping should be used together with the
otn-label-range-info and otn-label-start-end groupings to otn-label-range-info and otn-label-start-end groupings to
provide OTN technology-specific label information to the models provide OTN technology-specific label information to the
which use the label-restriction-info grouping defined in the models which use the label-restriction-info grouping defined
module ietf-te-types."; in the module ietf-te-types.";
choice range-type { container otn {
description description
"OTN label range type, either TPN range or TS range"; "Label step for OTN";
case trib-port { choice range-type {
leaf otn-tpn { description
when "../../range-type = 'trib-port'" { "OTN label range type, either TPN range or TS range";
case trib-port {
leaf tpn {
when "../../../otn-label-range/range-type =
'trib-port'" {
description
"Valid only when range-type represented by
trib-port";
}
type otn-tpn;
description description
"Valid only when range-type represented by trib-port"; "Label step which represents possible increments for
Tributary Port Number (TPN).";
reference
"RFC7139: GMPLS Signaling Extensions for Control of
Evolving G.709 Optical Transport Networks.";
} }
type otn-tpn;
description
"Label step which represents possible increments for
Tributary Port Number.";
reference
"RFC7139: GMPLS Signaling Extensions for Control of
Evolving G.709 Optical Transport Networks.";
} }
} case trib-slot {
case trib-slot { leaf ts {
leaf otn-ts { when "../../../otn-label-range/range-type =
when "../../range-type = 'trib-slot'" { 'trib-slot'" {
description
"Valid only when range-type represented by
trib-slot";
}
type otn-ts;
description description
"Valid only when range-type represented by trib-slot"; "Label step which represents possible increments for
Tributary Slot (TS) number.";
reference
"RFC7139: GMPLS Signaling Extensions for Control of
Evolving G.709 Optical Transport Networks.";
} }
type otn-ts;
description
"Label step which represents possible increments for
Tributary Slot Number.";
reference
"RFC7139: GMPLS Signaling Extensions for Control of
Evolving G.709 Optical Transport Networks.";
} }
} }
} }
} }
} }
<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
skipping to change at page 36, line 22 skipping to change at page 37, line 5
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
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-layer1-types namespace: urn:ietf:params:xml:ns:yang:ietf-layer1-types
prefix: l1-types prefix: l1-types
reference: RFC XXXX reference: RFC XXXX
RFC Editor Note: Please replace XXXX with the number assigned to the
RFC once this draft becomes an RFC.
8. Acknowledgements 8. Acknowledgements
The authors and the working group give their sincere thanks for The authors and the working group give their sincere thanks for
Robert Wilton for the YANG doctor review, and Tom Petch for his Robert Wilton for the YANG doctor review, and Tom Petch for his
comments during the model and document development. comments during the model and document development.
9. Contributors 9. Contributors
Dieter Beller Nokia Email: dieter.beller@nokia.com Dieter Beller Nokia Email: dieter.beller@nokia.com
skipping to change at page 38, line 39 skipping to change at page 39, line 20
[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.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
[RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, [RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"Common YANG Data Types for Traffic Engineering", "Common YANG Data Types for Traffic Engineering",
RFC 8776, DOI 10.17487/RFC8776, June 2020, RFC 8776, DOI 10.17487/RFC8776, June 2020,
<https://www.rfc-editor.org/info/rfc8776>. <https://www.rfc-editor.org/info/rfc8776>.
10.2. Informative References 10.2. Informative References
skipping to change at page 39, line 27 skipping to change at page 40, line 9
Ceccarelli, "A YANG Data Model for L1 Connectivity Service Ceccarelli, "A YANG Data Model for L1 Connectivity Service
Model (L1CSM)", Work in Progress, Internet-Draft, draft- Model (L1CSM)", Work in Progress, Internet-Draft, draft-
ietf-ccamp-l1csm-yang-16, 13 December 2021, ietf-ccamp-l1csm-yang-16, 13 December 2021,
<https://www.ietf.org/archive/id/draft-ietf-ccamp-l1csm- <https://www.ietf.org/archive/id/draft-ietf-ccamp-l1csm-
yang-16.txt>. yang-16.txt>.
[I-D.ietf-ccamp-otn-topo-yang] [I-D.ietf-ccamp-otn-topo-yang]
Zheng, H., Busi, I., Liu, X., Belotti, S., and O. G. D. Zheng, H., Busi, I., Liu, X., Belotti, S., and O. G. D.
Dios, "A YANG Data Model for Optical Transport Network Dios, "A YANG Data Model for Optical Transport Network
Topology", Work in Progress, Internet-Draft, draft-ietf- Topology", Work in Progress, Internet-Draft, draft-ietf-
ccamp-otn-topo-yang-13, 12 July 2021, ccamp-otn-topo-yang-14, 7 March 2022,
<https://www.ietf.org/archive/id/draft-ietf-ccamp-otn- <https://www.ietf.org/archive/id/draft-ietf-ccamp-otn-
topo-yang-13.txt>. topo-yang-14.txt>.
[I-D.ietf-ccamp-otn-tunnel-model] [I-D.ietf-ccamp-otn-tunnel-model]
Zheng, H., Busi, I., Belotti, S., Lopez, V., and Y. Xu, Zheng, H., Busi, I., Belotti, S., Lopez, V., and Y. Xu,
"OTN Tunnel YANG Model", Work in Progress, Internet-Draft, "OTN Tunnel YANG Model", Work in Progress, Internet-Draft,
draft-ietf-ccamp-otn-tunnel-model-14, 12 July 2021, draft-ietf-ccamp-otn-tunnel-model-15, 7 March 2022,
<https://www.ietf.org/archive/id/draft-ietf-ccamp-otn- <https://www.ietf.org/archive/id/draft-ietf-ccamp-otn-
tunnel-model-14.txt>. tunnel-model-15.txt>.
[I-D.ietf-ccamp-transport-nbi-app-statement] [I-D.ietf-ccamp-transport-nbi-app-statement]
Busi, I., King, D., Zheng, H., and Y. Xu, "Transport Busi, I., King, D., Zheng, H., and Y. Xu, "Transport
Northbound Interface Applicability Statement", Work in Northbound Interface Applicability Statement", Work in
Progress, Internet-Draft, draft-ietf-ccamp-transport-nbi- Progress, Internet-Draft, draft-ietf-ccamp-transport-nbi-
app-statement-13, 29 September 2021, app-statement-14, 25 March 2022,
<https://www.ietf.org/archive/id/draft-ietf-ccamp- <https://www.ietf.org/archive/id/draft-ietf-ccamp-
transport-nbi-app-statement-13.txt>. transport-nbi-app-statement-14.txt>.
[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
Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014,
<https://www.rfc-editor.org/info/rfc7138>. <https://www.rfc-editor.org/info/rfc7138>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
[RFC8792] Watsen, K., Auerswald, E., Farrel, A., and Q. Wu, [RFC8792] Watsen, K., Auerswald, E., Farrel, A., and Q. Wu,
"Handling Long Lines in Content of Internet-Drafts and "Handling Long Lines in Content of Internet-Drafts and
RFCs", RFC 8792, DOI 10.17487/RFC8792, June 2020, RFCs", RFC 8792, DOI 10.17487/RFC8792, June 2020,
<https://www.rfc-editor.org/info/rfc8792>. <https://www.rfc-editor.org/info/rfc8792>.
Appendix A. Examples of OTN Label Ranges Appendix A. Examples of OTN Label Ranges
This appendix provides some examples of how the TPN and TS label This appendix provides some examples of how the TPN and TS label
ranges described in Table 3 and Table 4 of [RFC7139] can be ranges described in Table 3 and Table 4 of [RFC7139] can be
represented in YANG using the groupings defined in this document. represented in YANG using the groupings defined in this document.
It also considers the OTUk links in addition to HO-ODUk links. It also considers the OTUk links in addition to HO-ODUk links.
The JSON code examples provided in this appendix provides some The JSON code examples provided in this appendix provides some
embedded comments following the conventions in section 3.2 of embedded comments following the conventions in section 3.2 of
[I-D.ietf-ccamp-transport-nbi-app-statement] and have been folded [I-D.ietf-ccamp-transport-nbi-app-statement] and have been folded
using the tool in [RFC8792]. using the tool in [RFC8792].
========== NOTE: '\\' line wrapping per BCP XXX (RFC XXXX) ========== =============== NOTE: '\\' line wrapping per RFC 8792 ===============
{ {
"examples of label-restrictions for different OTN Links": [ "// examples of label-restrictions for different OTN Links": [
{ {
"// ": "HO-ODU1 or OTU1 Link", "// example": "HO-ODU1 or OTU1 Link",
"label-restrictions": { "label-restrictions": {
"label-restriction": [ "label-restriction": [
{ {
"index ": 1, "index ": 1,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-port", "otn-label-range": {
"// ___NOT-PRESENT___ tsg": "", "range-type": "label-range-trib-port",
"odu-type-list": "[ ODU1 ]", "// not-present tsg": "",
"// ___DEFAULT___ priority": 7, "odu-type-list": "[ ODU1 ]",
"// default priority": 7
},
"// tpn-range": 1, "// tpn-range": 1,
"// ___ COMMENT ___": "Since no TS range and no TSG are \ "// comment": "Since no TS range and no TSG are reported\
\reported for ODU1, the link is an OTU1 Link. TS allocation is not n\ \ for ODU1, the link is an OTU1 Link. TS allocation is not needed an\
\eeded and TPN shall be set to '1' for mapping ODU1 over OTU1. This \ \d TPN shall be set to '1' for mapping ODU1 over OTU1. This entry is\
\entry is not present if the OTN Link is an HO-ODU1 Link." \ not present if the OTN Link is an HO-ODU1 Link."
}, },
{ {
"index ": 2, "index ": 2,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-slot", "otn-label-range": {
"tsg": "tsg-1.25G", "range-type": "label-range-trib-slot",
"odu-type-list": "[ ODU0 ]", "tsg": "tsg-1.25G",
"odu-type-list": "[ ODU0 ]",
"// default priority": 7
},
"// ts-range": "1-2", "// ts-range": "1-2",
"// ___ COMMENT ___": "Since no TPN range is reportd for\ "// comment": "Since no TPN range is reportd for ODU0 wi\
\ ODU0 with 1.25G TSG, the TPN allocation rule is fixed (TPN = TS#) \ \th 1.25G TSG, the TPN allocation rule is fixed (TPN = TS#) for mapp\
\for mapping LO-ODU0 over HO-ODU1 with 1.25G TSG. See Table 4 of [RF\ \ing LO-ODU0 over HO-ODU1 with 1.25G TSG. See Table 4 of [RFC7139]."
\C7139]."
} }
] ]
} }
}, },
{ {
"// ": "HO-ODU2 or OTU2 Link", "// example": "HO-ODU2 or OTU2 Link",
"label-restrictions": { "label-restrictions": {
"label-restriction": [ "label-restriction": [
{ {
"index ": 1, "index ": 1,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-port", "otn-label-range": {
"// ___NOT-PRESENT___ tsg": "", "range-type": "label-range-trib-port",
"odu-type-list": "[ ODU2 ]", "//not-present tsg": "",
"// ___ DEFAULT ___ priority": 7, "odu-type-list": "[ ODU2 ]",
"// default priority": 7
},
"// tpn-range": 1, "// tpn-range": 1,
"// ___ COMMENT ___": "Since no TS range and no TSG are \ "// comment": "Since no TS range and no TSG are reported\
\reported for ODU2, the link is an OTU2 Link. TS allocation is not n\ \ for ODU2, the link is an OTU2 Link. TS allocation is not needed an\
\eeded and TPN shall be set to '1' for mapping ODU2 over OTU2. This \ \d TPN shall be set to '1' for mapping ODU2 over OTU2. This entry is\
\entry is not present if the OTN Link is an HO-ODU2 Link." \ not present if the OTN Link is an HO-ODU2 Link."
}, },
{ {
"index ": 2, "index ": 2,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-slot", "otn-label-range": {
"tsg": "tsg-1.25G", "range-type": "label-range-trib-slot",
"odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ "tsg": "tsg-1.25G",
\ ]", "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, OD\
"// ___ DEFAULT ___ priority": 7, \U1 ]",
"// default priority": 7
},
"// ts-range": "1-8" "// ts-range": "1-8"
}, },
{ {
"index ": 3, "index ": 3,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-port", "otn-label-range": {
"tsg": "tsg-1.25G ", "range-type": "label-range-trib-port",
"odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0 ]", "tsg": "tsg-1.25G ",
"// ___ DEFAULT ___ priority": 7, "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0 ]",
"// default priority": 7
},
"// tpn-range": "1-8", "// tpn-range": "1-8",
"// ___ COMMENT ___": "Since this TPN range is reported \ "// comment": "Since this TPN range is reported for ODUf\
\for ODUflex and ODU0 with 1.25G TSG, the TPN assignment rule is fle\ \lex and ODU0 with 1.25G TSG, the TPN assignment rule is flexible wi\
\xible within a common range for mapping LO-ODUflex and LO-ODU0 over\ \thin a common range for mapping LO-ODUflex and LO-ODU0 over HO-ODU2\
\ HO-ODU2 with 1.25G TSG. See Table 4 of [RFC7139]." \ with 1.25G TSG. See Table 4 of [RFC7139]."
}, },
{ {
"index ": 4, "index ": 4,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-port", "otn-label-range": {
"tsg": "tsg-1.25G", "range-type": "label-range-trib-port",
"odu-type-list": "[ ODU1 ]", "tsg": "tsg-1.25G",
"// ___ DEFAULT ___ priority": 7, "odu-type-list": "[ ODU1 ]",
"// default priority": 7
},
"// tpn-range": "1-4", "// tpn-range": "1-4",
"// ___ COMMENT ___": "Since this TPN range is reported \ "// comment": "Since this TPN range is reported for ODU1\
\for ODU1 with 1.25G TSG, the TPN assignment rule is flexible within\ \ with 1.25G TSG, the TPN assignment rule is flexible within a commo\
\ a common range for mapping LO-ODU1 over HO-ODU2 with 1.25G TSG. Se\ \n range for mapping LO-ODU1 over HO-ODU2 with 1.25G TSG. See Table \
\e Table 4 of [RFC7139]." \4 of [RFC7139]."
}, },
{ {
"index ": 5, "index ": 5,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-slot", "otn-label-range": {
"tsg": "tsg-2.5G", "range-type": "label-range-trib-slot",
"odu-type-list": "[ ODU1 ]", "tsg": "tsg-2.5G",
"// ___ DEFAULT ___ priority": 7, "odu-type-list": "[ ODU1 ]",
"// default priority": 7
},
"// ts-range": "1-4", "// ts-range": "1-4",
"// ___ COMMENT ___": "Since no TPN range is reported fo\ "// comment": "Since no TPN range is reported for ODU1 w\
\r ODU1 with 2.5G TSG, the TPN allocation rule is fixed (TPN = TS#) \ \ith 2.5G TSG, the TPN allocation rule is fixed (TPN = TS#) for mapp\
\for mapping LO-ODU1 over HO-ODU2 with 2.5G TSG. See Table 3 of [RFC\ \ing LO-ODU1 over HO-ODU2 with 2.5G TSG. See Table 3 of [RFC7139]."
\7139]."
} }
] ]
} }
}, },
{ {
"// ": "HO-ODU3 or OTU3 Link", "// example": "HO-ODU3 or OTU3 Link",
"label-restrictions": { "label-restrictions": {
"label-restriction": [ "label-restriction": [
{ {
"index ": 1, "index ": 1,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-port", "otn-label-range": {
"// ___NOT-PRESENT___ tsg": "", "range-type": "label-range-trib-port",
"odu-type-list": "[ ODU3 ]", "//not-present tsg": "",
"// ___ DEFAULT ___ priority": 7, "odu-type-list": "[ ODU3 ]",
"// default priority": 7
},
"// tpn-range": 1, "// tpn-range": 1,
"// ___ COMMENT ___": "Since no TS range and no TSG are \ "// comment": "Since no TS range and no TSG are reported\
\reported for ODU3, the link is an OTU3 Link. TS allocation is not n\ \ for ODU3, the link is an OTU3 Link. TS allocation is not needed an\
\eeded and TPN shall be set to '1' for mapping ODU3 over OTU3. This \ \d TPN shall be set to '1' for mapping ODU3 over OTU3. This entry is\
\entry is not present if the OTN Link is an HO-ODU3 Link." \ not present if the OTN Link is an HO-ODU3 Link."
}, },
{ {
"index ": 2, "index ": 2,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-slot", "otn-label-range": {
"tsg": "tsg-1.25G", "range-type": "label-range-trib-slot",
"odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ "tsg": "tsg-1.25G",
\, ODU2, ODU2e ]", "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, OD\
"// ___ DEFAULT ___ priority": 7, \U1, ODU2, ODU2e ]",
"// default priority": 7
},
"// ts-range": "1-32" "// ts-range": "1-32"
}, },
{ {
"index ": 3, "index ": 3,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-port", "otn-label-range": {
"tsg": "tsg-1.25G", "range-type": "label-range-trib-port",
"odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU2\ "tsg": "tsg-1.25G",
\e ]", "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, OD\
"// ___ DEFAULT ___ priority": 7, \U2e ]",
"// default priority": 7
},
"// tpn-range": "1-32", "// tpn-range": "1-32",
"// ___ COMMENT ___": "Since this TPN range is reported \ "// comment": "Since this TPN range is reported for ODUf\
\for ODUflex, ODU0 and ODU2e with 1.25G TSG, the TPN assignment rule\ \lex, ODU0 and ODU2e with 1.25G TSG, the TPN assignment rule is flex\
\ is flexible within a common range for mapping LO-ODUflex, LO-ODU0 \ \ible within a common range for mapping LO-ODUflex, LO-ODU0 and LO-O\
\and LO-ODU2e over HO-ODU3 with 1.25G TSG. See Table 4 of [RFC7139]." \DU2e over HO-ODU3 with 1.25G TSG. See Table 4 of [RFC7139]."
}, },
{ {
"index ": 4, "index ": 4,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-port", "otn-label-range": {
"tsg": "tsg-1.25G", "range-type": "label-range-trib-port",
"odu-type-list": "[ ODU1 ]", "tsg": "tsg-1.25G",
"// ___ DEFAULT ___ priority": 7, "odu-type-list": "[ ODU1 ]",
"// default priority": 7
},
"// tpn-range": "1-16", "// tpn-range": "1-16",
"// ___ COMMENT ___": "Since this TPN range is reported \ "// comment": "Since this TPN range is reported for ODU1\
\for ODU1 with 1.25G TSG, the TPN assignment rule is flexible within\ \ with 1.25G TSG, the TPN assignment rule is flexible within a commo\
\ a common range for mapping LO-ODU1 over HO-ODU3 with 1.25G TSG. Se\ \n range for mapping LO-ODU1 over HO-ODU3 with 1.25G TSG. See Table \
\e Table 4 of [RFC7139]." \4 of [RFC7139]."
}, },
{ {
"index ": 5, "index ": 5,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-port", "otn-label-range": {
"tsg": "tsg-1.25G", "range-type": "label-range-trib-port",
"odu-type-list": "[ ODU2 ]", "tsg": "tsg-1.25G",
"// ___ DEFAULT ___ priority": 7, "odu-type-list": "[ ODU2 ]",
"// default priority": 7
},
"// tpn-range": "1-4", "// tpn-range": "1-4",
"// ___ COMMENT ___": "Since this TPN range is reported \ "// comment": "Since this TPN range is reported for ODU2\
\for ODU2 with 1.25G TSG, the TPN assignment rule is flexible within\ \ with 1.25G TSG, the TPN assignment rule is flexible within a commo\
\ a common range for mapping LO-ODU2 over HO-ODU3 with 1.25G TSG. Se\ \n range for mapping LO-ODU2 over HO-ODU3 with 1.25G TSG. See Table \
\e Table 4 of [RFC7139]." \4 of [RFC7139]."
}, },
{ {
"index ": 6, "index ": 6,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-slot", "otn-label-range": {
"tsg": "tsg-2.5G", "range-type": "label-range-trib-slot",
"odu-type-list": "[ ODU1, ODU2 ]", "tsg": "tsg-2.5G",
"// ___ DEFAULT ___ priority": 7, "odu-type-list": "[ ODU1, ODU2 ]",
"// default priority": 7
},
"// ts-range": "1-16" "// ts-range": "1-16"
}, },
{ {
"index ": 7, "index ": 7,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-port", "otn-label-range": {
"tsg": "tsg-2.5G ", "range-type": "label-range-trib-port",
"odu-type-list": "[ ODU2 ]", "tsg": "tsg-2.5G ",
"// ___ DEFAULT ___ priority": 7, "odu-type-list": "[ ODU2 ]",
"// default priority": 7
},
"// tpn-range": "1-4", "// tpn-range": "1-4",
"// ___ COMMENT ___": "Since this TPN range is reported \ "// comment": "Since this TPN range is reported for ODU2\
\for ODU2 with 2.5G TSG, the TPN assignment rule is flexible within \ \ with 2.5G TSG, the TPN assignment rule is flexible within a common\
\a common range for mapping LO-ODU2 over HO-ODU3. Since no TPN range\ \ range for mapping LO-ODU2 over HO-ODU3. Since no TPN range is repo\
\ is reported for ODU1 with 2.5G TSG, the TPN allocation rule is fix\ \rted for ODU1 with 2.5G TSG, the TPN allocation rule is fixed (TPN \
\ed (TPN = TS#) for mapping LO-ODU1 over HO-ODU3 with 2.5G TSG. See \ \= TS#) for mapping LO-ODU1 over HO-ODU3 with 2.5G TSG. See Table 3 \
\Table 3 of [RFC7139]." \of [RFC7139]."
} }
] ]
} }
}, },
{ {
"// ": "HO-ODU4 or OTU4 Link", "// example": "HO-ODU4 or OTU4 Link",
"label-restrictions": { "label-restrictions": {
"label-restriction": [ "label-restriction": [
{ {
"index ": 1, "index ": 1,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-port", "otn-label-range": {
"// ___NOT-PRESENT___ tsg": "", "range-type": "label-range-trib-port",
"odu-type-list": "[ ODU4 ]", "//not-present tsg": "",
"// ___ DEFAULT ___ priority": 7, "odu-type-list": "[ ODU4 ]",
"// default priority": 7
},
"// tpn-range": 1, "// tpn-range": 1,
"// ___ COMMENT ___": "Since no TS range and no TSG are \ "// comment": "Since no TS range and no TSG are reported\
\reported for ODU4, the link is an OTU4 Link. TS allocation is not n\ \ for ODU4, the link is an OTU4 Link. TS allocation is not needed an\
\eeded and TPN shall be set to '1' for mapping ODU4 over OTU4. This \ \d TPN shall be set to '1' for mapping ODU4 over OTU4. This entry is\
\entry is not present if the OTN Link is an HO-ODU4 Link." \ not present if the OTN Link is an HO-ODU4 Link."
}, },
{ {
"index ": 2, "index ": 2,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-slot", "otn-label-range": {
"tsg": "tsg-1.25G", "range-type": "label-range-trib-slot",
"odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ "tsg": "tsg-1.25G",
\, ODU2, ODU2e, ODU3 ]", "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, OD\
"// ___ DEFAULT ___ priority": 7, \U1, ODU2, ODU2e, ODU3 ]",
"// default priority": 7
},
"// ts-range": "1-80" "// ts-range": "1-80"
}, },
{ {
"index ": 3, "index ": 3,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-port", "otn-label-range": {
"tsg": "tsg-1.25G", "range-type": "label-range-trib-port",
"odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ "tsg": "tsg-1.25G",
\, ODU2, ODU2e, ODU3 ]", "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, OD\
"// ___ DEFAULT ___ priority": 7, \U1, ODU2, ODU2e, ODU3 ]",
"// default priority": 7
},
"// tpn-range": "1-80", "// tpn-range": "1-80",
"// ___ COMMENT ___": "Since this TPN range is reported \ "// comment": "Since this TPN range is reported for any \
\for any LO-ODUj with 1.25G TSG, the TPN assignment rule is flexible\ \LO-ODUj with 1.25G TSG, the TPN assignment rule is flexible within \
\ within a common range for mapping any LO-ODUj over HO-ODU4 with 1.\ \a common range for mapping any LO-ODUj over HO-ODU4 with 1.25G TSG.\
\25G TSG. See Table 4 of [RFC7139]." \ See Table 4 of [RFC7139]."
} }
] ]
} }
}, },
{ {
"// ": "ODUC1 Link", "// example": "ODUC1 Link",
"label-restrictions": { "label-restrictions": {
"label-restriction": [ "label-restriction": [
{ {
"index ": 1, "index ": 1,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-slot", "otn-label-range": {
"tsg": "tsg-5G", "range-type": "label-range-trib-slot",
"odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ "tsg": "tsg-5G",
\, ODU2, ODU2e, ODU3, ODU4 ]", "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, OD\
"// ___ DEFAULT ___ priority": 7, \U1, ODU2, ODU2e, ODU3, ODU4 ]",
"// default priority": 7
},
"// ts-range": "1-20", "// ts-range": "1-20",
"// ___ COMMENT ___": "Since the TS range is specified f\ "// comment": "Since the TS range is specified for any O\
\or any ODUk, the OTN Link is an ODUCn Link." \DUk, the OTN Link is an ODUCn Link."
}, },
{ {
"index ": 2, "index ": 2,
"// ___DEFAULT___ restriction": "inclusive", "// default restriction": "inclusive",
"range-type": "label-range-trib-port", "otn-label-range": {
"tsg": "tsg-5G", "range-type": "label-range-trib-port",
"odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, ODU1\ "tsg": "tsg-5G",
\, ODU2, ODU2e, ODU3, ODU4 ]", "odu-type-list": "[ ODUFlex-cbr, ODUFlex-gfp, ODU0, OD\
"// ___ DEFAULT ___ priority": 7, \U1, ODU2, ODU2e, ODU3, ODU4 ]",
"// default priority": 7
},
"// tpn-range": "1-10", "// tpn-range": "1-10",
"// ___ COMMENT ___": "Since this TPN range is reported \ "// comment": "Since this TPN range is reported for any \
\for any ODUk with 5G TSG, the TPN assignment rule is flexible withi\ \ODUk with 5G TSG, the TPN assignment rule is flexible within a comm\
\n a common range for mapping any ODUk over ODUCn with 5G TSG." \on range for mapping any ODUk over ODUCn with 5G TSG."
} }
] ]
} }
} }
] ]
} }
Authors' Addresses Authors' Addresses
Haomian Zheng Haomian Zheng
 End of changes. 94 change blocks. 
423 lines changed or deleted 498 lines changed or added

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