5908
PROPOSED STANDARD
Network Time Protocol (NTP) Server Option for DHCPv6
Authors: R. Gayraud, B. Lourdelet
Date: June 2010
Area: int
Working Group: ntp
Stream: IETF
Abstract
The NTP Server Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) provides NTPv4 (Network Time Protocol version 4) server location information to DHCPv6 hosts. [STANDARDS-TRACK]
RFC 5908
PROPOSED STANDARD
Errata Exist
Internet Engineering Task Force (IETF) R. Gayraud
Request for Comments: 5908 Unaffiliated
Category: Standards Track B. Lourdelet
ISSN: 2070-1721 Cisco Systems, Inc.
June 2010
<span class="h1">Network Time Protocol (NTP) Server Option for DHCPv6</span>
Abstract
The NTP Server Option for Dynamic Host Configuration Protocol for
IPv6 (DHCPv6) provides NTPv4 (Network Time Protocol version 4) server
location information to DHCPv6 hosts.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc5908">http://www.rfc-editor.org/info/rfc5908</a>.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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
described in the Simplified BSD License.
<span class="grey">Gayraud & Lourdelet Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc5908">RFC 5908</a> NTP Server Option for DHCPv6 June 2010</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Requirements Notation ...........................................<a href="#page-2">2</a>
<a href="#section-3">3</a>. Related Work and Usage Model ....................................<a href="#page-2">2</a>
<a href="#section-4">4</a>. NTP Server Option for DHCPv6 ....................................<a href="#page-3">3</a>
<a href="#section-4.1">4.1</a>. NTP Server Address Suboption ...............................<a href="#page-4">4</a>
<a href="#section-4.2">4.2</a>. NTP Multicast Address Suboption ............................<a href="#page-5">5</a>
<a href="#section-4.3">4.3</a>. NTP Server FQDN Suboption ..................................<a href="#page-6">6</a>
<a href="#section-5">5</a>. Appearance of This Option .......................................<a href="#page-6">6</a>
<a href="#section-6">6</a>. Security Considerations .........................................<a href="#page-7">7</a>
<a href="#section-7">7</a>. <a href="./rfc4075">RFC 4075</a> Deprecation ............................................<a href="#page-7">7</a>
<a href="#section-8">8</a>. IANA Considerations .............................................<a href="#page-7">7</a>
<a href="#section-9">9</a>. References ......................................................<a href="#page-8">8</a>
<a href="#section-9.1">9.1</a>. Normative References .......................................<a href="#page-8">8</a>
<a href="#section-9.2">9.2</a>. Informative References .....................................<a href="#page-8">8</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document defines a DHCPv6 option and associated suboptions to
provide Network Time Protocol version 4 [<a href="./rfc5905" title=""Network Time Protocol Version 4: Protocol and Algorithms Specification"">RFC5905</a>] or greater server
location information to DHCPv6 hosts.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Notation</span>
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 [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Related Work and Usage Model</span>
The NTP service is publicly offered on the Internet by a number of
organizations. Those servers can be used but should not be abused,
so any method that is tasked to disseminate locations of NTP servers
must act responsibly in a manner that does not lead to public server
overloading. When using DHCPv6 to offer NTP server location, and if
there is a need to distribute a host with a hardcoded configuration,
this configuration MUST NOT include server location that is not part
of the organization that distributes this device. Typical usage of
this option is to specify an NTP server that is part of the
organization that operates the DHCPv6 server.
The location of the NTP service, like any other Internet service, can
be specified by an IP address or a Fully Qualified Domain Name
(FQDN). By design, DHCP offers information to multiple devices and
is prone to amplification of mistakes, so great care must be taken to
define its configuration. Specification of the NTP service by FQDN
offers a level of indirection that works as a possible mitigation
<span class="grey">Gayraud & Lourdelet Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc5908">RFC 5908</a> NTP Server Option for DHCPv6 June 2010</span>
tool in case of misconfiguration. DNS can be used to redirect
misconfigured clients to an IPv6 address that is not configured on
any host instead of having to change the address of the NTP server
itself.
While the NTP specification defines a comprehensive set of
configuration parameters, modification of those parameters is best
left to the decision of the client itself. The DHCPv6 option for NTP
is therefore restricted to server location.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. NTP Server Option for DHCPv6</span>
This option serves as a container for server location information
related to one NTP server or Simple Network Time Protocol (SNTP)
[<a href="./rfc4330" title=""Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI"">RFC4330</a>] server. This option can appear multiple times in a DHCPv6
message. Each instance of this option is to be considered by the NTP
client or SNTP client as a server to include in its configuration.
The option itself does not contain any value. Instead, it contains
one or several suboptions that carry NTP server or SNTP server
location. This option MUST include one, and only one, time source
suboption. The currently defined time source suboptions are
NTP_OPTION_SRV_ADDR, NTP_OPTION_SRV_MC_ADDR, and NTP_OPTION_SRV_FQDN.
It carries the NTP server or SNTP server location as a unicast or
multicast IPv6 address or as an NTP server or SNTP server FQDN. More
time source suboptions may be defined in the future. While the FQDN
option offers the most deployment flexibility, resiliency as well as
security, the IP address options are defined to cover cases where a
DNS dependency is not desirable.
If the NTP server or SNTP server location is an IPv6 multicast
address, the client SHOULD use this address as an NTP multicast group
address and listen to messages sent to this group in order to
synchronize its clock.
<span class="grey">Gayraud & Lourdelet Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc5908">RFC 5908</a> NTP Server Option for DHCPv6 June 2010</span>
The format of the NTP Server Option is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_NTP_SERVER | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| suboption-1 |
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| suboption-2 |
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| suboption-n |
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_NTP_SERVER (56),
option-len: Total length of the included suboptions.
This document does not define any priority relationship between the
client's embedded configuration (if any) and the NTP or SNTP servers
discovered via this option. In particular, the client is allowed to
simultaneously use its own configured NTP servers or SNTP servers and
the servers discovered via DHCP.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. NTP Server Address Suboption</span>
This suboption is intended to appear inside the OPTION_NTP_SERVER
option. It specifies the IPv6 unicast address of an NTP server or
SNTP server available to the client.
<span class="grey">Gayraud & Lourdelet Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc5908">RFC 5908</a> NTP Server Option for DHCPv6 June 2010</span>
The format of the NTP Server Address Suboption is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NTP_SUBOPTION_SRV_ADDR | suboption-len = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| |
| IPv6 address of NTP server |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv6 address of the NTP server: An IPv6 address,
suboption-code: NTP_SUBOPTION_SRV_ADDR (1),
suboption-len: 16.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. NTP Multicast Address Suboption</span>
This suboption is intended to appear inside the OPTION_NTP_SERVER
option. It specifies the IPv6 address of the IPv6 multicast group
address used by NTP on the local network.
The format of the NTP Multicast Address Suboption is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NTP_SUBOPTION_MC_ADDR | suboption-len = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| |
| Multicast IPv6 address |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Multicast IPv6 address: An IPv6 address,
suboption-code: NTP_SUBOPTION_MC_ADDR (2),
suboption-len: 16.
<span class="grey">Gayraud & Lourdelet Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc5908">RFC 5908</a> NTP Server Option for DHCPv6 June 2010</span>
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. NTP Server FQDN Suboption</span>
This suboption is intended to appear inside the OPTION_NTP_SERVER
option. It specifies the FQDN of an NTP server or SNTP server
available to the client.
The format of the NTP Server FQDN Suboption is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NTP_SUBOPTION_SRV_FQDN | suboption-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| FQDN of NTP server |
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
suboption-code: NTP_SUBOPTION_SRV_FQDN (3),
suboption-len: Length of the included FQDN field,
FQDN: Fully-Qualified Domain Name of the NTP server or SNTP server.
This field MUST be encoded as described in <a href="./rfc3315#section-8">[RFC3315],
Section 8</a>. Internationalized domain names are not allowed
in this field.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Appearance of This Option</span>
The OPTION_NTP_SERVER option can appear multiple times in a DHCPv6
message. The order in which these options appear is not significant.
The client uses its usual algorithms to determine which server(s) or
multicast group(s) should be preferred to synchronize its clock.
The OPTION_NTP_SERVER option MUST NOT appear in messages other than
the following: Solicit, Advertise, Request, Renew, Rebind,
Information-Request, and Reply. If this option appears in messages
other than those specified above, the receiver MUST ignore it.
The option number for this option MAY appear in the "Option Request"
option [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>] in the following messages: Solicit, Request, Renew,
Rebind, Information-Request, and Reconfigure. If this option number
appears in the "Option Request" option in messages other than those
specified above, the receiver SHOULD ignore it.
<span class="grey">Gayraud & Lourdelet Standards Track [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc5908">RFC 5908</a> NTP Server Option for DHCPv6 June 2010</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
This option could be used by an intruder to advertise the address of
a malicious NTP server or SNTP server and adversely affect the clock
of clients on the network. The consequences of such an attack can be
critical, because many security protocols depend on time
synchronization to run their algorithms. As an example, an attacker
could break connectivity between SEND-enabled nodes [<a href="./rfc3971" title=""SEcure Neighbor Discovery (SEND)"">RFC3971</a>], simply
by affecting the clock on these nodes.
To prevent these attacks, it is strongly advisable to secure the use
of this option by either:
- using the NTPv4 Autokey public key authentication, as defined in
[<a href="./rfc5906" title=""Network Time Protocol Version 4: Autokey Specification"">RFC5906</a>] or,
- using authenticated DHCP as described in <a href="./rfc3315#section-21">[RFC3315], Section 21</a>.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. <a href="./rfc4075">RFC 4075</a> Deprecation</span>
"Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6"
[<a href="./rfc4075" title=""Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6"">RFC4075</a>] provides some degree of automatic time server configuration
for IPv6, as it specifies how to transmit SNTP [<a href="./rfc4330" title=""Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI"">RFC4330</a>] server
addresses through DHCPv6. However, this approach is not suitable for
all NTP deployments. It is not an extensible mechanism and
introduces some semantic confusion through the use of the "SNTP"
acronym. Additionally, the approach of only offering IPv6 addresses
to specify server location does not meet NTP requirements that make
use of an FQDN (Fully-Qualified Domain Name) as well. For all the
abovementioned reasons, this document makes [<a href="./rfc4075" title=""Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6"">RFC4075</a>] deprecated.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
IANA has assigned 56 as an option code from the "DHCPv6 Options
Codes" registry for OPTION_NTP_SERVER.
IANA is required to maintain a new number space of NTP time source
suboptions, located in the BOOTP-DHCP Parameters Registry. The
initial suboptions are described in <a href="#section-4">Section 4</a> of this document. IANA
assigns future NTP time source suboptions with an "IETF Consensus"
policy as described in [<a href="./rfc5226" title="">RFC5226</a>]. Future proposed suboptions are to
be referenced symbolically in the documents that describe them, and
shall be assigned numeric codes by IANA when approved for publication
as an RFC.
<span class="grey">Gayraud & Lourdelet Standards Track [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc5908">RFC 5908</a> NTP Server Option for DHCPv6 June 2010</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC3315">RFC3315</a>] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, July 2003.
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
May 2008.
[<a id="ref-RFC5905">RFC5905</a>] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
"Network Time Protocol Version 4: Protocol and Algorithms
Specification", <a href="./rfc5905">RFC 5905</a>, June 2010.
[<a id="ref-RFC5906">RFC5906</a>] Haberman, B., Ed. and D. Mills, "Network Time Protocol
Version 4: Autokey Specification", <a href="./rfc5906">RFC 5906</a>, June 2010.
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
[<a id="ref-RFC3971">RFC3971</a>] Arkko, J., Kempf, J., Zill, B., and P. Nikander, "SEcure
Neighbor Discovery (SEND)", <a href="./rfc3971">RFC 3971</a>, March 2005.
[<a id="ref-RFC4075">RFC4075</a>] Kalusivalingam, V., "Simple Network Time Protocol (SNTP)
Configuration Option for DHCPv6", <a href="./rfc4075">RFC 4075</a>, May 2005.
[<a id="ref-RFC4330">RFC4330</a>] Mills, D., "Simple Network Time Protocol (SNTP) Version 4
for IPv4, IPv6 and OSI", <a href="./rfc4330">RFC 4330</a>, January 2006.
<span class="grey">Gayraud & Lourdelet Standards Track [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc5908">RFC 5908</a> NTP Server Option for DHCPv6 June 2010</span>
Authors' Addresses
Richard Gayraud
Unaffiliated
EMail: [email protected]
Benoit Lourdelet
Cisco Systems, Inc.
Village ent. GreenSide, Bat T3,
400, Av de Roumanille,
06410 BIOT - Sophia-Antipolis Cedex
France
Phone: +33 4 97 23 26 23
EMail: [email protected]
Gayraud & Lourdelet Standards Track [Page 9]
Annotations
Select text to annotate