[Development] FW: [core] RFC 8323 on CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets

Thiago Macieira thiago.macieira at intel.com
Thu Feb 15 17:19:50 CET 2018


[links are broken, but you get the message]

-----Original Message-----
From: core [mailto:core-bounces at ietf.org] On Behalf Of rfc-editor at rfc-
Sent: Wednesday, February 14, 2018 5:35 PM
To: ietf-announce at ietf.org; rfc-dist at rfc-editor.org
Cc: drafts-update-ref at iana.org; core at ietf.org; rfc-editor at rfc-editor.org
Subject: [core] RFC 8323 on CoAP (Constrained Application Protocol) over TCP, 
TLS, and WebSockets

A new Request for Comments is now available in online RFC libraries.

        RFC 8323

        Title:      CoAP (Constrained Application Protocol) over 
                    TCP, TLS, and WebSockets 
        Author:     C. Bormann, 
                    S. Lemay,
                    H. Tschofenig,
                    K. Hartke,
                    B. Silverajan,
                    B. Raymor, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2018
        Mailbox:    cabo at tzi.org, 
                    slemay at zebra.com, 
                    Hannes.Tschofenig at gmx.net,
                    hartke at tzi.org, 
                    Bilhanan.Silverajan at tut.fi,
                    brianraymor at hotmail.com
        Pages:      54
        Characters: 110771
        Updates:    RFC 7641, RFC 7959

        I-D Tag:    draft-ietf-core-coap-tcp-tls-11.txt

        URL:        https://na01.safelinks.protection.outlook.com/?url=https

        DOI:        10.17487/RFC8323

The Constrained Application Protocol (CoAP), although inspired by HTTP, was 
designed to use UDP instead of TCP.  The message layer of CoAP over UDP 
includes support for reliable delivery, simple congestion control, and flow 

Some environments benefit from the availability of CoAP carried over reliable 
transports such as TCP or Transport Layer Security (TLS).
This document outlines the changes required to use CoAP over TCP, TLS, and 
WebSockets transports.  It also formally updates RFC 7641 for use with these 
transports and RFC 7959 to enable the use of larger messages over a reliable 

This document is a product of the Constrained RESTful Environments Working 
Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track protocol 
for the Internet community, and requests discussion and suggestions for 
improvements.  Please refer to the current edition of the Official Internet 
Protocol Standards (https://na01.safelinks.protection.outlook.com/?url=https
%7C-1&sdata=ZLUTQDmkGqerQ3YAFZRAt6qspHyABJOwC53R2QAzGDE%3D&reserved=0) for the 
standardization state and status of this protocol.  Distribution of this memo 
is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
Requests for special distribution should be addressed to either the author of 
the RFC in question, or to rfc-editor at rfc-editor.org.  Unless specifically 
noted otherwise on the RFC itself, all RFCs are for unlimited distribution.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

More information about the Development mailing list