Container Option for Server Configuration
draft-ietf-dhc-container-opt-06

The information below is for an old version of the document
Document Type Active Internet-Draft (dhc WG)
Last updated 2012-12-17
Replaces draft-droms-dhc-container-opt
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Ted Lemon
Send notices to dhc-chairs@tools.ietf.org, draft-ietf-dhc-container-opt@tools.ietf.org
dhc Working Group                                               R. Droms
Internet-Draft                                                  R. Penno
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: June 20, 2013                                 December 17, 2012

               Container Option for Server Configuration
                  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

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

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

   This Internet-Draft will expire on June 20, 2013.

Copyright Notice

   Copyright (c) 2012 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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Droms & Penno             Expires June 20, 2013                 [Page 1]
Internet-Draft            DHCP Container Option            December 2012

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Problem statement and requirements for RG DHCP
       server 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.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
   8.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . . . 8
     8.1.  Revision -02  . . . . . . . . . . . . . . . . . . . . . . . 8
     8.2.  Revision -03  . . . . . . . . . . . . . . . . . . . . . . . 9
     8.3.  Revision -04  . . . . . . . . . . . . . . . . . . . . . . . 9
   9.  Related Work  . . . . . . . . . . . . . . . . . . . . . . . . . 9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 9
     10.1. Normative References  . . . . . . . . . . . . . . . . . . . 9
     10.2. Informative References  . . . . . . . . . . . . . . . . . . 9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 9

Droms & Penno             Expires June 20, 2013                 [Page 2]
Internet-Draft            DHCP Container Option            December 2012

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
   Residential Gateway (RG), which can then be passed along to IPTV
   device(s) in the subscriber network.

   Existing RGs may pass some configuration information received by the
   RG DHCP client to the RG server for configuration of devices attached
   to the consumer network.  There are several motivations for this
   option:

   o  The devices attached to the consumer network may require different
      configuration information than the DHCP options provided to the
Show full document text