Applicability Statement: The use of the RPL protocol set in Home Automation and Building Control
draft-ietf-roll-applicability-home-building-00

The information below is for an old version of the document
Document Type Active Internet-Draft (roll WG)
Last updated 2013-05-13
Replaces draft-brandt-roll-rpl-applicability-home-building
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Roll                                                           A. Brandt
Internet-Draft                                             Sigma Designs
Intended status: Informational                               E. Baccelli
Expires: November 14, 2013                                         INRIA
                                                               R. Cragie
                                                               Gridmerge
                                                         P. van der Stok
                                                              Consultant
                                                            May 13, 2013

    Applicability Statement: The use of the RPL protocol set in Home
                    Automation and Building Control
             draft-ietf-roll-applicability-home-building-00

Abstract

   The purpose of this document is to provide guidance in the selection
   and use of RPL protocols to implement the features required in
   building and home environments.

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 November 14, 2013.

Copyright Notice

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

Brandt, et al.         Expires November 14, 2013                [Page 1]
Internet-Draft     RPL protocols in building control            May 2013

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Overview of requirements  . . . . . . . . . . . . . . . .   3
     1.3.  Out of scope requirements . . . . . . . . . . . . . . . .   3
   2.  Deployment Scenario . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Network Topologies  . . . . . . . . . . . . . . . . . . .   4
     2.2.  Traffic Characteristics . . . . . . . . . . . . . . . . .   5
       2.2.1.  Human user responsiveness . . . . . . . . . . . . . .   5
       2.2.2.  Source-sink (SS) communication paradigm . . . . . . .   6
       2.2.3.  Peer-to-peer (P2P) communication paradigm . . . . . .   6
       2.2.4.  Peer-to-multipeer (P2MP) communication paradigm . . .   6
       2.2.5.  RPL applicability per communication paradigm  . . . .   7
     2.3.  Link layer applicability  . . . . . . . . . . . . . . . .   7
   3.  Using RPL-P2P to meet requirements  . . . . . . . . . . . . .   7
   4.  RPL Profile for RPL-P2P . . . . . . . . . . . . . . . . . . .   7
     4.1.  RPL Features  . . . . . . . . . . . . . . . . . . . . . .   7
       4.1.1.  RPL Instances . . . . . . . . . . . . . . . . . . . .   8
       4.1.2.  Non-Storing Mode  . . . . . . . . . . . . . . . . . .   8
       4.1.3.  DAO Policy  . . . . . . . . . . . . . . . . . . . . .   8
       4.1.4.  Path Metrics  . . . . . . . . . . . . . . . . . . . .   8
       4.1.5.  Objective Function  . . . . . . . . . . . . . . . . .   9
       4.1.6.  DODAG Repair  . . . . . . . . . . . . . . . . . . . .   9
       4.1.7.  Multicast . . . . . . . . . . . . . . . . . . . . . .   9
       4.1.8.  Security  . . . . . . . . . . . . . . . . . . . . . .   9
       4.1.9.  P2P communications  . . . . . . . . . . . . . . . . .   9
     4.2.  Layer 2 features  . . . . . . . . . . . . . . . . . . . .   9
       4.2.1.  Security functions provided by layer-2  . . . . . . .  10
       4.2.2.  6LowPAN options assumed . . . . . . . . . . . . . . .  10
       4.2.3.  MLE and other things  . . . . . . . . . . . . . . . .  10
     4.3.  Recommended Configuration Defaults and Ranges . . . . . .  10
   5.  Manageability Considerations  . . . . . . . . . . . . . . . .  10
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
     6.1.  Security Considerations during initial deployment . . . .  10
Show full document text