draft-ietf-dhc-packetcable-00.txt   draft-ietf-dhc-packetcable-01.txt 
B. Beser DHC Working Group B. Beser
Internet Draft 3Com Internet Draft Pacific Broadband Communications
Document: draft-ietf-dhc-packetcable-00.txt March 2000 Document: draft-ietf-dhc-packetcable-01.txt October 2000
Category: Informational Category: Informational
DHCP Option for PacketCable VoIP Client Configuration DHCP Option for PacketCable VoIP Client Configuration
Status of this Memo Status of this Memo
This document is an Internet-Draft and is NOT offered in accordance This document is an Internet-Draft and is in full conformance with
with Section 10 of RFC2026 [1], and the author does not provide the all provisions of Section 10 of RFC2026 [1].
IETF with any rights other than to publish as an Internet-Draft
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Internet-Drafts are draft documents valid for a maximum of Drafts. Internet-Drafts are draft documents valid for a maximum of
six months and may be updated, replaced, or obsoleted by other six months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet- Drafts documents at any time. It is inappropriate to use Internet- Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." progress."
skipping to change at line 36 skipping to change at line 35
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.
1. Abstract 1. Abstract
The Voice over IP work carried over in the PacketCable project The Voice over IP work carried over in the PacketCable project
conducted by CableLabs. The configuration of the PacketCable Voice conducted by CableLabs. The configuration of the PacketCable Voice
over IP client is achieved using DHCP messaging. over IP client is achieved using DHCP messaging.
This document contains the definition of PacketCable VoIP Client This document contains the definition of the PacketCable VoIP Client
configuration option. configuration option.
2. Conventions used in this document 2. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
this document are to be interpreted as described in RFC-2119 [2]. document are to be interpreted as described in RFC-2119 [2].
3. DHCP Terminology 3. DHCP Terminology
o "DHCP client" o "DHCP client"
A DHCP client or "client" is an Internet host using DHCP to obtain A DHCP client or "client" is an Internet host using DHCP to obtain
configuration parameters such as a network address. configuration parameters such as a network address.
o "DHCP server" o "DHCP server"
Beser Informational Expiration May 2000 1
PacketCable VoIP Client Configuration October 2000
A DHCP server of "server"is an Internet host that returns A DHCP server of "server"is an Internet host that returns
configuration parameters to DHCP clients. configuration parameters to DHCP clients.
o "binding" o "binding"
A binding is a collection of configuration parameters, including A binding is a collection of configuration parameters, including at
at least an IP address, associated with or "bound to" a DHCP least an IP address, associated with or "bound to" a DHCP client.
client. Bindings are managed by DHCP servers. Bindings are managed by DHCP servers.
4. Introduction 4. Introduction
PacketCable is a project conducted by Cable Television Laboratories, PacketCable is a project conducted by Cable Television Laboratories,
Inc. (CableLabs) and its member companies aimed at identifying, Inc. (CableLabs) and its member companies aimed at identifying,
qualifying, and supporting Internet-based voice and video products qualifying, and supporting Internet-based voice and video products
over cable systems. These products will represent new classes of over cable systems. These products will represent new classes of
services utilizing cable-based packet communication networks. New services utilizing cable-based packet communication networks. New
service classes include telephone calls and videoconferencing over service classes include telephone calls and videoconferencing over
cable networks and the Internet. The services would be delivered cable networks and the Internet. The services would be delivered
using the basic Internet Protocol (IP) technology that is used to using the basic Internet Protocol (IP) technology that is used to
send data via the Internet. send data via the Internet.
PacketCable project produced specifications of VoIP elements which The PacketCable embedded-MTA (MTA) is a single physical device with
can be found in www.packetcable.com. The PacketCable VoIP Client dual personality: a Cable Modem (CM) and a VoIP device. Both of
uses DHCP for configration. Due to specific needs of PacketCable these devices are administered by different entities. Both of the
client a new DHCP option is needed. The new option is designed to personalities have different IP addresses and different IP
have a number of sub-information which is laid down in DHCP option configurations.
fashion [3].
PacketCable project produced specifications of VoIP elements, which
can be found in www.packetcable.com. The PacketCable VoIP Client uses
DHCP for configuration. Due to specific needs of PacketCable client a
new DHCP option is needed. The new option is designed to have a
number of sub-information, which is laid down in DHCP option fashion
[3].
5. PacketCable VoIP Client Configuration Option 5. PacketCable VoIP Client Configuration Option
The code for this option is TBD. The code for this option is TBD.
PacketCable VoIP Client Configuration option is used for PacketCable The PacketCable VoIP Client Configuration option is used by the
VoIP clients to identify a list of valid PacketCable network PacketCable VoIP clients to identify a list of valid PacketCable
servers. specific network servers.
The option contains sub-fields to contain information regarding
these servers. The option looks as depicted below at the DHCP OFFER.
-------------------------------------------------------- The option sub-fields contain information regarding these servers.
| TBD | Length | PacketCable VoIP Client Configuration |
--------------------------------------------------------
A client that recognizing the sub-fields sees the option as: The option is included in DHCP OFFER-s, and is laid out as depicted
below:
------------------------------------------------------------- -------------------------------------------------------------
| TBD | Length | Subfield 1 | Subfield 2 | ... | Subfield n | | TBD | Length | Subfield 1 | Subfield 2 | ... | Subfield n |
------------------------------------------------------------- -------------------------------------------------------------
Each sub-field is in the form of: Each sub-field is in the form of:
Beser Informational Expires May 2000 2
PacketCable VoIP Client Configuration October 2000
--------------------------------------------------- ---------------------------------------------------
| Sub-field Number | Length | Subfield information | | Sub-field Number | Length | Subfield information |
--------------------------------------------------- ---------------------------------------------------
Each sub-field of PacketCable VoIP Client Configuration identifies a Each sub-field of the PacketCable VoIP Client Configuration
particular type of PacketCable server. Sub-field 1 identifies the identifies a particular type of PacketCable server. Sub-fields 1 and
PacketCable network DHCP server, sub-field 2 identifies the 2 identify the primary and secondary PacketCable network DHCP
PacketCable service provider's SNMP entity, and sub-field 3 and 4 servers, sub-field 3 identifies the PacketCable service provider's
identifies the primary and secondary PacketCable network DNS SNMP entity, and sub-fields 4 and 5 identify the primary and
servers. The Sub-fields are summarized below: secondary PacketCable network DNS servers. The Sub-fields are
summarized below:
-------------------------------------------------------------------- --------------------------------------------------------------------
|Option |Sub-field | Description and Comments | |Option |Sub-field | Description and Comments |
==================================================================== ====================================================================
| TBD | 1 | Telephony Service Provider DHCP Server Address| | TBD | 1 | Telephony Service Provider Primary DHCP |
| | | Server Address |
| |----------------------------------------------------------- | |-----------------------------------------------------------
| | 2 | Telephony Service Provider SNMP Server Address| | | 2 | Telephony Service Provider Secondary DHCP |
| | | Server Address |
| |----------------------------------------------------------- | |-----------------------------------------------------------
| | 3 | Telephony Service Provider Network Primary | | | 3 | Telephony Service Provider SNMP Server Address|
| | | Domain Name Server |
| |----------------------------------------------------------- | |-----------------------------------------------------------
| | 4 | Telephony Service Provider Network Secondary | | | 4 | Telephony Service Provider Network Primary |
| | | Domain Name Server | | | | Domain Name Server Address |
| |-----------------------------------------------------------
| | 5 | Telephony Service Provider Network Secondary |
| | | Domain Name Server Address |
-------------------------------------------------------------------- --------------------------------------------------------------------
6. PacketCable VoIP Client option Sub-field Definitions 6. PacketCable VoIP Client option Sub-field Definitions
The following parts provide detailed descriptions of each sub-field The following parts provide detailed descriptions of each sub-field
of DHCP PacketCable VoIP Client option. Note that UDP port numbers of DHCP PacketCable VoIP Client option. Note that UDP port numbers
are normally standard values as defined in [4]. However, the format are normally standard values as defined in [4]. The port numbers
of the sub-field data fields defined here have a provision to MAY be omitted, if the standard protocol ports are to be used as
optionally include port numbers for these systems if a port number defined in [4]. E.g.:the standard DNS UDP port number is 42/udp. If
other than the standard is required. If no port number is specified, non-standard port numbers are used, these MUST be appended as shown
the standard port number based on the definitions [4] is assumed. below.
For example, the standard DNS UDP port number is 42/udp.
6.1. Telephony Service Provider's DHCP Server Address 6.1. Telephony Service Provider's DHCP Server Address
The Telephony Service Provider's DHCP Server Address identifies the The Telephony Service Provider's (TSP) DHCP Server Address identifies
DHCP server that will be used to obtain an MTA-unique IP address for the DHCP server that will be used to obtain an MTA-unique IP address
a given telephony service provider's network administrative domain. for a given telephony service provider's network administrative
This address can be configured as either an FQDN or as an IPv4 domain.
address.
The encoding of sub-field 1 is as follows: Sub-field 1 is the address of the network's primary Telephony Service
Provider DHCP server IP Address. Sub-field 2 is the address of the
network's secondary Telephony Service Provider DHCP server. Sub-field
2 MAY be specified to identify a redundant or backup DHCP server.
-------------------------------------------------------------------- Beser Informational Expires May 2000 3
PacketCable VoIP Client Configuration October 2000
The encoding syntax for sub-field 1 and sub-field 2 is as follows:
---------------------------------------------------------------------
|Sub-field | Value | Description and Comments | |Sub-field | Value | Description and Comments |
==================================================================== =====================================================================
| 1 |[x.y.z.y]:port | Either the IP address or the FQDN will| | 1 |[x.y.z.y]:port | IP address of Primary TSP DHCP Server |
| |---------------| be configured. The port number is to | | | | The port number is to be used only if |
| | FQDN:port | be used only if different than well | | | | different than the default port number |
| | | port number is to be used. | | | | is to be used. |
-------------------------------------------------------------------- ---------------------------------------------------------------------
| 2 |[x.y.z.y]:port | IP address of Secondary TSP DHCP Server|
| | | The port number is to be used only if |
| | | different than the default port number |
| | | is to be used. |
---------------------------------------------------------------------
6.2. Telephony Service Provider's SNMP Entity Address 6.2. Telephony Service Provider's SNMP Entity Address
The Telephony Service Provider's SNMP Entity Address is the network The Telephony Service Provider's SNMP Entity Address is the network
address of the default server for a given telephony service address of the default server for a given telephony service
provider's network administrative domain. The Telephony Service provider's network administrative domain. The Telephony Service
Provider's SNMP Entity Address component MUST be capable of Provider's SNMP Entity Address component MUST be capable of accepting
accepting SNMP traps. This address can be configured as either an SNMP traps. This address can be configured as either an FQDN or as an
FQDN or as an IPv4 address. IPv4 address.
The encoding of sub-field 2 is as follows: The encoding of sub-field 3 is as follows:
-------------------------------------------------------------------- --------------------------------------------------------------------
|Sub-field | Value | Description and Comments | |Sub-field | Value | Description and Comments |
==================================================================== ====================================================================
| 2 |[x.y.z.y]:port | Either the IP address or the FQDN will| | 3 |[x.y.z.y]:port | Either the IP address or the FQDN will|
| |---------------| be configured. The port number is to | | |---------------| be configured. The port number is to |
| | FQDN:port | be used only if different than well | | | FQDN:port | be used only if different than the |
| | | port number is to be used. | | | | default port number is to be used. |
-------------------------------------------------------------------- --------------------------------------------------------------------
6.3. DNS system 6.3. DNS system
The Telephony Service Provider's DNS server is required to resolve a The Telephony Service Provider's DNS server is required to resolve a
PacketCable device's FQDN into an IPv4 address. The DNS server's PacketCable device's FQDN into an IPv4 address. The DNS server's
address MUST be specified in the IPv4 format. address MUST be specified in the IPv4 format.
Sub-field 3 is the address of the network's primary DNS server and Sub-field 4 is the address of the network's primary DNS server IP
MUST be specified if sub-field 1 or sub-field 2 is in FQDN format. Address. Sub-field 5 is the address of the network's secondary DNS
Sub-field 4 is the address of the network's secondary DNS server. server. Sub-field 5 MAY be specified to identify a redundant or
Sub-field 4 MAY be specified to identify a redundant or backup DNS backup DNS server.
server.
The encoding syntax for sub-field 3 and sub-field 4 is as follows: The encoding syntax for sub-field 4 and sub-field 5 is as follows:
-------------------------------------------------------------------- Beser Informational Expires May 2000 4
PacketCable VoIP Client Configuration October 2000
---------------------------------------------------------------------
|Sub-field | Value | Description and Comments | |Sub-field | Value | Description and Comments |
==================================================================== =====================================================================
| 3 |[x.y.z.y]:port | Either the IP address of the telephony| | 4 |[x.y.z.y]:port | IP address of Primary TSP DNS Server |
| |---------------| service providers primary DNS server. | | | | The port number is to be used only if |
| | FQDN:port | Port will be defined only if different| | | | different than the default port number |
| | | than well-known port. | | | | is to be used. |
-------------------------------------------------------------------- ---------------------------------------------------------------------
| 4 |[x.y.z.y]:port | Either the IP address of the telephony| | 5 |[x.y.z.y]:port | IP address of Secondary TSP DNS Server |
| |---------------| service providers secondary DNS server| | | | The port number is to be used only if |
| | FQDN:port | Port will be defined only if different| | | | different than the default port number |
| | | than well-known port. | | | | is to be used. |
-------------------------------------------------------------------- ---------------------------------------------------------------------
6.4. Procedure for adding call control server types 6.4. Procedure for adding call control server types
A vendor may add a new sub-field by issuing an internet draft that A vendor may add a new sub-field by issuing an internet draft that
contains the new sub-field. The new sub-field code MUST be labeled contains the new sub-field. The new sub-field code MUST be labeled
"TBD." This draft will then be submitted to the DHC working group, "TBD." This draft will then be submitted to the DHC working group,
and, if accepted for inclusion in the DHCP specification, a sub- and, if accepted for inclusion in the DHCP specification, a sub-
option field code is assigned and the sub-option specification is option field code is assigned and the sub-option specification will
published as an RFC which updates this RFC. be published as an RFC, which will update this RFC.
6.5 Typical us of PacketCable VoIP Client Configuration option
MTA
--------------_______ Telephony
VoIP CM CM DHCP Server DHCP Server
| | | |
(MTA boots up) | |
| | | |
| | broadcast DISCOVER (1)| |
| |---------------------->| |
| | | |
| | CM IP configuration + | |
| | TSP DHCP Serv. IP@ (2)| |
| |<----------------------| |
| PCC (3) | | |
|<===========| | |
| | | |
| unicast DISCOVER (4) |
|----------------------------------------------------------->|
| | |
| | VoIP IP configuration + |
| | PacketCable Client Configuration (5) |
|<-----------------------------------------------------------|
| | |
(Telephony registration via |
Telephony Service Provider SNMP Server) |
Figure 1 Typical MTA IP Configuration via DHCP
Beser Informational Expires May 2000 5
PacketCable VoIP Client Configuration October 2000
The PacketCable VoIP Client Configuration option is used on the DHCP
messaging of both CM and VoIP device personalities. A typical MTA
boot operation is depicted in Figure 1 and can be described as
below:
1. When MTA boots the CM personality sends a broadcast DISCOVER
message with proper Vendor Client Identifier Option.
2. The DHCP server gives a proper address from CM IP address pool,
along with the PacketCable VoIP Client Configuration Option
populated with (at least) Telephony Service Provider DHCP Server IP
address(es).
3. The CM passes the PacketCable Client Configuration (PCC)
information to VoIP device.
4. The VoIP device uses the information in the Telephony Service
Provider IP DHCP Server Address field and unicasts the DISCOVER
message to the address(es).
5. Telephony Service Provider IP DHCP Server returns the IP
configuration for VoIP personality and PacketCable Client
Configuration information.
From this point on the MTA uses the FQDN information for PacketCable
SNMP server using Telephony Service Provider DNS servers, and
registers for service.
7. Security Considerations 7. Security Considerations
DHCP currently provides no authentication or security This draft relies on DHCP protocol [5] for authentication and
mechanisms. Potential exposures to attack are discussed security, i.e. it does not provide either in excess of what DHCP is
is section 7 of the protocol specification [5]. (or will be) providing.
9. References 9. References
1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996. 9, RFC 2026, October 1996.
2. Bradner, S., "Key words for use in RFCs to Indicate Requirement 2. Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
3. Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor 3. Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", RFC-2132, March 1997. Extensions", RFC-2132, March 1997.
4. Reynolds, J., Postel, J., _ASSIGNED NUMBERS_, RFC 1340, July 4. Reynolds, J., Postel, J., _ASSIGNED NUMBERS_, RFC 1340, July 1992.
1992.
6. Droms, R., "Dynamic Host Configuration Protocol", RFC-2131, March 5. Droms, R., "Dynamic Host Configuration Protocol", RFC-2131, March
1997. 1997.
Beser Informational Expires May 2000 6
PacketCable VoIP Client Configuration October 2000
10. Acknowledgments 10. Acknowledgments
I would like to extend a heartfelt thanks to all those who I would like to extend a heartfelt thanks to all those who
contributed to the development of PacketCable Provisioning contributed to the development of PacketCable Provisioning
specification. Particular thanks are given Sasha Medvinsky, Raj specification. Particular thanks are given Angela Lyda, Rick Morris
Deshpande (Motorola), Angela Lyda, Rick Morris (Arris Interactive); (Arris Interactive); Steven Bellovin (AT&T); Jiri Matousek (Bay
Steven Bellovin (AT&T); Jiri Matousek (Bay Networks); Klaus Networks); Klaus Hermanns, Azita Kia, Michael Thomas, Rich Woundy
Hermanns, Azita Kia, Michael Thomas, Rich Woundy (Cisco); Deepak (Cisco); Deepak Patil (Com21); Jeff Ollis, Rick Vetter, Sasha
Patil (Com21); Jeff Ollis, Rick Vetter (General Instrument); Roger Medvinsky, Raj Deshpande (Motorola); Roger Loots (Lucent); Roy
Loots (Lucent); Roy Spitzer (Telogy), Aviv Goren (Terayon); and Spitzer (Telogy), Aviv Goren (Terayon); and Prithivraj Narayanan
Prithivraj Narayanan (Wipro). (Wipro). Last but not least special thanks to Steve Gonczi (Network
Engines) for suggestions.
11. Author's Addresses 11. Author's Addresses
Burcak Beser Burcak Beser
3Com Pacific Broadband Communications
Mount Prospect, IL 60056 3103 North First Street,
Email: Burcak_Beser@3com.com San Jose, CA, 95134
Phone: (408) 468 6265
Email: Burcak@pbc.com
Beser Informational Expires May 2000 7
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/