draft-ietf-roll-mpl-parameter-configuration-03.txt   draft-ietf-roll-mpl-parameter-configuration-04.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: July 25, 2015 Itron, Inc Expires: October 24, 2015 Itron, Inc
January 21, 2015 April 22, 2015
MPL Parameter Configuration Option for DHCPv6 MPL Parameter Configuration Option for DHCPv6
draft-ietf-roll-mpl-parameter-configuration-03 draft-ietf-roll-mpl-parameter-configuration-04
Abstract Abstract
This draft defines a way to configure a parameter set of MPL This draft defines a way to configure a parameter set of MPL
(Multicast Protocol for Low power and Lossy Networks) via DHCPv6 (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
skipping to change at page 1, line 38 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 July 25, 2015. This Internet-Draft will expire on October 24, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
skipping to change at page 2, line 23 skipping to change at page 2, line 23
2.1. MPL Parameter Configuration Option Format . . . . . . . . 3 2.1. MPL Parameter Configuration Option Format . . . . . . . . 3
2.2. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . 5 2.2. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . 5
2.3. MPL Forwarder Behavior . . . . . . . . . . . . . . . . . 5 2.3. MPL Forwarder Behavior . . . . . . . . . . . . . . . . . 5
2.4. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . 6 2.4. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . 6
2.5. DHCPv6 Relay Behavior . . . . . . . . . . . . . . . . . . 6 2.5. DHCPv6 Relay Behavior . . . . . . . . . . . . . . . . . . 6
2.6. Operational Considerations . . . . . . . . . . . . . . . 6 2.6. Operational Considerations . . . . . . . . . . . . . . . 6
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Normative References . . . . . . . . . . . . . . . . . . 7 5.1. Normative References . . . . . . . . . . . . . . . . . . 7
5.2. Non-Normative References . . . . . . . . . . . . . . . . 7 5.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Update History . . . . . . . . . . . . . . . . . . . 7 Appendix A. Update History . . . . . . . . . . . . . . . . . . . 7
Appendix B. Considerations on Inconsistent Parameter Set . . . . 8 Appendix B. Considerations on Inconsistent Parameter Set . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 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 e.g. wireless mesh network among low power and lossy network e.g. wireless mesh
networks. MPL has a set of parameters to control an MPL domain. The networks. MPL has a set of parameters to control an MPL domain. The
parameter controls trade-off between end-to-end delay and network parameter controls trade-off between end-to-end delay and network
utilization. In most environments, the default parameters are utilization. In most environments, the default parameters are
acceptable. However, in some environments, the parameter set must be acceptable. However, in some environments, the parameter set must be
skipping to change at page 4, line 36 skipping to change at page 4, line 36
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 18 (without MPL option_len: Length of the option. It SHOULD be 18 (without MPL
domain address) or 34 (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 (7 bits) Reserved. Should be 0. Z (7 bits) Reserved. Should be 0.
TUNIT (unsigned 8 bit integer) Unit time of times in this option. TUNIT (unsigned 8 bit integer) Unit time of times in this option. 0
It SHALL NOT be 0 or 255. and 0xff are reserved and SHALL NOT be used.
SE_LIFETIME: SEED_SET_ENTRY_LIFETIME/TUNIT in milliseconds. It SE_LIFETIME: SEED_SET_ENTRY_LIFETIME/TUNIT in milliseconds. 0 and
SHALL NOT be 0 or 0xffff. 0xffff are reserved and SHALL NOT be used.
DM_K (unsigned 8 bit integer): DATA_MESSAGE_K. DM_K (unsigned 8 bit integer): DATA_MESSAGE_K.
DM_IMIN (unsigned 16 bit integer): DATA_MESSAGE_IMIN/TUNIT in DM_IMIN (unsigned 16 bit integer): DATA_MESSAGE_IMIN/TUNIT in
milliseconds. It SHALL NOT be 0 or 0xffff. milliseconds. 0 and 0xffff are reserved and SHALL NOT be used.
DM_IMAX (unsigned 16 bit integer): DATA_MESSAGE_IMAX/TUNIT in DM_IMAX (unsigned 16 bit integer): DATA_MESSAGE_IMAX/TUNIT in
milliseconds. It SHALL NOT be 0 or 0xffff. milliseconds. 0 and 0xffff are reserved and SHALL NOT be used.
DM_T_EXP (unsigned 16 bit integer): DATA_MESSAGE_TIMER_EXPIRATIONS/ DM_T_EXP (unsigned 16 bit integer): DATA_MESSAGE_TIMER_EXPIRATIONS/
TUNIT in milliseconds. It SHALL NOT be 0 or 0xffff. TUNIT in milliseconds. 0 and 0xffff are reserved and SHALL NOT be
used.
C_K (unsigned 8 bit integer): CONTROL_MESSAGE_K. C_K (unsigned 8 bit integer): CONTROL_MESSAGE_K.
C_IMIN (unsigned 16 bit integer): CONTROL_MESSAGE_IMIN/TUNIT in C_IMIN (unsigned 16 bit integer): CONTROL_MESSAGE_IMIN/TUNIT in
milliseconds. It SHALL NOT be 0 or 0xffff. milliseconds. 0 and 0xffff are reserved and SHALL NOT be used.
C_IMAX: CONTROL_MESSAGE_IMAX/TUNIT in milliseconds. It SHALL NOT be C_IMAX: CONTROL_MESSAGE_IMAX/TUNIT in milliseconds. 0 and 0xffff are
0 or 0xffff. reserved and SHALL NOT be used.
C_T_EXP: CONTROL_MESSAGE_TIMER_EXPIRATIONS/TUNIT in milliseconds. C_T_EXP: CONTROL_MESSAGE_TIMER_EXPIRATIONS/TUNIT in milliseconds. 0
It SHALL NOT be 0 or 0xffff. and 0xffff are reserved and SHALL NOT be used.
Note that all time values (Trickle timers and expiration periods) are Note that all time values (Trickle timers and expiration periods) are
in TUNIT milliseconds precision. For example, if TUNIT is 20 and the in TUNIT milliseconds precision. For example, if TUNIT is 20 and the
data message interval minimum (DATA_MESSAGE_IMIN) is 1000ms, then data message interval minimum (DATA_MESSAGE_IMIN) is 1000ms, then
DM_IMIN shall be set to 50. DM_IMIN shall be set to 50.
2.2. DHCPv6 Client Behavior 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
skipping to change at page 7, line 7 skipping to change at page 7, line 7
than 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 IANA is requested to assign one option code for OPTION_MPL_PARAMETERS
be assigned from IANA. from the "DHCP Option Codes" table of the Dynamic Host Configuration
Protocol for IPv6 (DHCPv6) Registry.
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
implementation dependent or may be derived from MAC/PHY implementation dependent or may be derived from MAC/PHY
specifications. DHCP server or the network itself shall be trusted specifications. DHCP server or the network itself shall be trusted
by some means including network access control or DHCP by some means including network access control or DHCP
authentications. authentications.
skipping to change at page 7, line 40 skipping to change at page 7, line 41
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC4242] Venaas, S., Chown, T., and B. Volz, "Information Refresh [RFC4242] Venaas, S., Chown, T., and B. Volz, "Information Refresh
Time Option for Dynamic Host Configuration Protocol for Time Option for Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 4242, November 2005. IPv6 (DHCPv6)", RFC 4242, November 2005.
5.2. Non-Normative References 5.2. Informative References
[RFC7227] Hankins, D., Mrugalski, T., Siodelski, M., Jiang, S., and [RFC7227] Hankins, D., Mrugalski, T., Siodelski, M., Jiang, S., and
S. Krishnan, "Guidelines for Creating New DHCPv6 Options", S. Krishnan, "Guidelines for Creating New DHCPv6 Options",
BCP 187, RFC 7227, May 2014. BCP 187, RFC 7227, May 2014.
Appendix A. Update History Appendix A. Update History
Updates on draft-ietf-roll-mpl-configuration-03 to draft-ietf-roll-
mpl-configuration-04:
o References updated (Non-normative -> Informative)
o IANA section is updated to make clear request of option ID
o Typo fixed
Updates on draft-ietf-roll-mpl-configuration-02 to draft-ietf-roll- Updates on draft-ietf-roll-mpl-configuration-02 to draft-ietf-roll-
mpl-configuration-03: mpl-configuration-03:
o References updated o References updated
o Removed reference for DHCPv6 stateless reconfiguration as it has o Removed reference for DHCPv6 stateless reconfiguration as it has
expired expired
Updates on draft-ietf-roll-mpl-configuration-01 to draft-ietf-roll- Updates on draft-ietf-roll-mpl-configuration-01 to draft-ietf-roll-
mpl-configuration-02: mpl-configuration-02:
o Short unsigned floating point is dropped (#159) o Short unsigned floating point is dropped (#159)
o Packed value is removed and now every value has its own byte(s) o Packed value is removed and now every value has its own byte(s)
(#159) (#159)
 End of changes. 17 change blocks. 
21 lines changed or deleted 32 lines changed or added

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