Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration
RFC 3495

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 06

Network Working Group                                           B. Beser
Request for Comments: 3495                              Juniper Networks
Category: Standards Track                                  P. Duffy, Ed.
                                                           Cisco Systems
                                                              March 2003

           Dynamic Host Configuration Protocol (DHCP) Option
                  for CableLabs Client Configuration

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

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

Abstract

   This document defines a Dynamic Host Configuration Protocol (DHCP)
   option that will be used to configure various devices deployed within
   CableLabs architectures.  Specifically, the document describes DHCP
   option content that will be used to configure one class of CableLabs
   client device: a PacketCable Media Terminal Adapter (MTA).  The
   option content defined within this document will be extended as
   future CableLabs client devices are developed.

Beser & Duffy               Standards Track                     [Page 1]
RFC 3495           DHCP Option for CableLabs Clients          March 2003

Table of Contents

   1.  Conventions used in this document............................  2
   2.  Terminology..................................................  2
   3.  Introduction.................................................  3
   4.  CableLabs Client Configuration Option Format.................  4
   5.  CableLabs Client Configuration Option: Sub-Option Definitions  5
       5.1.  TSP's DHCP Server Address Sub-Options..................  5
       5.2.  TSP's Provisioning Server Address Sub-Option...........  6
       5.3.  TSP's AS-REQ/AS-REP Backoff and Retry..................  6
       5.4.  TSP's AP-REQ/AP-REP Backoff and Retry..................  7
       5.5.  TSP's Kerberos Realm Name Sub-Option...................  8
       5.6.  TSP's Ticket Granting Server Utilization Sub-Option....  8
       5.7.  TSP's Provisioning Timer Sub-Option....................  8
   6.  Informational Description of CCC Option Usage................  9
   7.  IANA Considerations..........................................  9
   8.  Legacy Use Information.......................................  9
   9.  Procedure for Adding Additional Sub-options..................  9
   10. Security Considerations...................................... 10
   11. References................................................... 10
       11.1. Normative References................................... 10
       11.2. Informative References................................. 11
   12. Acknowledgments.............................................. 11
   13. Authors' Addresses........................................... 12
   14. Full Copyright Statement..................................... 13

1.  Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14, RFC 2119 [1].

2.  Terminology

   Definitions of terms used throughout this document:

      *  "Telephony Service Provider" or "TSP"

   The business entity from which a subscriber receives telephony
   service.

   See RFC 2131 [6] for additional DHCP terminology.

Beser & Duffy               Standards Track                     [Page 2]
RFC 3495           DHCP Option for CableLabs Clients          March 2003

3.  Introduction

   Cable Television Laboratories, Inc. (CableLabs) is a non-profit
   research and development consortium that serves the cable television
   industry via design and specification of new and emerging broadband
   service architectures.  Several CableLabs initiatives define DHCP
   clients that have specific DHCP configuration requirements.  One such
   initiative is the PacketCable project.

   The PacketCable project is aimed at architecting, qualifying, and
   supporting Internet-based multimedia services over cable-based packet
   networks.  These new multimedia services will include telephony and
   videoconferencing, delivered using the basic Internet Protocol (IP)
   technology that is used to send data via the Internet.

   PacketCable 1.0 provides Voice over IP (VoIP) service delivery.  The
   VoIP service is supported at the customer site by two key components:
   a Cable Modem (CM) and a Media Terminal Adapter (MTA).  The CM
   converts the cable RF signals to/from various IP voice protocols,
   while the MTA converts the VoIP protocols into analog telephony