Internet-Draft | Layer 0 Types - Revision 2 | February 2021 |
Beller, et al. | Expires 26 August 2021 | [Page] |
- Workgroup:
- CCAMP
- Internet-Draft:
- draft-esdih-ccamp-layer0-types-ext-00
- Updates:
- draft-ietf-ccamp-layer0-types (if approved)
- Published:
- Intended Status:
- Standards Track
- Expires:
A YANG Data Model for Layer 0 Types - Revision 2
Abstract
This document defines a collection of common data types and groupings in the YANG data modeling language, which are used in several YANG modules for wavelength Division multiplexing (WDM) transport networks. The YANG module ietf-layer0-types-ext updates ietf-layer0-types defined in draft-ietf-ccamp-layer0-types, which has been reduced in scope prior to publication to only cover spectrum management related aspects required for the YANG module ietf-wson-topology defined in draft-ietf-ccamp-wson-yang.¶
To be completed¶
Status of This Memo
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 26 August 2021.¶
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶
1. Introduction
YANG [RFC7950] is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols such as NETCONF [RFC6241]. The YANG language supports a small set of built-in data types and provides mechanisms to derive other types from the built-in types.¶
This document introduces a collection of common data types derived from the built-in YANG data types. The derived types and groupings are designed to be the common types applicable for modeling Traffic Engineering (TE) features as well as non-TE features (e.g., physical network configuration aspect) for Layer 0 optical networks in model(s) defined outside of this document.¶
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].¶
2. Extensions for the Layer 0 Types Module
This document defines YANG module extensions for common Layer 0 types. named ietf-layer0-types-ext. This module can be used for both WSON and Flexi-grid DWDM networks but in particular is adding common types used in the context of optical impairment aware topology model in WSON and SSONs. The ietf-layer0-types-ext module contains the following YANG identities, types and groupings that can be reused in other YANG modules:¶
transceiver-capabilities:¶
a YANG grouping to define the transceiver capabilities (also called "modes") needed to determine optical signal compatibility.¶
standard-mode:¶
a YANG grouping for ITU-T G.698.2 standard mode that guarantees interoperability.¶
organizational-mode:¶
a YANG grouping to define transponder operational mode supported by organizations or vendors.¶
common-explicit-mode:¶
a YANG grouping to define the list of attributes related to optical impairments limits in case of transceiver explicit mode. This grouping should be the same used in [I-D.ietf-ccamp-dwdm-if-param-yang].¶
common-organizational-explicit-mode:¶
a YANG grouping to define the common capabilities attributes limit range in case of operational mode and explicit mode. Also this grouping should be used in [I-D.ietf-ccamp-dwdm-if-param-yang].¶
cd-pmd-penalty:¶
a YANG grouping to define the triplet used as entries in the list optional penalty associated with a given accumulated CD and PMD. This list of triplet cd, pmd, penalty can be used to sample the function penalty = f(CD, PMD).¶
[Editor's note: There is still stuff from the xml template that needs to be removed]¶
3. Layer0 Types Revision 2 YANG CODE
The YANG code is developed on GitHub and can also be found in the following CCAMP repository:¶
https://github.com/ietf-ccamp-wg/ietf-ccamp-layer0-types-ext¶
[Editor's note: YANG code below has to be updated before submitting a new revision!]¶
4. Acknowledgements
To be added if any.¶
5. Contributors
Gabriele Galimberti
Cisco¶
Email: ggalimbe@cisco.com
¶
Enrico Griseri
Nokia¶
Email: Enrico.Griseri@nokia.com
¶
Aihua Guo
Futurewei¶
Email: aihuaguo@futurewei.com
¶
6. IANA Considerations
This memo includes no request to IANA.¶
All drafts are required to have an IANA considerations section (see Guidelines for Writing an IANA Considerations Section in RFCs [RFC5226] for a guide). If the draft does not require IANA to do anything, the section contains an explicit statement that this is the case (as above). If there are no requirements for IANA, the section will be removed during conversion into an RFC by the RFC Editor.¶
7. Security Considerations
All drafts are required to have a security considerations section. See RFC 3552 [RFC3552] for a guide.¶
8. References
8.1. Normative References
- [I-D.ietf-ccamp-layer0-types]
- Zheng, H., Lee, Y., Guo, A., Lopez, V., and D. King, "A YANG Data Model for Layer 0 Types", Work in Progress, Internet-Draft, draft-ietf-ccamp-layer0-types-09, , <https://tools.ietf.org/html/draft-ietf-ccamp-layer0-types-09>.
- [I-D.ietf-ccamp-optical-impairment-topology-yang]
- Lee, Y., Auge, L., Lopez, V., Galimberti, G., and D. Beller, "A Yang Data Model for Optical Impairment-aware Topology", Work in Progress, Internet-Draft, draft-ietf-ccamp-optical-impairment-topology-yang-05, , <https://tools.ietf.org/html/draft-ietf-ccamp-optical-impairment-topology-yang-05>.
- [I-D.ietf-ccamp-wson-yang]
- Zheng, H., Lee, Y., Guo, A., Lopez, V., and D. King, "A YANG Data Model for WSON (Wavelength Switched Optical Networks)", Work in Progress, Internet-Draft, draft-ietf-ccamp-wson-yang-28, , <https://tools.ietf.org/html/draft-ietf-ccamp-wson-yang-28>.
- [RFC2119]
- Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
- [RFC6241]
- Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, , <https://www.rfc-editor.org/info/rfc6241>.
- [RFC7950]
- Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, , <https://www.rfc-editor.org/info/rfc7950>.
- [RFC8795]
- Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and O. Gonzalez de Dios, "YANG Data Model for Traffic Engineering (TE) Topologies", RFC 8795, DOI 10.17487/RFC8795, , <https://www.rfc-editor.org/info/rfc8795>.
8.2. Informative References
- [I-D.ietf-ccamp-dwdm-if-param-yang]
- Galimberti, G., Kunze, R., Burk, A., Hiremagalur, D., and G. Grammel, "A YANG model to manage the optical interface parameters for an external transponder in a WDM network", Work in Progress, Internet-Draft, draft-ietf-ccamp-dwdm-if-param-yang-05, , <https://tools.ietf.org/html/draft-ietf-ccamp-dwdm-if-param-yang-05>.
- [RFC2629]
- Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, DOI 10.17487/RFC2629, , <https://www.rfc-editor.org/info/rfc2629>.
- [RFC3552]
- Rescorla, E. and B. Korver, "Guidelines for Writing RFC Text on Security Considerations", BCP 72, RFC 3552, DOI 10.17487/RFC3552, , <https://www.rfc-editor.org/info/rfc3552>.
- [RFC5226]
- Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", RFC 5226, DOI 10.17487/RFC5226, , <https://www.rfc-editor.org/info/rfc5226>.