Title: LS on consent of draft new Recommendation ITU-T Q.3065 (ex Q.SFCO) 
“Signalling requirements and data models for service function chaining 
orchestration based on SRv6”
Submission Date: 2026-01-19
URL of the IETF Web page: https://datatracker.ietf.org/liaison/2100/

To: Source Packet Routing in Networking (spring)
From: ITU-T SG 11
Purpose: For information


Email Addresses
---------------
From: [email protected]
To: Bruno Decraene <[email protected]>,Alvaro Retana 
<[email protected]>,Joel Halpern <[email protected]>
Cc: Jim Guichard <[email protected]>,Source Packet Routing in 
Networking Discussion List <[email protected]>,Joel Halpern 
<[email protected]>,Gunter Van de Velde 
<[email protected]>,Scott Mansfield 
<[email protected]>,Bruno Decraene <[email protected]>,Ketan 
Talaulikar <[email protected]>,Alvaro Retana <[email protected]>
Response Contacts: [email protected]
[email protected]
[email protected]
Technical Contacts: [email protected]


Body: ITU-T Study Group 11 would like to inform ITU-T SG13 and IETF Spring WG 
about the progress of draft new Recommendation ITU-T Q.3065 (ex Q.SFCO) 
“Signalling requirements and data models for service function chaining 
orchestration based on SRv6”, which was consented at the ITU-T SG11 meeting, 
Geneva, 17-26 November 2025.

This draft Recommendation specifies the architecture, signalling requirements, 
signalling procedures and data models for service function chaining 
orchestration based on SRv6.

ITU-T Study Group 11 looks forward to keeping continued collaboration and 
exchanging information with ITU-T SG13 and IETF Spring WG on this topic.
Attachments:

    Consent - draft Recommendation ITU-T Q.3065 (ex Q.SFCO) 
    
https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2026-01-19-itu-t-sg-11-spring-ls-on-consent-of-draft-new-recommendation-itu-t-q3065-ex-qsfco-signalling-requirements-and-data-models-for-ser-attachment-1.pdf


_______________________________________________
spring mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to