draft-ietf-dhc-container-opt-01.txt   draft-ietf-dhc-container-opt-02.txt 
dhc Working Group R. Droms dhc Working Group R. Droms
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track September 8, 2008 Intended status: Standards Track November 3, 2008
Expires: March 12, 2009 Expires: May 7, 2009
Container Option for Server Configuration Container Option for Server Configuration
draft-ietf-dhc-container-opt-01.txt draft-ietf-dhc-container-opt-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of 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), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 12, 2009. This Internet-Draft will expire on May 7, 2009.
Abstract Abstract
In some DHCP service deployments, it is desirable for a DHCP server In some DHCP service deployments, it is desirable for a DHCP server
in one administrative domain to pass configuration options to a DHCP in one administrative domain to pass configuration options to a DHCP
server in a different administrative domain. This DHCP option server in a different administrative domain. This DHCP option
carries a set of DHCP options that can be used by another DHCP carries a set of DHCP options that can be used by another DHCP
server. server.
1. Introduction 1. Introduction
skipping to change at page 3, line 17 skipping to change at page 3, line 17
consumer network connects to the broadband WAN; consumer network connects to the broadband WAN;
typically a layer 3 forwarding device typically a layer 3 forwarding device
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 terminology for DHCPv4 and DHCPv6 as defined in This document uses other terminology for DHCPv4 and DHCPv6 as defined
RFCs 2131 and 2132, 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 STB/CPE -+ +---------+ +------+ Client STB/CPE -+ +---------+ +------+
| | RG | | SP | | | RG | | SP |
Client STB/CPE -+ | Client+--- ... ---+ DHCP | Client STB/CPE -+ | Client+--- ... ---+ DHCP |
+--+Server | |server| +--+Server | |server|
skipping to change at page 7, line 46 skipping to change at page 7, line 46
management concerns management concerns
9. Normative References 9. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", [RFC2131] Droms, R., "Dynamic Host Configuration Protocol",
RFC 2131, March 1997. RFC 2131, March 1997.
[RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", RFC 2132, March 1997.
[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.
[RFC3118] Droms, R. and W. Arbaugh, "Authentication for DHCP [RFC3118] Droms, R. and W. Arbaugh, "Authentication for DHCP
Messages", RFC 3118, June 2001. Messages", RFC 3118, June 2001.
Author's Address Author's Address
Ralph Droms Ralph Droms
 End of changes. 5 change blocks. 
9 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/