draft-ietf-dhc-dhcpv6-stateless-00.txt

DHCPv6协议在Linux操作系统下的一个客户端实现。

      stateless DHCP service; the section numbers in this list refer to
      the DHCPv6 specification [1]:

      Preference:     Sent by a DHCP server to indicate the preference
         level for the server (section 22.8)

      Elapsed time:   Sent by a DHCP client to indicate the time since
         the client began the DHCP configuration process (section 22.9)

      User Class:     Sent by a DHCP client to give additional
         information to the server for selecting configuration
         parameters for the client (section 22.15)

      Vendor Class:   Sent by a DHCP client to give additional
         information about the client vendor and hardware to the server
         for selecting configuration parameters for the client (section
         22.16)

      Vendor-specific Information: Sent by a DHCP server to pass
         information to clients in options defined by vendors (section
         22.17)




Droms                    Expires October 5, 2003                [Page 5]

Internet-Draft    Stateless DHCPv6 Implementation Guide       April 2003


      Client DUID:    Sent by a DHCP client to identify itself (section
         22.2).  Clients are not required to send this option; servers
         never send this option

      Authentication: Used to provide authentication of DHCP messages
         (section 21)


   6. Interaction with DHCP for Address Assignment

      In some networks, there may be both clients that are using
      stateless address autoconfiguration [7] and DHCP for DNS
      configuration and clients that are using DHCP for stateful address
      configuration.  Depending on the deployment and configuration of
      relay agents, DHCP servers that are intended only for stateless
      configuration may receive messages from clients that are
      performing stateful address configuration.

      A DHCP server that is only able to provide stateless configuration
      information through an Information-request/Reply message exchange
      discards any other DHCP messages it receives.  Specifically, the
      server discards any messages other than Information-Request or
      Relay-forward it receives, and the server does not participate in
      any stateful address configuration messages exchanges.  If there
      are other DHCP servers that are configured to provide stateful
      address assignment, one of those servers will provide the address
      assignment.

   7. Security Considerations

      Stateless DHCPv6 service is a proper subset of the DHCPv6 service
      described in the DHCPv6 specification [1].  Therefore, stateless
      DHCPv6 service introduces no additional security considerations
      beyond those discussed in sections 21, 22.11 and 23 of the DHCPv6
      specification.

      Configuration information provided to a node through stateless
      DHCPv6 service may be used to mount spoofing, man-in-the-middle,
      denial-of-service and other attacks.  These attacks are described
      in more detail in the specifications for each of the options that
      carry configuration information.  Authenticated DHCPv6, as
      described in sections 21 and 22.11 of the DHCPv6 specification,
      can be used to avoid attacks mounted through the stateless DHCPv6
      service.

      Usually, a node using stateless DHCPv6 service will have
      configured its interfaces with IPv6 addresses through stateless
      address autoconfiguration.  A node that has configured an



Droms                    Expires October 5, 2003                [Page 6]

Internet-Draft    Stateless DHCPv6 Implementation Guide       April 2003


      appropriate IPv6 address can use IPsec [8] to authenticate and
      secure DHCPv6 messages exchanged between the node and the DHCPv6
      server.

   8. Acknowledgments

      Jim Bound, Ted Lemon and Bernie Volz reviewed this document and
      contributed editorial suggestions.  Thanks to Pekka Savola and
      Christian Huitema for their review and comments.

Normative References

      [1]  Bound, J., Carney, M., Perkins, C., Lemon, T., Volz, B. and
           R. Droms (ed.), "Dynamic Host Configuration Protocol for IPv6
           (DHCPv6)", draft-ietf-dhc-dhcpv6-28 (work in progress),
           October 2002.

      [2]  Deering, S. and R. Hinden, "Internet Protocol, Version 6
           (IPv6) Specification", RFC 2460, December 1998.

      [3]  Bound, J., Carney, M., Perkins, C., Lemon, T., Volz, B. and
           R. Droms, "DNS Configuration options for DHCPv6", draft-ietf-
           dhc-dhcpv6-opt-dnsconfig-01 (work in progress), October 2002.

      [4]  Vijayabhaskar, A., "Time Configuration Options for DHCPv6",
           draft-ietf-dhc-dhcpv6-opt-timeconfig-00 (work in progress),
           February 2002.

Informative References

      [5]  Narten, T., Nordmark, E. and W. Simpson, "Neighbor Discovery
           for IP Version 6 (IPv6)", RFC 2461, December 1998.

      [6]  Mockapetris, P., "Domain names - concepts and facilities",
           STD 13, RFC 1034, November 1987.

      [7]  Thomson, S. and T. Narten, "IPv6 Stateless Address
           Autoconfiguration", RFC 2462, December 1998.

      [8]  Kent, S. and R. Atkinson, "Security Architecture for the
           Internet Protocol", RFC 2401, November 1998.










Droms                    Expires October 5, 2003                [Page 7]

Internet-Draft    Stateless DHCPv6 Implementation Guide       April 2003


Author's Address

   Ralph Droms
   Cisco Systems
   300 Apollo Drive
   Chelmsford, MA  01824
   USA

   Phone: [phone]
   EMail: [e-mail]









































Droms                    Expires October 5, 2003                [Page 8]

Internet-Draft    Stateless DHCPv6 Implementation Guide       April 2003


Full Copyright Statement

      Copyright (C) The Internet Society (2003).  All Rights Reserved.

      This document and translations of it may be copied and furnished
      to others, and derivative works that comment on or otherwise
      explain it or assist in its implementation may be prepared,
      copied, published and distributed, in whole or in part, without
      restriction of any kind, provided that the above copyright notice
      and this paragraph are included on all such copies and derivative
      works.  However, this document itself may not be modified in any
      way, such as by removing the copyright notice or references to the
      Internet Society or other Internet organizations, except as needed
      for the purpose of developing Internet standards in which case the
      procedures for copyrights defined in the Internet Standards
      process must be followed, or as required to translate it into
      languages other than English.

      The limited permissions granted above are perpetual and will not
      be revoked by the Internet Society or its successors or assigns.

      This document and the information contained herein is provided on
      an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
      ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
      IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
      THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
      WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

      Funding for the RFC Editor function is currently provided by the
      Internet Society.



















Droms                    Expires October 5, 2003                [Page 9]