RFC 9453: Applicability and Use Cases for IPv6 over Networks of Resource-constrained Nodes (6lo)
In plain English — editorial summary, not part of the RFC
This document describes the applicability of IPv6 over constrained-node networks (6lo) and provides practical deployment examples. In addition to IEEE Std 802.15.4, various link-layer technologies are used as examples, such as ITU-T G.9959 (Z-Wave), Bluetooth Low Energy (Bluetooth LE), Digital Enhanced Cordless Telecommunications - Ultra Low Energy (DECT-ULE), Master-Slave/Token Passing (MS/TP), Near Field Communication (NFC), and Power Line Communication (PLC). This document targets an audience who would like to understand and evaluate running end-to-end IPv6 over the constrained-node networks for local or Internet connectivity.
Document record
- Document ID
- RFC9453
- Published
- September 2023
- Authors
- Y. Hong; C. Gomez; Y. Choi; A. Sangi; S. Chakrabarti
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 24
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9461Service Binding Mapping for DNS ServersCurrent
November 2023
- RFC 9462Discovery of Designated ResolversCurrent
November 2023
- RFC 9463DHCP and Router Advertisement Options for the Discovery of Network-designated Resolvers (DNR)Current
November 2023
- RFC 9442Static Context Header Compression (SCHC) over Sigfox Low-Power Wide Area Network (LPWAN)Current
July 2023
- RFC 9441Static Context Header Compression (SCHC) Compound Acknowledgement (ACK)Current
July 2023
- RFC 9434Drone Remote Identification Protocol (DRIP) ArchitectureCurrent
July 2023
- RFC 9433Segment Routing over IPv6 for the Mobile User PlaneCurrent
July 2023
- RFC 9428Transmission of IPv6 Packets over Near Field CommunicationCurrent
July 2023
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?