draft-ietf-dhc-bcmc-options-04.txt   draft-ietf-dhc-bcmc-options-05.txt 
Network Working Group K. Chowdhury Network Working Group K. Chowdhury
Internet-Draft Starent Networks Internet-Draft Starent Networks
Expires: March 31, 2006 P. Yegani Expires: April 2, 2006 P. Yegani
Cisco Systems Cisco Systems
L. Madour L. Madour
Ericsson Ericsson
September 27, 2005 September 29, 2005
DHCP Options for Broadcast and Multicast Control Servers DHCP Options for Broadcast and Multicast Control Servers
draft-ietf-dhc-bcmc-options-04.txt draft-ietf-dhc-bcmc-options-05.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 37 skipping to change at page 1, line 37
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 31, 2006. This Internet-Draft will expire on April 2, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
Abstract Abstract
This document defines new options to discover the Broadcast and This document defines new options to discover the Broadcast and
Multicast Service (BCMCS) controller in an IP network. BCMCS is Multicast Service (BCMCS) controller in an IP network. BCMCS is
being developed for 3rd generation (3G) cellular telephone networks. being developed for 3rd generation (3G) cellular telephone networks.
skipping to change at page 2, line 28 skipping to change at page 2, line 28
4.3 Broadcast & Multicast Service Controller IPv4 address 4.3 Broadcast & Multicast Service Controller IPv4 address
option for DHCPv4 . . . . . . . . . . . . . . . . . . . . 7 option for DHCPv4 . . . . . . . . . . . . . . . . . . . . 7
4.4 Broadcast & Multicast Service Controller IPv6 Address 4.4 Broadcast & Multicast Service Controller IPv6 Address
Option for DHCPv6 . . . . . . . . . . . . . . . . . . . . 8 Option for DHCPv6 . . . . . . . . . . . . . . . . . . . . 8
4.5 Consideration for Client Operation . . . . . . . . . . . . 9 4.5 Consideration for Client Operation . . . . . . . . . . . . 9
4.6 Consideration for Server Operation . . . . . . . . . . . . 9 4.6 Consideration for Server Operation . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
8. Normative References . . . . . . . . . . . . . . . . . . . . . 13 8. Normative References . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . . 15 Intellectual Property and Copyright Statements . . . . . . . . 15
1. Motivation 1. Motivation
Dynamic Host Configuration Protocol [RFC2131] and [RFC3315] can be Dynamic Host Configuration Protocol [RFC2131] and [RFC3315] can be
used to configure various non-IP address type of parameters. These used to configure various non-IP address type of parameters. These
parameters are required for normal operation of various services that parameters are required for normal operation of various services that
are offered over an IP network. are offered over an IP network.
Broadcast and multicast service (BCMCS) is one such service that is Broadcast and multicast service (BCMCS) is one such service that is
skipping to change at page 3, line 44 skipping to change at page 3, line 44
As described in [BCMCS], the MNs are required to know the IPv4 or the As described in [BCMCS], the MNs are required to know the IPv4 or the
IPv6 address of the BCMCS controller entity so that they can download IPv6 address of the BCMCS controller entity so that they can download
all the necessary information about a desired broadcast and/or a all the necessary information about a desired broadcast and/or a
multicast program. In a roaming environment static configuration of multicast program. In a roaming environment static configuration of
the BCMCS controller's IP address becomes unrealistic. Therefore, the BCMCS controller's IP address becomes unrealistic. Therefore,
DHCP is considered to be a method to dynamically configure the MNs DHCP is considered to be a method to dynamically configure the MNs
with the IP address or the fully qualified domain name of the BCMCS with the IP address or the fully qualified domain name of the BCMCS
controller in the 3G cellular telephone networks. controller in the 3G cellular telephone networks.
In order to allow the MNs to discover the BCMCS controllers, the MNs In order to allow the MNs to discover the BCMCS controllers, the MNs
request the appropriate option codes from the DHCP server using request the appropriate option codes from the DHCP server. The DHCP
Parameter Request List option. The DHCP servers need to return the servers need to return the corresponding configuration options that
corresponding configuration options that carry either BCMCS carry either BCMCS controller's IP address or fully qualified domain
controller's IP address or fully qualified domain name based on name based on configuration. This document defines the necessary
configuration. This document defines the necessary options and options and option codes.
option codes.
2. Overview of the 3GPP2 BCMCS Network 2. Overview of the 3GPP2 BCMCS Network
The Broadcast and Multicast Service architecture in a 3G cellular The Broadcast and Multicast Service architecture in a 3G cellular
telephone network such as 3GPP2 has the following model: telephone network such as 3GPP2 has the following model:
+------------+ +--------+ +------------+ +--------+
| BCMCS | | | | BCMCS | | |
| Controller | | DHCP | | Controller | | DHCP |
| | | Server | | | | Server |
skipping to change at page 7, line 40 skipping to change at page 7, line 40
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BCMCS Control Server Domain Name List | | BCMCS Control Server Domain Name List |
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_BCMCS_SERVER_D (TBD2). option-code: OPTION_BCMCS_SERVER_D (TBD2).
option-length: Length of the 'BCMCS Control Server Domain Name List' option-length: Length of the 'BCMCS Control Server Domain Name List'
field in octets; variable. field in octets; variable.
BCMCS Control Server Domain Name List: Identical content as in BCMCS Control Server Domain Name List: Identical format as in Section
Section 4.1 (except the Code and Len fields). 4.1 (except the Code and Len fields).
4.3 Broadcast & Multicast Service Controller IPv4 address option for 4.3 Broadcast & Multicast Service Controller IPv4 address option for
DHCPv4 DHCPv4
The Length byte (Len) is followed by a list of IPv4 addresses The Length byte (Len) is followed by a list of IPv4 addresses
indicating BCMCS controller IPv4 addresses. The BCMCS controllers indicating BCMCS controller IPv4 addresses. The BCMCS controllers
MUST be listed in order of preference. Its minimum length is 4, and MUST be listed in order of preference. Its minimum length is 4, and
the length MUST be a multiple of 4. The DHCPv4 option for this the length MUST be a multiple of 4. The DHCPv4 option for this
encoding has the following format: encoding has the following format:
skipping to change at page 9, line 27 skipping to change at page 9, line 27
option. In this case, the client SHOULD NOT use the BCMCS Controller option. In this case, the client SHOULD NOT use the BCMCS Controller
IPv6 or IPv4 Address option unless the server(s) in the BCMCS IPv6 or IPv4 Address option unless the server(s) in the BCMCS
Controller Domain Name List can not be resolved or reached. Controller Domain Name List can not be resolved or reached.
4.6 Consideration for Server Operation 4.6 Consideration for Server Operation
A server MAY send a client either the BCMCS Controller Domain Name A server MAY send a client either the BCMCS Controller Domain Name
List Option or the BCMCS Controller IPv6 Address/IPv4 Address options List Option or the BCMCS Controller IPv6 Address/IPv4 Address options
if the server is configured to do so. if the server is configured to do so.
If a client requests for both the options and the server is If a client requests both the options and the server is configured
configured with both types of information, the server MAY send the with both types of information, the server MAY send the client only
client only one of the options if it is configured to do so. In this one of the options if it is configured to do so. In this case the
case the server SHOULD send the BCMCS Controller Domain Name List server SHOULD send the BCMCS Controller Domain Name List option.
option.
A server configured with the BCMCS Controller IPv6 or IPv4 Address A server configured with the BCMCS Controller IPv6 or IPv4 Address
information MUST send a client the BCMCS Controller IPv6 or IPv4 information MUST send a client the BCMCS Controller IPv6 or IPv4
Address option if that client requested only the BCMCS Controller Address option if that client requested only the BCMCS Controller
IPv6 or IPv4 address option and not the BCMCS Controller Domain Name IPv6 or IPv4 address option and not the BCMCS Controller Domain Name
List option in the ORO or Parameter Request List option. List option in the ORO or Parameter Request List option.
If a client requests for the BCMCS Controller IPv6 or IPv4 Address If a client requests for the BCMCS Controller IPv6 or IPv4 Address
option and the Server is configured only with the domain name(s), the option and the Server is configured only with the domain name(s), the
Server MUST return the Domain Name List and vice versa. Server MUST return the Domain Name List and vice versa.
skipping to change at page 11, line 10 skipping to change at page 11, line 10
Neither option SHOULD MAY Neither option SHOULD MAY
Domain Name List MUST MAY Domain Name List MUST MAY
IPv6/IPv4 Address MAY MUST IPv6/IPv4 Address MAY MUST
Both options SHOULD MAY Both options SHOULD MAY
5. Security Considerations 5. Security Considerations
This document does not introduce any new security concerns beyond This document does not introduce any new security concerns beyond
those specified in the basic DHCP [RFC2131] and DHCPv6 [RFC3315] those specified in the basic DHCP [RFC2131] and DHCPv6 [RFC3315]
specifications. In the absence of message integrity protection for specifications. In the absence of message integrity protection for
these options, an attacker could modify the option values to these options, an attacker could modify the option values to divert
frustrate or divert requests for broadcast service. requests for broadcast service.
6. IANA Considerations 6. IANA Considerations
The following option codes for Broadcast & Multicast Service The following option codes for Broadcast & Multicast Service
Controller option must be assigned by IANA: Controller option must be assigned by IANA:
1. The BCMCS Controller Domain Name list (section 4.1) has been 1. The BCMCS Controller Domain Name list (section 4.1) has been
assigned a value of TBD1 from the DHCPv4 option space. assigned a value of TBD1 from the DHCPv4 option space.
2. The BCMCS Controller Domain Name list (section 4.2) has been 2. The BCMCS Controller Domain Name list (section 4.2) has been
skipping to change at page 13, line 18 skipping to change at page 13, line 18
comments during the development of this document: comments during the development of this document:
AC Mahendran, Jun Wang, Raymond Hsu, Jayshree Bharatia, Ralph Droms, AC Mahendran, Jun Wang, Raymond Hsu, Jayshree Bharatia, Ralph Droms,
Ted Lemon, Margaret Wasserman, Thomas Narten, Elwyn Davies, Pekka Ted Lemon, Margaret Wasserman, Thomas Narten, Elwyn Davies, Pekka
Savola, Bert Wijnen, David Kessens, Brian E Carpenter, and Stig Savola, Bert Wijnen, David Kessens, Brian E Carpenter, and Stig
Venaas. Venaas.
8. Normative References 8. Normative References
[BCMCS] 3GPP2, www.3gpp2.org, [BCMCS] 3GPP2, www.3gpp2.org,
ftp://ftp.3gpp2.org/TSGX/Projects/X.P0022 2ndV&V.zip, http://www.3gpp2.org/Public_html/specs/tsgx.cfm, "X.S0022,
"X.S0022, Broadcast and Multicast Service in cdma2000 Broadcast and Multicast Service in cdma2000 Wireless IP
Wireless IP Network. (pending publication)", Network.", December 2005.
December 2004.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987. specification", STD 13, RFC 1035, November 1987.
[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.
 End of changes. 10 change blocks. 
24 lines changed or deleted 21 lines changed or added

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