Internet Engineering Task Force                                  B. Volz
INTERNET DRAFT                                                  Ericsson
Expires: August 2003                                       April 4, 2003



                    Site Specific Options for DHCP for IPv6
                   draft-volz-dhc-dhcpv6-site-options-00.txt

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on October 4, 2003.

Copyright Notice

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


Abstract

   This document specifies that a portion of the DHCP for IPv6 [DHCPv6]
   16-bit option space is reserved for site-specific options. Site-
   specific options are to be used for site specific needs and MUST NOT
   be used for public (IANA assigned) or vendor specific options.


1. Introduction

   The DHCP for IPv6 base specification [DHCPv6] did not reserve a
   range of option numbers for private use within sites, as was defined
   for DHCP for IPv4 [RFC2132].

   This document specifies that a portion of the DHCP for IPv6 16-bit
   option space is reserved for site-specific options. Site-specific
   options are to be used for site specific needs and MUST NOT be used
   for public (IANA assigned) or vendor specific options.




Volz                       Expires  4 Oct 2003                  [Page 1]


Internet Draft  Site Specific Options for DHCP for IPv6   25 March, 2003


2. Requirements

   The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
   SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this
   document, are to be interpreted as described in RFC 2119 [RFC2119].


3. Site-Specific Options

   The DHCP for IPv6 option codes from 65,280 to 65,534 are to be
   reserved for use by site-specific options. This reserves 254 option
   values for site-specific use.

   This range of option codes MUST NOT be assigned by IANA to any public
   options.

   This document does not define the behavior of clients, servers, and
   relay agents with respect to site-specific options, as these are
   site issues. However, it is recommended that client implementations:

   a. allow the list of site-specific options to be included in an
      Option Request Option (DHCPv6) to be configured,

   b. allow the list of site-specific options and the corresponding
      values to be sent in client request messages to be configured, and

   c. allow application software to obtain the data returned for site-
      specific options.


4. IANA Recommendations

   IANA is requested to reserve the DHCP for IPv6 options from 65,280
   to 65,534 (decimal), inclusive, for site-specific options. IANA will
   not manage these options; sites will manage this space.


5. Security Considerations

   This document in and by itself provides no security, nor does it
   impact existing security.


Acknowledgements

   Thanks to Ralph Droms for his input into this document.









Volz                       Expires  4 Oct 2003                  [Page 2]


Internet Draft  Site Specific Options for DHCP for IPv6    April 4, 2003


References


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

   [RFC2132] Alexander, S. and R. Droms, "DHCP options and BOOTP Vendor
       Extensions", RFC 2132, March 1997.


   [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
       Requirement Levels", BCP 14, RFC 2119, March 1997.



Author's Address


   Bernie Volz
   Ericsson
   959 Concord Street
   Framingham, MA  01701
   Phone: +1 508 875 3162
   EMail: bernie.volz@ericsson.com





























Volz                       Expires  4 Oct 2003                  [Page 3]


Internet Draft  Site Specific Options for DHCP for IPv6    April 4, 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.























Volz                       Expires  4 Oct 2003                  [Page 4]