draft-ietf-dhc-bcmc-options-03.txt   draft-ietf-dhc-bcmc-options-04.txt 
Network Working Group K. Chowdhury Network Working Group K. Chowdhury
Internet-Draft Starent Networks Internet-Draft Starent Networks
Expires: February 2, 2006 P. Yegani Expires: March 31, 2006 P. Yegani
Cisco Systems Cisco Systems
L. Madour L. Madour
Ericsson Ericsson
August 1, 2005 September 27, 2005
DHCP Options for Broadcast and Multicast Control Servers DHCP Options for Broadcast and Multicast Control Servers
draft-ietf-dhc-bcmc-options-03.txt draft-ietf-dhc-bcmc-options-04.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 February 2, 2006. This Internet-Draft will expire on March 31, 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.
Users of the service interact with a controller in the network via Users of the service interact with a controller in the network via
the Mobile Node (MN) to derive information required to receive the Mobile Node (MN) to derive information required to receive
broadcast and multicast service. Dynamic Host Configuration Protocol broadcast and multicast service. Dynamic Host Configuration Protocol
can be used to configure the MN to acccess a particular controller. can be used to configure the MN to access a particular controller.
This document defines the related options and option codes. This document defines the related options and option codes.
Table of Contents Table of Contents
1. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Overview of the 3GPP2 BCMCS Network . . . . . . . . . . . . . 4 2. Overview of the 3GPP2 BCMCS Network . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Broadcast & Multicast Service Controller Options . . . . . . . 6 4. Broadcast & Multicast Service Controller Options . . . . . . . 6
4.1 Broadcast & Multicast Service Controller Domain Name 4.1 Broadcast & Multicast Service Controller Domain Name
list for DHCPv4 . . . . . . . . . . . . . . . . . . . . . 6 list for DHCPv4 . . . . . . . . . . . . . . . . . . . . . 6
4.2 Broadcast & Multicast Service Controller Domain Name 4.2 Broadcast & Multicast Service Controller Domain Name
List Option for DHCPv6 . . . . . . . . . . . . . . . . . . 7 List Option for DHCPv6 . . . . . . . . . . . . . . . . . . 7
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 . . . . . . . . . . . . 8 4.5 Consideration for Client Operation . . . . . . . . . . . . 9
4.6 Consideration for Server Operation . . . . . . . . . . . . 8 4.6 Consideration for Server Operation . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
8. Normative References . . . . . . . . . . . . . . . . . . . . . 12 8. Normative References . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 14
Intellectual Property and Copyright Statements . . . . . . . . 14 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
being standardized in various mobile wireless standard bodies such as being standardized in various mobile wireless standard bodies such as
skipping to change at page 4, line 29 skipping to change at page 4, line 29
| |
V V
+----+ +------------+ +------------+ +----+ +------------+ +------------+
| | | | | | | | | | | |
| MN/| bearer | Radio | | BCMCS | | MN/| bearer | Radio | | BCMCS |
|User|<-------| Access |<---| Content | |User|<-------| Access |<---| Content |
| | | Network | | Server | | | | Network | | Server |
+----+ +------------+ +------------+ +----+ +------------+ +------------+
Note that this figure is shown here for a basic understanding of how Note that this figure is shown here for a basic understanding of how
Broadcast and Multicast service works in a 3G cellular telehone Broadcast and Multicast service works in a 3G cellular telephone
network. The network elements except MN/user and the DHCP server are network. The network elements except MN/user and the DHCP server are
not relevant to the text in this document. not relevant to the text in this document.
The MN interacts with the BCMCS Controller to request broadcast/ The MN interacts with the BCMCS Controller to request broadcast/
multicast program information from the network (e.g., scheduled time, multicast program information from the network (e.g., scheduled time,
multicast IP address, port numbers). The MN may also be multicast IP address, port numbers). The MN may also be
authenticated by the BCMCS Controller while downloading the relevant authenticated by the BCMCS Controller while downloading the relevant
program security related information (such as encryption key). These program security related information (such as encryption key). These
interactions may happen via HTTP and XML as defined in [BCMCS]. interactions may happen via HTTP and XML as defined in [BCMCS].
There may be more than one BCMCS controller in the network. The MN There may be more than one BCMCS controller in the network. The MN
skipping to change at page 6, line 25 skipping to change at page 6, line 25
Code Len FQDN(s) of BCMCS Controller Code Len FQDN(s) of BCMCS Controller
+-----+-----+-----+-----+-----+-----+-----+-- +-----+-----+-----+-----+-----+-----+-----+--
| TBD1| n | s1 | s2 | s3 | s4 | s5 | ... | TBD1| n | s1 | s2 | s3 | s4 | s5 | ...
+-----+-----+-----+-----+-----+-----+-----+-- +-----+-----+-----+-----+-----+-----+-----+--
The option MAY contain multiple domain names, but these domain names The option MAY contain multiple domain names, but these domain names
SHOULD be used to construct SRV lookups as specified in [BCMCS], SHOULD be used to construct SRV lookups as specified in [BCMCS],
rather than querying for different A records. The client can try any rather than querying for different A records. The client can try any
or ALL of the domain names to construct the SRV lookups. The list of or ALL of the domain names to construct the SRV lookups. The list of
domain names MAY conatin the domain name of the access provider and domain names MAY contain the domain name of the access provider and
it's partner networks that also offer broadcast and multicast its partner networks that also offer broadcast and multicast service.
service.
As an example, the access provider may have one or more partners or
resellers often termed as MVNO (Mobile Virtual Network Operators) for
broadcast and multicast service. In this case, the access provider
should be able to use the same DHCP option to send multiple of those
domain names (MVNOs). To illustrate this further, let's assume that
the access provider (operator) has reseller agreement with two MVNOs:
mvno1 and mvno2. Therefore, the Broadcast & Multicast Service
Controller Domain Name list for DHCPv4 option will contain three
domain names: operator.com, mvno1.com, mvno2.com. Upon receiving
this option, the BCMCS client may choose to use one of the domain
names to fetch the appropriate BCMCS controller address (based on
user's preference or configuration). If no preferred domain name is
found in the received list, the client should use a default setting
e.g. use the first one in the list.
If the length of the domain list exceeds the maximum permissible If the length of the domain list exceeds the maximum permissible
length within a single option (254 octets), then the domain list MUST length within a single option (254 octets), then the domain list MUST
be represented in the DHCPv4 message as specified in [RFC3396] . An be represented in the DHCPv4 message as specified in [RFC3396] . An
example case when two controller domain names, example.com and example case when two controller domain names, example.com and
example.net are returned will be: example.net are returned will be:
+----+----+----+----+----+----+----+----+----+----+----+ +----+----+----+----+----+----+----+----+----+----+----+
|TBD1| 26 | 7 | 'e'| 'x'| 'a'| 'm'| 'p'| 'l'| 'e'| 3 | |TBD1| 26 | 7 | 'e'| 'x'| 'a'| 'm'| 'p'| 'l'| 'e'| 3 |
+----+----+----+----+----+----+----+----+----+----+----+ +----+----+----+----+----+----+----+----+----+----+----+
skipping to change at page 8, line 36 skipping to change at page 9, line 7
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_BCMCS_SERVER_A (TBD4). option-code: OPTION_BCMCS_SERVER_A (TBD4).
option-length: Length of the 'BCMCS Control Server IPv6 address' option-length: Length of the 'BCMCS Control Server IPv6 address'
field in octets; variable. field in octets; variable.
4.5 Consideration for Client Operation 4.5 Consideration for Client Operation
For DHCPv6, a client MAY request either or both of the BCMCS For DHCPv4, the client MAY request either or both of the BCMCS
Controller Domain Name List and the IPv4 Address options in the
Parameter Request List option (code 55) as defined in [RFC2132].
For DHCPv6, the client MAY request either or both of the BCMCS
Controller Domain Name List and the IPv6 Address options in the Controller Domain Name List and the IPv6 Address options in the
Options Request Option (ORO) as described in [RFC3315]. Options Request Option (ORO) as described in [RFC3315].
If a client receives both the BCMCS Controller Domain Name List and If the client receives both the BCMCS Controller Domain Name List and
IPv6 Address options, it SHOULD use the Domain Name List option. In IPv6 or IPv4 Address options, it SHOULD use the Domain Name List
this case, the client SHOULD NOT use the BCMCS Controller IPv6 option. In this case, the client SHOULD NOT use the BCMCS Controller
Address option unless the servers in the BCMCS Controller Domain Name IPv6 or IPv4 Address option unless the server(s) in the BCMCS
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.
In case of DHCPv6, If a client requests both options and the server If a client requests for both the options and the server is
is configured with both types of information, the server MAY send the configured with both types of information, the server MAY send the
client only one of these options if it is configured to do so. In client only one of the options if it is configured to do so. In this
this case the server SHOULD send the BCMCS Controller Domain Name case the server SHOULD send the BCMCS Controller Domain Name List
List option. option.
A server configured with the BCMCS Controller IPv6 Address A server configured with the BCMCS Controller IPv6 or IPv4 Address
information MUST send a client the BCMCS Controller IPv6 Address information MUST send a client the BCMCS Controller IPv6 or IPv4
option if that client requested only the BCMCS Controller IPv6 Address option if that client requested only the BCMCS Controller
address option and not the BCMCS Controller Domain Name List option IPv6 or IPv4 address option and not the BCMCS Controller Domain Name
in the ORO [RFC3315]. List option in the ORO or Parameter Request List option.
If a client requests for the BCMCS Controller IPv6 option and the If a client requests for the BCMCS Controller IPv6 or IPv4 Address
Server is configured only with the Domain Names, the Server MUST option and the Server is configured only with the domain name(s), the
return the Domain Names List and vice versa. Server MUST return the Domain Name List and vice versa.
The DNS name(s) MUST be concatenated and encoded using the technique The domain names MUST be concatenated and encoded using the technique
described in section 3.3 of "Domain Names - Implementation And described in section 3.3 of "Domain Names - Implementation And
Specification" [RFC1035]. DNS name compression MUST NOT be used. Specification" [RFC1035]. DNS name compression MUST NOT be used.
The following table summarizes the server's response for DHCPv6: The following table summarizes the server's response:
Client sends in ORO Domain Name List IPv6 Address List Client sends in ORO/
Parameter Request List Domain Name List IPv6/IPv4 Address
__________________________________________________________________ __________________________________________________________________
Neither option SHOULD MAY Neither option SHOULD MAY
Domain Name List MUST MAY Domain Name List MUST MAY
IPv6 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
frustrate or divert requests for broadcast service. frustrate or divert requests for broadcast service.
skipping to change at page 12, line 7 skipping to change at page 13, line 7
3. The BCMCS Controller IPv4 address option (section 4.3) has been 3. The BCMCS Controller IPv4 address option (section 4.3) has been
assigned a value of TBD3 from the DHCPv4 option space. assigned a value of TBD3 from the DHCPv4 option space.
4. The BCMCS Controller IPv6 address option (section 4.4) has been 4. The BCMCS Controller IPv6 address option (section 4.4) has been
assigned a value of TBD4 from the DHCPv6 option space, and a name of assigned a value of TBD4 from the DHCPv6 option space, and a name of
OPTION_BCMCS_SERVER_A. OPTION_BCMCS_SERVER_A.
7. Acknowledgements 7. Acknowledgements
Thanks to the following indivduals for their review and constructive Thanks to the following individuals for their review and constructive
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, and Bert Wijnen. Savola, Bert Wijnen, David Kessens, Brian E Carpenter, and Stig
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, ftp://ftp.3gpp2.org/TSGX/Projects/X.P0022 2ndV&V.zip,
"X.S0022, Broadcast and Multicast Service in cdma2000 "X.S0022, Broadcast and Multicast Service in cdma2000
Wireless IP Network. (pending publication)", Wireless IP Network. (pending publication)",
December 2004. 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.
[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.
[RFC3396] Lemon, T. and S. Cheshire, "Encoding Long Options in the [RFC3396] Lemon, T. and S. Cheshire, "Encoding Long Options in the
Dynamic Host Configuration Protocol (DHCPv4)", RFC 3396, Dynamic Host Configuration Protocol (DHCPv4)", RFC 3396,
November 2002. November 2002.
Authors' Addresses Authors' Addresses
 End of changes. 20 change blocks. 
42 lines changed or deleted 65 lines changed or added

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