draft-ietf-ntp-dhcpv6-ntp-opt-05.txt   draft-ietf-ntp-dhcpv6-ntp-opt-06.txt 
Network Working Group R. Gayraud Network Working Group R. Gayraud
Internet-Draft None Internet-Draft
Intended status: Standards Track B. Lourdelet Intended status: Standards Track B. Lourdelet
Expires: April 5, 2010 Cisco Systems, Inc. Expires: July 11, 2010 Cisco Systems, Inc.
October 2, 2009 January 7, 2010
Network Time Protocol (NTP) Server Option for DHCPv6 Network Time Protocol (NTP) Server Option for DHCPv6
draft-ietf-ntp-dhcpv6-ntp-opt-05.txt draft-ietf-ntp-dhcpv6-ntp-opt-06.txt
Abstract
The NTP Server Option for Dynamic Host Configuration Protocol for
IPv6 (DHCPv6) provides NTP (Network Time Protocol version 4) Server
location information to DHCPv6 hosts.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79.
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 5, 2010. This Internet-Draft will expire on July 11, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract 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 BSD License.
The NTP Server Option for Dynamic Host Configuration Protocol for This document may contain material from IETF Documents or IETF
IPv6 (DHCPv6) provides NTP (Network Time Protocol version 4) Server Contributions published or made publicly available before November
location information to DHCPv6 hosts. 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Requirements notation . . . . . . . . . . . . . . . . . . . . . 3 2. Requirements notation . . . . . . . . . . . . . . . . . . . . 4
3. Related Work and Usage Model . . . . . . . . . . . . . . . . . 3 3. Related Work and Usage Model . . . . . . . . . . . . . . . . . 4
4. NTP Server Option for DHCPv6 . . . . . . . . . . . . . . . . . 3 4. NTP Server Option for DHCPv6 . . . . . . . . . . . . . . . . . 4
4.1. NTP Server Address Suboption . . . . . . . . . . . . . . . 5 4.1. NTP Server Address Suboption . . . . . . . . . . . . . . . 6
4.2. NTP Multicast Address Suboption . . . . . . . . . . . . . . 5 4.2. NTP Multicast Address Suboption . . . . . . . . . . . . . 6
4.3. NTP Server FQDN Suboption . . . . . . . . . . . . . . . . . 6 4.3. NTP Server FQDN Suboption . . . . . . . . . . . . . . . . 7
5. Appearance of this Option . . . . . . . . . . . . . . . . . . . 6 5. Appearance of this Option . . . . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. RFC 4075 Deprecation . . . . . . . . . . . . . . . . . . . . . 7 7. RFC 4075 Deprecation . . . . . . . . . . . . . . . . . . . . . 8
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1. Normative References . . . . . . . . . . . . . . . . . . . 7 9.1. Normative References . . . . . . . . . . . . . . . . . . . 9
9.2. Informative References . . . . . . . . . . . . . . . . . . 8 9.2. Informative References . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
This document defines a DHCPv6 option and associated suboptions to This document defines a DHCPv6 option and associated suboptions to
provide Network Time Protocol version 4 [draft-ntpv4] or greater provide Network Time Protocol version 4 [draft-ntpv4] or greater
Server location information to DHCPv6 hosts. Server location information to DHCPv6 hosts.
2. Requirements notation 2. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Related Work and Usage Model 3. Related Work and Usage Model
The NTP service is publicly offered on the Internet by a number of The NTP service is publicly offered on the Internet by a number of
organizations. Those Servers can be used but not abused, so any organizations. Those Servers can be used but should not be abused,
method which is tasked to disseminate locations of NTP Servers must so any method which is tasked to disseminate locations of NTP Servers
act responsibly in a manner that does not lead to public Server must act responsibly in a manner that does not lead to public Server
overloading. When using DHCPv6 to offer NTP Server location, and if overloading. When using DHCPv6 to offer NTP Server location, and if
there is a need to distribute a host with a hardcoded configuration, there is a need to distribute a host with a hardcoded configuration,
this configuration MUST NOT include Server location that is not part this configuration MUST NOT include Server location that is not part
of the organization that distributes this device. Typical usage of of the organization that distributes this device. Typical usage of
this option is to specify an NTP Server that is part of the this option is to specify an NTP Server that is part of the
organization that operates the DHCPv6 Server. organization that operates the DHCPv6 Server.
The location of the NTP service, like any other Internet service, can The location of the NTP service, like any other Internet service, can
be specified by an IP address or a Fully Qualified Domain Name be specified by an IP address or a Fully Qualified Domain Name
(FQDN). By design, DHCP offers information to multiple devices and (FQDN). By design, DHCP offers information to multiple devices and
skipping to change at page 5, line 25 skipping to change at page 6, line 25
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NTP_SUBOPTION_SRV_ADDR | suboption-len = 16 | | NTP_SUBOPTION_SRV_ADDR | suboption-len = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| | | |
| IPv6 address of NTP Server | | IPv6 address of NTP Server |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv6 address of the NTP Server: An IPv6 address,
suboption-code: NTP_SUBOPTION_SRV_ADDR (1), suboption-code: NTP_SUBOPTION_SRV_ADDR (1),
suboption-len: 16. suboption-len: 16.
4.2. NTP Multicast Address Suboption 4.2. NTP Multicast Address Suboption
This suboption is intended to appear inside the OPTION_NTP_SERVER This suboption is intended to appear inside the OPTION_NTP_SERVER
option. It specifies the IPv6 address of the IPv6 multicast group option. It specifies the IPv6 address of the IPv6 multicast group
address used by NTP on the local network. address used by NTP on the local network.
skipping to change at page 5, line 48 skipping to change at page 7, line 18
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NTP_SUBOPTION_MC_ADDR | suboption-len = 16 | | NTP_SUBOPTION_MC_ADDR | suboption-len = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| | | |
| Multicast IPv6 address | | Multicast IPv6 address |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Multicast IPv6 address: An IPv6 address,
suboption-code: NTP_SUBOPTION_MC_ADDR (2), suboption-code: NTP_SUBOPTION_MC_ADDR (2),
suboption-len: 16. suboption-len: 16.
4.3. NTP Server FQDN Suboption 4.3. NTP Server FQDN Suboption
This suboption is intended to appear inside the OPTION_NTP_SERVER This suboption is intended to appear inside the OPTION_NTP_SERVER
option. It specifies the FQDN of an NTP Server or SNTP Server option. It specifies the FQDN of an NTP Server or SNTP Server
available to the client. available to the client.
skipping to change at page 6, line 29 skipping to change at page 7, line 48
| FQDN of NTP Server | | FQDN of NTP Server |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
suboption-code: NTP_SUBOPTION_SRV_FQDN (3), suboption-code: NTP_SUBOPTION_SRV_FQDN (3),
suboption-len: Length of the included FQDN field, suboption-len: Length of the included FQDN field,
FQDN: Fully Qualified Domain Name of the NTP Server or SNTP Server. FQDN: Fully Qualified Domain Name of the NTP Server or SNTP Server.
This field MUST be encoded as described in [RFC3315], This field MUST be encoded as described in [RFC3315],
section 8. section 8. Internationalized Domain Name are not allowed
in this field.
5. Appearance of this Option 5. Appearance of this Option
The OPTION_NTP_SERVER option can appear multiple times in a DHCPv6 The OPTION_NTP_SERVER option can appear multiple times in a DHCPv6
message. The order in which these options appear is not significant. message. The order in which these options appear is not significant.
The client uses its usual algorithms to determine which Server(s) or The client uses its usual algorithms to determine which Server(s) or
multicast group(s) should be prefered to synchronize its clock. multicast group(s) should be prefered to synchronize its clock.
The OPTION_NTP_SERVER option MUST NOT appear in messages other than The OPTION_NTP_SERVER option MUST NOT appear in messages other than
the following: Solicit, Advertise, Request, Renew, Rebind, the following: Solicit, Advertise, Request, Renew, Rebind,
skipping to change at page 7, line 42 skipping to change at page 9, line 13
requirements that make use of a FQDN (Fully Qualified Domain Name) as requirements that make use of a FQDN (Fully Qualified Domain Name) as
well. For all the abovementioned reasons, this document makes well. For all the abovementioned reasons, this document makes
[RFC4075] deprecated. [RFC4075] deprecated.
8. IANA Considerations 8. IANA Considerations
When this document is published, the IANA is requested to assign an When this document is published, the IANA is requested to assign an
option code from the "DHCPv6 Options Codes" registry for option code from the "DHCPv6 Options Codes" registry for
OPTION_NTP_SERVER. 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 section 4 of this document. IANA
assigns future NTP time source suboptions with a "IETF Consensus"
policy as described in [RFC5226]. Future proposed suboptions are to
be referenced symbolically in the Internet-Drafts that describe them,
and shall be assigned numeric codes by IANA when approved for
publication as an RFC.
9. References 9. References
9.1. Normative References 9.1. Normative References
[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.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[draft-ntpv4] [draft-ntpv4]
Burbank, J., Kasch, W., Martin, J., and D. Mills, "Network Burbank, J., Kasch, W., Martin, J., and D. Mills, "Network
Time Protocol Version 4 Protocol And Algorithms Time Protocol Version 4 Protocol And Algorithms
Specification", draft-ietf-ntp-ntpv4-proto-11 (work in Specification", draft-ietf-ntp-ntpv4-proto-11 (work in
progress), September 2008. progress), September 2008.
[draft-autokey] [draft-autokey]
Haberman, B. and D. Mills, "Network Time Protocol Version Haberman, B. and D. Mills, "Network Time Protocol Version
4 Autokey Specification", draft-ietf-ntp-autokey-06 (work 4 Autokey Specification", draft-ietf-ntp-autokey-06 (work
in progress), July 2009. in progress), July 2009.
skipping to change at page 8, line 33 skipping to change at page 10, line 17
[RFC4075] Kalusivalingam, V., "Simple Network Time Protocol (SNTP) [RFC4075] Kalusivalingam, V., "Simple Network Time Protocol (SNTP)
Configuration Option for DHCPv6", RFC 4075, May 2005. Configuration Option for DHCPv6", RFC 4075, May 2005.
[RFC4330] Mills, D., "Simple Network Time Protocol (SNTP) Version 4 [RFC4330] Mills, D., "Simple Network Time Protocol (SNTP) Version 4
for IPv4, IPv6 and OSI", RFC 4330, January 2006. for IPv4, IPv6 and OSI", RFC 4330, January 2006.
Authors' Addresses Authors' Addresses
Richard Gayraud Richard Gayraud
None
Email: richard.gayraud@free.fr Email: richard.gayraud@free.fr
Benoit Lourdelet Benoit Lourdelet
Cisco Systems, Inc. Cisco Systems, Inc.
Village ent. GreenSide, Bat T3, Village ent. GreenSide, Bat T3,
400, Av de Roumanille, 400, Av de Roumanille,
06410 BIOT - Sophia-Antipolis Cedex 06410 BIOT - Sophia-Antipolis Cedex
France France
 End of changes. 16 change blocks. 
46 lines changed or deleted 69 lines changed or added

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