Skip to main content

Liaison statement
Response to LSout to IETF on the Optical Cloud Networks (OCN)

Additional information about IETF liaison relationships is available on the IETF webpage and the Internet Architecture Board liaison webpage.
State Posted
Submitted Date 2025-01-27
From Group RTG
From Contact John Scudder
To Group ETSI-ISG-F5G
To Contacts marcus.brunner@huawei.com
Cc Gunter Van de Velde <gunter.van_de_velde@nokia.com>
The IETF Chair <chair@ietf.org>
John Scudder <jgs@juniper.net>
Jim Guichard <james.n.guichard@futurewei.com>
Response Contact John Scudder <jgs@juniper.net>
Jim Guichard <james.n.guichard@futurewei.com>
Gunter Van de Velde <gunter.van_de_velde@nokia.com>
Technical Contact ccamp-chairs@ietf.org
Purpose In response
Attachments (None)
Liaisons referred by this one LSout to IETF on the Optical Cloud Networks (OCN)
Liaisons referring to this one LSreply to IETF on the Optical Cloud Networks (OCN)
Body
Dear ETSI ISG F5G Liaison,

Thank you for your liaison statement regarding the OCN architecture and your
request for the IETF to consider defining the relevant protocols to support OSP
connection and service control functions. We appreciate your recognition of the
IETF as a natural standards organization for such efforts and your willingness
to collaborate on this topic.

As a contribution-driven organization, the IETF encourages proposals and
contributions from interested parties to progress work in alignment with our
goals and processes. If there is interest in advancing protocol definitions for
the OSP connection and service control functions within the IETF, we recommend
the following steps:

1. Engage with Relevant Working Groups:
   Potential contributors should identify and engage with IETF Working Groups
   that align with the proposed scope of work. Existing protocols mentioned in
   the liaison could be reviewed for applicability and extension within those
   groups. From the text of the liaison we tend to think that the CCAMP working
   group is the right one to submit a contribution to. If this is not the case,
   the chairs of the routing area will work together to find out the proper
   home/homes for your work.

2. Submit an Internet-Draft:
   The IETF process is initiated through the submission of Internet-Drafts that
   outline specific proposals. These drafts provide the basis for discussion
   and potential standardization. Guidance on submitting an Internet-Draft can
   be found on the [IETF website](https://www.ietf.org/standards/ids/).

3. Participate in IETF Meetings and Mailing Lists:
   Active participation in relevant IETF meetings and discussions on Working
   Group mailing lists is encouraged. This engagement ensures alignment of
   efforts and fosters collaboration among stakeholders.

We welcome contributions from ETSI ISG F5G participants and other interested
parties to explore how existing IETF protocols could be extended or how new
protocols might be developed to address these requirements. The IETF remains
committed to maintaining an open and transparent process to ensure broad
consensus and the development of robust standards.

As your next meeting is scheduled for February 25-28, 2025, we aim to provide
this initial response as an invitation to further collaboration. Should you or
your members have specific drafts or proposals to discuss, we would be pleased
to consider them through the standard IETF process.

We look forward to continued collaboration between ETSI ISG F5G and the IETF.

Best regards,

--John Scudder, for the IETF Routing Area