RFC 7102: Terms Used in Routing for Low-Power and Lossy Networks
In plain English — editorial summary, not part of the RFC
This document provides a glossary of terminology used in routing requirements and solutions for networks referred to as Low-Power and Lossy Networks (LLNs). An LLN is typically composed of many embedded devices with limited power, memory, and processing resources interconnected by a variety of links. There is a wide scope of application areas for LLNs, including industrial monitoring, building automation (e.g., heating, ventilation, air conditioning, lighting, access control, fire), connected home, health care, environmental monitoring, urban sensor networks, energy management, assets tracking, and refrigeration.
Document record
- Document ID
- RFC7102
- Published
- January 2014
- Authors
- JP. Vasseur
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7096Evaluation of Existing GMPLS Encoding against G.709v3 Optical Transport Networks (OTNs)Current
January 2014
- RFC 7110Return Path Specified Label Switched Path (LSP) PingUpdated
January 2014
- RFC 7115Origin Validation Operation Based on the Resource Public Key Infrastructure (RPKI)Current
January 2014
- RFC 7087A Thesaurus for the Interpretation of Terminology Used in MPLS Transport Profile (MPLS-TP) Internet-Drafts and RFCs in the Context of the ITU-T's Transport Network RecommendationsCurrent
December 2013
- RFC 7117Multicast in Virtual Private LAN Service (VPLS)Current
February 2014
- RFC 7121High Availability within a Forwarding and Control Element Separation (ForCES) Network ElementUpdated
February 2014
- RFC 7080Virtual Private LAN Service (VPLS) Interoperability with Provider Backbone BridgesCurrent
December 2013
- RFC 7079The Pseudowire (PW) and Virtual Circuit Connectivity Verification (VCCV) Implementation Survey ResultsCurrent
November 2013
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?