draft-ietf-dhc-container-opt-05.txt   draft-ietf-dhc-container-opt-06.txt 
dhc Working Group R. Droms dhc Working Group R. Droms
Internet-Draft Cisco Systems, Inc. Internet-Draft R. Penno
Intended status: Standards Track March 24, 2009 Intended status: Standards Track Cisco Systems, Inc.
Expires: September 25, 2009 Expires: June 20, 2013 December 17, 2012
Container Option for Server Configuration Container Option for Server Configuration
draft-ietf-dhc-container-opt-05.txt draft-ietf-dhc-container-opt-06.txt
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.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. 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."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on June 20, 2013.
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 September 25, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2012 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
In some DHCP service deployments, it is desirable for a DHCP server described in the Simplified BSD License.
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 Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Problem statement and requirements for RG DHCP server 3. Problem statement and requirements for RG DHCP
configuration . . . . . . . . . . . . . . . . . . . . . . . . . 4 server configuration . . . . . . . . . . . . . . . . . . . . . 4
4. Design alternatives . . . . . . . . . . . . . . . . . . . . . . 5 4. Design alternatives . . . . . . . . . . . . . . . . . . . . . . 5
5. Semantics and syntax of the Container option . . . . . . . . . 6 5. Semantics and syntax of the Container option . . . . . . . . . 6
5.1. DHCPv4 Container option . . . . . . . . . . . . . . . . . . 6 5.1. DHCPv4 Container option . . . . . . . . . . . . . . . . . . 6
5.2. DHCPv6 Container option . . . . . . . . . . . . . . . . . . 6 5.2. DHCPv6 Container option . . . . . . . . . . . . . . . . . . 6
5.3. SP server behavior . . . . . . . . . . . . . . . . . . . . 7 5.3. SP server behavior . . . . . . . . . . . . . . . . . . . . 7
5.4. RG client behavior . . . . . . . . . . . . . . . . . . . . 7 5.4. RG client behavior . . . . . . . . . . . . . . . . . . . . 7
5.5. RG server behavior . . . . . . . . . . . . . . . . . . . . 7 5.5. RG server behavior . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
8. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Revision -02 . . . . . . . . . . . . . . . . . . . . . . . 8 8.1. Revision -02 . . . . . . . . . . . . . . . . . . . . . . . 8
8.2. Revision -03 . . . . . . . . . . . . . . . . . . . . . . . 9 8.2. Revision -03 . . . . . . . . . . . . . . . . . . . . . . . 9
8.3. Revision -04 . . . . . . . . . . . . . . . . . . . . . . . 9 8.3. Revision -04 . . . . . . . . . . . . . . . . . . . . . . . 9
9. Related Work . . . . . . . . . . . . . . . . . . . . . . . . . 9 9. Related Work . . . . . . . . . . . . . . . . . . . . . . . . . 9
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
10.1. Normative References . . . . . . . . . . . . . . . . . . . 9 10.1. Normative References . . . . . . . . . . . . . . . . . . . 9
10.2. Informative References . . . . . . . . . . . . . . . . . . 9 10.2. Informative References . . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
In some DHCP service deployments, it is desirable to pass In some DHCP service deployments, it is desirable to pass
configuration options from a DHCP server in one administrative domain configuration options from a DHCP server in one administrative domain
to another DHCP server in a different administrative domain. In one to another DHCP server in a different administrative domain. In one
example of such a deployment, an IPTV service provider (SP) may need example of such a deployment, an IPTV service provider (SP) may need
to provide certain SP domain-specific information to IPTV device(s) to provide certain SP domain-specific information to IPTV device(s)
located in the consumer domain. This information is sent from the located in the consumer domain. This information is sent from the
IPTV SP DHCP server to the consumer DHCP server located in the IPTV SP DHCP server to the consumer DHCP server located in the
skipping to change at page 4, line 26 skipping to change at page 4, line 26
RG DHCP client (or "RG client") the DHCP client in the RG RG DHCP client (or "RG client") the DHCP client in the RG
RG DHCP server (or "RG server") the DHCP server in the RG RG DHCP server (or "RG server") the DHCP server in the RG
SP DHCP server (or "SP server") the DHCP server managed by the SP DHCP server (or "SP server") the DHCP server managed by the
service provider (SP) service provider (SP)
This document uses other terminology for DHCPv4 and DHCPv6 as defined This document uses other terminology for DHCPv4 and DHCPv6 as defined
in RFC 2131 and RFC 3315, respectively. in RFC 2131 and RFC 3315, respectively.
3. Problem statement and requirements for RG DHCP server configuration 3. Problem statement and requirements for RG DHCP server
configuration
The following diagram shows the components in a network deployment The following diagram shows the components in a network deployment
using the DHCP Container option: using the DHCP Container option:
Client host -+ +---------+ +------+ Client host -+ +---------+ +------+
| | RG | | SP | | | RG | | SP |
Client host -+ | Client+--- ... ---+ DHCP | Client host -+ | Client+--- ... ---+ DHCP |
+--+Server | |server| +--+Server | |server|
Client host -+ +---------+ +------+ Client host -+ +---------+ +------+
skipping to change at page 10, line 5 skipping to change at page 10, line 5
[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
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
10.2. Informative References 10.2. Informative References
[eRouter] CableLabs, "CableLabs' DHCP Options Registry (CL-SP-CANN- [eRouter] CableLabs, "CableLabs' DHCP Options Registry (CL-SP-CANN-
DHCP-Reg-I02-080306)", March 2008. DHCP-Reg-I02-080306)", March 2008.
Author's Address Authors' Addresses
Ralph Droms Ralph Droms
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Avenue 1414 Massachusetts Avenue
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Phone: +1 978.936.1674 Phone: +1 978.936.1674
Email: rdroms@cisco.com Email: rdroms@cisco.com
Reinaldo Penno
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134
USA
Email: repenno@cisco.com
 End of changes. 12 change blocks. 
33 lines changed or deleted 32 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/