Applicability Statement for the Routing Protocol for Low Power and Lossy Networks (RPL) in AMI Networks
draft-ietf-roll-applicability-ami-08

The information below is for an old version of the document
Document Type Active Internet-Draft (roll WG)
Authors Daniel Popa  , Matthew Gillmore  , Laurent Toutain  , Jonathan Hui  , Kazuya Monden  , Ruben Salazar 
Last updated 2014-02-14
Replaces draft-popa-roll-applicability-ami
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd Michael Richardson
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Roll                                                             D. Popa
Internet-Draft                                               M. Gillmore
Intended status: Standards Track                              Itron, Inc
Expires: August 03, 2014                                      L. Toutain
                                                        Telecom Bretagne
                                                                  J. Hui
                                                                   Cisco
                                                                R. Ruben
                                                              Landis+Gyr
                                                               K. Monden
                             Hitachi, Ltd., Yokohama Research Laboratory
                                                           February 2014

Applicability Statement for the Routing Protocol for Low Power and Lossy
                     Networks (RPL) in AMI Networks
                  draft-ietf-roll-applicability-ami-08

Abstract

   This document discusses the applicability of RPL in Advanced Metering
   Infrastructure (AMI) networks.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 03, 2014.

Copyright Notice

   Copyright (c) 2014 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

Popa, Gillmore, Toutain,ExpiresuAugustM03, 2014                 [Page 1]

Internet-Draft         RPL Applicability for AMI           February 2014

   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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
     1.1.  Requirements Language  . . . . . . . . . . . . . . . . . .  3
     1.2.  Required Reading . . . . . . . . . . . . . . . . . . . . .  3
     1.3.  Out of scope requirements  . . . . . . . . . . . . . . . .  3
   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 .  8
   5.  Layer 2 applicability. . . . . . . . . . . . . . . . . . . . .  9
     5.1.  IEEE Wireless Technology . . . . . . . . . . . . . . . . .  9
     5.2.  IEEE PowerLine 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.  Storing vs. Non-Storing Mode . . . . . . . . . . . . . 11
       7.1.3.  DAO Policy . . . . . . . . . . . . . . . . . . . . . . 11
       7.1.4.  Path Metrics . . . . . . . . . . . . . . . . . . . . . 11
       7.1.5.  Objective Function . . . . . . . . . . . . . . . . . . 12
       7.1.6.  DODAG Repair . . . . . . . . . . . . . . . . . . . . . 12
       7.1.7.  Multicast  . . . . . . . . . . . . . . . . . . . . . . 13
       7.1.8.  Security . . . . . . . . . . . . . . . . . . . . . . . 13
       7.1.9.  Peer-to-Peer communications  . . . . . . . . . . . . . 13
     7.2.  Description of Layer-two features  . . . . . . . . . . . . 13
       7.2.1.  IEEE 1901.2 PHY and MAC sub-layer features . . . . . . 13
       7.2.2.  IEEE 802.15.4 (g + e) PHY and MAC features . . . . . . 14
       7.2.3.  IEEE MAC sub-layer Security Features . . . . . . . . . 14
     7.3.  6LowPAN Options  . . . . . . . . . . . . . . . . . . . . . 16
     7.4.  Recommended Configuration Defaults and Ranges  . . . . . . 16
       7.4.1.  Trickle Parameters . . . . . . . . . . . . . . . . . . 16
       7.4.2.  Other Parameters . . . . . . . . . . . . . . . . . . . 18
   8.  Manageability Considerations . . . . . . . . . . . . . . . . . 18
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 19
     9.1.  Security Considerations during initial deployment  . . . . 19
     9.2.  Security Considerations during incremental deployment  . . 19
   10. Other Related Protocols  . . . . . . . . . . . . . . . . . . . 20
   11. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 20
   12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20
   13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
     13.1.  Informative References  . . . . . . . . . . . . . . . . . 20
     13.2.  Normative references  . . . . . . . . . . . . . . . . . . 20
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21

Popa, Gillmore, Toutain,ExpiresuAugustM03, 2014                 [Page 2]
Show full document text