draft-ietf-dhc-addr-registration-06.txt   draft-ietf-dhc-addr-registration-07.txt 
DHC Working Group S. Jiang DHC Working Group S. Jiang
Internet-Draft Huawei Technologies Co., Ltd Internet-Draft Huawei Technologies Co., Ltd
Intended status: Standards Track G. Chen Intended status: Standards Track G. Chen
Expires: January 21, 2015 China Mobile Expires: March 15, 2015 China Mobile
S. Krishnan S. Krishnan
Ericsson Ericsson
R. Asati R. Asati
Cisco Systems, Inc. Cisco Systems, Inc.
July 20, 2014 September 11, 2014
Registering Self-generated IPv6 Addresses in DNS using DHCPv6 Registering Self-generated IPv6 Addresses in DNS using DHCPv6
draft-ietf-dhc-addr-registration-06 draft-ietf-dhc-addr-registration-07
Abstract Abstract
In networks that are centrally managed, self-generated addresses In networks that are centrally managed, self-generated addresses
cause some traceability issues due to their decentralized nature. cause some traceability issues due to their decentralized nature.
One of the most important issues in this regard is the inability to One of the most important issues in this regard is the inability to
register such addresses in DNS. This document defines a mechanism to register such addresses in DNS. This document defines a mechanism to
register self-generated and statically configured addresses in DNS register self-generated and statically configured addresses in DNS
through a DHCPv6 server. through a DHCPv6 server.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 21, 2015. This Internet-Draft will expire on March 15, 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
skipping to change at page 2, line 18 skipping to change at page 2, line 18
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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 3 3. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 3
4. DHCPv6 ADDR-REGISTRATION-REQUEST Message . . . . . . . . . . 4 4. DHCPv6 ADDR-REGISTRATION-REQUEST Message . . . . . . . . . . 4
5. DHCPv6 Address Registration Procedure . . . . . . . . . . . . 5 5. DHCPv6 Address Registration Procedure . . . . . . . . . . . . 5
5.1. DHCPv6 Address Registration Request . . . . . . . . . . . 5 5.1. DHCPv6 Address Registration Request . . . . . . . . . . . 6
5.2. Registration Expiry and Refresh . . . . . . . . . . . . . 5 5.2. Registration Expiry and Refresh . . . . . . . . . . . . . 6
5.3. Acknowledging Registration and Retransmission . . . . . . 6 5.3. Acknowledging Registration and Retransmission . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 7 9.1. Normative References . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . 8 9.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
In several common network scenarios, IPv6 addresses are self- In several common network scenarios, IPv6 addresses are self-
generated by the end-hosts by appending a self-generated interface generated by the end-hosts by appending a self-generated interface
identifier to a network-specified prefix. Examples of self-generated identifier to a network-specified prefix. Examples of self-generated
addresses include those created using IPv6 Stateless Address addresses include those created using IPv6 Stateless Address
Configuration [RFC4862] , temporary addresses [RFC4941] and Configuration [RFC4862] , temporary addresses [RFC4941] and
Cryptographically Generated Addresses (CGA) [RFC3972] etc. In Cryptographically Generated Addresses (CGA) [RFC3972] etc. In
several tighly controlled networks, hosts with self-generated several tightly controlled networks, hosts with self-generated
addresses may face some limitations. One such limitation is related addresses may face some limitations. One such limitation is related
to the inability of nodes with self-generated addresses to register to the inability of nodes with self-generated addresses to register
their IPv6-address-to-FQDN bindings in DNS. This is related to the their IPv6-address-to-FQDN bindings in DNS. This is related to the
fact that, in such networks, only certain nodes (e.g. The DHCPv6 fact that, in such networks, only certain nodes (e.g. The DHCPv6
server) are allowed to update these bindings in order to prevent end- server) are allowed to update these bindings in order to prevent end-
hosts from registering arbitrary addresses for their FQDNs or hosts from registering arbitrary addresses for their FQDNs or
associating their addresses with arbitrary domain names. associating their addresses with arbitrary domain names. The
administrators may not want to distribute the address of
authoritative name-server. Also, there is no way to propagate the
address of authoritative name server by any protocols. It is
preferred that the address registration server, which is under the
same management with the authoritative name-server, to know the
address of the authoritative name-server and make registration
requests on behalf of clients. It is preferred by administrators to
establish and manage one trust relationship between a single DHCPv6
(address registration) server and the DNS authoritative name-server,
rather than to distribute and manage trust relationships between many
clients and the DNS authoritative name-server.
For nodes that obtain their addresses through DHCPv6, a solution has For nodes that obtain their addresses through DHCPv6, a solution has
been specified in [RFC4704]. The solution works by including a been specified in [RFC4704]. The solution works by including a
Client FQDN option in the SOLICIT, REQUEST, RENEW or REBIND messages Client FQDN option in the SOLICIT, REQUEST, RENEW or REBIND messages
during the process of acquiring an address through DHCPv6. This during the process of acquiring an address through DHCPv6. This
document provides an analogous mechanism to register self-generated document provides an analogous mechanism to register self-generated
addresses in DNS. addresses in DNS.
A new ADDR-REGISTRATION-REQUEST DHCPv6 message type is defined to A new ADDR-REGISTRATION-REQUEST DHCPv6 message type is defined to
initiate the address registration request, and two new Status codes initiate the address registration request, and two new Status codes
skipping to change at page 3, line 44 skipping to change at page 4, line 20
| | | | | |
| | ADDR-REGISTRATION-REQUEST | | | ADDR-REGISTRATION-REQUEST |
|-------------------------------------------->| |-------------------------------------------->|
| | |Register | | |Register
| | |address | | |address
| | Acknowledgment |in DNS | | Acknowledgment |in DNS
|<--------------------------------------------| |<--------------------------------------------|
Figure 1: Address Registration Procedure Figure 1: Address Registration Procedure
Furthermore, the registration server MAY apply certain filter/accept
criteria for the address registration requests, particularly for the
client chosen domain names.
It is RECOMMENDED to only set up one address registration server It is RECOMMENDED to only set up one address registration server
within an administration domain, although there may be multiple within an administration domain, although there may be multiple
DHCPv6 servers. While multiple address registration servers does DHCPv6 servers. While using multiple address registration servers
potentially increase the load on DNS, because of how [RFC4703] and does potentially increase the load on DNS, because of how [RFC4703]
[RFC4704] work, this should NOT be an issue - the servers should work and [RFC4704] work, this should NOT be an issue - the servers should
correctly in updating DNS (either adding or removing the entries). work correctly in updating DNS (either adding or removing the
The broken part with multiple servers is the 'extension' of the entries). The broken part with multiple servers is the 'extension'
registration. If there are two address registration servers and both of the registration. If there are two address registration servers
receive the initial registration and (correctly) update DNS, the and both receive the initial registration and (correctly) update DNS,
problem comes when the client extends this but one of the servers the problem comes when the client extends this but one of the servers
does not receive this extension. Then, the server that missed the does not receive this extension. Then, the server that missed the
extension removes the entry prematurely (i.e., when it expired extension removes the entry prematurely (i.e., when it expired
originally). The coordination of multiple address registration originally).
servers is out of scope.
4. DHCPv6 ADDR-REGISTRATION-REQUEST Message 4. DHCPv6 ADDR-REGISTRATION-REQUEST Message
The DHCPv6 client sends an ADDR-REGISTRATION-REQUEST message to a The DHCPv6 client sends an ADDR-REGISTRATION-REQUEST message to a
server to request an address to be registered in the DNS. The format server to request an address to be registered in the DNS. The format
of the ADDR-REGISTRATION-REQUEST message is described as follows: of the ADDR-REGISTRATION-REQUEST message is described as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 4, line 36 skipping to change at page 5, line 25
msg-type Identifies the DHCPv6 message type; msg-type Identifies the DHCPv6 message type;
Set to ADDR-REGISTRATION-REQUEST (TBA1). Set to ADDR-REGISTRATION-REQUEST (TBA1).
transaction-id The transaction ID for this message exchange. transaction-id The transaction ID for this message exchange.
options Options carried in this message. options Options carried in this message.
DHCPv6 ADDR-REGISTRATION-REQUEST message DHCPv6 ADDR-REGISTRATION-REQUEST message
The ADDR-REGISTRATION-REQUEST message MUST NOT contain server- The ADDR-REGISTRATION-REQUEST message MUST NOT contain server-
identifier option and MUST contain the IA_NA option and the DHCPv6 identifier option and MUST contain the IA Address option and the
FQDN option [RFC4704]. The ADDR-REGISTRATION-REQUEST message is DHCPv6 FQDN option [RFC4704]. The ADDR-REGISTRATION-REQUEST message
dedicated for clients to initiate an address registration request is dedicated for clients to initiate an address registration request
toward an address registration server. Consequently, clients MUST toward an address registration server. Consequently, clients MUST
NOT put any Option Request Option(s) in the ADDR-REGISTRATION-REQUEST NOT put any Option Request Option(s) in the ADDR-REGISTRATION-REQUEST
message. message.
Clients MUST discard any received ADDR-REGISTRATION-REQUEST messages. Clients MUST discard any received ADDR-REGISTRATION-REQUEST messages.
Servers MUST discard any ADDR-REGISTRATION-REQUEST messages that meet Servers MUST discard any ADDR-REGISTRATION-REQUEST messages that meet
any of the following conditions: any of the following conditions:
o the message does not include a Client Identifier option. o the message does not include a Client Identifier option;
o the message includes a Server Identifier option.
o the message does not include at least one IA_NA option. o the message includes a Server Identifier option;
o the message does not include an IAADDR option encapsulated within o the message does not include at least one IA Address option;
the IA_NA option(s).
o the message does not include FQDN option (or include multiple FQDN o the message does not include FQDN option (or include multiple FQDN
options). options);
o the message includes an Option Request Option. o the message includes an Option Request Option.
Servers MUST discard any ADDR-REGISTRATION-REQUEST messages that do
not Servers MUST discard any ADDR-REGISTRATION-REQUEST messages that
do include any Option Request Option(s).
5. DHCPv6 Address Registration Procedure 5. DHCPv6 Address Registration Procedure
The DHCPv6 protocol is used as the address registration protocol when The DHCPv6 protocol is used as the address registration protocol when
a DHCPv6 server performs the role of an address registration server. a DHCPv6 server performs the role of an address registration server.
The DHCPv6 IA_NA option [RFC3315] and the DHCPv6 FQDN option The DHCPv6 IA Address option [RFC3315] and the DHCPv6 FQDN option
[RFC4704] are adopted in order to fulfill the address registration [RFC4704] are adopted in order to fulfill the address registration
interactions. interactions.
5.1. DHCPv6 Address Registration Request 5.1. DHCPv6 Address Registration Request
The end-host sends a DHCPv6 ADDR-REGISTRATION-REQUEST message to the The end-host sends a DHCPv6 ADDR-REGISTRATION-REQUEST message to the
address registration server to the All_DHCP_Relay_Agents_and_Servers address registration server to the All_DHCP_Relay_Agents_and_Servers
multicast address (ff02::1:2). multicast address (ff02::1:2).
The end-host MUST include a Client Identifier option in the ADDR- The end-host MUST include a Client Identifier option in the ADDR-
REGISTRATION-REQUEST message to identify itself to the server. The REGISTRATION-REQUEST message to identify itself to the server. The
DHCPv6 ADDR-REGISTRATION-REQUEST message MUST contain at least one DHCPv6 ADDR-REGISTRATION-REQUEST message MUST contain at least one IA
IA_NA option and exactly one FQDN option. The IA_NA option MUST Address option and exactly one FQDN option. The valid-lifetime field
contain at least one IA Address option. The valid-lifetime field of of the IA Address option MUST be set to the period for which the
the IA Address option MUST be set to the period for which the client client would like to register the binding in DNS.
would like to register the binding in DNS.
After receiving this ADDR-REGISTRATION-REQUEST message, the address After receiving this ADDR-REGISTRATION-REQUEST message, the address
registration server MUST register the binding between the provided registration server MUST register the binding between the provided
FQDN and address(es) in DNS. If the DHCPv6 server does not support FQDN and address(es) in DNS. If the DHCPv6 server does not support
address registration function, a Reply message with includes a Status address registration function, it MUST sliently drop the message.
Code option with the value the RegistrationNotSupported (TBA2) MAY be
sent back to the initiated client.
5.2. Registration Expiry and Refresh 5.2. Registration Expiry and Refresh
For every successful binding registration, the address registration For every successful binding registration, the address registration
server MUST record the IPv6-address-to-FQDN bindings and associated server MUST record the IPv6-address-to-FQDN bindings and associated
valid-lifetimes in its storage. valid-lifetimes in its storage.
The address registration client MUST refresh the registration before The address registration client MUST refresh the registration before
it expires (i.e. before the valid-lifetime of the IA address elapses) it expires (i.e. before the valid-lifetime of the IA address elapses)
by sending a new ADDR-REGISTRATION-REQUEST to the address by sending a new ADDR-REGISTRATION-REQUEST to the address
skipping to change at page 6, line 24 skipping to change at page 6, line 51
valid-lifetime. Because RAs may periodically 'reset' the valid- valid-lifetime. Because RAs may periodically 'reset' the valid-
lifetime, the refresh timer MUST be independently maintained from the lifetime, the refresh timer MUST be independently maintained from the
address valid-lifetime. Clients SHOULD set a refresh timer to 85% of address valid-lifetime. Clients SHOULD set a refresh timer to 85% of
the valid-lifetime when they complete a registration operation and the valid-lifetime when they complete a registration operation and
only update this timer if 85% of any updated valid-lifetime would be only update this timer if 85% of any updated valid-lifetime would be
sooner than the timer. sooner than the timer.
5.3. Acknowledging Registration and Retransmission 5.3. Acknowledging Registration and Retransmission
After an address registration server accepts an address registration After an address registration server accepts an address registration
request, it MUST send a Reply message as the response to registration request, it MUST send a Reply message as the response to the client.
The server is responsilbe to register all the addresses in DNS. The The acceptence reply only means that the server has taken
server generates a Reply message and includes a Status Code option responsiblity to registry for the client. It may not have actually
with value Success, a Server Identifier option with the server's completed the update yet. The server is responsible to register all
DUID, and a Client Identifier option with the client's DUID. the addresses in DNS. The server generates a Reply message and
includes a Status Code option with value Success, a Server Identifier
option with the server's DUID, and a Client Identifier option with
the client's DUID.
If there is no reply received within some interval, the client SHOULD If there is no reply received within some interval, the client SHOULD
retransmits the message according to section 14 of [RFC3315], using retransmits the message according to section 14 of [RFC3315], using
the following parameters: the following parameters:
o IRT ADDR_REG_TIMEOUT o IRT ADDR_REG_TIMEOUT
o MRT ADDR_REG_MAX_RT o MRT ADDR_REG_MAX_RT
o MRC ADDR_REG_MAX_RC o MRC ADDR_REG_MAX_RC
o MRD 0 o MRD 0
Where ADDR_REG_TIMEOUT might be 1 second, ADDR_REG_MAX_RT might be 30 The below presents a table of values used to describe the message
minutes and ADDR_REG_MAX_RC might be 5. transmission behavior of clients and servers:
For each IA in the ADDR-REGISTRATION-REQUEST message for which the Parameter Default Description
server does not accept its associated in registration request, the ---------------------------------------------------------------------
server adds an IA option using the IAID from the ADDR-REGISTRATION- ADDR_REG_TIMEOUT 1 secs Initial Addr Registration Request timeout
REQUEST message, and includes a Status Code option with the value ADDR_REG_MAX_RT 60 secs Max Addr Registration Request timeout value
RegistrationDenied (TBA3) in the IA option. No other options are ADDR_REG_MAX_RC 5 Max Request retry attempts
included in the IA option.
For each IA Address option in the ADDR-REGISTRATION-REQUEST message
for which the server does not accept its associated registration
request, the server adds an IA Address option with the associated
IPv6 address, and includes a Status Code option with the value
RegistrationDenied (TBA2) in the IA Address option. No other options
are included in the IA Address option.
Upon receiving a RegistrationDenied error status code, the client MAY Upon receiving a RegistrationDenied error status code, the client MAY
also resend the message following normal retransmission routines also resend the message following normal retransmission routines
defined in [RFC3315] with above parameters. defined in [RFC3315] with above parameters. The client MUST wait out
the retransmission time before retrying.
6. Security Considerations 6. Security Considerations
An attacker may attempt to register large number of addresses in An attacker may attempt to register large number of addresses in
quick succession in order to overwhelm the address registration quick succession in order to overwhelm the address registration
server. These attacks may be prevented generic DHCPv6 protection by server. These attacks may be prevented generic DHCPv6 protection by
using the AUTH option [RFC3315] or Secure DHCPv6 using the AUTH option [RFC3315] or Secure DHCPv6
[I-D.ietf-dhc-sedhcpv6]. [I-D.ietf-dhc-sedhcpv6].
7. IANA Considerations 7. IANA Considerations
This document defines a new DHCPv6 message, the ADDR-REGISTRATION- This document defines a new DHCPv6 message, the ADDR-REGISTRATION-
REQUEST message (TBA1) described in Section 4, that requires an REQUEST message (TBA1) described in Section 4, that requires an
allocation out of the registry defined at allocation out of the registry of Message Types defined at
http://www.iana.org/assignments/dhcpv6-parameters/ http://www.iana.org/assignments/dhcpv6-parameters/
This document defines two new DHCPv6 Status code, the Value Description Reference
RegistrationNotSupported (TBA2) and RegistrationDenied (TBA3) -----------------------------------------------------
described in Section 5, that requires an allocation out of the TBA1 ADDR-REGISTRATION-REQUEST this document
registry defined at
This document defines a new DHCPv6 Status code, the
RegistrationDenied (TBA2) described in Section 5, that requires an
allocation out of the registry of Status Codes defined at
http://www.iana.org/assignments/dhcpv6-parameters/ http://www.iana.org/assignments/dhcpv6-parameters/
Code Name Reference
----------------------------------------------------
TBA2 RegistrationDenied this document
8. Acknowledgements 8. Acknowledgements
The authors would like to thank Ralph Droms, Ted Lemon, Bernie Volz, The authors would like to thank Ralph Droms, Ted Lemon, Bernie Volz,
Sten Carlsen, Erik Kline, Lorenzo Colitti, Joel Jaeggli, Sten Sten Carlsen, Erik Kline, Lorenzo Colitti, Joel Jaeggli, Sten
Carlsen, Mark Smith, Marcin Siodelski, Darpan Malhotra, Tomek Carlsen, Mark Smith, Marcin Siodelski, Darpan Malhotra, Tomek
Mrugalski and other members of dhc and v6ops working groups for their Mrugalski, Jinmei Tatuya and other members of dhc and v6ops working
valuable comments. groups for their valuable comments.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2136] Vixie, P., Thomson, S., Rekhter, Y., and J. Bound, [RFC2136] Vixie, P., Thomson, S., Rekhter, Y., and J. Bound,
"Dynamic Updates in the Domain Name System (DNS UPDATE)", "Dynamic Updates in the Domain Name System (DNS UPDATE)",
 End of changes. 29 change blocks. 
69 lines changed or deleted 89 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/