idnits 2.17.1 draft-ietf-dhc-bcmc-options-05.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 468. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 445. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 452. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 458. ** 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 (September 29, 2005) is 6784 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 390, 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: April 2, 2006 P. Yegani 5 Cisco Systems 6 L. Madour 7 Ericsson 8 September 29, 2005 10 DHCP Options for Broadcast and Multicast Control Servers 11 draft-ietf-dhc-bcmc-options-05.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 April 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 access 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 . . . . . . . . . . . . 9 68 4.6 Consideration for Server Operation . . . . . . . . . . . . 9 69 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 70 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 71 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 72 8. Normative References . . . . . . . . . . . . . . . . . . . . . 13 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13 74 Intellectual Property and Copyright Statements . . . . . . . . 15 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. The DHCP 116 servers need to return the corresponding configuration options that 117 carry either BCMCS controller's IP address or fully qualified domain 118 name based on configuration. This document defines the necessary 119 options and option codes. 121 2. Overview of the 3GPP2 BCMCS Network 123 The Broadcast and Multicast Service architecture in a 3G cellular 124 telephone network such as 3GPP2 has the following model: 126 +------------+ +--------+ 127 | BCMCS | | | 128 | Controller | | DHCP | 129 | | | Server | 130 +------------+ +--------+ 131 ^ 132 Control| 133 Info| 134 | 135 | 136 V 137 +----+ +------------+ +------------+ 138 | | | | | | 139 | MN/| bearer | Radio | | BCMCS | 140 |User|<-------| Access |<---| Content | 141 | | | Network | | Server | 142 +----+ +------------+ +------------+ 144 Note that this figure is shown here for a basic understanding of how 145 Broadcast and Multicast service works in a 3G cellular telephone 146 network. The network elements except MN/user and the DHCP server are 147 not relevant to the text in this document. 149 The MN interacts with the BCMCS Controller to request broadcast/ 150 multicast program information from the network (e.g., scheduled time, 151 multicast IP address, port numbers). The MN may also be 152 authenticated by the BCMCS Controller while downloading the relevant 153 program security related information (such as encryption key). These 154 interactions may happen via HTTP and XML as defined in [BCMCS]. 155 There may be more than one BCMCS controller in the network. The MN 156 should discover the appropriate BCMCS controller to request the 157 relevant program information. For details of Broadcast and Multicast 158 Service operation in 3GPP2, see [BCMCS]. 160 3. Terminology 162 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 163 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 164 this document are to be interpreted as described in RFC 2119. 166 4. Broadcast & Multicast Service Controller Options 168 This section defines the configuration option for the BCMCS 169 controller of the broadcast and multicast service. 171 4.1 Broadcast & Multicast Service Controller Domain Name list for 172 DHCPv4 174 The general format of the BCMCS Controller Domain list option for 175 DHCPv4 is as follows: 177 Code Len FQDN(s) of BCMCS Controller 178 +-----+-----+-----+-----+-----+-----+-----+-- 179 | TBD1| n | s1 | s2 | s3 | s4 | s5 | ... 180 +-----+-----+-----+-----+-----+-----+-----+-- 182 The option MAY contain multiple domain names, but these domain names 183 SHOULD be used to construct SRV lookups as specified in [BCMCS], 184 rather than querying for different A records. The client can try any 185 or ALL of the domain names to construct the SRV lookups. The list of 186 domain names MAY contain the domain name of the access provider and 187 its partner networks that also offer broadcast and multicast service. 189 As an example, the access provider may have one or more partners or 190 resellers often termed as MVNO (Mobile Virtual Network Operators) for 191 broadcast and multicast service. In this case, the access provider 192 should be able to use the same DHCP option to send multiple of those 193 domain names (MVNOs). To illustrate this further, let's assume that 194 the access provider (operator) has reseller agreement with two MVNOs: 195 mvno1 and mvno2. Therefore, the Broadcast & Multicast Service 196 Controller Domain Name list for DHCPv4 option will contain three 197 domain names: operator.com, mvno1.com, mvno2.com. Upon receiving 198 this option, the BCMCS client may choose to use one of the domain 199 names to fetch the appropriate BCMCS controller address (based on 200 user's preference or configuration). If no preferred domain name is 201 found in the received list, the client should use a default setting 202 e.g. use the first one in the list. 204 If the length of the domain list exceeds the maximum permissible 205 length within a single option (254 octets), then the domain list MUST 206 be represented in the DHCPv4 message as specified in [RFC3396] . An 207 example case when two controller domain names, example.com and 208 example.net are returned will be: 210 +----+----+----+----+----+----+----+----+----+----+----+ 211 |TBD1| 26 | 7 | 'e'| 'x'| 'a'| 'm'| 'p'| 'l'| 'e'| 3 | 212 +----+----+----+----+----+----+----+----+----+----+----+ 213 +----+----+----+----+----+----+----+----+----+----+----+ 214 |'c' |'o' | 'm'| 0 | 7 | 'e'| 'x'| 'a'| 'm'| 'p'| 'l'| 215 +----+----+----+----+----+----+----+----+----+----+----+ 216 +----+----+----+----+----+----+ 217 |'e' | 3 | 'n'| 'e'| 't'| 0 | 218 +----+----+----+----+----+----+ 220 4.2 Broadcast & Multicast Service Controller Domain Name List Option 221 for DHCPv6 223 The semantics and content of the DHCPv6 encoding of this option is 224 exactly the same as the encoding described in the previous section, 225 other than necessary differences between the way options are encoded 226 in DHCPv4 and DHCPv6. 228 Specifically, the DHCPv6 option for the BCMCS Control Server Domain 229 Names has the following format: 231 0 1 2 3 232 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 233 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 234 | OPTION_BCMCS_SERVER_D | option-length | 235 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 236 | BCMCS Control Server Domain Name List | 237 | ... | 238 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 240 option-code: OPTION_BCMCS_SERVER_D (TBD2). 242 option-length: Length of the 'BCMCS Control Server Domain Name List' 243 field in octets; variable. 245 BCMCS Control Server Domain Name List: Identical format as in Section 246 4.1 (except the Code and Len fields). 248 4.3 Broadcast & Multicast Service Controller IPv4 address option for 249 DHCPv4 251 The Length byte (Len) is followed by a list of IPv4 addresses 252 indicating BCMCS controller IPv4 addresses. The BCMCS controllers 253 MUST be listed in order of preference. Its minimum length is 4, and 254 the length MUST be a multiple of 4. The DHCPv4 option for this 255 encoding has the following format: 257 Code Len Address 1 Address 2 258 +-----+-----+-----+-----+-----+-----+-----+-- 259 |TBD3 | n | a1 | a2 | a3 | a4 | a1 | ... 260 +-----+-----+-----+-----+-----+-----+-----+-- 262 4.4 Broadcast & Multicast Service Controller IPv6 Address Option for 263 DHCPv6 265 This DHCPv6 option MUST carry one or more 128-bit IPv6 address(es) of 266 the BCMCS Controller in a operator's network. 268 0 1 2 3 269 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 270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 | OPTION_BCMCS_SERVER_A | option-length | 272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 273 | | 274 | BCMCS Control server-1 address (IPv6 address) | 275 | | 276 | | 277 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 278 | | 279 | BCMCS Control server-2 address (IPv6 address) | 280 | | 281 | | 282 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 283 | ... | 284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 286 option-code: OPTION_BCMCS_SERVER_A (TBD4). 288 option-length: Length of the 'BCMCS Control Server IPv6 address' 289 field in octets; variable. 291 4.5 Consideration for Client Operation 293 For DHCPv4, the client MAY request either or both of the BCMCS 294 Controller Domain Name List and the IPv4 Address options in the 295 Parameter Request List option (code 55) as defined in [RFC2132]. 297 For DHCPv6, the client MAY request either or both of the BCMCS 298 Controller Domain Name List and the IPv6 Address options in the 299 Options Request Option (ORO) as described in [RFC3315]. 301 If the client receives both the BCMCS Controller Domain Name List and 302 IPv6 or IPv4 Address options, it SHOULD use the Domain Name List 303 option. In this case, the client SHOULD NOT use the BCMCS Controller 304 IPv6 or IPv4 Address option unless the server(s) in the BCMCS 305 Controller Domain Name List can not be resolved or reached. 307 4.6 Consideration for Server Operation 309 A server MAY send a client either the BCMCS Controller Domain Name 310 List Option or the BCMCS Controller IPv6 Address/IPv4 Address options 311 if the server is configured to do so. 313 If a client requests both the options and the server is configured 314 with both types of information, the server MAY send the client only 315 one of the options if it is configured to do so. In this case the 316 server SHOULD send the BCMCS Controller Domain Name List option. 318 A server configured with the BCMCS Controller IPv6 or IPv4 Address 319 information MUST send a client the BCMCS Controller IPv6 or IPv4 320 Address option if that client requested only the BCMCS Controller 321 IPv6 or IPv4 address option and not the BCMCS Controller Domain Name 322 List option in the ORO or Parameter Request List option. 324 If a client requests for the BCMCS Controller IPv6 or IPv4 Address 325 option and the Server is configured only with the domain name(s), the 326 Server MUST return the Domain Name List and vice versa. 328 The domain names MUST be concatenated and encoded using the technique 329 described in section 3.3 of "Domain Names - Implementation And 330 Specification" [RFC1035]. DNS name compression MUST NOT be used. 332 The following table summarizes the server's response: 334 Client sends in ORO/ 335 Parameter Request List Domain Name List IPv6/IPv4 Address 336 __________________________________________________________________ 338 Neither option SHOULD MAY 339 Domain Name List MUST MAY 340 IPv6/IPv4 Address MAY MUST 341 Both options SHOULD MAY 343 5. Security Considerations 345 This document does not introduce any new security concerns beyond 346 those specified in the basic DHCP [RFC2131] and DHCPv6 [RFC3315] 347 specifications. In the absence of message integrity protection for 348 these options, an attacker could modify the option values to divert 349 requests for broadcast service. 351 6. IANA Considerations 353 The following option codes for Broadcast & Multicast Service 354 Controller option must be assigned by IANA: 356 1. The BCMCS Controller Domain Name list (section 4.1) has been 357 assigned a value of TBD1 from the DHCPv4 option space. 359 2. The BCMCS Controller Domain Name list (section 4.2) has been 360 assigned a value of TBD2 from the DHCPv6 option space, and a name of 361 OPTION_BCMCS_SERVER_D. 363 3. The BCMCS Controller IPv4 address option (section 4.3) has been 364 assigned a value of TBD3 from the DHCPv4 option space. 366 4. The BCMCS Controller IPv6 address option (section 4.4) has been 367 assigned a value of TBD4 from the DHCPv6 option space, and a name of 368 OPTION_BCMCS_SERVER_A. 370 7. Acknowledgements 372 Thanks to the following individuals for their review and constructive 373 comments during the development of this document: 375 AC Mahendran, Jun Wang, Raymond Hsu, Jayshree Bharatia, Ralph Droms, 376 Ted Lemon, Margaret Wasserman, Thomas Narten, Elwyn Davies, Pekka 377 Savola, Bert Wijnen, David Kessens, Brian E Carpenter, and Stig 378 Venaas. 380 8. Normative References 382 [BCMCS] 3GPP2, www.3gpp2.org, 383 http://www.3gpp2.org/Public_html/specs/tsgx.cfm, "X.S0022, 384 Broadcast and Multicast Service in cdma2000 Wireless IP 385 Network.", December 2005. 387 [RFC1035] Mockapetris, P., "Domain names - implementation and 388 specification", STD 13, RFC 1035, November 1987. 390 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 391 Requirement Levels", BCP 14, RFC 2119, March 1997. 393 [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", 394 RFC 2131, March 1997. 396 [RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor 397 Extensions", RFC 2132, March 1997. 399 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 400 and M. Carney, "Dynamic Host Configuration Protocol for 401 IPv6 (DHCPv6)", RFC 3315, July 2003. 403 [RFC3396] Lemon, T. and S. Cheshire, "Encoding Long Options in the 404 Dynamic Host Configuration Protocol (DHCPv4)", RFC 3396, 405 November 2002. 407 Authors' Addresses 409 Kuntal Chowdhury 410 Starent Networks 411 30 International Place 412 Tewksbury, MA 01876 413 US 415 Phone: +1 214-550-1416 416 Email: kchowdhury@starentnetworks.com 418 Parviz Yegani 419 Cisco Systems 420 3625 Cisco Way 421 San Jose, CA 95134 422 US 424 Phone: +1 408-832-5729 425 Email: pyegani@cisco.com 427 Lila Madour 428 Ericsson 429 8400, Decarie Blvd 430 Town of Mount Royal, Quebec H4P 2N2 431 CANADA 433 Phone: +1 514-345-7900 434 Email: Lila.Madour@ericsson.com 436 Intellectual Property Statement 438 The IETF takes no position regarding the validity or scope of any 439 Intellectual Property Rights or other rights that might be claimed to 440 pertain to the implementation or use of the technology described in 441 this document or the extent to which any license under such rights 442 might or might not be available; nor does it represent that it has 443 made any independent effort to identify any such rights. Information 444 on the procedures with respect to rights in RFC documents can be 445 found in BCP 78 and BCP 79. 447 Copies of IPR disclosures made to the IETF Secretariat and any 448 assurances of licenses to be made available, or the result of an 449 attempt made to obtain a general license or permission for the use of 450 such proprietary rights by implementers or users of this 451 specification can be obtained from the IETF on-line IPR repository at 452 http://www.ietf.org/ipr. 454 The IETF invites any interested party to bring to its attention any 455 copyrights, patents or patent applications, or other proprietary 456 rights that may cover technology that may be required to implement 457 this standard. Please address the information to the IETF at 458 ietf-ipr@ietf.org. 460 Disclaimer of Validity 462 This document and the information contained herein are provided on an 463 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 464 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 465 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 466 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 467 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 468 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 470 Copyright Statement 472 Copyright (C) The Internet Society (2005). This document is subject 473 to the rights, licenses and restrictions contained in BCP 78, and 474 except as set forth therein, the authors retain all their rights. 476 Acknowledgment 478 Funding for the RFC Editor function is currently provided by the 479 Internet Society.