draft-ietf-roll-applicability-template-06.txt   draft-ietf-roll-applicability-template-07.txt 
Network Working Group M. Richardson Network Working Group M. Richardson
Internet-Draft SSW Internet-Draft SSW
Intended status: Informational November 10, 2014 Intended status: Informational May 11, 2015
Expires: May 14, 2015 Expires: November 12, 2015
ROLL Applicability Statement Template ROLL Applicability Statement Template
draft-ietf-roll-applicability-template-06 draft-ietf-roll-applicability-template-07
Abstract Abstract
This document is a template applicability statement for the Routing This document is a template applicability statement for the Routing
over Low-power and Lossy Networks (ROLL) WG. This document is not over Low-power and Lossy Networks (ROLL) WG. This document is not
for publication, but rather is to be used as a template. for publication, but rather is to be used as a template.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 14, 2015. This Internet-Draft will expire on November 12, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Relationship to other documents . . . . . . . . . . . . . 3 1.1. Relationship to other documents . . . . . . . . . . . . . 3
1.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 4
1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
1.4. Required Reading . . . . . . . . . . . . . . . . . . . . 4 1.4. Required Reading . . . . . . . . . . . . . . . . . . . . 4
1.5. Out of scope requirements . . . . . . . . . . . . . . . . 4 1.5. Out of scope requirements . . . . . . . . . . . . . . . . 4
2. Deployment Scenario . . . . . . . . . . . . . . . . . . . . . 4 2. Deployment Scenario . . . . . . . . . . . . . . . . . . . . . 4
2.1. Network Topologies . . . . . . . . . . . . . . . . . . . 4 2.1. Network Topologies . . . . . . . . . . . . . . . . . . . 4
2.2. Traffic Characteristics . . . . . . . . . . . . . . . . . 4 2.2. Traffic Characteristics . . . . . . . . . . . . . . . . . 4
2.2.1. General . . . . . . . . . . . . . . . . . . . . . . . 4 2.2.1. General . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.2. Source-sink (SS) communication paradigm . . . . . . . 4 2.2.2. Source-sink (SS) communication paradigm . . . . . . . 5
2.2.3. Publish-subscribe (PS, or pub/sub) communication 2.2.3. Publish-subscribe (PS, or pub/sub) communication
paradigm . . . . . . . . . . . . . . . . . . . . . . 4 paradigm . . . . . . . . . . . . . . . . . . . . . . 5
2.2.4. Peer-to-peer (P2P) communication paradigm . . . . . . 4 2.2.4. Peer-to-peer (P2P) communication paradigm . . . . . . 5
2.2.5. Peer-to-multipeer (P2MP) communication paradigm . . . 4 2.2.5. Peer-to-multipeer (P2MP) communication paradigm . . . 5
2.2.6. Additional considerations: Duocast and N-cast . . . . 5 2.2.6. Additional considerations: Duocast and N-cast . . . . 5
2.2.7. RPL applicability per communication paradigm . . . . 5 2.2.7. RPL applicability per communication paradigm . . . . 5
2.3. Layer-2 applicability. . . . . . . . . . . . . . . . . . 5 2.3. Layer-2 applicability. . . . . . . . . . . . . . . . . . 5
3. Using RPL to Meet Functional Requirements . . . . . . . . . . 5 3. Using RPL to Meet Functional Requirements . . . . . . . . . . 5
4. RPL Profile . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. RPL Profile . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. RPL Features . . . . . . . . . . . . . . . . . . . . . . 5 4.1. RPL Features . . . . . . . . . . . . . . . . . . . . . . 5
4.1.1. RPL Instances . . . . . . . . . . . . . . . . . . . . 5 4.1.1. RPL Instances . . . . . . . . . . . . . . . . . . . . 5
4.1.2. Storing vs. Non-Storing Mode . . . . . . . . . . . . 5 4.1.2. Storing vs. Non-Storing Mode . . . . . . . . . . . . 5
4.1.3. DAO Policy . . . . . . . . . . . . . . . . . . . . . 5 4.1.3. DAO Policy . . . . . . . . . . . . . . . . . . . . . 5
4.1.4. Path Metrics . . . . . . . . . . . . . . . . . . . . 5 4.1.4. Path Metrics . . . . . . . . . . . . . . . . . . . . 6
4.1.5. Objective Function . . . . . . . . . . . . . . . . . 5 4.1.5. Objective Function . . . . . . . . . . . . . . . . . 6
4.1.6. DODAG Repair . . . . . . . . . . . . . . . . . . . . 5 4.1.6. DODAG Repair . . . . . . . . . . . . . . . . . . . . 6
4.1.7. Multicast . . . . . . . . . . . . . . . . . . . . . . 5 4.1.7. Multicast . . . . . . . . . . . . . . . . . . . . . . 6
4.1.8. Security . . . . . . . . . . . . . . . . . . . . . . 5 4.1.8. Security . . . . . . . . . . . . . . . . . . . . . . 6
4.1.9. P2P communications . . . . . . . . . . . . . . . . . 5 4.1.9. P2P communications . . . . . . . . . . . . . . . . . 6
4.1.10. IPv6 address configuration . . . . . . . . . . . . . 6 4.1.10. IPv6 address configuration . . . . . . . . . . . . . 6
4.2. Layer-2 features . . . . . . . . . . . . . . . . . . . . 6 4.2. Layer-2 features . . . . . . . . . . . . . . . . . . . . 6
4.2.1. Specifics about layer-2 . . . . . . . . . . . . . . . 6 4.2.1. Specifics about layer-2 . . . . . . . . . . . . . . . 6
4.2.2. Services provided at layer-2 . . . . . . . . . . . . 6 4.2.2. Services provided at layer-2 . . . . . . . . . . . . 6
4.2.3. 6LowPAN options assumed. . . . . . . . . . . . . . . 6 4.2.3. 6LowPAN options assumed. . . . . . . . . . . . . . . 6
4.2.4. MLE and other things . . . . . . . . . . . . . . . . 6 4.2.4. MLE and other things . . . . . . . . . . . . . . . . 6
4.3. Recommended Configuration Defaults and Ranges . . . . . . 6 4.3. Recommended Configuration Defaults and Ranges . . . . . . 6
4.3.1. Trickle Parameters . . . . . . . . . . . . . . . . . 6 4.3.1. Trickle Parameters . . . . . . . . . . . . . . . . . 6
4.3.2. Other Parameters . . . . . . . . . . . . . . . . . . 6 4.3.2. Other Parameters . . . . . . . . . . . . . . . . . . 6
5. MPL Profile . . . . . . . . . . . . . . . . . . . . . . . . . 7 5. MPL Profile . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Recommended Configuration Defaults and Ranges . . . . . . 8 5.1. Recommended Configuration Defaults and Ranges . . . . . . 8
5.1.1. Trickle Parameters . . . . . . . . . . . . . . . . . 8 5.1.1. Trickle Parameters . . . . . . . . . . . . . . . . . 8
5.1.2. Other Parameters . . . . . . . . . . . . . . . . . . 8 5.1.2. Other Parameters . . . . . . . . . . . . . . . . . . 8
6. Manageability Considerations . . . . . . . . . . . . . . . . 8 6. Manageability Considerations . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7.1. Security Considerations during initial deployment . . . . 8 7.1. Security Considerations during initial deployment . . . . 8
7.2. Security Considerations during incremental deployment . . 8 7.2. Security Considerations during incremental deployment . . 8
7.3. Security Considerations for P2P uses . . . . . . . . . . 8 7.3. Security Considerations for P2P uses . . . . . . . . . . 8
8. Other Related Protocols . . . . . . . . . . . . . . . . . . . 8 8. Other Related Protocols . . . . . . . . . . . . . . . . . . . 9
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
11.1. Normative References . . . . . . . . . . . . . . . . . . 9 11.1. Normative References . . . . . . . . . . . . . . . . . . 9
11.2. Informative References . . . . . . . . . . . . . . . . . 9 11.2. Informative References . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
This document describes a series of questions which should be This document describes a series of questions which should be
answered. This document is intended to remain as a Internet Draft. answered. This document is intended to remain as a Internet Draft.
skipping to change at page 8, line 25 skipping to change at page 8, line 37
5.1.2.1. Hot Limit 5.1.2.1. Hot Limit
6. Manageability Considerations 6. Manageability Considerations
7. Security Considerations 7. Security Considerations
7.1. Security Considerations during initial deployment 7.1. Security Considerations during initial deployment
(This section explains how nodes get their initial trust anchors, (This section explains how nodes get their initial trust anchors,
initial network keys. It explains if this happens at the factory, in initial network keys. It explains if this happens at the factory, in
a deployment truck, if it is done in the field, perhaps like http:// a deployment truck, if it is done in the field, perhaps like
www.lix.polytechnique.fr/hipercom/SmartObjectSecurity/papers/ http://www.lix.polytechnique.fr/hipercom/SmartObjectSecurity/papers/
CullenJennings.pdf) CullenJennings.pdf)
7.2. Security Considerations during incremental deployment 7.2. Security Considerations during incremental deployment
(This section explains how that replaces a failed node takes on the (This section explains how that replaces a failed node takes on the
dead nodes' identity, or not. How are nodes retired. How are nodes dead nodes' identity, or not. How are nodes retired. How are nodes
removed if they are compromised) removed if they are compromised)
7.3. Security Considerations for P2P uses 7.3. Security Considerations for P2P uses
 End of changes. 10 change blocks. 
21 lines changed or deleted 21 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/