RFC 6568: Design and Application Spaces for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)
In plain English — editorial summary, not part of the RFC
This document investigates potential application scenarios and use cases for low-power wireless personal area networks (LoWPANs). This document provides dimensions of design space for LoWPAN applications. A list of use cases and market domains that may benefit and motivate the work currently done in the 6LoWPAN Working Group is provided with the characteristics of each dimension. A complete list of practical use cases is not the goal of this document. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6568
- Published
- April 2012
- Authors
- E. Kim; D. Kaspar; JP. Vasseur
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 28
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6572RADIUS Support for Proxy Mobile IPv6Updated
June 2012
- RFC 6564A Uniform Format for IPv6 Extension HeadersCurrent
April 2012
- RFC 6554An IPv6 Routing Header for Source Routes with the Routing Protocol for Low-Power and Lossy Networks (RPL)Current
March 2012
- RFC 6553The Routing Protocol for Low-Power and Lossy Networks (RPL) Option for Carrying RPL Information in Data-Plane DatagramsUpdated
March 2012
- RFC 6547RFC 3627 to Historic StatusCurrent
February 2012
- RFC 6540IPv6 Support Required for All IP-Capable NodesCurrent
April 2012
- RFC 6602Bulk Binding Update Support for Proxy Mobile IPv6Current
May 2012
- RFC 6603Prefix Exclude Option for DHCPv6-based Prefix DelegationCurrent
May 2012
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?