draft-ietf-dhc-addr-registration-03.txt   draft-ietf-dhc-addr-registration-04.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: March 2, 2014 China Mobile Expires: August 18, 2014 China Mobile
S. Krishnan S. Krishnan
Ericsson Ericsson
August 29, 2013 R. Asati
Cisco Systems
February 14, 2014
Registering self-generated IPv6 Addresses in DNS using DHCPv6 Registering self-generated IPv6 Addresses in DNS using DHCPv6
draft-ietf-dhc-addr-registration-03 draft-ietf-dhc-addr-registration-04
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 addresses in DNS through a DHCPv6 server. register self-generated and statically configured addresses in DNS
through a DHCPv6 server.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 March 2, 2014. This Internet-Draft will expire on August 18, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 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
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . 5
5.2. Acknowledging successful registration . . . . . . . . . . . 5 5.2. Registration expiry and refresh . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 5.3. Acknowledging successful registration . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Normative References . . . . . . . . . . . . . . . . . . . 6 9.1. Normative References . . . . . . . . . . . . . . . . . . . 6
9.2. Informative References . . . . . . . . . . . . . . . . . . 7 9.2. Informative References . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
In several common network scenarios, IPv6 addresses are self- In several common network scenarios, IPv6 addresses are self-
skipping to change at page 4, line 10 skipping to change at page 4, line 10
request, the DHCPv6 server registers the IPv6 address to FQDN binding request, the DHCPv6 server registers the IPv6 address to FQDN binding
towards a configured DNS server. An acknowledgement MAY be sent back towards a configured DNS server. An acknowledgement MAY be sent back
to the end host to indicate whether or not the registration operation to the end host to indicate whether or not the registration operation
succeeded.. succeeded..
+----+ +-----------+ +---------------+ +----+ +-----------+ +---------------+
|Host| |Edge router| |Addr-Reg Server| |Host| |Edge router| |Addr-Reg Server|
+----+ +-----------+ +---------------+ +----+ +-----------+ +---------------+
| SLAAC | | | SLAAC | |
|<--------->| | |<--------->| |
| | | | |
| ADDR-REGISTRATION-REQUEST | | | ADDR-REGISTRATION-REQUEST |
|------------------------------------->| |------------------------------------------------->|
| |Register | | |Register
| |address | | |address
| Optional Acknowledgment |in DNS | | Optional Acknowledgment |in DNS
|<-------------------------------------| |<-------------------------------------------------|
Figure 1: Address Registration Procedure Figure 1: Address Registration Procedure
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
skipping to change at page 5, line 24 skipping to change at page 5, line 24
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 exactly one DHCPv6 ADDR-REGISTRATION-REQUEST message MUST contain exactly one
IA_NA option and exactly one FQDN option. The IA_NA option MUST IA_NA option and exactly one FQDN option. The IA_NA option MUST
contain at least one IA Address option. contain at least one IA Address option. The valid-lifetime field of
the IA Address option MUST be set to the period for which the client
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, a Reply message with includes a Status
Code option with the value the RegistrationNotSupported (TBA2) MAY be Code option with the value the RegistrationNotSupported (TBA2) MAY be
sent back to the initiated client. sent back to the initiated client.
5.2. Acknowledging successful registration 5.2. Registration expiry and refresh
The address registration client MUST refresh the registration before
it expires (i.e. before the valid-lifetime of the IA address elapses)
by sending a new ADDR-REGISTRATION-REQUEST to the address
registration server. If the address registration server does not
receive such a refresh after the valid-lifetime has passed, it SHOULD
remove the IPv6-address-to-FQDN bindings in DNS.
5.3. Acknowledging successful registration
After all the addresses have been successfully registered in DNS, the After all the addresses have been successfully registered in DNS, the
address registration server MAY send a Reply message as the response address registration server MAY send a Reply message as the response
to registration requests. The server generates a Reply message and to registration requests. The server generates a Reply message and
includes a Status Code option with value Success, a Server Identifier includes a Status Code option with value Success, a Server Identifier
option with the server's DUID, and a Client Identifier option with option with the server's DUID, and a Client Identifier option with
the client's DUID. For each IA in the Release message for which the the client's DUID. For each IA in the ADDR-REGISTRATION-REQUEST
server does not succeed in registering, the server adds an IA option message for which the server does not succeed in registering, the
using the IAID from the ADDR-REGISTRATION-REQUEST message, and server adds an IA option using the IAID from the ADDR-REGISTRATION-
includes a Status Code option with the value RegistrationDenied REQUEST message, and includes a Status Code option with the value
(TBA3) in the IA option. No other options are included in the IA RegistrationDenied (TBA3) in the IA option. No other options are
option. included in the IA option.
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-secure-dhcpv6]. [I-D.ietf-dhc-secure-dhcpv6].
7. IANA Considerations 7. IANA Considerations
skipping to change at page 6, line 28 skipping to change at page 6, line 38
RegistrationNotSupported (TBA2) and RegistrationDenied (TBA3) RegistrationNotSupported (TBA2) and RegistrationDenied (TBA3)
described in Section 6, that requires an allocation out of the described in Section 6, that requires an allocation out of the
registry defined at registry defined at
http://www.iana.org/assignments/dhcpv6-parameters/ http://www.iana.org/assignments/dhcpv6-parameters/
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 and other members of dhc and v6ops working groups Carlsen, Mark Smith, Marcin Siodelski and other members of dhc and
for their valuable comments. v6ops working 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.
[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
skipping to change at page 7, line 36 skipping to change at page 8, line 4
Authors' Addresses Authors' Addresses
Sheng Jiang Sheng Jiang
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
Q14, Huawei Campus Q14, Huawei Campus
No.156 Beiqing Road No.156 Beiqing Road
Hai-Dian District, Beijing 100095 Hai-Dian District, Beijing 100095
P.R. China P.R. China
Email: jiangsheng@huawei.com Email: jiangsheng@huawei.com
Gang Chen Gang Chen
China Mobile China Mobile
53A, Xibianmennei Ave., Xuanwu District, Beijing 53A, Xibianmennei Ave., Xuanwu District, Beijing
P.R. China P.R. China
Phone: 86-13910710674 Phone: 86-13910710674
Email: phdgang@gmail.com Email: phdgang@gmail.com
Suresh Krishnan Suresh Krishnan
Ericsson Ericsson
8400 Decarie Blvd. 8400 Decarie Blvd.
Town of Mount Royal, QC Town of Mount Royal, QC
Canada Canada
Phone: +1 514 345 7900 x42871 Phone: +1 514 345 7900 x42871
Email: suresh.krishnan@ericsson.com Email: suresh.krishnan@ericsson.com
Rajiv Asati
Cisco Systems
Email: rajiva@cisco.com
 End of changes. 15 change blocks. 
26 lines changed or deleted 41 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/