[CCAMP]Re: Proposed LS text for OIF

["BRUNGARD, DEBORAH A" <[e-mail]>]

Hi Italo,

Agree with Adrian - really great to kickoff a liaison relationship on this topic!

A couple of quick nits:

CCAMP WG is pretty confident/s/CCAMP is reasonably confident

We are looking forward open and fruitful relationship with OIF to be align the YANG data models developed by IETF following closely the technical progress of CMIS and C-CMIS specifications
/s/
We are looking forward to an open and fruitful relationship with OIF to facilitate alignment of the YANG data models developed by IETF with the evolution of the CMIS and C-CMIS specifications

Cheers,
Deborah

________________________________
From: Adrian Farrel <[e-mail]>
Sent: Tuesday, October 13, 2026 5:40 AM
To: 'Italo Busi' <[e-mail]>; 'CCAMP' <[e-mail]>
Subject: [CCAMP]Re: Proposed LS text for OIF

I like this, Italo. Thanks. Well thought through. Is it possible that the term “WG” will not be known by the OIF? Maybe s/approved/approved for publication as an RFC/ (In a couple of places) s/analysis of with respect/analysis with


I like this, Italo. Thanks. Well thought through.



Is it possible that the term “WG” will not be known by the OIF?

Maybe s/approved/approved for publication as an RFC/  (In a couple of places)

s/analysis of with respect/analysis with respect/

s/forum (including/forums (including)



Given “identify if there are missing attributes defined in other SDOs/forum (including OIF)” should we also be sending a request for input to any other SDOs?



Cheers,

Adrian



From: Italo Busi <Italo.Busi=[e-mail]>
Sent: 13 October 2026 08:47
To: 'CCAMP' <[e-mail]>
Subject: [CCAMP]Proposed LS text for OIF



Hi CCAMP WG,



During the latest calls on WDM topic, we have prepared an initial draft text for a LS from CCAMP WG to OIF to start sharing information about the control and management of the pluggable optical transceiver modules



Please find below the initial draft text and let us know if you have any comments or suggestions



CCAMP WG would like to inform OIF about the on-going work regarding the control and management of the pluggable optical transceiver modules.

This work can be split in 3 areas:

  1.  Operator use cases and network scenarios needed for the control and management of the packet over optical networks where the optical transceivers are located inside pluggable modules hosted by packet network devices.

These use cases include both coherent and non-coherent optical transceivers.

See: draft-ietf-ccamp-actn-poi-pluggable-usecases-gaps<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-ccamp-actn-poi-pluggable-usecases-gaps/__;!!BhdT!kZ463L6SjbSlUHbHi_oSk39OyqpbbZVtwNL0YKuug54So5bE6d0rBQ1jNhKpPiVw3J4J2u0f4-o8k2f0$>, which is work in progress within CCAMP WG

  1.  YANG data models exposed by host devices or network controllers to provide optical module (pluggable and non pluggable) capabilities, configuration, states, and telemetry data.

See:

  *   draft-ietf-ccamp-rfc9093-bis<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc9093-bis/__;!!BhdT!kZ463L6SjbSlUHbHi_oSk39OyqpbbZVtwNL0YKuug54So5bE6d0rBQ1jNhKpPiVw3J4J2u0f46r8H9qs$>, which has been recently approved (now in the RFC Editor Queue)
  *   draft-ietf-ccamp-optical-impairment-topology-yang<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-ccamp-optical-impairment-topology-yang/__;!!BhdT!kZ463L6SjbSlUHbHi_oSk39OyqpbbZVtwNL0YKuug54So5bE6d0rBQ1jNhKpPiVw3J4J2u0f402yKSoj$>, which has been recently approved (now in the RFC Editor Queue)
  *   draft-ietf-ccamp-wdm-tunnel-yang<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-ccamp-wdm-tunnel-yang/__;!!BhdT!kZ463L6SjbSlUHbHi_oSk39OyqpbbZVtwNL0YKuug54So5bE6d0rBQ1jNhKpPiVw3J4J2u0f40ASZbp0$>, which is work in progress within CCAMP WG
  *   draft-ietf-ccamp-optical-path-computation-yang<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-ccamp-optical-path-computation-yang/__;!!BhdT!kZ463L6SjbSlUHbHi_oSk39OyqpbbZVtwNL0YKuug54So5bE6d0rBQ1jNhKpPiVw3J4J2u0f4wHSnilh$>, which is work in progress within CCAMP WG
  *   draft-ietf-ccamp-dwdm-if-param-yang<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-ccamp-dwdm-if-param-yang/__;!!BhdT!kZ463L6SjbSlUHbHi_oSk39OyqpbbZVtwNL0YKuug54So5bE6d0rBQ1jNhKpPiVw3J4J2u0f4yyj3ggV$>, which is getting ready for CCAMP WG Last Call

  1.  Gap analysis of with respect to existing IETF work (like the drafts in point 2) to identify if there are missing attributes defined in other SDOs/forum (including OIF), addressing the specific aspect of pluggability of transceiver modules.

See: draft-ietf-ccamp-actn-wdm-pluggable-modelling<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-ccamp-actn-wdm-pluggable-modelling/__;!!BhdT!kZ463L6SjbSlUHbHi_oSk39OyqpbbZVtwNL0YKuug54So5bE6d0rBQ1jNhKpPiVw3J4J2u0f4_sehfe3$>, which is work in progress within CCAMP WG

Our understanding is that CMIS, as defined by OIF, and the YANG data models under definition in CCAMP WG are complementary since the CMIS is targeting the interface between the host and the pluggable modules while the YANG data models are targeting the northbound interfaces exposed by hosts or by network controllers. Therefore, we believe that not all the CMIS parameters need to be exposed by the host via YANG, but some of them (e.g., the carrier central frequency) may need to be exposed.

CCAMP WG is pretty confident that our YANG models are already aligned with CMIS 5.3 and C-CMIS 1.4S, and would like to start working on the new features supported by CMIS 5.4, C-CMIS 1.5, and beyond.

The CCAMP WG would appreciate any review from OIF experts on the content, parameter description, gaps and suggestion to improve the IETF documents mentioned above.

The CCAMP WG encourages the use of CCAMP WG mailing list (https://www.ietf.org/mailman/listinfo/ccamp/<https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ccamp/__;!!BhdT!kZ463L6SjbSlUHbHi_oSk39OyqpbbZVtwNL0YKuug54So5bE6d0rBQ1jNhKpPiVw3J4J2u0f4xDIMKMN$>) as the most effective and expedient way of exchanging information, answering questions, and progressing any work.

Given the importance of the Common Management Interface Specification (CMIS) developed by OIF, in the context of management and control of pluggable module, CCAMP WG would ask OIF to share relevant work in progress documents, such as future CMIS and C-CMIS versions, to help CCAMP WG to work in parallel on the required YANG models update and to allow a host implementing the YANG data models defined by IETF CCAMP WG to support also the future CMIS and C-CMIS features.

We are looking forward open and fruitful relationship with OIF to be align the YANG data models developed by IETF following closely the technical progress of CMIS and C-CMIS specifications.

The next OIF meeting is scheduled on November 2-5, 2026 and it would be great if we can finalize and send the LS in time for their considerations at that meeting



Thanks, Italo (on behalf of contributors)