Skip to content

ietf-ccamp-wg/ietf-ccamp-layer0-types-ext-RFC9093-bis

Repository files navigation

ietf-layer0-types-ext

CCAMP WG repository for ietf-layer0-types-ext. This is the working area for the IETF CCAMP WG ietf-layer0-types-ext YANG module, which is the starting point for revision 2 of ietf-layer0-types. When the initial version of the YANG module ietf-layer0-types will have been published as RFC, ietf-layer0-types-ext will be renamed to ietf-layer0-types.

Note: draft-esdih-ccamp-layer0-types-ext-00 is intended to be submitted on Mon, Feb 22, 2021

Branches

  • carry-over-ietf-layer0-types: this temporary branch is used for the material that was removed from ietf-layer0-types when it's scope was reduced to spectrum management only.
  • transponder-model-types: this temporary branch will be used for developing type defs and groupings that are used in various YANG models that include optical transponders (e.g.: draft-ietf-ccamp-dwdm-if-param-yang, draft-ietf-ccamp-optical-impairment-topology-yang, etc.)

Material from the two branches above will ber merged into ietf-layer0-types-ext.yang (to be created) on the master branch.

Contributing

This repository relates to activities in the Internet Engineering Task Force (IETF). All material in this repository is considered Contributions to the IETF Standards Process, as defined in the intellectual property policies of IETF currently designated as BCP 78, BCP 79 and the IETF Trust Legal Provisions (TLP) Relating to IETF Documents.

Any edit, commit, pull request, issue, comment or other change made to this repository constitutes Contributions to the IETF Standards Process (https://www.ietf.org/).

You agree to comply with all applicable IETF policies and procedures, including, BCP 78, 79, the TLP, and the TLP rules regarding code components (e.g. being subject to a Simplified BSD License) in Contributions.

Other Resources

Discussion of this work occurs on the CCAMP working group mailing list (subscribe). In addition to contributions in GitHub, you are encouraged to participate in discussions there.

Note: Some working groups adopt a policy whereby substantive discussion of technical issues needs to occur on the mailing list.

You might also like to familiarize yourself with other working group documents.