draft-ietf-roll-applicability-template-04.txt   draft-ietf-roll-applicability-template-05.txt 
Network Working Group M. Richardson Network Working Group M. Richardson
Internet-Draft SSW Internet-Draft SSW
Intended status: Informational January 25, 2014 Intended status: Informational May 08, 2014
Expires: July 29, 2014 Expires: November 09, 2014
ROLL Applicability Statement Template ROLL Applicability Statement Template
draft-ietf-roll-applicability-template-04 draft-ietf-roll-applicability-template-05
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 July 29, 2014. This Internet-Draft will expire on November 09, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Relationship to other documents . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.3. Required Reading . . . . . . . . . . . . . . . . . . . . 3 1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
1.4. Out of scope requirements . . . . . . . . . . . . . . . . 3 1.4. Required Reading . . . . . . . . . . . . . . . . . . . . 4
2. Deployment Scenario . . . . . . . . . . . . . . . . . . . . . 3 1.5. Out of scope requirements . . . . . . . . . . . . . . . . 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 . . . . . . . 4
2.2.3. Publish-subscribe (PS, or pub/sub) communication 2.2.3. Publish-subscribe (PS, or pub/sub) communication
paradigm . . . . . . . . . . . . . . . . . . . . . . 4 paradigm . . . . . . . . . . . . . . . . . . . . . . 4
2.2.4. Peer-to-peer (P2P) communication paradigm . . . . . . 4 2.2.4. Peer-to-peer (P2P) communication paradigm . . . . . . 4
2.2.5. Peer-to-multipeer (P2MP) communication paradigm . . . 4 2.2.5. Peer-to-multipeer (P2MP) communication paradigm . . . 4
2.2.6. Additional considerations: Duocast and N-cast . . . . 4 2.2.6. Additional considerations: Duocast and N-cast . . . . 5
2.2.7. RPL applicability per communication paradigm . . . . 4 2.2.7. RPL applicability per communication paradigm . . . . 5
2.3. Layer-2 applicability. . . . . . . . . . . . . . . . . . 4 2.3. Layer-2 applicability. . . . . . . . . . . . . . . . . . 5
3. Using RPL to Meet Functional Requirements . . . . . . . . . . 4 3. Using RPL to Meet Functional Requirements . . . . . . . . . . 5
4. RPL Profile . . . . . . . . . . . . . . . . . . . . . . . . . 4 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 . . . . . . . . . . . . . . . . . . . . 5
4.1.5. Objective Function . . . . . . . . . . . . . . . . . 5 4.1.5. Objective Function . . . . . . . . . . . . . . . . . 5
4.1.6. DODAG Repair . . . . . . . . . . . . . . . . . . . . 5 4.1.6. DODAG Repair . . . . . . . . . . . . . . . . . . . . 5
4.1.7. Multicast . . . . . . . . . . . . . . . . . . . . . . 5 4.1.7. Multicast . . . . . . . . . . . . . . . . . . . . . . 5
4.1.8. Security . . . . . . . . . . . . . . . . . . . . . . 5 4.1.8. Security . . . . . . . . . . . . . . . . . . . . . . 5
4.1.9. P2P communications . . . . . . . . . . . . . . . . . 5 4.1.9. P2P communications . . . . . . . . . . . . . . . . . 5
4.1.10. IPv6 address configuration . . . . . . . . . . . . . 5 4.1.10. IPv6 address configuration . . . . . . . . . . . . . 6
4.2. Layer-2 features . . . . . . . . . . . . . . . . . . . . 5 4.2. Layer-2 features . . . . . . . . . . . . . . . . . . . . 6
4.2.1. Specifics about layer-2 . . . . . . . . . . . . . . . 5 4.2.1. Specifics about layer-2 . . . . . . . . . . . . . . . 6
4.2.2. Services provided at layer-2 . . . . . . . . . . . . 5 4.2.2. Services provided at layer-2 . . . . . . . . . . . . 6
4.2.3. 6LowPAN options assumed. . . . . . . . . . . . . . . 5 4.2.3. 6LowPAN options assumed. . . . . . . . . . . . . . . 6
4.2.4. MLE and other things . . . . . . . . . . . . . . . . 5 4.2.4. MLE and other things . . . . . . . . . . . . . . . . 6
4.3. Recommended Configuration Defaults and Ranges . . . . . . 5 4.3. Recommended Configuration Defaults and Ranges . . . . . . 6
4.3.1. Trickle Parameters . . . . . . . . . . . . . . . . . 5 4.3.1. Trickle Parameters . . . . . . . . . . . . . . . . . 6
4.3.2. Other Parameters . . . . . . . . . . . . . . . . . . 6 4.3.2. Other Parameters . . . . . . . . . . . . . . . . . . 6
5. MPL Profile . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. MPL Profile . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Recommended Configuration Defaults and Ranges . . . . . . 7 5.1. Recommended Configuration Defaults and Ranges . . . . . . 8
5.1.1. Trickle Parameters . . . . . . . . . . . . . . . . . 7 5.1.1. Trickle Parameters . . . . . . . . . . . . . . . . . 8
5.1.2. Other Parameters . . . . . . . . . . . . . . . . . . 7 5.1.2. Other Parameters . . . . . . . . . . . . . . . . . . 8
6. Manageability Considerations . . . . . . . . . . . . . . . . 7 6. Manageability Considerations . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7.1. Security Considerations during initial deployment . . . . 7 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 . . . . . . . . . . . . . . . . . . . 8
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
11.1. Normative References . . . . . . . . . . . . . . . . . . 8 11.1. Normative References . . . . . . . . . . . . . . . . . . 9
11.2. Informative References . . . . . . . . . . . . . . . . . 8 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.
The idea is that current and future Applicability statements will use The idea is that current and future Applicability statements will use
the table of contents provided. The goal is that all applicability the table of contents provided. The goal is that all applicability
statements will have to cover the listed items as a minimum. statements will have to cover the listed items as a minimum.
1.1. Requirements Language 1.1. Relationship to other documents
EDITORIAL: The following should appear in all applicability
statements:
ROLL has specified a set of routing protocols for Lossy and Low-
resource Networks (LLN) [RFC6550]. This applicability text describes
a subset of these protocols and the conditions which make the subset
the correct choice. The text recommends and motivates the
accompanying parameter value ranges. Multiple applicability domains
are recognized including: Building and Home, and Advanced Metering
Infrastructure. The applicability domains distinguish themselves in
the way they are operated, their performance requirements, and the
most probable network structures. Each applicability statement
identifies the distinguishing properties according to a common set of
subjects described in as many sections.
A common set of security threats are described in
[I-D.ietf-roll-security-threats]. The applicability statements
complement the security threats document by describing preferred
security settings and solutions within the applicability statement
conditions. This applicability statements may recommend more light
weight security solutions and specify the conditions under which
these solutions are appropriate.
1.2. Requirements Language
(RFC2119 reference) (RFC2119 reference)
1.2. Terminology 1.3. Terminology
A reference to draft-ietf-roll-terminology is appropriate. A A reference to draft-ietf-roll-terminology is appropriate. A
reference to layer-2 specific terminology and/or inclusion of any reference to layer-2 specific terminology and/or inclusion of any
terms that are normatively referenced is appropriate here. terms that are normatively referenced is appropriate here.
1.3. Required Reading 1.4. Required Reading
References/Overview of requirements documents, both IETF and industry References/Overview of requirements documents, both IETF and industry
group. (two pages maximum. This text should be (very) technical, group. (two pages maximum. This text should be (very) technical,
should be aimed at IETF *participants*, not industry group should be aimed at IETF *participants*, not industry group
participants, and should explain this industries' specific issues) participants, and should explain this industries' specific issues)
1.4. Out of scope requirements 1.5. Out of scope requirements
This should list other documents (if any) which deal with situations This should list other documents (if any) which deal with situations
where things are not in scope for this document. where things are not in scope for this document.
(For instance, the AMI document tries to cover both line-powered (For instance, the AMI document tries to cover both line-powered
urban metering networks, and energy-constrained metering networks, urban metering networks, and energy-constrained metering networks,
and also tries to deal with rural requirements. This should be three and also tries to deal with rural requirements. This should be three
or four documents, so this section should list the limits of what or four documents, so this section should list the limits of what
this document covers) this document covers)
skipping to change at page 8, line 44 skipping to change at page 9, line 15
A number of edits were contributed from Peter van der Stok, including A number of edits were contributed from Peter van der Stok, including
the MPL considerations/calculations the MPL considerations/calculations
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[I-D.ietf-roll-security-threats]
Tsao, T., Alexander, R., Dohler, M., Daza, V., Lozano, A.,
and M. Richardson, "A Security Threat Analysis for Routing
Protocol for Low-power and lossy networks (RPL)", draft-
ietf-roll-security-threats-06 (work in progress), December
2013.
11.2. Informative References 11.2. Informative References
[RFC6206] Levis, P., Clausen, T., Hui, J., Gnawali, O., and J. Ko,
"The Trickle Algorithm", RFC 6206, March 2011.
[RFC6550] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R., [RFC6550] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R.,
Levis, P., Pister, K., Struik, R., Vasseur, JP., and R. Levis, P., Pister, K., Struik, R., Vasseur, JP., and R.
Alexander, "RPL: IPv6 Routing Protocol for Low-Power and Alexander, "RPL: IPv6 Routing Protocol for Low-Power and
Lossy Networks", RFC 6550, March 2012. Lossy Networks", RFC 6550, March 2012.
Author's Address Author's Address
Michael C. Richardson Michael C. Richardson
Sandelman Software Works Sandelman Software Works
470 Dawson Avenue 470 Dawson Avenue
 End of changes. 14 change blocks. 
36 lines changed or deleted 72 lines changed or added

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