--- 1/draft-ietf-dhc-container-opt-04.txt 2009-03-25 08:12:05.000000000 +0100 +++ 2/draft-ietf-dhc-container-opt-05.txt 2009-03-25 08:12:05.000000000 +0100 @@ -1,75 +1,85 @@ dhc Working Group R. Droms Internet-Draft Cisco Systems, Inc. -Intended status: Standards Track November 28, 2008 -Expires: June 1, 2009 +Intended status: Standards Track March 24, 2009 +Expires: September 25, 2009 Container Option for Server Configuration - draft-ietf-dhc-container-opt-04.txt + draft-ietf-dhc-container-opt-05.txt Status of this Memo - By submitting this Internet-Draft, each author represents that any - applicable patent or other IPR claims of which he or she is aware - have been or will be disclosed, and any of which he or she becomes - aware will be disclosed, in accordance with Section 6 of BCP 79. + This Internet-Draft is submitted to IETF in full conformance with the + provisions of BCP 78 and BCP 79. 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 June 1, 2009. + This Internet-Draft will expire on September 25, 2009. + +Copyright Notice + + Copyright (c) 2009 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 in effect on the date of + publication of this document (http://trustee.ietf.org/license-info). + Please review these documents carefully, as they describe your rights + and restrictions with respect to this document. Abstract In some DHCP service deployments, it is desirable for a DHCP server in one administrative domain to pass configuration options to a DHCP server in a different administrative domain. This DHCP option carries a set of DHCP options that can be used by another DHCP server. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 + 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Problem statement and requirements for RG DHCP server - configuration . . . . . . . . . . . . . . . . . . . . . . . . 4 - 4. Design alternatives . . . . . . . . . . . . . . . . . . . . . 5 + configuration . . . . . . . . . . . . . . . . . . . . . . . . . 4 + 4. Design alternatives . . . . . . . . . . . . . . . . . . . . . . 5 5. Semantics and syntax of the Container option . . . . . . . . . 6 - 5.1. DHCPv4 Container option . . . . . . . . . . . . . . . . . 6 - 5.2. DHCPv6 Container option . . . . . . . . . . . . . . . . . 6 + 5.1. DHCPv4 Container option . . . . . . . . . . . . . . . . . . 6 + 5.2. DHCPv6 Container option . . . . . . . . . . . . . . . . . . 6 5.3. SP server behavior . . . . . . . . . . . . . . . . . . . . 7 5.4. RG client behavior . . . . . . . . . . . . . . . . . . . . 7 5.5. RG server behavior . . . . . . . . . . . . . . . . . . . . 7 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 - 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 + 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 + 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 8. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 8 8.1. Revision -02 . . . . . . . . . . . . . . . . . . . . . . . 8 8.2. Revision -03 . . . . . . . . . . . . . . . . . . . . . . . 9 8.3. Revision -04 . . . . . . . . . . . . . . . . . . . . . . . 9 9. Related Work . . . . . . . . . . . . . . . . . . . . . . . . . 9 - 10. Normative References . . . . . . . . . . . . . . . . . . . . . 9 + 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 + 10.1. Normative References . . . . . . . . . . . . . . . . . . . 9 + 10.2. Informative References . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9 - Intellectual Property and Copyright Statements . . . . . . . . . . 11 1. Introduction In some DHCP service deployments, it is desirable to pass configuration options from a DHCP server in one administrative domain to another DHCP server in a different administrative domain. In one example of such a deployment, an IPTV service provider (SP) may need to provide certain SP domain-specific information to IPTV device(s) located in the consumer domain. This information is sent from the IPTV SP DHCP server to the consumer DHCP server located in the @@ -341,78 +351,42 @@ Added pointer to "CableLabs' DHCP Options Registry" as background for this option. 9. Related Work The Container option is based on the CableLabs eRouter DHCP Container vendor-identifying vendor-specific option, as defined in "CableLabs' DHCP Options Registry" [eRouter]. -10. Normative References +10. References + +10.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 1997. [RFC3118] Droms, R. and W. Arbaugh, "Authentication for DHCP Messages", RFC 3118, June 2001. [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. +10.2. Informative References + [eRouter] CableLabs, "CableLabs' DHCP Options Registry (CL-SP-CANN- DHCP-Reg-I02-080306)", March 2008. Author's Address Ralph Droms Cisco Systems, Inc. 1414 Massachusetts Avenue Boxborough, MA 01719 USA Phone: +1 978.936.1674 Email: rdroms@cisco.com - -Full Copyright Statement - - Copyright (C) The IETF Trust (2008). - - This document is subject to the rights, licenses and restrictions - contained in BCP 78, and except as set forth therein, the authors - retain all their rights. - - This document and the information contained herein are provided on an - "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS - OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND - THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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. - -Intellectual Property - - The IETF takes no position regarding the validity or scope of any - Intellectual Property Rights or other rights that might be claimed to - pertain to the implementation or use of the technology described in - this document or the extent to which any license under such rights - might or might not be available; nor does it represent that it has - made any independent effort to identify any such rights. Information - on the procedures with respect to rights in RFC documents can be - found in BCP 78 and BCP 79. - - Copies of IPR disclosures made to the IETF Secretariat and any - assurances of licenses to be made available, or the result of an - attempt made to obtain a general license or permission for the use of - such proprietary rights by implementers or users of this - specification can be obtained from the IETF on-line IPR repository at - http://www.ietf.org/ipr. - - The IETF invites any interested party to bring to its attention any - copyrights, patents or patent applications, or other proprietary - rights that may cover technology that may be required to implement - this standard. Please address the information to the IETF at - ietf-ipr@ietf.org.