Title: LS on initiation of new work item Q.SFCP "Monitoring parameters for 
service function orchestration based on service function chaining"
Submission Date: 2026-01-19
URL of the IETF Web page: https://datatracker.ietf.org/liaison/2102/

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]
Technical Contacts: [email protected]


Body: ITU-T Study Group 11 would like to inform SG13 and IETF SPRING about the 
initiation of new work item Q.SFCP "Monitoring parameters for service function 
orchestration based on service function chaining", which was started at the 
ITU-T SG11 meeting, Geneva, 17-26 November 2025.

This draft Recommendation aims to provide monitoring parameters for service 
function orchestration based on service function chaining, and ensures the 
availability and service experience of SFCs through joint monitoring of the 
service layer, orchestration layer, control layer, and infrastructure layer.

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

    Output - draft baseline of new work item Q.SFCP
    
https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2026-01-19-itu-t-sg-11-spring-ls-on-initiation-of-new-work-item-qsfcp-monitoring-parameters-for-service-function-orchestration-based-on-service-attachment-1.pdf


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

Reply via email to