RFC 5826: Home Automation Routing Requirements in Low-Power and Lossy Networks
In plain English — editorial summary, not part of the RFC
This document presents requirements specific to home control and automation applications for Routing Over Low power and Lossy (ROLL) networks. In the near future, many homes will contain high numbers of wireless devices for a wide set of purposes. Examples include actuators (relay, light dimmer, heating valve), sensors (wall switch, water leak, blood pressure), and advanced controllers (radio-frequency-based AV remote control, central server for light and heat control). Because such devices only cover a limited radio range, routing is often required. The aim of this document is to specify the routing requirements for networks comprising such constrained devices in a home-control and automation environment. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5826
- Published
- April 2010
- Authors
- A. Brandt; J. Buron; G. Porcu
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5548Routing Requirements for Urban Low-Power and Lossy NetworksCurrent
May 2009
- RFC 6551Routing Metrics Used for Path Calculation in Low-Power and Lossy NetworksCurrent
March 2012
- RFC 6997Reactive Discovery of Point-to-Point Routes in Low-Power and Lossy NetworksCurrent
August 2013
- RFC 6998A Mechanism to Measure the Routing Metrics along a Point-to-Point Route in a Low-Power and Lossy NetworkCurrent
August 2013
- RFC 7416A Security Threat Analysis for the Routing Protocol for Low-Power and Lossy Networks (RPLs)Current
January 2015
- RFC 7731Multicast Protocol for Low-Power and Lossy Networks (MPL)Current
February 2016
- RFC 5824Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPNCurrent
April 2010
- RFC 5828Generalized Multiprotocol Label Switching (GMPLS) Ethernet Label Switching Architecture and FrameworkCurrent
March 2010
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?