draft-ietf-dhc-dhcpv6-opt-dnsdomain-01.txt   draft-ietf-dhc-dhcpv6-opt-dnsdomain-02.txt 
DHC Working Group R. Yan DHC Working Group R. Yan
Internet Draft Y. Jiang Internet Draft Y. Jiang
Expiration Date: August 2006 L. Gui Expiration Date: September 2006 L. Gui
Alcatel Shanghai Bell Alcatel Shanghai Bell
X. Duan X. Duan
China Mobile China Mobile
Domain Suffix Option for DHCPv6 Domain Suffix Option for DHCPv6
<draft-ietf-dhc-dhcpv6-opt-dnsdomain-01.txt> <draft-ietf-dhc-dhcpv6-opt-dnsdomain-02.txt>
February 6, 2006 March 6, 2006
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 38 skipping to change at page 1, line 38
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 6, 2006. This Internet-Draft will expire on September 6, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document specifies a new DHCPv6 (DHCP for IPv6) option which is This document specifies a new DHCPv6 (DHCP for IPv6) option which is
passed from a DHCPv6 server to a DHCPv6 client to specify the passed from a DHCPv6 server to a DHCPv6 client to specify the
domain suffix name. domain suffix name.
skipping to change at page 3, line 7 skipping to change at page 3, line 7
Length: Length of the "domain suffix" field in octets. Length: Length of the "domain suffix" field in octets.
Domain suffix: The specification of a domain suffix. Domain suffix: The specification of a domain suffix.
The domain suffix in the 'domain suffix' field MUST include only one The domain suffix in the 'domain suffix' field MUST include only one
item, and MUST be encoded as specified in the section of RFC3315 item, and MUST be encoded as specified in the section of RFC3315
titled "Representation and use of domain names". titled "Representation and use of domain names".
2.1 Usage 2.1 Usage
A DHCPv6 client MUST include the option code in Option Request
Option [RFC3315] if it desires the domain suffix option, and the
DHCPv6 server SHOULD include this option in an Advertise or Reply
if requested by the client in the Option Request Option.
A DHCPv6 server may provide different values for the domain suffix A DHCPv6 server may provide different values for the domain suffix
option to different clients. The mechanism for choosing which option to different clients. The mechanism for choosing which
suffix to assign to which client is a matter of implementation and suffix to assign to which client is a matter of implementation and
administrative policy, and is therefore not specified in this administrative policy, and is therefore not specified in this
document. document.
3. Security Considerations 3. Security Considerations
Security considerations in DHCP are described in section 23, Security considerations in DHCP are described in section 23,
"Security Considerations" of RFC3315. "Security Considerations" of RFC3315.
4. IANA Considerations 4. IANA Considerations
IANA is requested to assign a DHCPv6 option code for the Domain IANA is requested to assign a DHCPv6 option code for the Domain
Suffix Option. Suffix Option.
5. Acknowledgements 5. Acknowledgements
The authors thank Ralph Droms, Ted Lemon, Bernie Volz, Tatuya Jinmei, The authors thank Ralph Droms, Ted Lemon, Bernie Volz, Tatuya Jinmei,
Joe Quanaim and Stefaan De Cnodder for valuable discussions and Joe Quanaim, Stefaan De Cnodder, and Stig Venaas for valuable
comments. discussions and comments.
6. References 6. References
6.1 Normative References 6.1 Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3315] Bound, J., Carney, M., Perkins, C., Lemon, T., Volz, B. [RFC3315] Bound, J., Carney, M., Perkins, C., Lemon, T., Volz, B.
and R. Droms (ed.), "Dynamic Host Configuration Protocol and R. Droms (ed.), "Dynamic Host Configuration Protocol
 End of changes. 6 change blocks. 
6 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/