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

The information below is for an old version of the document
Document Type Active Internet-Draft (roll WG)
Last updated 2015-07-02
Replaces draft-brandt-roll-rpl-applicability-home-building
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Yvonne-Anne Pignolet
Shepherd write-up Show (last changed 2015-03-09)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Needs 7 more YES or NO OBJECTION positions to pass.
Responsible AD Alvaro Retana
Send notices to roll-chairs@ietf.org, draft-ietf-roll-applicability-home-building.ad@ietf.org, draft-ietf-roll-applicability-home-building@ietf.org, yvonneanne.pignolet@gmail.com, draft-ietf-roll-applicability-home-building.shepherd@ietf.org
IANA IANA review state Version Changed - Review Needed
IANA action state None
Roll                                                           A. Brandt
Internet-Draft                                             Sigma Designs
Intended status: Standards Track                             E. Baccelli
Expires: January 3, 2016                                           INRIA
                                                               R. Cragie
                                                                ARM Ltd.
                                                         P. van der Stok
                                                              Consultant
                                                            July 2, 2015

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

Abstract

   The purpose of this document is to provide guidance in the selection
   and use of protocols from the RPL protocol suite to implement the
   features required for control 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 January 3, 2016.

Copyright Notice

   Copyright (c) 2015 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 January 3, 2016                [Page 1]

Internet-Draft          RPL in home and building               July 2015

   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.  Relationship to other documents . . . . . . . . . . . . .   4
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Required Reading  . . . . . . . . . . . . . . . . . . . .   5
     1.4.  Out of scope requirements . . . . . . . . . . . . . . . .   5
   2.  Deployment Scenario . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Network Topologies  . . . . . . . . . . . . . . . . . . .   6
     2.2.  Traffic Characteristics . . . . . . . . . . . . . . . . .   7
       2.2.1.  General . . . . . . . . . . . . . . . . . . . . . . .   8
       2.2.2.  Source-sink (SS) communication paradigm . . . . . . .   8
       2.2.3.  Publish-subscribe (PS, or pub/sub)) communication
               paradigm  . . . . . . . . . . . . . . . . . . . . . .   9
       2.2.4.  Peer-to-peer (P2P) communication paradigm . . . . . .   9
       2.2.5.  Peer-to-multipeer (P2MP) communication paradigm . . .  10
       2.2.6.  Additional considerations: Duocast and N-cast . . . .  10
       2.2.7.  RPL applicability per communication paradigm  . . . .  10
     2.3.  Layer-2 applicability . . . . . . . . . . . . . . . . . .  11
   3.  Using RPL to meet Functional Requirements . . . . . . . . . .  12
   4.  RPL Profile . . . . . . . . . . . . . . . . . . . . . . . . .  13
     4.1.  RPL Features  . . . . . . . . . . . . . . . . . . . . . .  13
       4.1.1.  RPL Instances . . . . . . . . . . . . . . . . . . . .  13
       4.1.2.  Storing vs. Non-Storing Mode  . . . . . . . . . . . .  14
       4.1.3.  DAO Policy  . . . . . . . . . . . . . . . . . . . . .  14
       4.1.4.  Path Metrics  . . . . . . . . . . . . . . . . . . . .  14
       4.1.5.  Objective Function  . . . . . . . . . . . . . . . . .  14
       4.1.6.  DODAG Repair  . . . . . . . . . . . . . . . . . . . .  14
       4.1.7.  Multicast . . . . . . . . . . . . . . . . . . . . . .  15
       4.1.8.  Security  . . . . . . . . . . . . . . . . . . . . . .  16
       4.1.9.  P2P communications  . . . . . . . . . . . . . . . . .  19
       4.1.10. IPv6 address configuration  . . . . . . . . . . . . .  19
     4.2.  Layer 2 features  . . . . . . . . . . . . . . . . . . . .  19
Show full document text