CoAP Plugfest at IETF-78 in Maastricht

CoAP Plugfest at IETF-78 in Maastricht

• When: July 25th from 10-16 CET. TBD: A second plugfest repeat likely to also be held sometime during the week for those that can't make Sunday.
• Where: Maastricht MECC (room TBD) and the Internet
• What: Implementation, interop and specification testing of CoAP
• Protocol: draft-ietf-core-coap-01
• Experimental: draft-bormann-coap-misc, draft-hartke-coap-observe, draft-eggert-core-congestion-control

Plugfest Technical Information

• Chat: irc.freenode.net #coap
• Default port: 61616
• IP version: IPv6 by default, IPv4 optional

coap-01 test servers already on-line

• coap://ns.tzi.org:61616/

• Basic header and option header support
• Content-Type and Uri-Path Option support
• GET support
• Synchronous transactions with CON, NON, ACK, RST
• Unicast and multicast support (no retransmission)

Minimal CoAP server configuration

• Basic header and option header support
• Content-Type and Uri-Path Option support
• GET support
• Synchronous transactions with CON, NON, ACK, RST
• Static /.well-known/r resource list
• Unicast and multicast support

Minimal CoAP proxy configuration
Just in case someone wants to try out proxying (CoAP-CoAP or CoAP-HTTP), here are the minimal requirements in addition to those above:

• Uri-Scheme and Uri-Authority support
• Caching, Max-Age and Etag support

Optional feature sets

• POST, PUT, DELETE support
• Asynchronous transaction support
• Retransmission
• Max-Age, Etag and Location Option support
• Caching
• Dynamic /.well-known/r with query string support

Experimental features for verification

• Congestion control mechanisms (draft-eggert-core-congestion-control)
• Subscription (draft-hartke-coap-observe)
• Proposed duration format (draft-bormann-coap-misc)
• Accept Option Header (draft-bormann-coap-misc)
• 30X redirect responses

Source: IETF