draft-ietf-roll-mpl-parameter-configuration-00.txt   draft-ietf-roll-mpl-parameter-configuration-01.txt 
roll Y. Doi roll Y. Doi
Internet-Draft TOSHIBA Corporation Internet-Draft TOSHIBA Corporation
Intended status: Standards Track M. Gillmore Intended status: Standards Track M. Gillmore
Expires: September 12, 2014 Itron, Inc Expires: January 3, 2015 Itron, Inc
March 11, 2014 July 2, 2014
MPL Parameter Configuration Option for DHCPv6 MPL Parameter Configuration Option for DHCPv6
draft-ietf-roll-mpl-parameter-configuration-00 draft-ietf-roll-mpl-parameter-configuration-01
Abstract Abstract
This draft defines a way to configure MPL parameter set via DHCPv6 This draft defines a way to configure MPL parameter set via DHCPv6
option. MPL has a set of parameters to control its behavior, and the option. MPL has a set of parameters to control its behavior, and the
parameter set is often configured as a network-wide parameter because parameter set is often configured as a network-wide parameter because
the parameter set should be identical for each MPL forwarder in an the parameter set should be identical for each MPL forwarder in an
MPL domain. Using the MPL Parameter Configuration Option defined in MPL domain. Using the MPL Parameter Configuration Option defined in
this document, a network can be configured with a single set of MPL this document, a network can be configured with a single set of MPL
parameter easily. parameter easily.
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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 September 12, 2014. This Internet-Draft will expire on January 3, 2015.
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. MPL Parameter Configuration Option . . . . . . . . . . . . . . 3 2. MPL Parameter Configuration Option . . . . . . . . . . . . . 2
2.1. Unsigned Short Floating Point . . . . . . . . . . . . . . . 4 2.1. Unsigned Short Floating Point . . . . . . . . . . . . . . 3
2.2. MPL Parameter Configuration Option Format . . . . . . . . . 5 2.2. MPL Parameter Configuration Option Format . . . . . . . . 4
2.3. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . . 6 2.3. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . 6
2.4. MPL Forwarder Behavior . . . . . . . . . . . . . . . . . . 6 2.4. MPL Forwarder Behavior . . . . . . . . . . . . . . . . . 6
2.5. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . 7 2.5. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . 7
2.6. DHCPv6 Relay Behavior . . . . . . . . . . . . . . . . . . . 7 2.6. DHCPv6 Relay Behavior . . . . . . . . . . . . . . . . . . 7
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 2.7. Operational Considerations . . . . . . . . . . . . . . . 7
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
5.1. Normative References . . . . . . . . . . . . . . . . . . . 8 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.2. Non-Normative References . . . . . . . . . . . . . . . . . 8 5.1. Normative References . . . . . . . . . . . . . . . . . . 8
Appendix A. Update History . . . . . . . . . . . . . . . . . . . . 8 5.2. Non-Normative References . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 Appendix A. Update History . . . . . . . . . . . . . . . . . . . 8
Appendix B. Considerations on Inconsistent Parameter Set . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
Multicast Protocol for Low power and Lossy Networks (MPL) Multicast Protocol for Low power and Lossy Networks (MPL)
[I-D.ietf-roll-trickle-mcast] defines a protocol to make a multicast [I-D.ietf-roll-trickle-mcast] defines a protocol to make a multicast
network among low power and lossy network i.e. wireless mesh network among low power and lossy network i.e. wireless mesh
networks. MPL has a set of parameters to control its behavior and networks. MPL has a set of parameters to control its behavior and
tradeoff between end-to-end delay and network utilization. In most tradeoff between end-to-end delay and network utilization. In most
environments, the default parameters are acceptable. However, in environments, the default parameters are acceptable. However, in
some environments, the parameter set must be configured carefully in some environments, the parameter set must be configured carefully in
skipping to change at page 4, line 23 skipping to change at page 3, line 47
uses base-10 unsigned short floating point number with 3-bit exponent uses base-10 unsigned short floating point number with 3-bit exponent
and 13-bit significand defined as follows (exp. stands for exponent). and 13-bit significand defined as follows (exp. stands for exponent).
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| exp.| significand | | exp.| significand |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The represented value is (significand) * 10^(exp.). The minimum The represented value is (significand) * 10^(exp.). The minimum
exponent is 0 (binary 000) and the maximum is 6 (binary 110). exp=7 exponent is 0 (binary 000) and the maximum is 6 (binary 110). exp=7
(binary 111) is reserved for future use. The minimum significand is (binary 111) is reserved for future use. The minimum significand is
0 (all 0) and the maximum is 8191 (all 1). 0 (all 0) and the maximum is 8191 (all 1).
Unlike IEEE754 half precision floating point (binary16), there is no Unlike IEEE754 half precision floating point (binary16), there is no
sign bit (no negative value for a timer), exponent is not biased (no sign bit (no negative value for a timer), exponent is not biased (no
fractional value for a timer), no implicit leading 1 in siginificand, fractional value for a timer), no implicit leading 1 in siginificand,
and base is 10. Therefore, there could be more than one and base is 10. Therefore, there could be more than one
representation for a value. representation for a value.
Followings are examples of common timer values represented by unit of Followings are examples of common timer values represented by unit of
skipping to change at page 6, line 44 skipping to change at page 6, line 19
and 22.7. As a convenience to the reader, we mention here that the and 22.7. As a convenience to the reader, we mention here that the
client includes requested option codes in Option Request Option. client includes requested option codes in Option Request Option.
Clients MUST discard MPL Parameter Configuration Option if it is Clients MUST discard MPL Parameter Configuration Option if it is
invalid (i.e. it sets reserved bits or it has timers with reserved invalid (i.e. it sets reserved bits or it has timers with reserved
exp=7 in Unsigned Short Floating Point). exp=7 in Unsigned Short Floating Point).
2.4. MPL Forwarder Behavior 2.4. MPL Forwarder Behavior
If a DHCPv6 client requests and receives MPL Parameter Configuration If a DHCPv6 client requests and receives MPL Parameter Configuration
Option, the node SHOULD join the MPL domain given by the option and Option, the node MAY join the MPL domain given by the option and act
act as an MPL forwarder. Each node SHOULD configure its MPL as an MPL forwarder. Each joining node SHOULD configure its MPL
forwarder with the given parameter set for the MPL domain. forwarder with the given parameter set for the MPL domain.
The priority of MPL Parameter Configuration applied for an MPL Domain The priority of MPL Parameter Configuration applied for an MPL Domain
is as follows (high to low). is as follows (high to low).
o Specific MPL Parameter Configuration to the MPL Domain (optlen=32) o Specific MPL Parameter Configuration to the MPL Domain (optlen=32)
o Wildcard MPL Parameter Configuration (optlen=16) o Wildcard MPL Parameter Configuration (optlen=16)
o Default configuration given in the MPL specification. o Default configuration given in the MPL specification.
skipping to change at page 7, line 39 skipping to change at page 7, line 13
[I-D.jiang-dhc-stateless-reconfiguration] may be used (if approved). [I-D.jiang-dhc-stateless-reconfiguration] may be used (if approved).
2.5. DHCPv6 Server Behavior 2.5. DHCPv6 Server Behavior
Sections 17.2.2 and 18.2 of RFC3315 [RFC3315] govern server operation Sections 17.2.2 and 18.2 of RFC3315 [RFC3315] govern server operation
in regards to option assignment. As a convenience to the reader, we in regards to option assignment. As a convenience to the reader, we
mention here that the server will send MPL Parameter Configuration mention here that the server will send MPL Parameter Configuration
Option only if configured with specific value for MPL Parameter Option only if configured with specific value for MPL Parameter
Configuration Option and the client requested it. Configuration Option and the client requested it.
Servers MUST ignore incoming MPL Parameter Configuration Option. Servers SHALL ignore incoming MPL Parameter Configuration Option.
2.6. DHCPv6 Relay Behavior 2.6. DHCPv6 Relay Behavior
It's never appropriate for a relay agent to add options to a message It's never appropriate for a relay agent to add options to a message
heading toward the client, and relay agents don't actually construct heading toward the client, and relay agents don't actually construct
Relay-Reply messages anyway. There are no additional requirements Relay-Reply messages anyway. There are no additional requirements
for relays. for relays.
2.7. Operational Considerations
A parameter set for an MPL domain SHOULD NOT updated more often than
two times of expected refresh interval.
If a node with MPL forwarder configured by MPL Parameter
configuration Option failed to refresh the option for two times of
information refresh time, it SHALL suspend the MPL forwarders of MPL
domains configured by the option. MPL forwarders configured by other
methods such as static configuration file SHALL NOT be suspended.
3. IANA Considerations 3. IANA Considerations
A DHCPv6 option code for MPL Parameter Configuration Option needs to A DHCPv6 option code for MPL Parameter Configuration Option needs to
be assigned from IANA. be assigned from IANA.
4. Security Considerations 4. Security Considerations
A forged option may cause excessive layer-2 broadcasting. A forged option may cause excessive layer-2 broadcasting.
Implementations should set reasonable bounds for each parameter. For Implementations should set reasonable bounds for each parameter. For
example, not too high K, not too low IMIN, etc. These may be example, not too high K, not too low IMIN, etc. These may be
skipping to change at page 8, line 48 skipping to change at page 8, line 38
January 2014. January 2014.
[I-D.jiang-dhc-stateless-reconfiguration] [I-D.jiang-dhc-stateless-reconfiguration]
Jiang, S. and B. Liu, "Stateless Reconfiguration in Jiang, S. and B. Liu, "Stateless Reconfiguration in
Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
draft-jiang-dhc-stateless-reconfiguration-01 (work in draft-jiang-dhc-stateless-reconfiguration-01 (work in
progress), February 2014. progress), February 2014.
Appendix A. Update History Appendix A. Update History
Updates on draft-doi-roll-mpl-configuration-05 to Updates on draft-doi-roll-mpl-configuration-05 to draft-ietf-roll-
draft-ietf-roll-mpl-configuration-00: mpl-configuration-01:
o Operational considerations (normative) and appendix considerations
(non-normative) are added (Issue #157)
o More control on nodes / allow constrained nodes to ignore the
configuration: "the node s/SHOULD/MAY/ join the MPL domain given
by the option" (Issue #158)
Updates on draft-doi-roll-mpl-configuration-05 to draft-ietf-roll-
mpl-configuration-00:
o I-D renamed. o I-D renamed.
Appendix B. Considerations on Inconsistent Parameter Set
This draft introduces dynamic update of MPL parameters. Because the
update process is not synchronized, nodes may have inconsistent
parameter set.
Inconsistent parameter may reduce performance. On the other hand, it
shall work as long as both parameter set are reasonable parameter set
for a given communication load. As motivations for parameter update
are update on environment, node density, or communication load,
operators of MPL networks shall be aware of unupdated nodes and make
sure old and new parameter sets are reasonable for expected refresh
intervals.
Authors' Addresses Authors' Addresses
Yusuke Doi Yusuke Doi
TOSHIBA Corporation TOSHIBA Corporation
Komukai Toshiba Cho 1 Komukai Toshiba Cho 1
Saiwai-Ku Saiwai-Ku
Kawasaki, Kanagawa 2128582 Kawasaki, Kanagawa 2128582
JAPAN JAPAN
Phone: +81-45-342-7230 Phone: +81-45-342-7230
Email: yusuke.doi@toshiba.co.jp Email: yusuke.doi@toshiba.co.jp
URI:
Matthew Gillmore Matthew Gillmore
Itron, Inc Itron, Inc
2111 N Molter Rd. 2111 N Molter Rd.
Liberty Lake, WA 99019 Liberty Lake, WA 99019
USA USA
Email: matthew.gillmore@itron.com Email: matthew.gillmore@itron.com
 End of changes. 12 change blocks. 
27 lines changed or deleted 63 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/