idnits 2.17.1 draft-chowdhury-dhc-bcmcv6-option-01.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 3667, Section 5.1 on line 17. -- Found old boilerplate from RFC 3978, Section 5.5 on line 357. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 334. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 341. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 347. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 363), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 39. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. 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 : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 155: '... The option MAY contain multiple dom...' RFC 2119 keyword, line 156: '... SHOULD be used to construct SRV lookups as specified in [BCMCS],...' RFC 2119 keyword, line 157: '...ferent A records. The client MUST try...' RFC 2119 keyword, line 186: '...This DHCP option SHALL carry one or mo...' RFC 2119 keyword, line 214: '... A client MAY request either or both...' (11 more instances...) 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 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 17, 2004) is 7192 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) -- Looks like a reference, but probably isn't: '5' on line 153 == Unused Reference: 'RFC1035' is defined on line 286, 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: 8 errors (**), 0 flaws (~~), 3 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group K. Chowdhury 2 Internet-Draft Nortel Networks 3 Expires: February 15, 2005 P. Yegani 4 Cisco Systems 5 L. Madour 6 Ericsson 7 August 17, 2004 9 DHCPv6 Options for Broadcast and Multicast Control Servers 10 draft-chowdhury-dhc-bcmcv6-option-01.txt 12 Status of this Memo 14 By submitting this Internet-Draft, I certify that any applicable 15 patent or other IPR claims of which I am aware have been disclosed, 16 and any of which I become aware will be disclosed, in accordance with 17 RFC 3668. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as 22 Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt. 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 This Internet-Draft will expire on February 15, 2005. 37 Copyright Notice 39 Copyright (C) The Internet Society (2004). All Rights Reserved. 41 Abstract 43 This document defines new options for Broadcast and Multicast Service 44 controller discovery in an IP network. Broadcast and Multicast 45 service over 3G wireless networks are being developed at the time of 46 writing this document. Users of this service interact with a 47 controller in the network to derive informations that are required to 48 receive broadcast service. Dynamic Host Configuration Protocol can 49 be used to configure the controller IPv6 addresses in the user's 50 devices. This document defines the related options and option codes. 52 Table of Contents 54 1. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 57 4. Broadcast Service Controller Options . . . . . . . . . . . . . 6 58 4.1 Broadcast Service Controller Domain Name List option . . . 6 59 4.2 Broadcast Service Controller IPv6 address option . . . . . 6 60 5. Consideration for Client Operation . . . . . . . . . . . . . . 8 61 6. Consideration for Server Operation . . . . . . . . . . . . . . 9 62 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 63 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 64 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 65 10. Normative References . . . . . . . . . . . . . . . . . . . . 12 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 12 67 Intellectual Property and Copyright Statements . . . . . . . . 14 69 1. Motivation 71 Dynamic Host Configuration Protocol can be used to configure various 72 non-IP address type of parameters. These parameters are required for 73 normal operation of various services that are offered over an IP 74 network. 76 In 3G wirelesss network standards body such as 3GPP2 (www.3gpp2.org), 77 broadcast and multicast service is being developed [BCMCS]. The 78 service includes a controller component that is responsible for 79 managing the service via interaction with the users and other network 80 entities. The users of the service are required to know the IPv6 81 address of the controller entity so that they can download all the 82 necessary information about a desired broadcast program. In a 83 roaming environment static configuration of the controller IPv6 84 address becomes unrealistic. Therefore, DHCP [RFC3315] is considered 85 to be a method to dynamically configure controller IPv6 address in 86 the user's devices in the 3G wireless networks. DHCP can also be 87 used to convey the fully qualified domain name of the broadcast 88 service controller to the user. The user in turn makes DNS queries 89 to obtain the IPv6 address of the associated broadcast service 90 controller. 92 In order to allow the users to discover the broadcast controllers, 93 the clients need to request for appropriate option codes from the DHC 94 servers using Option-Request-Option and the DHC servers need to 95 return corresponding configuration options that carry the broadcast 96 and multicast service controller IPv6 address or Domain Name list. 97 The motivation for this document is to define the necessary options 98 and option codes. 100 2. Overview 102 The Broadcast and Multicast Service architecture in a 3G wireless 103 network such as 3GPP2 has the following model: 105 +------------+ +--------+ 106 | | | | 107 | Controller | | DHCP | 108 | | | Server | 109 +------------+ +--------+ 110 | 111 Control| 112 Info| 113 | 114 | 115 V 116 +----+ +------------+ +------------+ 117 | | | | | | 118 | MN/| bearer | Radio | | Broadcast | 119 |User|<-------| Access |<---| Content | 120 | | | Network | | Server | 121 +----+ +------------+ +------------+ 123 Note that this inforamtive figure is shown here for broad 124 understanding of how Broadcast and Multicast service works in a 3G 125 radio network. The network elements except MN/user and the DHCP 126 server are not relevant to the text in this document. 128 The user interacts with the Controller to request for broadcast/ 129 multicast program information from the network (e.g., scheduled time, 130 multicast IP address, port numbers). The User may also be 131 authenticated by the Controller while downloading the relevant 132 program security related information (such as encryption key). These 133 interactions happen via HTTP and XML. For details of Broadcast and 134 Multicast Service operation in 3GPP2, see [BCMCS]. There may be more 135 than one controller in the network. The user should discover the 136 appropriate controller to request the relevant program information. 138 3. Terminology 140 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 141 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 142 this document are to be interpreted as described in RFC 2119. 144 4. Broadcast Service Controller Options 146 This section defines the configuration options for the controller of 147 Broadcast Service. The options in the document are specified similar 148 to [RFC3319]. 150 4.1 Broadcast Service Controller Domain Name List option 152 The option length is followed by a sequence of labels, encoded 153 according to Section 3.1 of RFC 1035 [5]. 155 The option MAY contain multiple domain names, but these domain names 156 SHOULD be used to construct SRV lookups as specified in [BCMCS], 157 rather than querying for different A records. The client MUST try 158 the records in the order listed, applying the mechanism described in 159 [BCMCS] for each entry. The client only resolves the subsequent 160 domain names if attempts to contact the first one failed or yielded 161 no common transport protocols between the client and the controller 162 or denote a domain administratively prohibited by client's policy. 163 Use of multiple domain names is not meant to replace the SRV records, 164 but rather to allow a single DHCP server to indicate the broadcast 165 controllers in the access provider's network. 167 The DHCPv6 option for Boradcast Service Controller Domain Names has 168 the format shown below. 170 option-code: OPTION_BCMCS_SERVER_D (TBD) 172 option-length: Length of the 'Broadcast Control Server Domain Name 173 List' field in octets; variable. 175 0 1 2 3 176 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 177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 178 | OPTION_BCMCS_SERVER_D | option-length | 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | Broadcast Control Domain Name List | 181 | ... | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 184 4.2 Broadcast Service Controller IPv6 address option 186 This DHCP option SHALL carry one or more 128-bit IPv6 address(es) of 187 the Broadcast Service Controller in a operators network. 189 option-code: OPTION_BCMCS_SERVER_A (TBD) 191 option-length: Length of the 'Broadcast Control Server IPv6 address' 192 field in octets; variable. 194 0 1 2 3 195 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 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | OPTION_BCMCS_SERVER_A | option-length | 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 | | 200 | Broadcast Control server-1 address (IPv6 address) | 201 | | 202 | | 203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 204 | | 205 | Broadcast Control server-2 address (IPv6 address) | 206 | | 207 | | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 | ... | 210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 212 5. Consideration for Client Operation 214 A client MAY request either or both of the Broadcast Service 215 Controller Domain Name List and the IPv6 Address options in the 216 Options Request Option (ORO) as described in [RFC3315]. 218 If a client receives both the Broadcast Service Controller Domain 219 Name List and IPv6 Address options, it SHOULD use the Domain Name 220 List option. In this case, the client MAY use the Broadcast Service 221 Controller IPv6 Address option only if, no server in the Broadcast 222 Service Controller Domain Name List can be resolved or reached. 224 6. Consideration for Server Operation 226 A server MAY send a client one or both of the Broadcast Service 227 Controller Domain Name List and Broadcast Service Controller IPv6 228 Address options if the server is configured to do so. 230 If a client requests both options and the server is configured with 231 both types of information, the server MAY send the client only one of 232 these options if it is configured to do so. In this case the server 233 SHOULD send the Broadcast Service Controller Domain Name List option. 235 A server configured with the Broadcast Service Controller IPv6 236 Address information MUST send a client the Broadcast Service 237 Controller IPv6 Address option if that client requested only the 238 Broadcast Service Controller IPv6 address option and not the 239 Broadcast Service Controller Domain Name List option in the ORO 240 (RFC3315]). 242 If a client requests for the Broadcast Service Controller IPv6 option 243 and the Server is configured only with the Domain Names, the Server 244 MUST return the Domain Names List and vice versa. 246 The following table summarizes the server's response: 248 Client sends in ORO Domain Name List IPv6 Address List 249 __________________________________________________________________ 251 Neither option SHOULD MAY 252 Domain Name List MUST MAY 253 IPv6 Address MAY MUST 254 Both options SHOULD MAY 256 7. Security Considerations 258 The security considerations in the base DHCPv6 spec [RFC3315] 259 applies. An attacker may change information of the Broadcast Service 260 Controller in packets that are in-tranist from DHCP server to the MN, 261 if integrity protection is not in place. In that event, the user of 262 the Broadcast service may be diverted to a rogue broadcast service 263 controller. In the absence of a mutual authentication procedure 264 between MN and the Broadcast controller, the MN may receive wrong or 265 fraudulent information about Broadcast Service. 267 8. IANA Considerations 269 The option codes OPTION_BCMCS_SERVER_A, OPTION_BCMCS_SERVER_D for 270 Broadcast Service Controller Domain Name list and IPv6 address 271 respectively Must be assigned by IANA. 273 9. Acknowledgements 275 Thanks to the follwoing indivduals for their review and constructive 276 comments during the development of this document: 278 AC Mahendran, Jun Wang, Raymond Hsu, Jayshree Bharatia, Ralph Dorms, 279 Bernie Volz. 281 10 Normative References 283 [BCMCS] 3GPP2, www.3gpp2.org, "X.P0022, Broadcast and Multicast 284 Service in cdma2000 Wireless IP Network.", October 2003. 286 [RFC1035] Mockapetris, P., "Domain names - implementation and 287 specification", STD 13, RFC 1035, November 1987. 289 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C. and 290 M. Carney, "Dynamic Host Configuration Protocol for IPv6 291 (DHCPv6)", RFC 3315, July 2003. 293 [RFC3319] Schulzrinne, H. and B. Volz, "Dynamic Host Configuration 294 Protocol (DHCPv6) Options for Session Initiation Protocol 295 (SIP) Servers", RFC 3319, July 2003. 297 Authors' Addresses 299 Kuntal Chowdhury 300 Nortel Networks 301 2221 Lakeside Blvd. 302 Richardson, TX 75082 303 US 305 Phone: +1 972-685-7788 306 EMail: chowdury@nortelnetworks.com 308 Parviz Yegani 309 Cisco Systems 310 3625 Cisco Way 311 San Jose, CA 95134 312 US 314 Phone: +1 408-832-5729 315 EMail: pyegani@cisco.com 316 Lila Madour 317 Ericsson 318 8400, Decarie Blvd 319 Town of Mount Royal, Quebec H4P 2N2 320 CANADA 322 Phone: +1 514-345-7900 323 EMail: Lila.Madour@ericsson.com 325 Intellectual Property Statement 327 The IETF takes no position regarding the validity or scope of any 328 Intellectual Property Rights or other rights that might be claimed to 329 pertain to the implementation or use of the technology described in 330 this document or the extent to which any license under such rights 331 might or might not be available; nor does it represent that it has 332 made any independent effort to identify any such rights. Information 333 on the procedures with respect to rights in RFC documents can be 334 found in BCP 78 and BCP 79. 336 Copies of IPR disclosures made to the IETF Secretariat and any 337 assurances of licenses to be made available, or the result of an 338 attempt made to obtain a general license or permission for the use of 339 such proprietary rights by implementers or users of this 340 specification can be obtained from the IETF on-line IPR repository at 341 http://www.ietf.org/ipr. 343 The IETF invites any interested party to bring to its attention any 344 copyrights, patents or patent applications, or other proprietary 345 rights that may cover technology that may be required to implement 346 this standard. Please address the information to the IETF at 347 ietf-ipr@ietf.org. 349 Disclaimer of Validity 351 This document and the information contained herein are provided on an 352 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 353 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 354 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 355 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 356 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 357 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 359 Copyright Statement 361 Copyright (C) The Internet Society (2004). This document is subject 362 to the rights, licenses and restrictions contained in BCP 78, and 363 except as set forth therein, the authors retain all their rights. 365 Acknowledgment 367 Funding for the RFC Editor function is currently provided by the 368 Internet Society.