Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control Servers
RFC 4280
| Document | Type | RFC - Proposed Standard (December 2005) Errata | |
|---|---|---|---|
| Authors | Kuntal Chowdhury , Parviz Yegani , Lila Madour | ||
| Last updated | 2013-03-02 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| IESG | Responsible AD | Margaret Cullen | |
| Send notices to | (None) |
RFC 4280
TRILL Working Group H. Zhai
Internet-Draft F. Hu
Intended status: Standards Track ZTE
Expires: May 15, 2012 R. Perlman
Intel Labs
D. Eastlake 3rd
Huawei
November 12, 2011
RBridge: Pseudonode Nickname
draft-hu-trill-pseudonode-nickname-01
Abstract#x27;| 't'| 0 |
+----+----+----+----+----+----+
4.2. Broadcast and Multicast Service Controller Domain Name List Option
for 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.
Specifically, the DHCPv6 option for the BCMCS Control Server Domain
Names has the following format:
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).
option-length: Length of the 'BCMCS Control Server Domain Name List'
field in octets; variable.
Chowdhury, et al. Standards Track [Page 5]
RFC 4280 DHCP Options for BMCS November 2005
BCMCS Control Server Domain Name List: Identical format as in Section
4.1 (except the Code and Len fields).
4.3. Broadcast and Multicast Service Controller IPv4 Address Option for
DHCPv4
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:
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
This DHCPv6 option MUST carry one or more 128-bit IPv6 address(es) of
the BCMCS Controller in an operator's network.
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).
option-length: Length of the 'BCMCS Control Server IPv6 address'
field in octets; variable.
Chowdhury, et al. Standards Track [Page 6]
RFC 4280 DHCP Options for BMCS November 2005
4.5. Consideration for Client Operation
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
Options Request Option (ORO) as described in [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.
4.6. Consideration for Server Operation
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.
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.
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.
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.
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.
Chowdhury, et al. Standards Track [Page 7]
RFC 4280 DHCP Options for BMCS November 2005
The following table summarizes the server's response:
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
5. Security Considerations
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.
6. IANA Considerations
The following option codes for Broadcast and Multicast Service
Controller option have been assigned by IANA:
1. The BCMCS Controller Domain Name list (Section 4.1) has been
assigned a value of 88 from the DHCPv4 option space.
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.
3. The BCMCS Controller IPv4 Address option (Section 4.3) has been
assigned a value of 89 from the DHCPv4 option space.
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.
7. Acknowledgements
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.
Chowdhury, et al. Standards Track [Page 8]
RFC 4280 DHCP Options for BMCS November 2005
8. Normative References
[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.
[RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol",
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.,
and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC3396] Lemon, T. and S. Cheshire, "Encoding Long Options in the
Dynamic Host Configuration Protocol (DHCPv4)", RFC 3396,
November 2002.
Chowdhury, et al. Standards Track [Page 9]
RFC 4280 DHCP Options for BMCS November 2005
Authors' Addresses
Kuntal Chowdhury
Starent Networks
30 International Place
Tewksbury, MA 01876
US
Phone: +1 214-550-1416
EMail: kchowdhury@starentnetworks.com
Parviz Yegani
Cisco Systems
3625 Cisco Way
San Jose, CA 95134
US
Phone: +1 408-832-5729
EMail: pyegani@cisco.com
Lila Madour
Ericsson
8400, Decarie Blvd
Town of Mount Royal, Quebec H4P 2N2
CANADA
Phone: +1 514-345-7900
EMail: Lila.Madour@ericsson.com
Chowdhury, et al. Standards Track [Page 10]
RFC 4280 DHCP Options for BMCS November 2005
Full Copyright Statement
Copyright (C) The Internet Society (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.
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.
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.
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.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Chowdhury, et al. Standards Track [Page 11]