Routing Requirements for Urban Low-Power and Lossy Networks
RFC 5548, “Routing Requirements for Urban Low-Power and Lossy Networks”, is an Informational document published in May 2009 by M. Dohler, T. Watteyne, T. Winter, D. Barthel. The canonical text is published by the RFC Editor.
Abstract
The application-specific routing requirements for Urban Low-Power and Lossy Networks (U-LLNs) are presented in this document. In the near future, sensing and actuating nodes will be placed outdoors in urban environments so as to improve people's living conditions as well as to monitor compliance with increasingly strict environmental laws. These field nodes are expected to measure and report a wide gamut of data (for example, the data required by applications that perform smart-metering or that monitor meteorological, pollution, and allergy conditions). The majority of these nodes are expected to communicate wirelessly over a variety of links such as IEEE 802.15.4, low-power IEEE 802.11, or IEEE 802.15.1 (Bluetooth), which given the limited radio range and the large number of nodes requires the use of suitable routing protocols. The design of such protocols will be mainly impacted by the limited resources of the nodes (memory, processing power, battery, etc.) and the particularities of the outdoor urban application scenarios. As such, for a wireless solution for Routing Over Low-Power and Lossy (ROLL) networks to be useful, the protocol(s) ought to be energy-efficient, scalable, and autonomous. This documents aims to specify a set of IPv6 routing requirements reflecting these and further U-LLNs' tailored characteristics. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5548 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5547 A Session Description Protocol Offer/Answer Mechanism to Enable File Transfer
- RFC 5549 Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop
- RFC 5546 iCalendar Transport-Independent Interoperability Protocol
- RFC 5550 The Internet Email to Support Diverse Service Environments Profile
- RFC 5545 Internet Calendaring and Scheduling Core Object Specification
- RFC 5551 Lemonade Notifications Architecture
- RFC 5552 SIP Interface to VoiceXML Media Services
- RFC 5543 BGP Traffic Engineering Attribute