RFC 5867: Building Automation Routing Requirements in Low-Power and Lossy Networks
In plain English — editorial summary, not part of the RFC
The Routing Over Low-Power and Lossy (ROLL) networks Working Group has been chartered to work on routing solutions for Low-Power and Lossy Networks (LLNs) in various markets: industrial, commercial (building), home, and urban networks. Pursuant to this effort, this document defines the IPv6 routing requirements for building automation. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5867
- Published
- June 2010
- Authors
- J. Martocci; P. De Mil; N. Riou; W. Vermeylen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 26
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5862Path Computation Clients (PCC) - Path Computation Element (PCE) Requirements for Point-to-Multipoint MPLS-TECurrent
June 2010
- RFC 5860Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport NetworksCurrent
May 2010
- RFC 5880Bidirectional Forwarding Detection (BFD)Updated
June 2010
- RFC 5881Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)Current
June 2010
- RFC 5882Generic Application of Bidirectional Forwarding Detection (BFD)Current
June 2010
- RFC 5852RSVP-TE Signaling Extension for LSP Handover from the Management Plane to the Control Plane in a GMPLS-Enabled Transport NetworkCurrent
April 2010
- RFC 5883Bidirectional Forwarding Detection (BFD) for Multihop PathsCurrent
June 2010
- RFC 5884Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)Updated
June 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?