draft-ietf-dhc-nsso-03.txt   draft-ietf-dhc-nsso-04.txt 
Network Working Group C. Smith Network Working Group C. Smith
Internet Draft Sun Microsystems, Inc. Internet Draft Sun Microsystems, Inc.
February 2000 June 2000
Expires August 2000 Expires December 2000
The Name Service Search Option for DHCP The Name Service Search Option for DHCP
<draft-ietf-dhc-nsso-03.txt> <draft-ietf-dhc-nsso-04.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 3, line 6 skipping to change at page 3, line 6
types of name server. The current list of name services and their types of name server. The current list of name services and their
DHCP option codes, taken from RFC 2132, includes DHCP option codes, taken from RFC 2132, includes
Name Service Value Name Service Value
Domain Name Server Option 6 Domain Name Server Option 6
Network Information Servers Option 41 Network Information Servers Option 41
NetBIOS over TCP/IP Name Server Option 44 NetBIOS over TCP/IP Name Server Option 44
Network Information Service+ Servers Option 65 Network Information Service+ Servers Option 65
A name service option code of 0 is used to indicate that the
client should refer to local naming information (e.g. an
/etc/hosts file on a UNIX machine).
A DHCP server wishing to express that a client should first search A DHCP server wishing to express that a client should first search
DNS, then NIS+, would send DNS, then NIS+, would send
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TBD | 4 | 6 | | TBD | 4 | 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 65 | | 65 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
A name service option code of 0 is used to indicate that the client
should refer to local naming information (e.g. an /etc/hosts file on
a UNIX machine).
DHCP Client Behavior DHCP Client Behavior
The DHCP client will use this option to create a search list for name The DHCP client will use this option to create a search list for name
resolution. The client SHOULD ignore any name services appearing in resolution. The client SHOULD ignore any name services appearing in
this option that it does not support or has not been configured to this option that it does not support or has not been configured to
access. Clients will interpret this option in a system-specific access. Clients will interpret this option in a system-specific
manner whose specification is outside the scope of this document. manner whose specification is outside the scope of this document.
Security Considerations Security Considerations
DHCP currently provides no authentication or security mechanisms. DHCP currently provides no authentication or security mechanisms.
Potential exposures to attack are discussed in section 7 of the DHCP Potential exposures to attack are discussed in section 7 of the DHCP
protocol specification [1]. protocol specification [1].
IANA Considerations
IANA has assigned a value of TBD for the DHCP option code described
in this document.
References References
[1] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March [1] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March
1997. 1997.
[2] Alexander, S. and Droms, R., "DHCP Options and BOOTP Vendor [2] Alexander, S. and Droms, R., "DHCP Options and BOOTP Vendor
Extensions", RFC 2132, March 1997. Extensions", RFC 2132, March 1997.
[3] Bradner, S., "Key words for use in RFCs to indicate requirement [3] Bradner, S., "Key words for use in RFCs to indicate requirement
levels", RFC 2119, March 1997. levels", RFC 2119, March 1997.
[4] Cohen, D., "On Holy Wars and a Plea for Peace", Computer, IEEE, [4] Cohen, D., "On Holy Wars and a Plea for Peace", Computer, IEEE,
October 1981. October 1981.
skipping to change at page 4, line 9 skipping to change at page 4, line 15
Author Information Author Information
Carl Smith Carl Smith
Sun Microsystems, Inc. Sun Microsystems, Inc.
901 San Antonio Road 901 San Antonio Road
Palo Alto, CA 94043 Palo Alto, CA 94043
email: cs@Eng.Sun.COM email: cs@Eng.Sun.COM
Expiration Expiration
This document will expire on August 31, 2000. This document will expire on December 15, 2000.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
 End of changes. 

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