draft-ietf-roll-mpl-parameter-configuration-02.txt   draft-ietf-roll-mpl-parameter-configuration-03.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 22, 2015 Itron, Inc Expires: July 25, 2015 Itron, Inc
July 21, 2014 January 21, 2015
MPL Parameter Configuration Option for DHCPv6 MPL Parameter Configuration Option for DHCPv6
draft-ietf-roll-mpl-parameter-configuration-02 draft-ietf-roll-mpl-parameter-configuration-03
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 January 22, 2015. This Internet-Draft will expire on July 25, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 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
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 19 skipping to change at page 2, line 19
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. MPL Parameter Configuration Option . . . . . . . . . . . . . 3 2. MPL Parameter Configuration Option . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . . . . . . . . 6 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 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. Non-Normative References . . . . . . . . . . . . . . . . 7
Appendix A. Update History . . . . . . . . . . . . . . . . . . . 8 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 . . . . . . . . . . . . . . . . . . . . . . . 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 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
skipping to change at page 3, line 5 skipping to change at page 3, line 5
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). And a parameter set are required to identical parameter set). And a parameter set are required to
configure an MPL domain. configure an MPL domain.
This document is to define the way to distribute parameter sets for This document is to define the way to distribute parameter sets for
MPL forwarders as a DHCPv6 [RFC3315] option. This document is MPL forwarders as a DHCPv6 [RFC3315] option. This document is
intended to follow the guideline [RFC7227]. intended to follow the guideline [RFC7227].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
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
skipping to change at page 6, line 13 skipping to change at page 6, line 17
from a DHCPv6 server previously. 2) The node has received an updated from a DHCPv6 server previously. 2) The node has received an updated
MPL Parameter Configuration Option without a configuration for the MPL Parameter Configuration Option without a configuration for the
MPL domain. MPL domain.
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 message may be
keep forwarder parameter sets synchronized. For stateless DHCPv6, used to keep forwarder parameter sets synchronized.
[I-D.jiang-dhc-stateless-reconfiguration] may be used (if approved).
2.4. 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.
skipping to change at page 7, line 18 skipping to change at page 7, line 26
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.
5. References 5. References
5.1. Normative References 5.1. Normative References
[I-D.ietf-roll-trickle-mcast] [I-D.ietf-roll-trickle-mcast]
Hui, J. and R. Kelsey, "Multicast Forwarding Using Hui, J. and R. Kelsey, "Multicast Forwarding Using
Trickle", draft-ietf-roll-trickle-mcast-07 (work in Trickle", draft-ietf-roll-trickle-mcast-11 (work in
progress), Feburary 2014. progress), November 2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
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. Non-Normative References
[I-D.ietf-dhc-option-guidelines]
Hankins, D., Mrugalski, T., Siodelski, M., Jiang, S., and
S. Krishnan, "Guidelines for Creating New DHCPv6 Options",
draft-ietf-dhc-option-guidelines-17 (work in progress),
January 2014.
[I-D.jiang-dhc-stateless-reconfiguration]
Jiang, S. and B. Liu, "Stateless Reconfiguration in
Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
draft-jiang-dhc-stateless-reconfiguration-01 (work in
progress), February 2014.
[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-02 to draft-ietf-roll-
mpl-configuration-03:
o References updated
o Removed reference for DHCPv6 stateless reconfiguration as it has
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)
Updates on draft-ietf-roll-mpl-configuration-00 to draft-ietf-roll- Updates on draft-ietf-roll-mpl-configuration-00 to draft-ietf-roll-
mpl-configuration-01: mpl-configuration-01:
 End of changes. 11 change blocks. 
25 lines changed or deleted 26 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/