Network Working Group K. Chowdhury
Request for Comments: 4280 Starent Networks
Category: Standards Track P. Yegani
Cisco Systems
L. Madour
Ericsson
November 2005
Network Working Group K. Chowdhury
Request for Comments: 4280 Starent Networks
Category: Standards Track P. Yegani
Cisco Systems
L. Madour
Ericsson
November 2005
Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control Servers
广播和多播控制服务器的动态主机配置协议（DHCP）选项
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
Abstract
摘要
This document defines new options to discover the Broadcast and Multicast Service (BCMCS) controller in an IP network. BCMCS is being developed for Third generation (3G) cellular telephone networks. Users of the service interact with a controller in the network via the Mobile Node (MN) to derive information required to receive Broadcast and Multicast Service. Dynamic Host Configuration Protocol can be used to configure the MN to access a particular controller. This document defines the related options and option codes.
本文档定义了在IP网络中发现广播和多播服务（BCMCS）控制器的新选项。BCMCS正在为第三代（3G）蜂窝电话网络开发。服务的用户经由移动节点（MN）与网络中的控制器交互以导出接收广播和多播服务所需的信息。动态主机配置协议可用于配置MN以访问特定控制器。本文件定义了相关选项和选项代码。
Table of Contents
目录
1. Motivation ......................................................2
2. Overview of the 3GPP2 BCMCS Network .............................3
3. Terminology .....................................................4
4. Broadcast and Multicast Service Controller Options ..............4
4.1. Broadcast and Multicast Service Controller Domain
Name List for DHCPv4 .......................................4
4.2. Broadcast and Multicast Service Controller Domain
Name List Option for DHCPv6 ................................5
4.3. Broadcast and Multicast Service Controller IPv4
Address Option for DHCPv4 ..................................6
4.4. Broadcast and Multicast Service Controller IPv6
Address Option for DHCPv6 ..................................6
4.5. Consideration for Client Operation .........................7
4.6. Consideration for Server Operation .........................7
5. Security Considerations .........................................8
6. IANA Considerations .............................................8
7. Acknowledgements ................................................8
8. Normative References ............................................9
1. Motivation ......................................................2
2. Overview of the 3GPP2 BCMCS Network .............................3
3. Terminology .....................................................4
4. Broadcast and Multicast Service Controller Options ..............4
4.1. Broadcast and Multicast Service Controller Domain
Name List for DHCPv4 .......................................4
4.2. Broadcast and Multicast Service Controller Domain
Name List Option for DHCPv6 ................................5
4.3. Broadcast and Multicast Service Controller IPv4
Address Option for DHCPv4 ..................................6
4.4. Broadcast and Multicast Service Controller IPv6
Address Option for DHCPv6 ..................................6
4.5. Consideration for Client Operation .........................7
4.6. Consideration for Server Operation .........................7
5. Security Considerations .........................................8
6. IANA Considerations .............................................8
7. Acknowledgements ................................................8
8. Normative References ............................................9
Dynamic Host Configuration Protocol [RFC2131] and [RFC3315] can be used to configure various non-IP address type of parameters. These parameters are required for normal operation of various services that are offered over an IP network.
动态主机配置协议[RFC2131]和[RFC3315]可用于配置各种非IP地址类型的参数。这些参数是通过IP网络提供的各种服务正常运行所必需的。
Broadcast and Multicast Service (BCMCS) is one such service that is being standardized in various mobile wireless standard bodies such as Third Generation Partnership Project 2 (3GPP2), Open Mobile Alliance (OMA), and 3GPP. A description of the BCMCS as defined in 3GPP2 can be found in [BCMCS].
广播和多播服务（BCMCS）是在各种移动无线标准机构（如第三代合作伙伴关系项目2（3GPP2）、开放移动联盟（OMA）和3GPP）中被标准化的服务之一。3GPP2中定义的BCMCS的描述可在[BCMCS]中找到。
While DHCP already defines many options for device configuration, no option exists for configuring a mobile device to use BCMCS. This memo defines extensions for both DHCPv4 and DHCPv6 so that DHCP can be used to provide necessary configuration information to a mobile device about the BCMCS controllers.
虽然DHCP已经为设备配置定义了许多选项，但不存在将移动设备配置为使用BCMCS的选项。此备忘录定义了DHCPv4和DHCPv6的扩展，以便可以使用DHCP向移动设备提供有关BCMCS控制器的必要配置信息。
DHCP is being used in 3GPP2, to assist Mobile Nodes (MNs) with the discovery of the BCMCS Controller in a mobile operator's IP network. The BCMCS includes a controller component that is responsible for managing the service via interaction with the MN and other network entities. In this document, we will call this a BCMCS controller.
DHCP正在3GPP2中使用，以协助移动节点（MN）在移动运营商的IP网络中发现BCMCS控制器。BCMCS包括一个控制器组件，负责通过与MN和其他网络实体的交互来管理服务。在本文档中，我们将其称为BCMCS控制器。
An overview of the 3GPP2 BCMCS architecture is given in the next section. It provides enough information to understand the basics of the 3GPP2 BCMCS operation. Readers are encouraged to find a more detailed description in [BCMCS].
下一节将概述3GPP2 BCMCS体系结构。它提供了足够的信息来理解3GPP2 BCMCS操作的基础知识。鼓励读者在[BCMCS]中找到更详细的描述。
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 all the necessary information about a desired broadcast and/or a multicast program. In a roaming environment, static configuration of the BCMCS controller's IP address becomes unrealistic. Therefore, DHCP is considered to be a method to dynamically configure the MNs with the IP address or the fully qualified domain name (FQDN) of the BCMCS controller in the 3G cellular telephone networks.
如[BCMCS]中所述，MN需要知道BCMCS控制器实体的IPv4或IPv6地址，以便能够下载有关所需广播和/或多播节目的所有必要信息。在漫游环境中，BCMCS控制器IP地址的静态配置变得不现实。因此，DHCP被认为是在3G蜂窝电话网络中使用BCMCS控制器的IP地址或完全限定域名（FQDN）动态配置MNs的方法。
In order to allow the MNs to discover the BCMCS controllers, the MNs request the appropriate option codes from the DHCP server. The DHCP servers need to return the corresponding configuration options that carry either BCMCS controller's IP address or FQDN based on configuration. This document defines the necessary options and option codes.
为了允许MNs发现BCMCS控制器，MNs从DHCP服务器请求适当的选项代码。DHCP服务器需要返回相应的配置选项，这些选项根据配置携带BCMCS控制器的IP地址或FQDN。本文件定义了必要的选项和选项代码。
The Broadcast and Multicast Service architecture in a 3G cellular telephone network such as 3GPP2 has the following model:
3G蜂窝电话网络（例如3GPP2）中的广播和多播服务架构具有以下模型：
+------------+ +--------+
| BCMCS | | |
| Controller | | DHCP |
| | | Server |
+------------+ +--------+
^
Control|
Info|
|
|
V
+----+ +------------+ +------------+
| | | | | |
| MN/| bearer | Radio | | BCMCS |
|User|<-------| Access |<---| Content |
| | | Network | | Server |
+----+ +------------+ +------------+
+------------+ +--------+
| BCMCS | | |
| Controller | | DHCP |
| | | Server |
+------------+ +--------+
^
Control|
Info|
|
|
V
+----+ +------------+ +------------+
| | | | | |
| MN/| bearer | Radio | | BCMCS |
|User|<-------| Access |<---| Content |
| | | Network | | Server |
+----+ +------------+ +------------+
Note that this figure is shown here for a basic understanding of how Broadcast and Multicast Service works in a 3G cellular telephone network. The network elements except MN/user and the DHCP server are not relevant to the text in this document.
请注意，此处显示此图是为了基本了解广播和多播服务在3G蜂窝电话网络中的工作方式。除MN/user和DHCP服务器之外的网络元素与本文档中的文本无关。
The MN interacts with the BCMCS Controller to request broadcast/ multicast program information from the network (e.g., scheduled time, multicast IP address, port numbers). The MN may also be authenticated by the BCMCS Controller while downloading the relevant program-security-related information (such as encryption key). These interactions may happen via HTTP and XML as defined in [BCMCS]. There may be more than one BCMCS controller in the network. The MN should discover the appropriate BCMCS controller to request the relevant program information. For details of Broadcast and Multicast Service operation in 3GPP2, see [BCMCS].
MN与BCMCS控制器交互以从网络请求广播/多播节目信息（例如，预定时间、多播IP地址、端口号）。在下载相关的程序安全相关信息（例如加密密钥）时，MN还可以由BCMCS控制器进行认证。这些交互可能通过[BCMCS]中定义的HTTP和XML进行。网络中可能有多个BCMCS控制器。MN应发现适当的BCMCS控制器，以请求相关的程序信息。有关3GPP2中广播和多播服务操作的详细信息，请参阅[BCMCS]。
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不得”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
This section defines the configuration option for the BCMCS controller of the Broadcast and Multicast Service.
本节定义了广播和多播服务的BCMCS控制器的配置选项。
4.1. Broadcast and Multicast Service Controller Domain Name List for DHCPv4
4.1. DHCPv4的广播和多播服务控制器域名列表
The general format of the BCMCS Controller Domain list option for DHCPv4 is as follows:
DHCPv4的BCMCS控制器域列表选项的一般格式如下：
Code Len FQDN(s) of BCMCS Controller
+-----+-----+-----+-----+-----+-----+-----+--
| 88 | n | s1 | s2 | s3 | s4 | s5 | ...
+-----+-----+-----+-----+-----+-----+-----+--
Code Len FQDN(s) of BCMCS Controller
+-----+-----+-----+-----+-----+-----+-----+--
| 88 | n | s1 | s2 | s3 | s4 | s5 | ...
+-----+-----+-----+-----+-----+-----+-----+--
The option MAY contain multiple domain names, but these domain names SHOULD be used to construct Service Record (SRV) lookups as specified in [BCMCS], 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 domain names MAY contain the domain name of the access provider and its partner networks that also offer Broadcast and Multicast Service.
该选项可能包含多个域名，但这些域名应用于构造[BCMCS]中指定的服务记录（SRV）查找，而不是查询不同的A记录。客户端可以尝试任何或所有域名来构建SRV查找。域名列表可能包含接入提供商及其也提供广播和多播服务的伙伴网络的域名。
As an example, the access provider may have one or more partners or resellers often termed as MVNOs (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 a reseller agreement with two MVNOs: mvno1 and mvno2. Therefore, the Broadcast and
例如，接入提供商可以具有一个或多个通常被称为MVNOs（移动虚拟网络运营商）的伙伴或转售商，用于广播和多播服务。在这种情况下，访问提供商应该能够使用相同的DHCP选项发送多个域名（MVNO）。为了进一步说明这一点，我们假设访问提供商（运营商）与两个mvno1和mvno2签订了经销商协议。因此，广播和
Multicast Service Controller Domain Name list for the DHCPv4 option will contain three domain names: operator.com, mvno1.com, and 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.
DHCPv4选项的多播服务控制器域名列表将包含三个域名：operator.com、mvno1.com和mvno2.com。收到此选项后，BCMCS客户端可选择使用其中一个域名获取适当的BCMCS控制器地址（基于用户的偏好或配置）。如果在收到的列表中未找到首选域名，客户端应使用默认设置，例如，使用列表中的第一个。
If the length of the domain list exceeds the maximum permissible length within a single option (254 octets), then the domain list MUST be represented in the DHCPv4 message as specified in [RFC3396]. An example case when two controller domain names, example.com and example.net, are returned will be:
如果域列表的长度超过单个选项内允许的最大长度（254个八位字节），则域列表必须按照[RFC3396]中的规定在DHCPv4消息中表示。返回两个控制器域名example.com和example.net的示例如下：
+----+----+----+----+----+----+----+----+----+----+----+
| 88 | 26 | 7 | 'e'| 'x'| 'a'| 'm'| 'p'| 'l'| 'e'| 3 |
+----+----+----+----+----+----+----+----+----+----+----+
+----+----+----+----+----+----+----+----+----+----+----+
|'c' |'o' | 'm'| 0 | 7 | 'e'| 'x'| 'a'| 'm'| 'p'| 'l'|
+----+----+----+----+----+----+----+----+----+----+----+
+----+----+----+----+----+----+
|'e' | 3 | 'n'| 'e'| 't'| 0 |
+----+----+----+----+----+----+
+----+----+----+----+----+----+----+----+----+----+----+
| 88 | 26 | 7 | 'e'| 'x'| 'a'| 'm'| 'p'| 'l'| 'e'| 3 |
+----+----+----+----+----+----+----+----+----+----+----+
+----+----+----+----+----+----+----+----+----+----+----+
|'c' |'o' | 'm'| 0 | 7 | 'e'| 'x'| 'a'| 'm'| 'p'| 'l'|
+----+----+----+----+----+----+----+----+----+----+----+
+----+----+----+----+----+----+
|'e' | 3 | 'n'| 'e'| 't'| 0 |
+----+----+----+----+----+----+
4.2. Broadcast and Multicast Service Controller Domain Name List Option for DHCPv6
4.2. DHCPv6的广播和多播服务控制器域名列表选项
The semantics and content of the DHCPv6 encoding of this option are exactly the same as the encoding described in the previous section, other than necessary differences between the way options are encoded in DHCPv4 and DHCPv6.
该选项的DHCPv6编码的语义和内容与上一节中描述的编码完全相同，不同之处在于DHCPv4和DHCPv6中选项的编码方式存在必要的差异。
Specifically, the DHCPv6 option for the BCMCS Control Server Domain Names has the following format:
具体而言，BCMCS控制服务器域名的DHCPv6选项具有以下格式：
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_BCMCS_SERVER_D | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BCMCS Control Server Domain Name List |
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_BCMCS_SERVER_D | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BCMCS Control Server Domain Name List |
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_BCMCS_SERVER_D (33).
选项代码：选项\u BCMCS\u服务器\u D（33）。
option-length: Length of the 'BCMCS Control Server Domain Name List' field in octets; variable.
选项长度：“BCMCS控制服务器域名列表”字段的长度（以八位字节为单位）；变量
BCMCS Control Server Domain Name List: Identical format as in Section 4.1 (except the Code and Len fields).
BCMCS控制服务器域名列表：与第4.1节中的格式相同（代码和Len字段除外）。
4.3. Broadcast and Multicast Service Controller IPv4 Address Option for DHCPv4
4.3. DHCPv4的广播和多播服务控制器IPv4地址选项
The Length byte (Len) is followed by a list of IPv4 addresses indicating BCMCS controller IPv4 addresses. The BCMCS controllers 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 encoding has the following format:
长度字节（Len）后面是指示BCMCS控制器IPv4地址的IPv4地址列表。BCMCS控制器必须按优先顺序列出。其最小长度为4，且长度必须是4的倍数。此编码的DHCPv4选项具有以下格式：
Code Len Address 1 Address 2
+-----+-----+-----+-----+-----+-----+-----+--
| 89 | n | a1 | a2 | a3 | a4 | a1 | ...
+-----+-----+-----+-----+-----+-----+-----+--
Code Len Address 1 Address 2
+-----+-----+-----+-----+-----+-----+-----+--
| 89 | n | a1 | a2 | a3 | a4 | a1 | ...
+-----+-----+-----+-----+-----+-----+-----+--
4.4. Broadcast and Multicast Service Controller IPv6 Address Option for DHCPv6
4.4. DHCPv6的广播和多播服务控制器IPv6地址选项
This DHCPv6 option MUST carry one or more 128-bit IPv6 address(es) of the BCMCS Controller in an operator's network.
此DHCPv6选项必须在运营商网络中承载BCMCS控制器的一个或多个128位IPv6地址。
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_BCMCS_SERVER_A | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| BCMCS Control server-1 address (IPv6 address) |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| BCMCS Control server-2 address (IPv6 address) |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_BCMCS_SERVER_A | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| BCMCS Control server-1 address (IPv6 address) |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| BCMCS Control server-2 address (IPv6 address) |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_BCMCS_SERVER_A (34).
选项代码：选项\u BCMCS\u服务器\u A（34）。
option-length: Length of the 'BCMCS Control Server IPv6 address' field in octets; variable.
选项长度：“BCMCS控制服务器IPv6地址”字段的长度（以八位字节为单位）；变量
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].
对于DHCPv4，客户端可以请求[RFC2132]中定义的参数请求列表选项（代码55）中的BCMCS控制器域名列表和IPv4地址选项中的一个或两个。
For DHCPv6, the client MAY request either or both of the BCMCS Controller Domain Name List and the IPv6 Address options in the Options Request Option (ORO) as described in [RFC3315].
对于DHCPv6，客户机可以请求选项请求选项（ORO）中的BCMCS控制器域名列表和IPv6地址选项中的一个或两个，如[RFC3315]中所述。
If the client receives both the BCMCS Controller Domain Name List and IPv6 or IPv4 Address options, it SHOULD use the Domain Name List option. In this case, the client SHOULD NOT use the BCMCS Controller IPv6 or IPv4 Address option unless the server(s) in the BCMCS Controller Domain Name List cannot be resolved or reached.
如果客户端同时收到BCMCS控制器域名列表和IPv6或IPv4地址选项，则应使用域名列表选项。在这种情况下，除非无法解析或访问BCMCS控制器域名列表中的服务器，否则客户端不应使用BCMCS控制器IPv6或IPv4地址选项。
A server MAY send a client either the BCMCS Controller Domain Name List Option or the BCMCS Controller IPv6 Address/IPv4 Address options if the server is configured to do so.
如果服务器配置为向客户端发送BCMCS控制器域名列表选项或BCMCS控制器IPv6地址/IPv4地址选项，则服务器可以向客户端发送。
If a client requests both the options and the server is configured with both types of information, the server MAY send the client only one of the options if it is configured to do so. In this case, the server SHOULD send the BCMCS Controller Domain Name List option.
如果客户端同时请求这两个选项，并且服务器配置了这两种类型的信息，则服务器可能只向客户端发送其中一个选项（如果服务器配置为发送）。在这种情况下，服务器应发送BCMCS控制器域名列表选项。
A server configured with the BCMCS Controller IPv6 or IPv4 Address information MUST send a client the BCMCS Controller IPv6 or IPv4 Address option if that client requested only the BCMCS Controller IPv6 or IPv4 Address option and not the BCMCS Controller Domain Name List option in the ORO or Parameter Request List option.
如果客户端仅请求BCMCS控制器IPv6或IPv4地址选项，而未请求ORO或参数请求列表选项中的BCMCS控制器域名列表选项，则配置有BCMCS控制器IPv6或IPv4地址信息的服务器必须向客户端发送BCMCS控制器IPv6或IPv4地址选项。
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 server MUST return the Domain Name List and vice versa.
如果客户端请求BCMCS控制器IPv6或IPv4地址选项，并且服务器仅配置了域名，则服务器必须返回域名列表，反之亦然。
The domain names MUST be concatenated and encoded using the technique described in Section 3.3 of "Domain Names - Implementation and Specification" [RFC1035]. DNS name compression MUST NOT be used.
域名必须使用“域名-实现和规范”[RFC1035]第3.3节中描述的技术进行连接和编码。不得使用DNS名称压缩。
The following table summarizes the server's response:
下表总结了服务器的响应：
Client sends in ORO/
Parameter Request List Domain Name List IPv6/IPv4 Address
__________________________________________________________________
Client sends in ORO/
Parameter Request List Domain Name List IPv6/IPv4 Address
__________________________________________________________________
Neither option SHOULD MAY Domain Name List MUST MAY IPv6/IPv4 Address MAY MUST Both options SHOULD MAY
两个选项都不应该，域名列表必须是IPv6/IPv4地址必须是IPv6，两个选项都应该是
This document does not introduce any new security concerns beyond those specified in the basic DHCP [RFC2131] and DHCPv6 [RFC3315] specifications. In the absence of message integrity protection for these options, an attacker could modify the option values to divert requests for broadcast service.
除了基本DHCP[RFC2131]和DHCPv6[RFC3315]规范中规定的安全问题外，本文档不会引入任何新的安全问题。在这些选项没有消息完整性保护的情况下，攻击者可以修改选项值以转移广播服务请求。
The following option codes for Broadcast and Multicast Service Controller option have been assigned by IANA:
IANA为广播和多播服务控制器选项分配了以下选项代码：
1. The BCMCS Controller Domain Name list (Section 4.1) has been assigned a value of 88 from the DHCPv4 option space.
1. BCMCS控制器域名列表（第4.1节）已从DHCPv4选项空间分配了88的值。
2. The BCMCS Controller Domain Name list (Section 4.2) has been assigned a value of 33 from the DHCPv6 option space, and a name of OPTION_BCMCS_SERVER_D.
2. BCMCS控制器域名列表（第4.2节）已从DHCPv6选项空间中分配了一个值33和一个选项名称\u BCMCS\u服务器\u D。
3. The BCMCS Controller IPv4 Address option (Section 4.3) has been assigned a value of 89 from the DHCPv4 option space.
3. BCMCS控制器IPv4地址选项（第4.3节）已从DHCPv4选项空间分配了89的值。
4. The BCMCS Controller IPv6 Address option (Section 4.4) has been assigned a value of 34 from the DHCPv6 option space, and a name of OPTION_BCMCS_SERVER_A.
4. BCMCS控制器IPv6地址选项（第4.4节）已从DHCPv6选项空间中分配了一个值34和一个选项名称\u BCMCS\u SERVER\u a。
Thanks to the following individuals for their review and constructive comments during the development of this document:
感谢以下人员在本文件编制过程中的审查和建设性意见：
AC Mahendran, Jun Wang, Raymond Hsu, Jayshree Bharatia, Ralph Droms, Ted Lemon, Margaret Wasserman, Thomas Narten, Elwyn Davies, Pekka Savola, Bert Wijnen, David Kessens, Brian E. Carpenter, and Stig Venaas.
AC马亨德兰、王军、徐雷蒙、贾斯瑞·巴拉蒂亚、拉尔夫·德罗姆斯、特德·莱蒙、玛格丽特·瓦瑟曼、托马斯·纳滕、埃尔温·戴维斯、佩卡·萨沃拉、伯特·维恩、大卫·凯森斯、布莱恩·卡彭特和斯蒂格·维纳斯。
[BCMCS] 3GPP2, www.3gpp2.org, http://www.3gpp2.org/Public_html/specs/tsgx.cfm, "X.S0022, Broadcast and Multicast Service in cdma2000 Wireless IP Network.", December 2005.
[BCMCS]3GPP2，www.3GPP2.org，http://www.3gpp2.org/Public_html/specs/tsgx.cfm，“X.S0022，cdma2000无线IP网络中的广播和多播服务”，2005年12月。
[RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987.
[RFC1035]Mockapetris，P.，“域名-实现和规范”，STD 13，RFC 1035，1987年11月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 1997.
[RFC2131]Droms，R.，“动态主机配置协议”，RFC21311997年3月。
[RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor Extensions", RFC 2132, March 1997.
[RFC2132]Alexander，S.和R.Droms，“DHCP选项和BOOTP供应商扩展”，RFC 21321997年3月。
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC3315]Droms，R.，Bound，J.，Volz，B.，Lemon，T.，Perkins，C.，和M.Carney，“IPv6的动态主机配置协议（DHCPv6）”，RFC3315，2003年7月。
[RFC3396] Lemon, T. and S. Cheshire, "Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4)", RFC 3396, November 2002.
[RFC3396]Lemon，T.和S.Cheshire，“动态主机配置协议（DHCPv4）中的长选项编码”，RFC 3396，2002年11月。
Authors' Addresses
作者地址
Kuntal Chowdhury Starent Networks 30 International Place Tewksbury, MA 01876 US
Kuntal Chowdhury Starent Networks美国马萨诸塞州托克斯伯里国际广场30号01876
Phone: +1 214-550-1416
EMail: kchowdhury@starentnetworks.com
Phone: +1 214-550-1416
EMail: kchowdhury@starentnetworks.com
Parviz Yegani Cisco Systems 3625 Cisco Way San Jose, CA 95134 US
美国加利福尼亚州圣何塞市思科路3625号帕维兹·耶加尼思科系统公司，邮编95134
Phone: +1 408-832-5729
EMail: pyegani@cisco.com
Phone: +1 408-832-5729
EMail: pyegani@cisco.com
Lila Madour Ericsson 8400, Decarie Blvd Town of Mount Royal, Quebec H4P 2N2 CANADA
加拿大魁北克皇家山Decarie Blvd镇Lila Madour Ericsson 8400 H4P 2N2
Phone: +1 514-345-7900
EMail: Lila.Madour@ericsson.com
Phone: +1 514-345-7900
EMail: Lila.Madour@ericsson.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。