






Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
This ppt discusses about the need of CoAP, the need of RESTful framework, CoAP working, and CoAP methods,Californium overview, security with DTLS and open research problems.
Typology: Slides
1 / 10
This page cannot be seen from the preview
Don't miss anything!







The Internet of Things: What & Why IPv6's vast address space has enabled the vision of a Web of Things โ smart devices uniquely identified, communicating seamlessly, and interacting intelligently with their environment. Unique Identity Every device is a distinct object, addressable and integrated into the global network. Intelligent Communication Devices exchange data autonomously, sensing and responding to their environment. IPv6 Scale Billions of endpoints become possible, making IoT a global-scale reality.
Client-Server
Stateless
Cacheable & Layered
Uniform Interface
CoRE & CoAP: Designed for Constraints Why Not Plain REST? HTTP's complex headers, TCP overhead, and XML parsing are ill-suited for constrained networks like 6LoWPAN. CoRE (Constrained RESTful Environments) addresses these gaps with a lightweight application layer. CoAP is built on UDP โ not TCP โ reducing overhead while retaining REST semantics like GET, PUT, POST, and DELETE.
CoAP: Methods & Response Codes Request Methods GET Retrieve resource โ safe & idempotent POST Process representation โ neither safe nor idempotent PUT Create or update resource โ idempotent DELETE Remove resource โ idempotent Response Code Classes 2.xx โ Success 2.01 Created ยท 2.04 Changed ยท 2.05 Content 4.xx โ Client Error 4.00 Bad Request ยท 4.04 Not Found ยท 4.01 Unauthorized 5.xx โ Server Error 5.00 Internal Error ยท 5.03 Service Unavailable
CoAP: Security with DTLS CoAP uses DTLS (Datagram Transport Layer Security) to secure UDP communications. Four security modes balance protection with device capability. 1 NoSec DTLS disabled โ suitable only for trusted, isolated networks. 2 PreSharedKey DTLS enabled with pre-shared symmetric keys โ lightweight and fast. 3 RawPublicKey DTLS with a raw asymmetric public key โ no certificate chain needed. 4 Certificate Full X.509 certificate with asymmetric key pair โ highest assurance.
Open Research Problems & Takeaways ๐ Security Gaps Multicast security semantics remain undefined; end-to-end DTLS/TLS mapping at proxies needs standardization. ๐ Connectivity Resilience How do CoAP systems behave when internet connectivity is lost? Safety fallback mechanisms are an open area. ๐ Physical Layer Challenges Path loss, signal power, and energy-efficient communication in lossy networks require further study. Key Takeaway: CoAP brings RESTful web architecture to constrained devices โ enabling scalable, interoperable IoT through UDP efficiency, DTLS security, and frameworks like Californium.