Liaison statement
Title: LS on initiation of new work item Q.TSTP_CoAP “Test suite structure and test purposes for conformance testing of the Constrained Application Protocol (CoAP)”

Additional information about IETF liaison relationships is available on the IETF webpage and the Internet Architecture Board liaison webpage.
State Posted
Submitted Date 2026-04-27
From Group ITU-T-SG-11
From Contact tsbsg11@itu.int
To Group core
To Contacts Marco Tiloca <marco.tiloca@ri.se>
Jaime Jimenez <jaime@iki.fi>
Carsten Bormann <cabo@tzi.org>
Cc Mike Bishop <mbishop@evequefou.be>
Carsten Bormann <cabo@tzi.org>
Constrained RESTful Environments Discussion List <core@ietf.org>
Scott Mansfield <Scott.Mansfield@Ericsson.com>
Marco Tiloca <marco.tiloca@ri.se>
Jaime Jimenez <jaime@iki.fi>
Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Response Contact tejpal.singh70@gov.in
anshulkr.gupta@gov.in
Technical Contact tejpal.singh70@gov.in
Action Holder Contacts scott.mansfield@ericsson.com
Purpose For information
Attachments A.1 justification for proposed draft new recommendation ITU-T Q.TSTP_CoAP
Body 
During the ITU-T Study Group 11 meeting (Geneva, 3-11 March 2026),
Q12/11(Testing of internet of things, its applications and identification
systems) has initiated the new work item Q.TSTP_CoAP “Test suite structure and
test purposes for conformance testing of the Constrained Application Protocol
(CoAP)”.

Q.TSTP_CoAP proposes to cover test suite structure and test purposes for
conformance testing of the Constrained Application Protocol (CoAP), as
specified in IETF RFC 7252 and related extensions. It will cover conformance
requirements applicable to both CoAP client and CoAP server implementations
deployed in constrained IoT environments. This draft Recommendation will be
developed as a protocol-specific complement to the draft new recommendation
ITU-T Q.TFCT_IoT framework and will align with ITU-T testing methodologies.
Security-specific test requirements are out of scope of this draft
Recommendation.

ITU-T SG11 would like to thank ITU-T SG20, IETF and oneM2M for your attention
and cooperation on this topic.