draft-ietf-dhc-dhcpv6-opt-nisconfig-03.txt   draft-ietf-dhc-dhcpv6-opt-nisconfig-04.txt 
Network Working Group A.K. Vijayabhaskar Network Working Group Vijayabhaskar A Kalusivalingam
Internet-Draft Hewlett-Packard Internet-Draft Hewlett-Packard
Expires: April 16, 2004 15 Oct 2003 Expires: May 2004 Nov 2003
NIS Configuration Options for DHCPv6 NIS Configuration Options for DHCPv6
draft-ietf-dhc-dhcpv6-opt-nisconfig-03.txt draft-ietf-dhc-dhcpv6-opt-nisconfig-04
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. all provisions of Section 10 of RFC2026.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
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 April 16, 2004. This Internet-Draft will expire on May 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This document describes four options for NIS-related configuration This document describes four options for Network Information
information in DHCPv6: NIS Servers [3], NIS+ Servers [3], NIS Client Service (NIS) [3] related configuration information in
DHCPv6 (RFC 3315 [1]): NIS Servers [3], NIS+ Servers [3], NIS Client
Domain Name [3], NIS+ Client Domain name [3]. Domain Name [3], NIS+ Client Domain name [3].
1. Introduction 1. Introduction
This document describes four options for configuration information This document describes four options for passing configuration
related to Network Information Service (NIS) in DHCPv6 [1]. information related to Network Information Service (NIS) [3] in
DHCPv6 [1].
2. Requirements 2. Terminology
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be
document, are to be interpreted as described in RFC 2119 [2] interpreted as described in RFC2119 [2].
3. Terminology Throughout this document, unless otherwise specified, the acronym
DHCP refers to DHCP as specified in RFC 3315 [1].
This document uses terminology specific to IPv6 and DHCPv6 as defined This document uses terminology specific to IPv6 and DHCP as defined
in "Terminology" section of the DHCPv6 specification [1]. in section "Terminology" of RFC 3315 [1].
4. Network Information Service (NIS) Servers option 3. Network Information Service (NIS) Servers Option
The Network Information Service (NIS) [3] Servers option provides a The Network Information Service (NIS) [3] Servers option provides a
list of one or more IPv6 addresses of NIS servers available to the list of one or more IPv6 addresses of NIS servers available to the
client. The NIS servers SHOULD be listed in the order of preference. client. Clients MUST treat the list of NIS servers as an ordered
list. The server MAY list the NIS servers in the order of
preference.
The format of the Network Information Service Servers option is as The format of the Network Information Service Servers option is as
as shown below: shown below:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_NIS_SERVERS | option-len | | OPTION_NIS_SERVERS | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| NIS server (IPv6 address) | | NIS server (IPv6 address) |
| | | |
| | | |
skipping to change at page 2, line 44 skipping to change at page 2, line 47
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_NIS_SERVERS (tbd) option-code: OPTION_NIS_SERVERS (tbd)
option-len: Length of the 'NIS server' fields in octets; It must be option-len: Length of the 'NIS server' fields in octets; It must be
a multiple of 16 a multiple of 16
NIS server: IPv6 address of NIS server NIS server: IPv6 address of NIS server
5. Network Information Service V2 (NIS+) Servers option 4. Network Information Service V2 (NIS+) Servers Option
The Network Information Service V2 (NIS+) [3] Servers option provides The Network Information Service V2 (NIS+) [3] Servers option provides
a list of one or more IPv6 addresses of NIS+ servers available to a list of one or more IPv6 addresses of NIS+ servers available to
the client. The NIS+ servers SHOULD be listed in the order of the client. Clients MUST treat the list of NIS+ servers as an
ordered list. The server MAY list the NIS+ servers in the order of
preference. preference.
The format of the Network Information Service V2 (NIS+) Servers The format of the Network Information Service V2 (NIS+) Servers
option is as shown below: option is as shown below:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_NISP_SERVERS | option-len | | OPTION_NISP_SERVERS | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 3, line 30 skipping to change at page 3, line 30
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_NISP_SERVERS (tbd) option-code: OPTION_NISP_SERVERS (tbd)
option-len: Length of the 'NIS+ server' fields in octets; It must be option-len: Length of the 'NIS+ server' fields in octets; It must be
a multiple of 16 a multiple of 16
NIS+ server: IPv6 address of NIS+ server NIS+ server: IPv6 address of NIS+ server
6. Network Information Service (NIS) Domain Name option 5. Network Information Service (NIS) Domain Name Option
The Network Information Service (NIS) [3] Domain Name option is used The Network Information Service (NIS) [3] Domain Name option is used
by the server to convey client's NIS Domain Name info to the by the server to convey client's NIS Domain Name info to the
client. client.
The format of the NIS Domain Name option is as shown below: The format of the NIS Domain Name option is as shown below:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 4, line 5 skipping to change at page 4, line 5
option-code: OPTION_NIS_DOMAIN_NAME (tbd) option-code: OPTION_NIS_DOMAIN_NAME (tbd)
option-len: Length of the 'nis-domain-name' field in octets option-len: Length of the 'nis-domain-name' field in octets
nis-domain-name: NIS Domain name for client nis-domain-name: NIS Domain name for client
The 'nis-domain-name' MUST be encoded as specified in section The 'nis-domain-name' MUST be encoded as specified in section
"Representation and Use of domain names" of the DHCPv6 "Representation and Use of domain names" of the DHCPv6
specification [1]. specification [1].
7. Network Information Service V2 (NIS+) Domain Name option 6. Network Information Service V2 (NIS+) Domain Name Option
The Network Information Service V2 (NIS+) [3] Domain Name option is The Network Information Service V2 (NIS+) [3] Domain Name option is
used by the server to convey client's NIS+ Domain Name info to the used by the server to convey client's NIS+ Domain Name info to the
client. client.
The format of the NIS+ Domain Name option is as shown below: The format of the NIS+ Domain Name option is as shown below:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 4, line 32 skipping to change at page 4, line 32
option-code: OPTION_NISP_DOMAIN_NAME (tbd) option-code: OPTION_NISP_DOMAIN_NAME (tbd)
option-len: Length of the 'nisp-domain-name' field in octets option-len: Length of the 'nisp-domain-name' field in octets
nisp-domain-name: NIS+ Domain name for client nisp-domain-name: NIS+ Domain name for client
The 'nisp-domain-name' MUST be encoded as specified in section The 'nisp-domain-name' MUST be encoded as specified in section
"Representation and Use of domain names" of the DHCPv6 "Representation and Use of domain names" of the DHCPv6
specification [1]. specification [1].
8. Appearance of these options 7. Appearance of these Options
The NIS servers, NIS+ servers, NIS domain name and NIS+ domain name The NIS servers, NIS+ servers, NIS domain name and NIS+ domain name
options MUST NOT appear in other than the following messages: Solicit, options MUST NOT appear in other than the following messages: Solicit,
Advertise, Request, Renew, Rebind, Information-Request and Reply. Advertise, Request, Renew, Rebind, Information-Request and Reply.
The option number for these options MAY appear in the Option Request The option number for these options MAY appear in the Option Request
Option [1] in the following messages: Solicit, Request, Renew, Option [1] in the following messages: Solicit, Request, Renew,
Rebind, Information-Request and Reconfigure. Rebind, Information-Request and Reconfigure.
9. Security Considerations 8. Security Considerations
The NIS servers, NIS+ servers, NIS domain name and NIS+ domain name The NIS servers, NIS+ servers, NIS domain name and NIS+ domain name
options may be used by an intruder DHCPv6 server to assign invalid options may be used by an intruder DHCPv6 server to assign invalid
NIS parameters, resulting in clients unable to use NIS service. NIS parameters, resulting in clients unable to use NIS service.
To avoid attacks through these options, the DHCP client SHOULD use The NIS servers and NIS+ servers options may be used by an intruder
authenticated DHCP (see section "Authentication of DHCP messages" DHCPv6 server to cause the DHCPv6 clients to send their queries to an
in the DHCPv6 specification [1]). intruder NIS/NIS+ server. This misdirected searches may be used to
spoof NIS/NIS+ names.
10. IANA Considerations The NIS domain name and NIS+ domain name options may be used by an
intruder DHCPv6 server to cause the DHCPv6 clients to search through
invalid domains for incompletely specified domain names. The results
of these misdirected searches may be used to spoof NIS/NIS+ names.
To avoid attacks through these options, the DHCPv6 client SHOULD use
authenticated DHCP (see section "Authentication of DHCP messages" in
the DHCPv6 specification [1]).
9. IANA Considerations
IANA is requested to assign an option code to the following options IANA is requested to assign an option code to the following options
from the option-code space defined in "DHCPv6 Options" section of the from the option-code space defined in "DHCPv6 Options" section of the
DHCPv6 specification [1]. DHCPv6 specification [1].
Option Name Value Described in Option Name Value Described in
OPTION_NIS_SERVERS tbd Section 4 OPTION_NIS_SERVERS tbd Section 3
OPTION_NISP_SERVERS tbd Section 5 OPTION_NISP_SERVERS tbd Section 4
OPTION_NIS_DOMAIN_NAME tbd Section 6 OPTION_NIS_DOMAIN_NAME tbd Section 5
OPTION_NISP_DOMAIN_NAME tbd Section 7 OPTION_NISP_DOMAIN_NAME tbd Section 6
11. Normative References 10. Normative References
[1] Bound, J., Carney, M., Perkins, C., Lemon, T., Volz, B. and R. [1] Bound, J., Carney, M., Perkins, C., Lemon, T., Volz, B. and R.
Droms (ed.), "Dynamic Host Configuration Protocol for IPv6 Droms (ed.), "Dynamic Host Configuration Protocol for IPv6
(DHCPv6)", RFC 3315, July 2003. (DHCPv6)", RFC 3315, July 2003.
12. Informative References
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
11. Informative References
[3] Sun Microsystems, "System and Network Administration", [3] Sun Microsystems, "System and Network Administration",
March 1990. March 1990.
Author's Address Author's Address
Vijayabhaskar A K Vijayabhaskar A Kalusivalingam
Hewlett-Packard STSD-I Hewlett-Packard STSD-I
29, Cunningham Road 29, Cunningham Road
Bangalore - 560052 Bangalore - 560052
India India
Phone: +91-80-2053085 Phone: +91-80-2053085
E-Mail: vijayak@india.hp.com E-Mail: vijayak@india.hp.com
Full Copyright Statement Full Copyright Statement
skipping to change at page 6, line 38 skipping to change at page 6, line 38
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Thanks to the DHC Working Group for their time and Internet Society. Thanks to the DHC Working Group for their time and
input into the specification. In particular, thanks to (in input into the specification. In particular, thanks to (in
alphabetical order) Bernie Volz, Jim Bound, Ralph Droms and Thomas alphabetical order) Bernie Volz, Jim Bound, Margaret Wasserman, Pekka
Narten for their thorough review. Savola, Ralph Droms and Thomas Narten for their thorough review.
 End of changes. 

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