idnits 2.17.1 draft-ietf-dhc-bcmc-options-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 447. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 424. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 431. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 437. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 1, 2005) is 6842 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2119' is defined on line 373, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'BCMCS' ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) Summary: 5 errors (**), 0 flaws (~~), 4 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group K. Chowdhury 3 Internet-Draft Starent Networks 4 Expires: February 2, 2006 P. Yegani 5 Cisco Systems 6 L. Madour 7 Ericsson 8 August 1, 2005 10 DHCP Options for Broadcast and Multicast Control Servers 11 draft-ietf-dhc-bcmc-options-03.txt 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on February 2, 2006. 38 Copyright Notice 40 Copyright (C) The Internet Society (2005). 42 Abstract 44 This document defines new options to discover the Broadcast and 45 Multicast Service (BCMCS) controller in an IP network. BCMCS is 46 being developed for 3rd generation (3G) cellular telephone networks. 47 Users of the service interact with a controller in the network via 48 the Mobile Node (MN) to derive information required to receive 49 broadcast and multicast service. Dynamic Host Configuration Protocol 50 can be used to configure the MN to acccess a particular controller. 51 This document defines the related options and option codes. 53 Table of Contents 55 1. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2. Overview of the 3GPP2 BCMCS Network . . . . . . . . . . . . . 4 57 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 58 4. Broadcast & Multicast Service Controller Options . . . . . . . 6 59 4.1 Broadcast & Multicast Service Controller Domain Name 60 list for DHCPv4 . . . . . . . . . . . . . . . . . . . . . 6 61 4.2 Broadcast & Multicast Service Controller Domain Name 62 List Option for DHCPv6 . . . . . . . . . . . . . . . . . . 7 63 4.3 Broadcast & Multicast Service Controller IPv4 address 64 option for DHCPv4 . . . . . . . . . . . . . . . . . . . . 7 65 4.4 Broadcast & Multicast Service Controller IPv6 Address 66 Option for DHCPv6 . . . . . . . . . . . . . . . . . . . . 8 67 4.5 Consideration for Client Operation . . . . . . . . . . . . 8 68 4.6 Consideration for Server Operation . . . . . . . . . . . . 8 69 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 70 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 71 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 72 8. Normative References . . . . . . . . . . . . . . . . . . . . . 12 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 12 74 Intellectual Property and Copyright Statements . . . . . . . . 14 76 1. Motivation 78 Dynamic Host Configuration Protocol [RFC2131] and [RFC3315] can be 79 used to configure various non-IP address type of parameters. These 80 parameters are required for normal operation of various services that 81 are offered over an IP network. 83 Broadcast and multicast service (BCMCS) is one such service that is 84 being standardized in various mobile wireless standard bodies such as 85 3GPP2, OMA, and 3GPP. A description of the BCMCS as defined in 3GPP2 86 can be found in [BCMCS]. 88 While DHCP already defines many options for device configuration, no 89 option exists for configuring a mobile device to use BCMCS. This 90 memo defines extensions for both DHCPv4 and DHCPv6 so that DHCP can 91 be used to provide necessary configuration information to a mobile 92 device about the BCMCS controllers. 94 DHCP is being used in 3GPP2, to assist mobile nodes (MN) with the 95 discovery of the BCMCS Controller in a mobile operator's IP network. 96 The BCMCS includes a controller component that is responsible for 97 managing the service via interaction with the MN and other network 98 entities. In this document we will call this a BCMCS controller. 100 An overview of the 3GPP2 BCMCS architecture is given in the next 101 section. It provides enough information to understand the basics of 102 the 3GPP2 BCMCS operation. Readers are encouraged to find a more 103 detailed description in [BCMCS]. 105 As described in [BCMCS], the MNs are required to know the IPv4 or the 106 IPv6 address of the BCMCS controller entity so that they can download 107 all the necessary information about a desired broadcast and/or a 108 multicast program. In a roaming environment static configuration of 109 the BCMCS controller's IP address becomes unrealistic. Therefore, 110 DHCP is considered to be a method to dynamically configure the MNs 111 with the IP address or the fully qualified domain name of the BCMCS 112 controller in the 3G cellular telephone networks. 114 In order to allow the MNs to discover the BCMCS controllers, the MNs 115 request the appropriate option codes from the DHCP server using 116 Parameter Request List option. The DHCP servers need to return the 117 corresponding configuration options that carry either BCMCS 118 controller's IP address or fully qualified domain name based on 119 configuration. This document defines the necessary options and 120 option codes. 122 2. Overview of the 3GPP2 BCMCS Network 124 The Broadcast and Multicast Service architecture in a 3G cellular 125 telephone network such as 3GPP2 has the following model: 127 +------------+ +--------+ 128 | BCMCS | | | 129 | Controller | | DHCP | 130 | | | Server | 131 +------------+ +--------+ 132 ^ 133 Control| 134 Info| 135 | 136 | 137 V 138 +----+ +------------+ +------------+ 139 | | | | | | 140 | MN/| bearer | Radio | | BCMCS | 141 |User|<-------| Access |<---| Content | 142 | | | Network | | Server | 143 +----+ +------------+ +------------+ 145 Note that this figure is shown here for a basic understanding of how 146 Broadcast and Multicast service works in a 3G cellular telehone 147 network. The network elements except MN/user and the DHCP server are 148 not relevant to the text in this document. 150 The MN interacts with the BCMCS Controller to request broadcast/ 151 multicast program information from the network (e.g., scheduled time, 152 multicast IP address, port numbers). The MN may also be 153 authenticated by the BCMCS Controller while downloading the relevant 154 program security related information (such as encryption key). These 155 interactions may happen via HTTP and XML as defined in [BCMCS]. 156 There may be more than one BCMCS controller in the network. The MN 157 should discover the appropriate BCMCS controller to request the 158 relevant program information. For details of Broadcast and Multicast 159 Service operation in 3GPP2, see [BCMCS]. 161 3. Terminology 163 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 164 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 165 this document are to be interpreted as described in RFC 2119. 167 4. Broadcast & Multicast Service Controller Options 169 This section defines the configuration option for the BCMCS 170 controller of the broadcast and multicast service. 172 4.1 Broadcast & Multicast Service Controller Domain Name list for 173 DHCPv4 175 The general format of the BCMCS Controller Domain list option for 176 DHCPv4 is as follows: 178 Code Len FQDN(s) of BCMCS Controller 179 +-----+-----+-----+-----+-----+-----+-----+-- 180 | TBD1| n | s1 | s2 | s3 | s4 | s5 | ... 181 +-----+-----+-----+-----+-----+-----+-----+-- 183 The option MAY contain multiple domain names, but these domain names 184 SHOULD be used to construct SRV lookups as specified in [BCMCS], 185 rather than querying for different A records. The client can try any 186 or ALL of the domain names to construct the SRV lookups. The list of 187 domain names MAY conatin the domain name of the access provider and 188 it's partner networks that also offer broadcast and multicast 189 service. 191 If the length of the domain list exceeds the maximum permissible 192 length within a single option (254 octets), then the domain list MUST 193 be represented in the DHCPv4 message as specified in [RFC3396] . An 194 example case when two controller domain names, example.com and 195 example.net are returned will be: 197 +----+----+----+----+----+----+----+----+----+----+----+ 198 |TBD1| 26 | 7 | 'e'| 'x'| 'a'| 'm'| 'p'| 'l'| 'e'| 3 | 199 +----+----+----+----+----+----+----+----+----+----+----+ 200 +----+----+----+----+----+----+----+----+----+----+----+ 201 |'c' |'o'| 'm'| 0 | 7 | 'e'| 'x'| 'a'| 'm'| 'p'| 'l'| 202 +----+----+----+----+----+----+----+----+----+----+----+ 203 +----+----+----+----+----+----+ 204 |'e' | 3 | 'n'| 'e'| 't'| 0 | 205 +----+----+----+----+----+----+ 207 4.2 Broadcast & Multicast Service Controller Domain Name List Option 208 for DHCPv6 210 The semantics and content of the DHCPv6 encoding of this option is 211 exactly the same as the encoding described in the previous section, 212 other than necessary differences between the way options are encoded 213 in DHCPv4 and DHCPv6. 215 Specifically, the DHCPv6 option for the BCMCS Control Server Domain 216 Names has the following format: 218 0 1 2 3 219 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 | OPTION_BCMCS_SERVER_D | option-length | 222 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 223 | BCMCS Control Server Domain Name List | 224 | ... | 225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 227 option-code: OPTION_BCMCS_SERVER_D (TBD2). 229 option-length: Length of the 'BCMCS Control Server Domain Name List' 230 field in octets; variable. 232 BCMCS Control Server Domain Name List: Identical content as in 233 Section 4.1 (except the Code and Len fields). 235 4.3 Broadcast & Multicast Service Controller IPv4 address option for 236 DHCPv4 238 The Length byte (Len) is followed by a list of IPv4 addresses 239 indicating BCMCS controller IPv4 addresses. The BCMCS controllers 240 MUST be listed in order of preference. Its minimum length is 4, and 241 the length MUST be a multiple of 4. The DHCPv4 option for this 242 encoding has the following format: 244 Code Len Address 1 Address 2 245 +-----+-----+-----+-----+-----+-----+-----+-- 246 |TBD3 | n | a1 | a2 | a3 | a4 | a1 | ... 247 +-----+-----+-----+-----+-----+-----+-----+-- 249 4.4 Broadcast & Multicast Service Controller IPv6 Address Option for 250 DHCPv6 252 This DHCPv6 option MUST carry one or more 128-bit IPv6 address(es) of 253 the BCMCS Controller in a operator's network. 255 0 1 2 3 256 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 258 | OPTION_BCMCS_SERVER_A | option-length | 259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 260 | | 261 | BCMCS Control server-1 address (IPv6 address) | 262 | | 263 | | 264 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 265 | | 266 | BCMCS Control server-2 address (IPv6 address) | 267 | | 268 | | 269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 270 | ... | 271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 273 option-code: OPTION_BCMCS_SERVER_A (TBD4). 275 option-length: Length of the 'BCMCS Control Server IPv6 address' 276 field in octets; variable. 278 4.5 Consideration for Client Operation 280 For DHCPv6, a client MAY request either or both of the BCMCS 281 Controller Domain Name List and the IPv6 Address options in the 282 Options Request Option (ORO) as described in [RFC3315]. 284 If a client receives both the BCMCS Controller Domain Name List and 285 IPv6 Address options, it SHOULD use the Domain Name List option. In 286 this case, the client SHOULD NOT use the BCMCS Controller IPv6 287 Address option unless the servers in the BCMCS Controller Domain Name 288 List can not be resolved or reached. 290 4.6 Consideration for Server Operation 292 A server MAY send a client either the BCMCS Controller Domain Name 293 List Option or the BCMCS Controller IPv6 Address/IPv4 Address options 294 if the server is configured to do so. 296 In case of DHCPv6, If a client requests both options and the server 297 is configured with both types of information, the server MAY send the 298 client only one of these options if it is configured to do so. In 299 this case the server SHOULD send the BCMCS Controller Domain Name 300 List option. 302 A server configured with the BCMCS Controller IPv6 Address 303 information MUST send a client the BCMCS Controller IPv6 Address 304 option if that client requested only the BCMCS Controller IPv6 305 address option and not the BCMCS Controller Domain Name List option 306 in the ORO [RFC3315]. 308 If a client requests for the BCMCS Controller IPv6 option and the 309 Server is configured only with the Domain Names, the Server MUST 310 return the Domain Names List and vice versa. 312 The DNS name(s) MUST be concatenated and encoded using the technique 313 described in section 3.3 of "Domain Names - Implementation And 314 Specification" [RFC1035]. DNS name compression MUST NOT be used. 316 The following table summarizes the server's response for DHCPv6: 318 Client sends in ORO Domain Name List IPv6 Address List 319 __________________________________________________________________ 321 Neither option SHOULD MAY 322 Domain Name List MUST MAY 323 IPv6 Address MAY MUST 324 Both options SHOULD MAY 326 5. Security Considerations 328 This document does not introduce any new security concerns beyond 329 those specified in the basic DHCP [RFC2131] and DHCPv6 [RFC3315] 330 specifications. In the absence of message integrity protection for 331 these options, an attacker could modify the option values to 332 frustrate or divert requests for broadcast service. 334 6. IANA Considerations 336 The following option codes for Broadcast & Multicast Service 337 Controller option must be assigned by IANA: 339 1. The BCMCS Controller Domain Name list (section 4.1) has been 340 assigned a value of TBD1 from the DHCPv4 option space. 342 2. The BCMCS Controller Domain Name list (section 4.2) has been 343 assigned a value of TBD2 from the DHCPv6 option space, and a name of 344 OPTION_BCMCS_SERVER_D. 346 3. The BCMCS Controller IPv4 address option (section 4.3) has been 347 assigned a value of TBD3 from the DHCPv4 option space. 349 4. The BCMCS Controller IPv6 address option (section 4.4) has been 350 assigned a value of TBD4 from the DHCPv6 option space, and a name of 351 OPTION_BCMCS_SERVER_A. 353 7. Acknowledgements 355 Thanks to the following indivduals for their review and constructive 356 comments during the development of this document: 358 AC Mahendran, Jun Wang, Raymond Hsu, Jayshree Bharatia, Ralph Droms, 359 Ted Lemon, Margaret Wasserman, Thomas Narten, Elwyn Davies, Pekka 360 Savola, and Bert Wijnen. 362 8. Normative References 364 [BCMCS] 3GPP2, www.3gpp2.org, 365 ftp://ftp.3gpp2.org/TSGX/Projects/X.P0022 2ndV&V.zip, 366 "X.S0022, Broadcast and Multicast Service in cdma2000 367 Wireless IP Network. (pending publication)", 368 December 2004. 370 [RFC1035] Mockapetris, P., "Domain names - implementation and 371 specification", STD 13, RFC 1035, November 1987. 373 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 374 Requirement Levels", BCP 14, RFC 2119, March 1997. 376 [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", 377 RFC 2131, March 1997. 379 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 380 and M. Carney, "Dynamic Host Configuration Protocol for 381 IPv6 (DHCPv6)", RFC 3315, July 2003. 383 [RFC3396] Lemon, T. and S. Cheshire, "Encoding Long Options in the 384 Dynamic Host Configuration Protocol (DHCPv4)", RFC 3396, 385 November 2002. 387 Authors' Addresses 389 Kuntal Chowdhury 390 Starent Networks 391 30 International Place 392 Tewksbury, MA 01876 393 US 395 Phone: +1 214-550-1416 396 Email: kchowdhury@starentnetworks.com 397 Parviz Yegani 398 Cisco Systems 399 3625 Cisco Way 400 San Jose, CA 95134 401 US 403 Phone: +1 408-832-5729 404 Email: pyegani@cisco.com 406 Lila Madour 407 Ericsson 408 8400, Decarie Blvd 409 Town of Mount Royal, Quebec H4P 2N2 410 CANADA 412 Phone: +1 514-345-7900 413 Email: Lila.Madour@ericsson.com 415 Intellectual Property Statement 417 The IETF takes no position regarding the validity or scope of any 418 Intellectual Property Rights or other rights that might be claimed to 419 pertain to the implementation or use of the technology described in 420 this document or the extent to which any license under such rights 421 might or might not be available; nor does it represent that it has 422 made any independent effort to identify any such rights. Information 423 on the procedures with respect to rights in RFC documents can be 424 found in BCP 78 and BCP 79. 426 Copies of IPR disclosures made to the IETF Secretariat and any 427 assurances of licenses to be made available, or the result of an 428 attempt made to obtain a general license or permission for the use of 429 such proprietary rights by implementers or users of this 430 specification can be obtained from the IETF on-line IPR repository at 431 http://www.ietf.org/ipr. 433 The IETF invites any interested party to bring to its attention any 434 copyrights, patents or patent applications, or other proprietary 435 rights that may cover technology that may be required to implement 436 this standard. Please address the information to the IETF at 437 ietf-ipr@ietf.org. 439 Disclaimer of Validity 441 This document and the information contained herein are provided on an 442 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 443 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 444 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 445 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 446 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 447 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 449 Copyright Statement 451 Copyright (C) The Internet Society (2005). This document is subject 452 to the rights, licenses and restrictions contained in BCP 78, and 453 except as set forth therein, the authors retain all their rights. 455 Acknowledgment 457 Funding for the RFC Editor function is currently provided by the 458 Internet Society.