--- 1/draft-ietf-roll-applicability-template-03.txt 2014-01-25 09:14:31.410749256 -0800 +++ 2/draft-ietf-roll-applicability-template-04.txt 2014-01-25 09:14:31.430749771 -0800 @@ -1,18 +1,18 @@ Network Working Group M. Richardson Internet-Draft SSW -Intended status: Informational September 17, 2013 -Expires: March 21, 2014 +Intended status: Informational January 25, 2014 +Expires: July 29, 2014 ROLL Applicability Statement Template - draft-ietf-roll-applicability-template-03 + draft-ietf-roll-applicability-template-04 Abstract This document is a template applicability statement for the Routing over Low-power and Lossy Networks (ROLL) WG. This document is not for publication, but rather is to be used as a template. Status of This Memo This Internet-Draft is submitted in full conformance with the @@ -21,25 +21,25 @@ 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 March 21, 2014. + This Internet-Draft will expire on July 29, 2014. 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. 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 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 @@ -85,29 +85,29 @@ 4.3. Recommended Configuration Defaults and Ranges . . . . . . 5 4.3.1. Trickle Parameters . . . . . . . . . . . . . . . . . 5 4.3.2. Other Parameters . . . . . . . . . . . . . . . . . . 6 5. MPL Profile . . . . . . . . . . . . . . . . . . . . . . . . . 6 5.1. Recommended Configuration Defaults and Ranges . . . . . . 7 5.1.1. Trickle Parameters . . . . . . . . . . . . . . . . . 7 5.1.2. Other Parameters . . . . . . . . . . . . . . . . . . 7 6. Manageability Considerations . . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 7.1. Security Considerations during initial deployment . . . . 7 - 7.2. Security Considerations during incremental deployment . . 7 - 7.3. Security Considerations for P2P uses . . . . . . . . . . 7 - 8. Other Related Protocols . . . . . . . . . . . . . . . . . . . 7 - 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 - 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 + 7.2. Security Considerations during incremental deployment . . 8 + 7.3. Security Considerations for P2P uses . . . . . . . . . . 8 + 8. Other Related Protocols . . . . . . . . . . . . . . . . . . . 8 + 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 + 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 11.1. Normative References . . . . . . . . . . . . . . . . . . 8 11.2. Informative References . . . . . . . . . . . . . . . . . 8 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 1. Introduction This document describes a series of questions which should be answered. This document is intended to remain as a Internet Draft. The idea is that current and future Applicability statements will use the table of contents provided. The goal is that all applicability statements will have to cover the listed items as a minimum. @@ -221,22 +221,50 @@ 4.2.2. Services provided at layer-2 4.2.3. 6LowPAN options assumed. 4.2.4. MLE and other things 4.3. Recommended Configuration Defaults and Ranges 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 + 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 This section should list the various features of MPL. In considering the parameters, a number of questions come up: 1) What are the maximum and minimum 1-hop MPL router neighbours of all the MPL routers? 2) what is the arrival rate of new packets that need repetition in a MPL router