draft-ietf-roll-applicability-template-03.txt   draft-ietf-roll-applicability-template-04.txt 
Network Working Group M. Richardson Network Working Group M. Richardson
Internet-Draft SSW Internet-Draft SSW
Intended status: Informational September 17, 2013 Intended status: Informational January 25, 2014
Expires: March 21, 2014 Expires: July 29, 2014
ROLL Applicability Statement Template ROLL Applicability Statement Template
draft-ietf-roll-applicability-template-03 draft-ietf-roll-applicability-template-04
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 March 21, 2014. This Internet-Draft will expire on July 29, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 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
skipping to change at page 2, line 52 skipping to change at page 2, line 52
4.3. Recommended Configuration Defaults and Ranges . . . . . . 5 4.3. Recommended Configuration Defaults and Ranges . . . . . . 5
4.3.1. Trickle Parameters . . . . . . . . . . . . . . . . . 5 4.3.1. Trickle Parameters . . . . . . . . . . . . . . . . . 5
4.3.2. Other Parameters . . . . . . . . . . . . . . . . . . 6 4.3.2. Other Parameters . . . . . . . . . . . . . . . . . . 6
5. MPL Profile . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. MPL Profile . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Recommended Configuration Defaults and Ranges . . . . . . 7 5.1. Recommended Configuration Defaults and Ranges . . . . . . 7
5.1.1. Trickle Parameters . . . . . . . . . . . . . . . . . 7 5.1.1. Trickle Parameters . . . . . . . . . . . . . . . . . 7
5.1.2. Other Parameters . . . . . . . . . . . . . . . . . . 7 5.1.2. Other Parameters . . . . . . . . . . . . . . . . . . 7
6. Manageability Considerations . . . . . . . . . . . . . . . . 7 6. Manageability Considerations . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7.1. Security Considerations during initial deployment . . . . 7 7.1. Security Considerations during initial deployment . . . . 7
7.2. Security Considerations during incremental deployment . . 7 7.2. Security Considerations during incremental deployment . . 8
7.3. Security Considerations for P2P uses . . . . . . . . . . 7 7.3. Security Considerations for P2P uses . . . . . . . . . . 8
8. Other Related Protocols . . . . . . . . . . . . . . . . . . . 7 8. Other Related Protocols . . . . . . . . . . . . . . . . . . . 8
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
11.1. Normative References . . . . . . . . . . . . . . . . . . 8 11.1. Normative References . . . . . . . . . . . . . . . . . . 8
11.2. Informative References . . . . . . . . . . . . . . . . . 8 11.2. Informative References . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 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.
skipping to change at page 6, line 4 skipping to change at page 5, line 46
4.2.2. Services provided at layer-2 4.2.2. Services provided at layer-2
4.2.3. 6LowPAN options assumed. 4.2.3. 6LowPAN options assumed.
4.2.4. MLE and other things 4.2.4. MLE and other things
4.3. Recommended Configuration Defaults and Ranges 4.3. Recommended Configuration Defaults and Ranges
4.3.1. Trickle Parameters 4.3.1. Trickle Parameters
This section is intended to document the specific value (or ranges)
appropriate for this kind of deployment. This includes trickle
specific parameters such as those of RFC6550, section 8.3.1: Imin
(DIOInternvalMin), Imax (DIOIntrevalDoublings), and k
(DIORedundancyConstant). While it is not necessary to hard code
these parameters into RPL nodes, as they are announced as part of the
DIO message, it is important for researchers who are trying to
validate the convergence properties of the resulting deployment to
understand what values have been selected.
4.3.2. Other Parameters 4.3.2. Other Parameters
There are additional values which are present in the DODAG
Configuration option. The purpose of this section is to: a) document
what values are configured, b) if a default value is used, if it is
appropriate for this deployment.
These values include: MaxRankIncrease, MinHopRankIncrease, the
Objective Code Point to use, Default Lifetime, Lifetime Units...
In addition, the kinds of metrics which will be used (RFC6551) needs
to be specified. If Objective Function 0 (RFC6552) is used, then it
specifies a number of values, but also needs definitions of the
stretch_of_rank, and rank_factor.
If MRHOF (RFC6719) is used, then section 5 of this document requires
selection of: MAX_LINK_METRIC, MAX_PATH_COST,
PARENT_SWITCH_THRESHOLD, PARENT_SET_SIZE, and ALLOW_FLOATING_ROOT.
5. MPL Profile 5. MPL Profile
This section should list the various features of MPL. In considering This section should list the various features of MPL. In considering
the parameters, a number of questions come up: the parameters, a number of questions come up:
1) What are the maximum and minimum 1-hop MPL router neighbours of 1) What are the maximum and minimum 1-hop MPL router neighbours of
all the MPL routers? all the MPL routers?
2) what is the arrival rate of new packets that need repetition in 2) what is the arrival rate of new packets that need repetition in
a MPL router a MPL router
 End of changes. 8 change blocks. 
11 lines changed or deleted 39 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/