Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 8323

CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets,February 2018

File formats:
icon for text fileicon for PDFicon for HTML
Status:
PROPOSED STANDARD
Updates:
RFC 7641,RFC 7959
Updated by:
RFC 8974
Authors:
C. Bormann
S. Lemay
H. Tschofenig
K. Hartke
B. Silverajan
B. Raymor, Ed.
Stream:
IETF
Source:
core (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8323

Discuss this RFC: Send questions or comments to the mailing listcore@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8323


Abstract

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

Some environments benefit from the availability of CoAP carried overreliable 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 7641for use with these transports and RFC 7959 to enable the use oflarger messages over a reliable transport.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp