Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal RFC 7252 The Constrained Application Protocol (CoAP) June 2014Ĭopyright (c) 2014 IETF Trust and the persons identified as the Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained at Internet Standards is available in Section 2 of RFC 5741. Internet Engineering Steering Group (IESG).

Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This is an Internet Standards Track document. Such as multicast support, very low overhead, and simplicity for

CoAP is designed to easily interface with HTTPįor integration with the Web while meeting specialized requirements Resources, and includes key concepts of the Web such as URIs and To-machine (M2M) applications such as smart energy and buildingĬoAP provides a request/response interaction model betweenĪpplication endpoints, supports built-in discovery of services and (6LoWPANs) often have high packet error rates and a typical Networks such as IPv6 over Low-Power Wireless Personal Area Networks

Microcontrollers with small amounts of ROM and RAM, while constrained Transfer protocol for use with constrained nodes and constrained

The Constrained Application Protocol (CoAP) is a specialized web The Constrained Application Protocol (CoAP) Updated by: 7959, 8613, 8974, 9175 Errata Exist Internet Engineering Task Force (IETF) Z. RFC 7252: The Constrained Application Protocol (CoAP)

Wise disk cleaner 10.2.4