< draft-ietf-ccamp-layer1-types-04.txt | draft-ietf-ccamp-layer1-types-05.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: June 7, 2020 December 5, 2019 | Expires: June 27, 2020 December 25, 2019 | |||
A YANG Data Model for Layer 1 Types | A YANG Data Model for Layer 1 Types | |||
draft-ietf-ccamp-layer1-types-04 | draft-ietf-ccamp-layer1-types-05 | |||
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 June 7, 2020. | This Internet-Draft will expire on June 27, 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 15 ¶ | skipping to change at page 2, line 15 ¶ | |||
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 | |||
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 . . . . . . . . . . . . . . . . . . . 21 | |||
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 | |||
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 | 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 | |||
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 21 | 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 | |||
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 | 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 | |||
10.1. Normative References . . . . . . . . . . . . . . . . . . 22 | 10.1. Normative References . . . . . . . . . . . . . . . . . . 23 | |||
10.2. Informative References . . . . . . . . . . . . . . . . . 24 | 10.2. Informative References . . . . . . . . . . . . . . . . . 25 | |||
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 | |||
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 networks. | Engineering (TE) features for Layer 1 networks. | |||
Typical Layer 1 network, the Optical Transport Networking, was | Typical Layer 1 network, the Optical Transport Networking, was | |||
specified in [RFC7062]. Corresponding routing and signaling protocol | specified in [RFC7062]. Corresponding routing and signaling protocol | |||
have been specified in [RFC7138] and [RFC7139]. The types and | have been specified in [RFC7138] and [RFC7139]. The types and | |||
groupings defined in this document is consistent to these document, | groupings defined in this document is consistent to these document, | |||
and will be imported in other Layer 1 data models, including but not | and will be imported in other Layer 1 data models, including but not | |||
restrictive to, [I-D.ietf-ccamp-otn-topo-yang], | restrictive to, [I-D.ietf-ccamp-otn-topo-yang], | |||
[I-D.ietf-ccamp-otn-tunnel-model] and [I-D.ietf-ccamp-l1csm-yang]. | [I-D.ietf-ccamp-otn-tunnel-model], | |||
[I-D.ietf-ccamp-client-signal-yang] 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 other specifications, including [MEF63] for Layer 1 | consistent with other specifications, including [MEF63] for Layer 1 | |||
service attributes, [ITU-Tg709] and [ITU-Tgsup43] for OTN data plane | service attributes, [ITU-Tg709] and [ITU-Tgsup43] for OTN data plane | |||
definitions. | definitions. | |||
2. Terminology and Notations | 2. Terminology and Notations | |||
skipping to change at page 3, line 14 ¶ | skipping to change at page 3, line 14 ¶ | |||
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. | |||
+-------------+---------------------------+----------------------+ | +-------------+---------------------------+----------------------+ | |||
| Prefix | YANG module | Reference | | | Prefix | YANG module | Reference | | |||
+-------------+---------------------------+----------------------+ | +-------------+---------------------------+----------------------+ | |||
| layer1-types| ietf-layer1-types | This Document | | | l1-types | ietf-layer1-types | This Document | | |||
+-------------+---------------------------+----------------------+ | +-------------+---------------------------+----------------------+ | |||
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 | |||
objective is to specifies common Layer 1 TE types that can be | objective is to specifies common Layer 1 TE types that can be | |||
imported by layer 1 specific technology, for example OTN, in its | imported by layer 1 specific technology, for example OTN, in its | |||
technology-specific modules such as topology and tunnels. It is | technology-specific modules such as topology and tunnels. It is | |||
worth noting that the generic traffic-engineering (TE) types module | worth noting that the generic traffic-engineering (TE) types module | |||
is specified in [I-D.ietf-teas-yang-te-types] as ietf-te-types, and | is specified in [I-D.ietf-teas-yang-te-types] as ietf-te-types, and | |||
both the module ietf-te-types and ietf-layer1-types are needed to be | both the module ietf-te-types and ietf-layer1-types are needed to be | |||
imported when the OTN is configured. | imported when the OTN is configured. Generic attributes such as te- | |||
bandwidth and te-label, are indicated in ietf-te-types in | ||||
[I-D.ietf-teas-yang-te-types], while the OTN-specific attributes, | ||||
such as odu-type, are indicated in 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 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, | |||
skipping to change at page 4, line 4 ¶ | skipping to change at page 4, line 9 ¶ | |||
odu-type: | odu-type: | |||
This is to specify the type of ODUk LSP, including the types | This is to specify the type of ODUk LSP, including the types | |||
specified in [RFC7139] and [RFC7963]. | 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 | |||
Fiber Channel have been specified. | [Telcordia] and 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: | |||
skipping to change at page 6, line 17 ¶ | skipping to change at page 6, line 21 ¶ | |||
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 in the otn-label-range-info grouping. | 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-12-05.yang" | <CODE BEGINS>file "ietf-layer1-types@2019-12-25.yang" | |||
module ietf-layer1-types { | module ietf-layer1-types { | |||
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 "layer1-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> | |||
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) 2019 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 | |||
skipping to change at page 6, line 47 ¶ | skipping to change at page 7, line 4 ¶ | |||
Copyright (c) 2019 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-12-05" { | revision "2019-12-25" { | |||
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 | |||
} | } | |||
typedef otn-tpn | ||||
{ | ||||
type uint16; | ||||
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; | ||||
description | ||||
"Tributary Slot for OTN. "; | ||||
reference | ||||
"RFC7139: GMPLS Signaling Extensions for Control of Evolving | ||||
G.709 Optical Transport Networks."; | ||||
} | ||||
identity tributary-slot-granularity { | identity tributary-slot-granularity { | |||
description | description | |||
"Tributary slot granularity"; | "Tributary slot granularity"; | |||
reference | reference | |||
"G.709/Y.1331, February 2016: Interfaces for the Optical | "G.709/Y.1331, February 2016: Interfaces for the Optical | |||
Transport Network (OTN)"; | Transport Network (OTN)"; | |||
} | } | |||
identity tsg-1.25G { | identity tsg-1.25G { | |||
base tributary-slot-granularity; | base tributary-slot-granularity; | |||
skipping to change at page 7, line 46 ¶ | skipping to change at page 8, 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, which is | "ODU0 protocol (1.24G)"; | |||
categorized as standards track ."; | reference "RFC7139/ITU-T G.709"; | |||
} | } | |||
identity ODU1 { | identity ODU1 { | |||
base odu-type; | base odu-type; | |||
description | description | |||
"ODU1 protocol (2.49G), RFC7139/ITU-T G.709, which is | "ODU1 protocol (2.49G)."; | |||
categorized as standards track ."; | reference "RFC7139/ITU-T G.709"; | |||
} | } | |||
identity ODU1e { | identity ODU1e { | |||
base odu-type; | base odu-type; | |||
description | description | |||
"ODU1e protocol (10.35G), RFC7963/ITU-T G.sup43, which is | "ODU1e protocol (10.35G)."; | |||
categorized as informational."; | reference "RFC7963/ITU-T G.sup43"; | |||
} | } | |||
identity ODU2 { | identity ODU2 { | |||
base odu-type; | base odu-type; | |||
description | description | |||
"ODU2 protocol (10.03G), RFC7139/ITU-T G.709, which is | "ODU2 protocol (10.03G)."; | |||
categorized as standards track ."; | reference "RFC7139/ITU-T G.709"; | |||
} | } | |||
identity ODU2e { | identity ODU2e { | |||
base odu-type; | base odu-type; | |||
description | description | |||
"ODU2e protocol (10.39G), RFC7139/ITU-T G.709, which is | "ODU2e protocol (10.39G)."; | |||
categorized as standards track ."; | reference "RFC7139/ITU-T G.709"; | |||
} | } | |||
identity ODU3 { | identity ODU3 { | |||
base odu-type; | base odu-type; | |||
description | description | |||
"ODU3 protocol (40.31G), RFC7139/ITU-T G.709, which is | "ODU3 protocol (40.31G)."; | |||
categorized as standards track ."; | reference "RFC7139/ITU-T G.709"; | |||
} | } | |||
identity ODU3e1 { | identity ODU3e1 { | |||
base odu-type; | base odu-type; | |||
description | description | |||
"ODU3e1 protocol (41.77G), RFC7963/ITU-T G.sup43, which is | "ODU3e1 protocol (41.77G)."; | |||
categorized as informational."; | reference "RFC7963/ITU-T G.sup43"; | |||
} | } | |||
identity ODU3e2 { | identity ODU3e2 { | |||
base odu-type; | base odu-type; | |||
description | description | |||
"ODU3e2 protocol (41.78G), RFC7963/ITU-T G.sup43, which is | "ODU3e2 protocol (41.78G)."; | |||
categorized as informational."; | reference "RFC7963/ITU-T G.sup43"; | |||
} | } | |||
identity ODU4 { | identity ODU4 { | |||
base odu-type; | base odu-type; | |||
description | description | |||
"ODU4 protocol (104.79G), RFC7139/ITU-T G.709, which is | "ODU4 protocol (104.79G)."; | |||
categorized as standards track ."; | reference "RFC7139/ITU-T G.709"; | |||
} | } | |||
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"; | |||
reference "RFC7139/ITU-T G.709"; | ||||
} | } | |||
identity ODUFlex-gfp { | identity ODUFlex-gfp { | |||
base odu-type; | base odu-type; | |||
description | description | |||
"ODU Flex GFP protocol for transporting stream of packets | "ODU Flex GFP protocol for transporting stream of packets | |||
using Generic Framing Procedure"; | using Generic Framing Procedure"; | |||
reference "RFC7139/ITU-T G.709"; | ||||
} | } | |||
identity client-signal { | identity client-signal { | |||
description | description | |||
"Base identity from which specific client signals for the | "Base identity from which specific client signals for the | |||
tunnel are derived"; | tunnel are derived"; | |||
} | } | |||
identity ETH-1Gb { | identity ETH-1Gb { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of 1GbE"; | "Client signal type of 1GbE"; | |||
reference "RFC7139/ITU-T G.709"; | ||||
} | } | |||
identity ETH-10Gb-LAN { | identity ETH-10Gb-LAN { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of 10GbE LAN"; | "Client signal type of ETH-10Gb-LAN (10.3 Gb/s)"; | |||
reference "RFC7139/ITU-T G.709/IEEE 802.3 Clause 49"; | ||||
} | } | |||
identity ETH-10Gb-WAN { | identity ETH-10Gb-WAN { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of 10GbE WAN"; | "Client signal type of ETH-10Gb-WAN (9.95 Gb/s)"; | |||
reference "RFC7139/ITU-T G.709/IEEE 802.3 Clause 50"; | ||||
} | } | |||
identity ETH-40Gb { | identity ETH-40Gb { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of 40GbE"; | "Client signal type of 40GbE"; | |||
reference "RFC7139/ITU-T G.709"; | ||||
} | } | |||
identity ETH-100Gb { | identity ETH-100Gb { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of 100GbE"; | "Client signal type of 100GbE"; | |||
reference "RFC7139/ITU-T G.709"; | ||||
} | } | |||
identity STM-1 { | identity STM-1 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of STM-1"; | "Client signal type of STM-1"; | |||
reference "RFC7139/ITU-T G.709"; | ||||
} | } | |||
identity STM-4 { | identity STM-4 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of STM-4"; | "Client signal type of STM-4"; | |||
reference "RFC7139/ITU-T G.709"; | ||||
} | } | |||
identity STM-16 { | identity STM-16 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of STM-16"; | "Client signal type of STM-16"; | |||
reference "RFC7139/ITU-T G.709"; | ||||
} | } | |||
identity STM-64 { | identity STM-64 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of STM-64"; | "Client signal type of STM-64"; | |||
reference "RFC7139/ITU-T G.709"; | ||||
} | } | |||
identity STM-256 { | identity STM-256 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of STM-256"; | "Client signal type of STM-256"; | |||
reference "RFC7139/ITU-T G.709"; | ||||
} | } | |||
identity OC-3 { | identity OC-3 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of OC3"; | "Client signal type of OC3"; | |||
reference "Telcordia GR-253-CORE"; | ||||
} | } | |||
identity OC-12 { | identity OC-12 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of OC12"; | "Client signal type of OC12"; | |||
reference "Telcordia GR-253-CORE"; | ||||
} | } | |||
identity OC-48 { | identity OC-48 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of OC48"; | "Client signal type of OC48"; | |||
reference "Telcordia GR-253-CORE"; | ||||
} | } | |||
identity OC-192 { | identity OC-192 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of OC192"; | "Client signal type of OC192"; | |||
reference "Telcordia GR-253-CORE"; | ||||
} | } | |||
identity OC-768 { | identity OC-768 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of OC768"; | "Client signal type of OC768"; | |||
reference "Telcordia GR-253-CORE"; | ||||
} | } | |||
identity FC-100 { | identity FC-100 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of Fibre Channel FC-100"; | "Client signal type of Fibre Channel FC-100"; | |||
reference "RFC4328/RFC7139"; | ||||
} | } | |||
identity FC-200 { | identity FC-200 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of Fibre Channel FC-200"; | "Client signal type of Fibre Channel FC-200"; | |||
reference "RFC4328/RFC7139"; | ||||
} | } | |||
identity FC-400 { | identity FC-400 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of Fibre Channel FC-400"; | "Client signal type of Fibre Channel FC-400"; | |||
reference "RFC4328/RFC7139"; | ||||
} | } | |||
identity FC-800 { | identity FC-800 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of Fibre Channel FC-800"; | "Client signal type of Fibre Channel FC-800"; | |||
reference "RFC4328/RFC7139"; | ||||
} | } | |||
identity FC-1200 { | identity FC-1200 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of Fibre Channel FC-1200"; | "Client signal type of Fibre Channel FC-1200"; | |||
reference "RFC4328/RFC7139"; | ||||
} | } | |||
identity FC-1600 { | identity FC-1600 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of Fibre Channel FC-1600"; | "Client signal type of Fibre Channel FC-1600"; | |||
reference "RFC4328/RFC7139"; | ||||
} | } | |||
identity FC-3200 { | identity FC-3200 { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of Fibre Channel FC-3200"; | "Client signal type of Fibre Channel FC-3200"; | |||
reference "RFC4328/RFC7139"; | ||||
} | } | |||
identity FICON-4G { | identity FICON-4G { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of Fibre Connection 4G"; | "Client signal type of Fibre Connection 4G"; | |||
reference "RFC4328/RFC7139"; | ||||
} | } | |||
identity FICON-8G { | identity FICON-8G { | |||
base client-signal; | base client-signal; | |||
description | description | |||
"Client signal type of Fibre Connection 8G"; | "Client signal type of Fibre Connection 8G"; | |||
reference "RFC4328/RFC7139"; | ||||
} | } | |||
identity otn-label-range-type { | identity otn-label-range-type { | |||
description | description | |||
"Base identity from which specific OTN label | "Base identity from which specific OTN label | |||
range types derived"; | range types derived"; | |||
} | } | |||
identity label-range-trib-slot { | identity label-range-trib-slot { | |||
base otn-label-range-type; | base otn-label-range-type; | |||
description | description | |||
"Defines a range of OTN tributary slots"; | "Defines a range of OTN tributary slots"; | |||
} | } | |||
identity label-range-trib-port { | identity label-range-trib-port { | |||
base otn-label-range-type; | base otn-label-range-type; | |||
description | description | |||
"Defines a range of OTN tributary ports"; | "Defines a range of OTN tributary ports"; | |||
} | } | |||
identity coding-func { | ||||
description | ||||
"Base identity from which coding function is derived."; | ||||
} | ||||
identity ETH-1000X { | ||||
base "coding-func"; | ||||
description | ||||
"PCS clause 36 coding function that corresponds to | ||||
1000BASE-X"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity ETH-10GW { | ||||
base "coding-func"; | ||||
description | ||||
"PCS clause 49 and WIS clause 50 coding func that | ||||
corresponds to 10GBASE-W (WAN PHY)"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity ETH-10GR { | ||||
base "coding-func"; | ||||
description | ||||
"PCS clause 49 coding function that corresponds to | ||||
10GBASE-R (LAN PHY)"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity ETH-40GR { | ||||
base "coding-func"; | ||||
description | ||||
"PCS clause 82 coding function that corresponds to | ||||
40GBASE-R"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity ETH-100GR { | ||||
base "coding-func"; | ||||
description | ||||
"PCS clause 82 coding function that corresponds to | ||||
100GBASE-R"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity optical-interface-func { | ||||
description | ||||
"base identity from which optical-interface-function is | ||||
derived."; | ||||
} | ||||
identity SX-PMD-1000 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"SX-PMD-clause-38 Optical Interface function for | ||||
1000BASE-X PCS-36"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity LX-PMD-1000 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"LX-PMD-clause-38 Optical Interface function for | ||||
1000BASE-X PCS-36"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity LX10-PMD-1000 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"LX10-PMD-clause-59 Optical Interface function for | ||||
1000BASE-X PCS-36"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity BX10-PMD-1000 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"BX10-PMD-clause-59 Optical Interface function for | ||||
1000BASE-X PCS-36"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity LW-PMD-10G { | ||||
base "optical-interface-func"; | ||||
description | ||||
"LW-PMD-clause-52 Optical Interface function for | ||||
10GBASE-W PCS-49-WIS-50"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity EW-PMD-10G { | ||||
base "optical-interface-func"; | ||||
description | ||||
"EW-PMD-clause-52 Optical Interface function for | ||||
10GBASE-W PCS-49-WIS-50"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity LR-PMD-10G { | ||||
base "optical-interface-func"; | ||||
description | ||||
"LR-PMD-clause-52 Optical Interface function for | ||||
10GBASE-R PCS-49"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity ER-PMD-10G { | ||||
base "optical-interface-func"; | ||||
description | ||||
"ER-PMD-clause-52 Optical Interface function for | ||||
10GBASE-R PCS-49"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity LR4-PMD-40G { | ||||
base "optical-interface-func"; | ||||
description | ||||
"LR4-PMD-clause-87 Optical Interface function for | ||||
40GBASE-R PCS-82"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity ER4-PMD-40G { | ||||
base "optical-interface-func"; | ||||
description | ||||
"ER4-PMD-clause-87 Optical Interface function for | ||||
40GBASE-R PCS-82"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity FR-PMD-40G { | ||||
base "optical-interface-func"; | ||||
description | ||||
"FR-PMD-clause-89 Optical Interface function for | ||||
40GBASE-R PCS-82"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity LR4-PMD-100G { | ||||
base "optical-interface-func"; | ||||
description | ||||
"LR4-PMD-clause-88 Optical Interface function for | ||||
100GBASE-R PCS-82"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity ER4-PMD-100G { | ||||
base "optical-interface-func"; | ||||
description | ||||
"ER4-PMD-clause-88 Optical Interface function for | ||||
100GBASE-R PCS-82"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity service-performance-metric { | ||||
description | ||||
"Base identity of service-specific performance metric"; | ||||
} | ||||
identity one-way-delay { | ||||
base "service-performance-metric"; | ||||
description "one way delay."; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity one-way-errored-second { | ||||
base "service-performance-metric"; | ||||
description "one way errored second"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity one-way-severely-errored-second { | ||||
base "service-performance-metric"; | ||||
description "one way severely errored second"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity one-way-unavailable-second { | ||||
base "service-performance-metric"; | ||||
description "one way unavailable second"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity one-way-availability { | ||||
base "service-performance-metric"; | ||||
description "one way availability"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
grouping otn-link-bandwidth { | grouping otn-link-bandwidth { | |||
description "link bandwidth attributes for OTN"; | description "link bandwidth attributes for OTN"; | |||
list odulist { | list odulist { | |||
key "odu-type"; | key "odu-type"; | |||
description | description | |||
"OTN bandwidth definition"; | "OTN bandwidth definition"; | |||
leaf odu-type { | leaf odu-type { | |||
type identityref { | type identityref { | |||
base layer1-types:odu-type; | base l1-types:odu-type; | |||
} | } | |||
description "ODU type"; | description "ODU type"; | |||
} | } | |||
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 l1-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"; | |||
leaf range-type { | leaf range-type { | |||
type identityref { | type identityref { | |||
base layer1-types:otn-label-range-type; | base l1-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 l1-types:tributary-slot-granularity; | |||
} | } | |||
description | description | |||
"Tributary slot granularity."; | "Tributary slot granularity (TSG) to which the label range | |||
applies."; | ||||
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. | |||
skipping to change at page 14, line 4 ¶ | skipping to change at page 19, line 6 ¶ | |||
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 | Empty odu-type-list means all the ODU types are applicable | |||
per label range. "; | per label range. "; | |||
} | } | |||
leaf priority { | leaf priority { | |||
type uint8; | type uint8; | |||
description "priority."; | description | |||
"Priority in Interface Switching Capability | ||||
Descriptor (ISCD)."; | ||||
reference "RFC4203."; | ||||
} | } | |||
} | } | |||
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."; | |||
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 otn-tpn { | |||
type uint16 { | type l1-types:otn-tpn; | |||
range "1..4095"; | ||||
} | ||||
description | description | |||
"Tributary Port Number applicable in case of mux services."; | "Tributary Port 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."; | |||
} | } | |||
} | } | |||
case tributary-slot { | case tributary-slot { | |||
leaf ts { | leaf otn-ts { | |||
type uint16 { | type l1-types:otn-ts; | |||
range "1..4095"; | ||||
} | ||||
description | description | |||
"Tributary Slot Number applicable in case of mux services."; | "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."; | |||
} | } | |||
} | } | |||
} | } | |||
} | } | |||
grouping otn-label-hop { | grouping otn-label-hop { | |||
description "label information for OTN, for label-hop"; | description "OTN Label. "; | |||
leaf tpn { | reference "RFC7139, section 6. "; | |||
type uint16 { | leaf otn-tpn { | |||
range "1..4095"; | type l1-types:otn-tpn; | |||
} | ||||
description | description | |||
"Tributary Port Number applicable in case of mux services."; | "Tributary Port 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."; | |||
} | } | |||
leaf tsg { | leaf tsg { | |||
type identityref { | type identityref { | |||
base layer1-types:tributary-slot-granularity; | base l1-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})?)*)"; | |||
} | } | |||
description | description | |||
"A list of available tributary slots ranging | "A list of available tributary slots ranging | |||
between 1 and 4095. | between 1 and 4095. If multiple values or | |||
For example 1-20,25,50-1000"; | ranges are given, they all MUST be disjoint | |||
reference "RFC 7139: GMPLS Signaling Extensions for Control | and MUST be in ascending order. | |||
of Evolving G.709 Optical Transport Networks"; | 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 "Label step for OTN"; | description "Label step for OTN"; | |||
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 otn-tpn { | |||
type uint16 { | type l1-types:otn-tpn; | |||
range "1..4095"; | ||||
} | ||||
default 1; | default 1; | |||
description | description | |||
"Label step which represents possible increments for | "Label step which represents possible increments for | |||
Tributary Port Number."; | Tributary Port Number."; | |||
reference | reference | |||
"RFC7139: GMPLS Signaling Extensions for Control of Evolving | "RFC7139: GMPLS Signaling Extensions for Control of | |||
G.709 Optical Transport Networks."; | Evolving G.709 Optical Transport Networks."; | |||
} | ||||
} | ||||
} | } | |||
case tributary-slot { | case tributary-slot { | |||
leaf ts { | leaf otn-ts { | |||
type uint16 { | type l1-types:otn-ts; | |||
range "1..4095"; | ||||
} | ||||
default 1; | default 1; | |||
description | description | |||
"Label step which represents possible increments for | "Label step which represents possible increments for | |||
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."; | |||
} | } | |||
} | } | |||
} | } | |||
} | } | |||
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: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
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: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity ETH-10GR-PCS-49 { | ||||
base "coding-func"; | ||||
description | ||||
"PCS clause 49 coding function that corresponds to | ||||
10GBASE-R (LAN PHY)"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity ETH-40GR-PCS-82 { | ||||
base "coding-func"; | ||||
description | ||||
"PCS clause 82 coding function that corresponds to | ||||
40GBASE-R"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity ETH-100GR-PCS-82 { | ||||
base "coding-func"; | ||||
description | ||||
"PCS clause 82 coding function that corresponds to | ||||
100GBASE-R"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity optical-interface-func { | ||||
description | ||||
"base identity from which optical-interface-function is | ||||
derived."; | ||||
} | ||||
identity SX-PMD-clause-38 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"SX-PMD-clause-38 Optical Interface function for | ||||
1000BASE-X PCS-36"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity LX-PMD-clause-38 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"LX-PMD-clause-38 Optical Interface function for | ||||
1000BASE-X PCS-36"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity LX10-PMD-clause-59 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"LX10-PMD-clause-59 Optical Interface function for | ||||
1000BASE-X PCS-36"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity BX10-PMD-clause-59 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"BX10-PMD-clause-59 Optical Interface function for | ||||
1000BASE-X PCS-36"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity LW-PMD-clause-52 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"LW-PMD-clause-52 Optical Interface function for | ||||
10GBASE-W PCS-49-WIS-50"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity EW-PMD-clause-52 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"EW-PMD-clause-52 Optical Interface function for | ||||
10GBASE-W PCS-49-WIS-50"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity LR-PMD-clause-52 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"LR-PMD-clause-52 Optical Interface function for | ||||
10GBASE-R PCS-49"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity ER-PMD-clause-52 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"ER-PMD-clause-52 Optical Interface function for | ||||
10GBASE-R PCS-49"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity LR4-PMD-clause-87 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"LR4-PMD-clause-87 Optical Interface function for | ||||
40GBASE-R PCS-82"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity ER4-PMD-clause-87 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"ER4-PMD-clause-87 Optical Interface function for | ||||
40GBASE-R PCS-82"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity FR-PMD-clause-89 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"FR-PMD-clause-89 Optical Interface function for | ||||
40GBASE-R PCS-82"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity LR4-PMD-clause-88 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"LR4-PMD-clause-88 Optical Interface function for | ||||
100GBASE-R PCS-82"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity ER4-PMD-clause-88 { | ||||
base "optical-interface-func"; | ||||
description | ||||
"ER4-PMD-clause-88 Optical Interface function for | ||||
100GBASE-R PCS-82"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity service-performance-metric { | ||||
description | ||||
"list of service-specific performance metric"; | ||||
} | ||||
identity One-way-Delay { | ||||
base "service-performance-metric"; | ||||
description "one-way-delay"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity One-way-Errored-Second { | ||||
base "service-performance-metric"; | ||||
description "one-way-errored-second"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity One-way-Severely-Errored-Second { | ||||
base "service-performance-metric"; | ||||
description "one-way-severely-errored-second"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity One-way-Unavailable-Second { | ||||
base "service-performance-metric"; | ||||
description "one-way-unavailable-second"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity One-way-Availability { | ||||
base "service-performance-metric"; | ||||
description "one-way-availability"; | ||||
reference "MEF63: Subscriber Layer 1 Service Attributes"; | ||||
} | ||||
identity network-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 | |||
is the secure transport layer, and the mandatory-to-implement secure | is the secure transport layer, and the mandatory-to-implement secure | |||
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer | transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer | |||
skipping to change at page 20, line 48 ¶ | skipping to change at page 21, line 44 ¶ | |||
The NETCONF access control model [RFC8341] provides the means to | The NETCONF access control model [RFC8341] provides the means to | |||
restrict access for particular NETCONF or RESTCONF users to a | restrict access for particular NETCONF or RESTCONF users to a | |||
preconfigured subset of all available NETCONF or RESTCONF protocol | preconfigured subset of all available NETCONF or RESTCONF protocol | |||
operations and content. | operations and content. | |||
The YANG module in this document defines layer 1 type definitions | The YANG module in this document defines layer 1 type definitions | |||
(i.e., typedef, identity and grouping statements) in YANG data | (i.e., typedef, identity and grouping statements) in YANG data | |||
modeling language to be imported and used by other layer 1 | modeling language to be imported and used by other layer 1 | |||
technology-specific modules. When imported and used, the resultant | technology-specific modules. When imported and used, the resultant | |||
schema will have data nodes that can be writable, or readable. The | schema will have data nodes that can be writable, or readable. The | |||
access to such data nodes may be onsidered sensitive or vulnerable in | access to such data nodes may be considered sensitive or vulnerable | |||
some network environments. Write operations (e.g., edit-config) to | in some network environments. Write operations (e.g., edit-config) | |||
these data nodes without proper protection can have a negative effect | to these data nodes without proper protection can have a negative | |||
on network operations. | effect on network operations. | |||
The security considerations spelled out in the YANG 1.1 specification | The security considerations spelled out in the YANG 1.1 specification | |||
[RFC7950] apply for this document as well. | [RFC7950] apply for this document as well. | |||
7. IANA Considerations | 7. IANA Considerations | |||
It is proposed that IANA should assign new URIs from the "IETF XML | It is proposed that IANA should assign new URIs from the "IETF XML | |||
Registry" [RFC3688] as follows: | Registry" [RFC3688] as follows: | |||
URI: urn:ietf:params:xml:ns:yang:ietf-layer1-types | URI: urn:ietf:params:xml:ns:yang:ietf-layer1-types | |||
Registrant Contact: The IESG | Registrant Contact: The IESG | |||
XML: N/A; the requested URI is an XML namespace. | XML: N/A; the requested URI is an XML namespace. | |||
This document registers 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: l1-types | |||
reference: RFC XXXX | reference: RFC XXXX | |||
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 | |||
skipping to change at page 24, line 19 ¶ | skipping to change at page 25, line 14 ¶ | |||
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., | [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., | |||
and R. Wilton, "Network Management Datastore Architecture | and R. Wilton, "Network Management Datastore Architecture | |||
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, | (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, | |||
<https://www.rfc-editor.org/info/rfc8342>. | <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>. | |||
[Telcordia] | ||||
Telcordia, "Synchronous Optical Network Transport Systems: | ||||
Common Generic Criteria, Issue 5", Telcordia GR-253-CORE, | ||||
October 2009. | ||||
10.2. Informative References | 10.2. Informative References | |||
[I-D.ietf-ccamp-client-signal-yang] | ||||
Zheng, H., Guo, A., Busi, I., Snitser, A., Lazzeri, F., | ||||
Xu, Y., Zhao, Y., Liu, X., and G. Fioccola, "A YANG Data | ||||
Model for Transport Network Client Signals", draft-ietf- | ||||
ccamp-client-signal-yang-01 (work in progress), November | ||||
2019. | ||||
[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., Busi, I., Liu, X., Belotti, S., and O. Dios, "A | Zheng, H., Busi, I., Liu, X., Belotti, S., and O. Dios, "A | |||
YANG Data Model for Optical Transport Network Topology", | YANG Data Model for Optical Transport Network Topology", | |||
draft-ietf-ccamp-otn-topo-yang-09 (work in progress), | draft-ietf-ccamp-otn-topo-yang-09 (work in progress), | |||
End of changes. 78 change blocks. | ||||
283 lines changed or deleted | 337 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/ |