DHC Working Group                                               S. Jiang
Internet-Draft                              Huawei Technologies Co., Ltd
Intended status: Standards Track                                 G. Chen
Expires: August 29, 2013 March 2, 2014                                      China Mobile
                                                             S. Krishnan
                                                                Ericsson
                                                       February 25,
                                                         August 29, 2013

      A Generic

     Registering self-generated IPv6 Addresses Registration Solution Using in DNS using DHCPv6
                  draft-ietf-dhc-addr-registration-02
                  draft-ietf-dhc-addr-registration-03

Abstract

   In networks that are centrally managed, self-generated addresses
   cause some traceability issues due to their decentralized nature.  To
   minimize
   One of the most important issues due in this regard is the inability to lack of traceability, these self-generated
   register such addresses can be registered with the network for allowing centralized
   address administration. in DNS.  This document defines a generic address
   registration solution using DHCPv6, using a new ND option and a new
   DHCPv6 option in order mechanism to communicate the use of
   register self-generated
   addresses.  A new Addr-registration-request message type is defined
   for initiate the address registration request, among with two new
   Status codes to indicate registration errors on the server side. addresses in DNS through a DHCPv6 server.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 29, 2013. March 2, 2014.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Overview of Generic Address Registration  Solution Overview . . . . . . . 3
   4.  Propagating the Address Registration Solicitation . . . . . . . 4
     4.1.  ND Address Registration Solicitation Option . . . . . . . . 5
     4.2.  DHCPv6 Address Registration Solicitation Option . . . . . . 5
   5. 3
   4.  DHCPv6 Addr-registration-request ADDR-REGISTRATION-REQUEST Message  . . . . . . . . . . . 6
   6. 4
   5.  DHCPv6 Address Registration Procedure . . . . . . . . . . . . . 6
     6.1. 5
     5.1.  DHCPv6 Address Registration Request . . . . . . . . . . . . 6
     6.2.  DHCPv6 Address Registration Acknowledge 5
     5.2.  Acknowledging successful registration . . . . . . . . . . 7
   7. . 5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   8. 5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   9. 6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 8
   10. 6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 8
     10.1. 6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . . . 8
     10.2. 6
     9.2.  Informative References  . . . . . . . . . . . . . . . . . . 9 7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 9 7

1.  Introduction

   In several common network scenarios, IPv6 addresses are self-
   generated by the end-hosts using some information propogated to them by the network (i.e. the network prefix). appending a self-generated interface
   identifier to a network-specified prefix.  Examples of self-generated
   addresses include those created using IPv6 Stateless Address
   Configuration [RFC4862] , temporary addresses [RFC4941] and
   Cryptographically Generated Addresses (CGA) [RFC3972] etc.  These
   addresses are potentially incompatible with networks  In
   several tighly controlled networks, hosts with a centrally
   managed address architecture such as DHCPv6 [RFC3315] as they lack
   traceability and stability.

   Many operators of enterprise networks and similarly tightly
   administered networks have expressed the desire to be at least aware
   of the hosts' self-generated
   addresses when migrating to IPv6. may face some limitations.  One potential way such limitation is related
   to provide network administrators with most the inability of
   their needs while retaining compatibility nodes with normal stateless
   configuration would be to register the self-generated addresses with
   the systems to register
   their IPv6-address-to-FQDN bindings in place DNS.  This is related to centrally administer the addresses.
   fact that, in such networks, only certain nodes (e.g.  The edge
   router DHCPv6
   server) are allowed to update these bindings in order to prevent end-
   hosts from registering arbitrary addresses for their FQDNs or
   associating their addresses with arbitrary domain names.

   For nodes that observes hosts' obtain their addresses through the Neighbor Discovery
   protocol is the most suitable devices to register these addresses.

   This document introduces DHCPv6, a new IPv6 Neighbor Discovery option and a
   new DHCPv6 option to solicite edge routers to register addresses. solution has
   been specified in [RFC4704].  The DHCPv6 protocol is used to perform the address registration
   procedure while the address registration server role may be performed solution works by including a DHCPv6 server
   Client FQDN option in the SOLICIT, REQUEST, RENEW or a stand-alone server, which is also considered
   as a DHCPv6 server from REBIND messages
   during the DHCPv6 protocol perspective. process of acquiring an address through DHCPv6.  This
   document provides an analogous mechanism to register self-generated
   addresses in DNS.

   A new Addr-
   registration-request ADDR-REGISTRATION-REQUEST DHCPv6 message type is defined to
   initiate the address registration request, and two new Status codes
   is defined to indicate registration errors on the server side.

2.  Terminology

   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].

3.  Overview of Generic Address Registration  Solution

   In the generic address registration solution, the network management
   system solicits the edge routers to register addresses, by sending
   solicitation messages from either upstream router (step 1a in Figure
   1) or DHCPv6 server (step 1b in Figure 1). Overview

   After receiving such solicitations, successfully assigning a self-generated IPv6 address on one of
   its interfaces, an edge router end-host implementing this specification SHOULD
   send an Addr-registration-request ADDR-REGISTRATION-REQUEST message to the
   address registration server (step 2 in Figure 1, defined in Section 5
   of this document).  The address registration server may be acted by a DHCPv6 address
   registration server.  By received  After receiving the address registration
   request, the
   address registration DHCPv6 server records the requested address in registers the IPv6 address registration database, which MAY be used by other network
   functions, such as to FQDN binding
   towards a configured DNS or ACL, etc. server.  An acknowledgement MAY be sent
   back to the edge router (step 3 in Figure 1).
       +----+   +-----------+   +---------------+   +---------------+
       |Host|   |Edge router|   |Upstream Router|   |Addr-Reg Server|
       +----+   +-----------+   +---------------+   +---------------+
         |    ND     |                   |                  |
         |<--------->|                   |                  |
                     |                   |                  |
                     |Addr Register Solicitation(1a)        |
                     |<------------------|                  |
                     |                                      |
                     |   Addr Register Solicitation(1b)     |
                     |<-------------------------------------|
                     |                                      |
                     |       Addr-registration-request(2)   |
                     |------------------------------------->|
                     |                                      |Register
                     |  Acknowledgment addr registration(3) |address
                     |<-------------------------------------|

                 Figure 1: Address Registration Procedure

4.  Propagating the Address Registration Solicitation

   In order to notify the edge routers the availabilityof the address
   registration service, new solicitation options are needed.  There is
   more than one mechanism by which configuration parameters could be
   pushed to the edge routers.  The address registration solicitation
   option can be carried in Router Advertisement (RA) message, which is
   broadcasted by upstream routers.  In the DHCPv6 managed network, it
   can also be carried in DHCPv6 messages.  This document defines a new
   ND option and a new DHCPv6 option for this purpose.  Since the
   address registration process is through the standard DHCPv6 client/
   server communication - send packets to ff02::1:2, the
   All_DHCP_Relay_Agents_and_Servers multicast address, these
   solicitation options do not contain the IP address of address
   registration server.

   After receving a message containing an address registration
   solicitation option, an edge router implementing this specification
   SHOULD register addresses to the address registration server.

4.1.  ND Address Registration Solicitation Option

   The ND Address Registration Solicitation Option allows an upstream
   router to propagate the solicitation for edge routers to register
   addresses.  The format of the ND Address Registration Solicitation
   Option is described as follows:

        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
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |     Type      |    Length     |                               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               +
       |                           Reserved                            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

       Type         TBA1

       Length       1 (in units of 8 octets, Type and Length themselves
                    are included).

       Reserved     Padding bits. For future use also. The value MUST
                    be initialized to zero by the sender, and MUST be
                    ignored by the receiver.

                ND Address Registration Solicitation Option

4.2.  DHCPv6 Address Registration Solicitation Option

   The DHCPv6 Address Registration Solicitation Option allows a DHCPv6
   server be sent back
   to propagate the solicitation for edge routers end host to register
   addresses.  This option MAY be propagated together with DHCPv6 Prefix
   Delegation Option, [RFC3633].  The format of indicate whether or not the DHCPv6 Address
   Registration Solicitation Option is described as follows:

        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
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ registration operation
   succeeded..

       +----+   +-----------+                       +---------------+
       |Host|   |Edge router|                       |Addr-Reg Server|
       +----+   +-----------+                       +---------------+
         |  OPTION_ADDR_REG_SOLICITATION   SLAAC   |       option-len                                      |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         option-code   OPTION_ADDR_REG_SOLICITATION (TBA2).

         option-len    0, Length of this option in octets (not including
                       option-code and option-len).

               DHCPv6 Addr
         |<--------->|                                      |
                     |                                      |
                     |       ADDR-REGISTRATION-REQUEST      |
                     |------------------------------------->|
                     |                                      |Register
                     |                                      |address
                     |       Optional Acknowledgment        |in DNS
                     |<-------------------------------------|

                 Figure 1: Address Registration Solicitation Option

5. Procedure

4.  DHCPv6 Addr-registration-request ADDR-REGISTRATION-REQUEST Message

   A

   The DHCPv6 client (the edge router) sends an Addr-registration-request ADDR-REGISTRATION-REQUEST message to a
   server to request addresses an address to be registered. registered in the DNS.  The format
   of the Addr-registration-request ADDR-REGISTRATION-REQUEST message is described as
   follows, compliant with Section 6 in [RFC3315]: follows:

      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
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |    msg-type   |               transaction-id                  |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                                                               |
     .                            options                            .
     .                           (variable)                          .
     |                                                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      msg-type             Identifies the DHCPv6 message type; (TBA3).
                           Set to ADDR-REGISTRATION-REQUEST (TBA1).

      transaction-id       The transaction ID for this message exchange.

      options              Options carried in this message.

                 DHCPv6 Addr-Registration-Request ADDR-REGISTRATION-REQUEST message

   This Addr-registration-request

   The ADDR-REGISTRATION-REQUEST message MUST NOT contain server-
   identifier option and SHOULD only MUST contain the IA_NA option(s) option and Client
   Identifier option. the DHCPv6
   FQDN option [RFC4704].

   Clients MUST discard any received Addr-registration-request ADDR-REGISTRATION-REQUEST messages.
   Servers MUST discard any Addr-Registration-Request ADDR-REGISTRATION-REQUEST messages that do
   not include a Client Identifier option or that do include a Server
   Identifier option.

6.

5.  DHCPv6 Address Registration Procedure

   The DHCPv6 protocol is reused used as the address registration protocol
   while when
   a DHCPv6 server can play performs the role of an address registration server.
   The IA_NA DHCPv6 IA_NA option [RFC3315] is and the DHCPv6 FQDN option
   [RFC4704] are reused in order to fulfill the address registration
   interactions.

6.1.

5.1.  DHCPv6 Address Registration Request

   The edge router end-host sends a DHCPv6 Addr-registration-request ADDR-REGISTRATION-REQUEST message to the
   address registration server to ff02::1:2, the All_DHCP_Relay_Agents_and_Servers
   multicast address. address (ff02::1:2).

   The edge router end-host MUST include a Client Identifier option in the Addr-
   registration-request ADDR-
   REGISTRATION-REQUEST message to identify itself to the server.  The
   DHCPv6 Addr-registration-request ADDR-REGISTRATION-REQUEST message SHOULD MUST contain at least exactly one
   IA_NA option and exactly one FQDN option.  The IA_NA option SHOULD MUST
   contain at least one IA Address option.

   After receiving this Addr-Registration-Request ADDR-REGISTRATION-REQUEST message, the address
   registration server MUST register the requested binding between the provided
   FQDN and address(es) in its
   address registration database, which may further be used by other
   network functions, such as DNS, network access control lists, etc. DNS.  If the DHCPv6 server does not support
   address registration function, a Reply message with includes a Status
   Code option with the value the RegistrationNotSupported (TBA4) (TBA2) MAY be
   sent back to the initiated client.

6.2.  DHCPv6 Address Registration Acknowledge

5.2.  Acknowledging successful registration

   After all the addresses have been processed, successfully registered in DNS, the
   address registration server MAY send a Reply message as the response
   to registration requests.  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.  For each IA in the Release message for which the
   server does no
   register, not succeed in registering, the server adds an IA option
   using the IAID from the Addr-
   registration-request ADDR-REGISTRATION-REQUEST message, and
   includes a Status Code option with the value RegistrationDenied (TBA5)
   (TBA3) in the IA option.  No other options are included in the IA
   option.

7.

6.  Security Considerations

   An attacker may attempt to register large number of fake addresses with the
   network in
   quick succession in order to overwhelm the address registration
   server.  These attacks may be prevented generic DHCPv6 protection by
   using the AUTH option [RFC3315] or Secure DHCPv6
   [I-D.ietf-dhc-secure-dhcpv6].

8.

7.  IANA Considerations

   This document defines a new IPv6 Neighbor Discovery option, the
   Address Registration Solicitation Option (TBA1) described in Section
   4.1, that requires an allocation out of the registry defined at

   http://www.iana.org/assignments/icmpv6-parameters

   This document defines a new DHCPv6 option, the
   OPTION_ADDR_REG_SOLICITATION (TBA2) described in Section 4.2, that
   requires an allocation out of the registry defined at
   http://www.iana.org/assignments/dhcpv6-parameters/

   This document defines a new DHCPv6 message, the Addr-registration-
   request ADDR-REGISTRATION-
   REQUEST message (TBA3) (TBA1) described in Section 5, that requires an
   allocation out of the registry defined at

   http://www.iana.org/assignments/dhcpv6-parameters/

   This document defines two new DHCPv6 Status code, the
   RegistrationNotSupported (TBA4) (TBA2) and RegistrationDenied (TBA5) (TBA3)
   described in Section 6, that requires an allocation out of the
   registry defined at

   http://www.iana.org/assignments/dhcpv6-parameters/

9.

8.  Acknowledgements

   The authors would like to thank Ralph Droms, Ted Lemon, Bernie Volz,
   Sten Carlsen, Erik Kline, Lorenzo Colitti, Joel Jaeggli, Sten
   Carlsen, Mark Smith and other members of dhc and v6ops working groups
   for their valuable comments.

10.

9.  References

10.1.

9.1.  Normative References

   [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.,
              and M. Carney, "Dynamic Host Configuration Protocol for
              IPv6 (DHCPv6)", RFC 3315, July 2003.

   [RFC3633]  Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
              Host Configuration Protocol (DHCP) version 6", RFC 3633,
              December 2003.

   [RFC3971]  Arkko, J., Kempf, J., Zill, B., and P. Nikander, "SEcure
              Neighbor Discovery (SEND)", RFC 3971, March 2005.

   [RFC3972]  Aura, T., "Cryptographically Generated Addresses (CGA)",
              RFC 3972, March 2005.

   [RFC4704]  Volz, B., "The Dynamic Host Configuration Protocol for
              IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN)
              Option", RFC 4704, October 2006.

   [RFC4862]  Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
              Address Autoconfiguration", RFC 4862, September 2007.

   [RFC4941]  Narten, T., Draves, R., and S. Krishnan, "Privacy
              Extensions for Stateless Address Autoconfiguration in
              IPv6", RFC 4941, September 2007.

10.2.

9.2.  Informative References

   [I-D.ietf-dhc-secure-dhcpv6]
              Jiang, S. and S. Shen, "Secure DHCPv6 Using CGAs",
              draft-ietf-dhc-secure-dhcpv6-07 (work in progress),
              September 2012.

Authors' Addresses

   Sheng Jiang
   Huawei Technologies Co., Ltd
   Q14, Huawei Campus
   No.156 Beiqing Road
   Hai-Dian District, Beijing 100095
   P.R. China

   Email: jiangsheng@huawei.com

   Gang Chen
   China Mobile
   53A, Xibianmennei Ave., Xuanwu District, Beijing
   P.R. China

   Phone: 86-13910710674
   Email: phdgang@gmail.com
   Suresh Krishnan
   Ericsson
   8400 Decarie Blvd.
   Town of Mount Royal, QC
   Canada

   Phone: +1 514 345 7900 x42871
   Email: suresh.krishnan@ericsson.com