draft-ietf-roll-mpl-parameter-configuration-01.txt   draft-ietf-roll-mpl-parameter-configuration-02.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: January 3, 2015 Itron, Inc Expires: January 22, 2015 Itron, Inc
July 2, 2014 July 21, 2014
MPL Parameter Configuration Option for DHCPv6 MPL Parameter Configuration Option for DHCPv6
draft-ietf-roll-mpl-parameter-configuration-01 draft-ietf-roll-mpl-parameter-configuration-02
Abstract Abstract
This draft defines a way to configure MPL parameter set via DHCPv6 This draft defines a way to configure a parameter set of MPL
(Multicast Protocol for Low power and Lossy Networks) 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
skipping to change at page 1, line 37 skipping to change at page 1, line 38
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 January 3, 2015. This Internet-Draft will expire on January 22, 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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. MPL Parameter Configuration Option . . . . . . . . . . . . . 2 2. MPL Parameter Configuration Option . . . . . . . . . . . . . 3
2.1. Unsigned Short Floating Point . . . . . . . . . . . . . . 3 2.1. MPL Parameter Configuration Option Format . . . . . . . . 3
2.2. MPL Parameter Configuration Option Format . . . . . . . . 4 2.2. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . 5
2.3. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . 6 2.3. MPL Forwarder Behavior . . . . . . . . . . . . . . . . . 5
2.4. MPL Forwarder Behavior . . . . . . . . . . . . . . . . . 6 2.4. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . 6
2.5. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . 7 2.5. DHCPv6 Relay Behavior . . . . . . . . . . . . . . . . . . 6
2.6. DHCPv6 Relay Behavior . . . . . . . . . . . . . . . . . . 7 2.6. Operational Considerations . . . . . . . . . . . . . . . 6
2.7. Operational Considerations . . . . . . . . . . . . . . . 7 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 5.1. Normative References . . . . . . . . . . . . . . . . . . 7
5.1. Normative References . . . . . . . . . . . . . . . . . . 8 5.2. Non-Normative References . . . . . . . . . . . . . . . . 7
5.2. Non-Normative References . . . . . . . . . . . . . . . . 8
Appendix A. Update History . . . . . . . . . . . . . . . . . . . 8 Appendix A. Update History . . . . . . . . . . . . . . . . . . . 8
Appendix B. Considerations on Inconsistent Parameter Set . . . . 9 Appendix B. Considerations on Inconsistent Parameter Set . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
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 e.g. wireless mesh
networks. MPL has a set of parameters to control its behavior and networks. MPL has a set of parameters to control an MPL domain. The
tradeoff between end-to-end delay and network utilization. In most parameter controls trade-off between end-to-end delay and network
environments, the default parameters are acceptable. However, in utilization. In most environments, the default parameters are
some environments, the parameter set must be configured carefully in acceptable. However, in some environments, the parameter set must be
order to meet the requirements of each environment. According to the configured carefully in order to meet the requirements of each
MPL draft section 5.4, each parameter in the set should be same for environment. According to the MPL draft section 5.4, each parameter
all nodes within an MPL domain. And the MPL draft does not define a in the set should be same for all nodes within an MPL domain. And
method to configure the MPL parameter set. the MPL draft does not define a method to configure the MPL parameter
set.
Some managed wireless mesh networks may have a DHCP server to Some managed wireless mesh networks may have a DHCP server to
configure network parameters. MPL parameter set shall be considered configure network parameters. MPL parameter set shall be considered
as a part of network parameters (nodes in an MPL domain should use an as a part of network parameters (nodes in an MPL domain should use an
identical parameter set). This document is to define the way to identical parameter set). And a parameter set are required to
distribute parameter sets for MPL forwarders as a simple DHCPv6 configure an MPL domain.
[RFC3315] option.
This document is to define the way to distribute parameter sets for
MPL forwarders as a DHCPv6 [RFC3315] option. This document is
intended to follow the guideline [RFC7227].
2. MPL Parameter Configuration Option 2. MPL Parameter Configuration Option
Per MPL domain, there are following 10 parameters. An MPL domain is Per MPL domain, there are following 10 parameters. An MPL domain is
defined by an MPL domain address. defined by an MPL domain address.
o PROACTIVE_FORWARDING o PROACTIVE_FORWARDING
o SEED_SET_ENTRY_LIFETIME o SEED_SET_ENTRY_LIFETIME
o DATA_MESSAGE_IMIN o DATA_MESSAGE_IMIN
o DATA_MESSAGE_IMAX o DATA_MESSAGE_IMAX
skipping to change at page 3, line 32 skipping to change at page 3, line 35
o CONTROL_MESSAGE_K o CONTROL_MESSAGE_K
o CONTROL_MESSAGE_TIMER_EXPIRATIONS o CONTROL_MESSAGE_TIMER_EXPIRATIONS
One network may have multiple MPL domains with different One network may have multiple MPL domains with different
configurations. To configure more than one MPL domain via DHCP, configurations. To configure more than one MPL domain via DHCP,
there may be more than one MPL Parameter Configuration Option given there may be more than one MPL Parameter Configuration Option given
to DHCP clients from a DHCP server. to DHCP clients from a DHCP server.
2.1. Unsigned Short Floating Point 2.1. MPL Parameter Configuration Option Format
MPL has many timer parameters. Expected range of the timers depends
on the network topology or MAC/PHY nature. To accommodate wide range
of timer values efficiently, the MPL Parameter Configuration Option
uses base-10 unsigned short floating point number with 3-bit exponent
and 13-bit significand defined as follows (exp. stands for exponent).
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| exp.| significand |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The represented value is (significand) * 10^(exp.). The minimum
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
0 (all 0) and the maximum is 8191 (all 1).
Unlike IEEE754 half precision floating point (binary16), there is 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,
and base is 10. Therefore, there could be more than one
representation for a value.
Followings are examples of common timer values represented by unit of
millisecond.
One second (1,000 milliseconds): exp = 3, significand = 1, 0x6001.
One minute (60,000 milliseconds): exp = 4, significand = 6, 0x8006.
One hour (3,600,000 milliseconds): exp = 5, significand = 36,
0xa024.
One day (86,400,000 milliseconds): exp = 5, significand = 864,
0xa360
Maximum timer length represented by an unsigned short floating point
with millisecond precision is 8191 * 10^6 milliseconds (13 weeks 3
days 19 hours 16 minutes 40 seconds).
With exponent and significand, an unsigned short floating point
(usfp) can be encoded as follows.
usfp = (exponent << 13)|(0x1fff & significand);
2.2. MPL Parameter Configuration Option Format
To distribute a configuration of an MPL domain or a default value for To distribute a configuration of an MPL domain or a default value for
all MPL domains (wildcard) under the network managed by the DHCP all MPL domains (wildcard) under the network managed by the DHCP
server, this document defines a DHCPv6 option format as follows. server, this document defines a DHCPv6 option format as follows.
Short floating point format is used to describe wide range of timer Short floating point format is used to describe wide range of timer
values. values.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_MPL_PARAMETERS | option_len | | OPTION_MPL_PARAMETERS | option_len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|P| Z | C_K | Z2 | DM_K | SE_LIFETIME | |P| Z | TUNIT | SE_LIFETIME |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DM_IMIN | DM_IMAX | | DM_K | DM_IMIN | DM_IMAX >
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DM_T_EXP | C_IMIN | > (cont'ed) | DM_T_EXP | C_K |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C_IMAX | C_T_EXP | | C_IMIN | C_IMAX |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C_T_EXP |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
(if option_len = 32 ) (if option_len = 34 )
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MPL Domain Address (128bits) | | MPL Domain Address >
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (cont'ed) | > MPL Domain Address (128bits) >
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (cont'ed) | > (cont'ed) >
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (cont'ed) | > (cont'ed) >
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> (cont'ed) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
OPTION_MPL_PARAMETERS: DHCPv6 option identifier (not yet assigned). OPTION_MPL_PARAMETERS: DHCPv6 option identifier (not yet assigned).
option_len: Length of the option. It SHOULD be 16 (without MPL option_len: Length of the option. It SHOULD be 18 (without MPL
domain address) or 32 (with MPL domain address) domain address) or 34 (with MPL domain address)
P (1 bit): A flag to indicate PROACTIVE_FORWARDING P (1 bit): A flag to indicate PROACTIVE_FORWARDING
Z (1 bit) Reserved. Should be 0. Z (7 bits) Reserved. Should be 0.
C_K (5 bits): CONTROL_MESSAGE_K. TUNIT (unsigned 8 bit integer) Unit time of times in this option.
It SHALL NOT be 0 or 255.
Z2 (3 bits) Reserved. Should be all 0. SE_LIFETIME: SEED_SET_ENTRY_LIFETIME/TUNIT in milliseconds. It
SHALL NOT be 0 or 0xffff.
DM_K (5 bits): DATA_MESSAGE_K. DM_K (unsigned 8 bit integer): DATA_MESSAGE_K.
SE_LIFETIME: SEED_SET_ENTRY_LIFETIME. The unit is millisecond and DM_IMIN (unsigned 16 bit integer): DATA_MESSAGE_IMIN/TUNIT in
the type is unsigned short floating point. milliseconds. It SHALL NOT be 0 or 0xffff.
DM_IMIN: DATA_MESSAGE_IMIN. The unit is millisecond and the type is DM_IMAX (unsigned 16 bit integer): DATA_MESSAGE_IMAX/TUNIT in
unsigned short floating point. milliseconds. It SHALL NOT be 0 or 0xffff.
DM_IMAX: DATA_MESSAGE_IMAX. The unit is millisecond and the type is DM_T_EXP (unsigned 16 bit integer): DATA_MESSAGE_TIMER_EXPIRATIONS/
unsigned short floating point. TUNIT in milliseconds. It SHALL NOT be 0 or 0xffff.
DM_T_EXP: DATA_MESSAGE_TIMER_EXPIRATIONS. The unit is millisecond C_K (unsigned 8 bit integer): CONTROL_MESSAGE_K.
and the type is unsigned short floating point.
C_IMIN: CONTROL_MESSAGE_IMIN. The unit is millisecond and the type C_IMIN (unsigned 16 bit integer): CONTROL_MESSAGE_IMIN/TUNIT in
is unsigned short floating point. milliseconds. It SHALL NOT be 0 or 0xffff.
C_IMAX: CONTROL_MESSAGE_IMAX. The unit is millisecond and the type C_IMAX: CONTROL_MESSAGE_IMAX/TUNIT in milliseconds. It SHALL NOT be
is unsigned short floating point. 0 or 0xffff.
C_T_EXP: CONTROL_MESSAGE_TIMER_EXPIRATIONS. The unit is millisecond C_T_EXP: CONTROL_MESSAGE_TIMER_EXPIRATIONS/TUNIT in milliseconds.
and the type is unsigned short floating point. It SHALL NOT be 0 or 0xffff.
2.3. DHCPv6 Client Behavior Note that all time values (Trickle timers and expiration periods) are
in TUNIT milliseconds precision. For example, if TUNIT is 20 and the
data message interval minimum (DATA_MESSAGE_IMIN) is 1000ms, then
DM_IMIN shall be set to 50.
2.2. DHCPv6 Client Behavior
Clients MAY request MPL Parameter Configuration Option, as described Clients MAY request MPL Parameter Configuration Option, as described
in RFC3315 [RFC3315], sections 17.1.1, 18.1.1, 18.1.3, 18.1.4, 18.1.5 in RFC3315 [RFC3315], sections 17.1.1, 18.1.1, 18.1.3, 18.1.4, 18.1.5
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 (e.g. 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.3. 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 MAY join the MPL domain given by the option and act Option, the node MAY join the MPL domain given by the option and act
as an MPL forwarder. Each joining 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=34)
o Wildcard MPL Parameter Configuration (optlen=16) o Wildcard MPL Parameter Configuration (optlen=18)
o Default configuration given in the MPL specification. o Default configuration given in the MPL specification.
There SHALL be no more than one MPL Parameter Configuration Option There SHALL be no more than one MPL Parameter Configuration Option
for a MPL domain or the wildcard. Thus, the order of DHCPv6 options for a MPL domain or the wildcard. Thus, the order of DHCPv6 options
in the packet has no effect on precedence. in the packet has no effect on precedence.
A node MAY leave from an MPL domain if the following two conditions A node MAY leave from an MPL domain if the following two conditions
are satisfied. 1) The MPL domain is configured by a DHCPv6 option are satisfied. 1) The MPL domain is configured by a DHCPv6 option
from a DHCPv6 server previously. 2) The node has received an updated from a DHCPv6 server previously. 2) The node has received an updated
skipping to change at page 7, line 5 skipping to change at page 6, line 17
MPL parameter may be updated occasionally. With stateful DHCPv6, MPL parameter may be updated occasionally. With stateful DHCPv6,
updates can be done when the renewal timer expires. Information updates can be done when the renewal timer expires. Information
Refresh Time Option [RFC4242] shall be used to keep each forwarders Refresh Time Option [RFC4242] shall be used to keep each forwarders
updated. updated.
To reduce periodical update traffic a node may try to use very long To reduce periodical update traffic a node may try to use very long
interval between updates. In the case, reconfigure shall be used to interval between updates. In the case, reconfigure shall be used to
keep forwarder parameter sets synchronized. For stateless DHCPv6, keep forwarder parameter sets synchronized. For stateless DHCPv6,
[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.4. 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 SHALL ignore incoming MPL Parameter Configuration Option. Servers SHALL ignore incoming MPL Parameter Configuration Option.
2.6. DHCPv6 Relay Behavior 2.5. 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 2.6. Operational Considerations
A parameter set for an MPL domain SHOULD NOT updated more often than A parameter set for an MPL domain SHOULD NOT be updated more often
two times of expected refresh interval. than two times of expected refresh interval.
If a node with MPL forwarder configured by MPL Parameter If a node with MPL forwarder configured by MPL Parameter
configuration Option failed to refresh the option for two times of configuration Option failed to refresh the option for two times of
information refresh time, it SHALL suspend the MPL forwarders of MPL information refresh time, it SHALL suspend the MPL forwarders of MPL
domains configured by the option. MPL forwarders configured by other domains configured by the option. MPL forwarders configured by other
methods such as static configuration file SHALL NOT be suspended. 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
skipping to change at page 8, line 36 skipping to change at page 7, line 43
S. Krishnan, "Guidelines for Creating New DHCPv6 Options", S. Krishnan, "Guidelines for Creating New DHCPv6 Options",
draft-ietf-dhc-option-guidelines-17 (work in progress), draft-ietf-dhc-option-guidelines-17 (work in progress),
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.
[RFC7227] Hankins, D., Mrugalski, T., Siodelski, M., Jiang, S., and
S. Krishnan, "Guidelines for Creating New DHCPv6 Options",
BCP 187, RFC 7227, May 2014.
Appendix A. Update History Appendix A. Update History
Updates on draft-doi-roll-mpl-configuration-05 to draft-ietf-roll- Updates on draft-ietf-roll-mpl-configuration-01 to draft-ietf-roll-
mpl-configuration-02:
o Short unsigned floating point is dropped (#159)
o Packed value is removed and now every value has its own byte(s)
(#159)
Updates on draft-ietf-roll-mpl-configuration-00 to draft-ietf-roll-
mpl-configuration-01: mpl-configuration-01:
o Operational considerations (normative) and appendix considerations o Operational considerations (normative) and appendix considerations
(non-normative) are added (Issue #157) (non-normative) are added (Issue #157)
o More control on nodes / allow constrained nodes to ignore the o More control on nodes / allow constrained nodes to ignore the
configuration: "the node s/SHOULD/MAY/ join the MPL domain given configuration: "the node s/SHOULD/MAY/ join the MPL domain given
by the option" (Issue #158) by the option" (Issue #158)
Updates on draft-doi-roll-mpl-configuration-05 to draft-ietf-roll- Updates on draft-doi-roll-mpl-configuration-05 to draft-ietf-roll-
 End of changes. 43 change blocks. 
121 lines changed or deleted 101 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/