RFC 8387: Practical Considerations and Implementation Experiences in Securing Smart Object Networks
In plain English — editorial summary, not part of the RFC
This memo describes challenges associated with securing resource- constrained smart object devices. The memo describes a possible deployment model where resource-constrained devices sign message objects, discusses the availability of cryptographic libraries for resource-constrained devices, and presents some preliminary experiences with those libraries for message signing on resource- constrained devices. Lastly, the memo discusses trade-offs involving different types of security approaches.
Document record
- Document ID
- RFC8387
- Published
- May 2018
- Authors
- M. Sethi; J. Arkko; A. Keranen; H. Back
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 33
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9770Notification of Revoked Access Tokens in the Authentication and Authorization for Constrained Environments (ACE) FrameworkCurrent
June 2025
- RFC 9787Guidance on End-to-End Email SecurityCurrent
August 2025
- RFC 8352Energy-Efficient Features of Internet of Things ProtocolsCurrent
April 2018
- RFC 8915Network Time Security for the Network Time ProtocolCurrent
September 2020
- RFC 9172Bundle Protocol Security (BPSec)Current
January 2022
- RFC 9173Default Security Contexts for Bundle Protocol Security (BPSec)Current
January 2022
- RFC 8323CoAP (Constrained Application Protocol) over TCP, TLS, and WebSocketsUpdated
February 2018
- RFC 8152CBOR Object Signing and Encryption (COSE)Obsoleted
July 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?