Applicability Statement for the Routing Protocol for Low-Power and Lossy Networks (RPL) in Advanced Metering Infrastructure (AMI) Networks
RFC 8036
Internet Engineering Task Force (IETF) N. Cam-Winget, Ed.
Request for Comments: 8036 Cisco Systems
Category: Standards Track J. Hui
ISSN: 2070-1721 Nest
D. Popa
Itron, Inc
January 2017
Applicability Statement for
the Routing Protocol for Low-Power and Lossy Networks (RPL) in
Advanced Metering Infrastructure (AMI) Networks
Abstract
This document discusses the applicability of the Routing Protocol for
Low-Power and Lossy Networks (RPL) in Advanced Metering
Infrastructure (AMI) networks.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8036.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Cam-Winget, et al. Standards Track [Page 1]
RFC 8036 RPL Applicability for AMI January 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.2. Required Reading . . . . . . . . . . . . . . . . . . . . 3
1.3. Out-of-Scope Requirements . . . . . . . . . . . . . . . . 4
2. Routing Protocol for LLNs (RPL) . . . . . . . . . . . . . . . 4
3. Description of AMI Networks for Electric Meters . . . . . . . 4
3.1. Deployment Scenarios . . . . . . . . . . . . . . . . . . 5
4. Smart Grid Traffic Description . . . . . . . . . . . . . . . 7
4.1. Smart Grid Traffic Characteristics . . . . . . . . . . . 7
4.2. Smart Grid Traffic QoS Requirements . . . . . . . . . . . 8
4.3. RPL Applicability per Smart Grid Traffic Characteristics 9
5. Layer-2 Applicability . . . . . . . . . . . . . . . . . . . . 9
5.1. IEEE Wireless Technology . . . . . . . . . . . . . . . . 9
5.2. IEEE Power Line Communication (PLC) Technology . . . . . 9
6. Using RPL to Meet Functional Requirements . . . . . . . . . . 10
7. RPL Profile . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. RPL Features . . . . . . . . . . . . . . . . . . . . . . 11
7.1.1. RPL Instances . . . . . . . . . . . . . . . . . . . . 11
7.1.2. DAO Policy . . . . . . . . . . . . . . . . . . . . . 11
7.1.3. Path Metrics . . . . . . . . . . . . . . . . . . . . 11
7.1.4. Objective Function . . . . . . . . . . . . . . . . . 12
7.1.5. DODAG Repair . . . . . . . . . . . . . . . . . . . . 12
7.1.6. Multicast . . . . . . . . . . . . . . . . . . . . . . 12
7.1.7. Security . . . . . . . . . . . . . . . . . . . . . . 13
7.2. Description of Layer-2 Features . . . . . . . . . . . . . 13
7.2.1. IEEE 1901.2 PHY and MAC Sub-layer Features . . . . . 13
7.2.2. IEEE 802.15.4 (Amendments G and E) PHY and MAC
Features . . . . . . . . . . . . . . . . . . . . . . 14
7.2.3. IEEE MAC Sub-layer Security Features . . . . . . . . 15
7.3. 6LowPAN Options . . . . . . . . . . . . . . . . . . . . . 17
7.4. Recommended Configuration Defaults and Ranges . . . . . . 17
7.4.1. Trickle Parameters . . . . . . . . . . . . . . . . . 17
7.4.2. Other Parameters . . . . . . . . . . . . . . . . . . 18
8. Manageability Considerations . . . . . . . . . . . . . . . . 18
9. Security Considerations . . . . . . . . . . . . . . . . . . . 19
9.1. Security Considerations during Initial Deployment . . . . 20
9.2. Security Considerations during Incremental Deployment . . 20
Show full document text