draft-ietf-dhc-dhcpv6-opt-nisconfig-05.txt   rfc3898.txt 
Network Working Group Vijayabhaskar A Kalusivalingam Network Working Group V. Kalusivalingam
Internet-Draft Hewlett-Packard Request for Comments: 3898 Cisco Systems (India) Private Limited
Expires: Jun 2004 Dec 2003 Category: Standards Track October 2004
NIS Configuration Options for DHCPv6 Network Information Service (NIS)
draft-ietf-dhc-dhcpv6-opt-nisconfig-05 Configuration Options for
Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC2026. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Internet-Drafts are working documents of the Internet Engineering Official Protocol Standards" (STD 1) for the standardization state
Task Force (IETF), its areas, and its working groups. Note that and status of this protocol. Distribution of this memo is unlimited.
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on Jun 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004).
Abstract Abstract
This document describes four options for Network Information Service This document describes four options for Network Information Service
(NIS) related configuration information in DHCPv6: NIS Servers, NIS+ (NIS) related configuration information in Dynamic Host Configuration
Servers, NIS Client Domain Name, NIS+ Client Domain name. Protocol for IPv6 (DHCPv6): NIS Servers, NIS+ Servers, NIS Client
Domain Name, NIS+ Client Domain name.
1. Introduction 1. Introduction
This document describes four options for passing configuration This document describes four options for passing configuration
information related to Network Information Service (NIS) [3] in information related to Network Information Service (NIS) [3] in
DHCPv6 (RFC 3315 [1]). DHCPv6 (RFC 3315 [1]).
The options defined in this document can only be used to configure
information about NIS servers that can be reached using IPv6. The
DHCP option to configure information about IPv4 NIS servers can be
found in RFC 2132 [4]. Mechanisms for configuring IPv4/IPv6 dual-
stack applications are being considered, but are not specified in
this document.
2. Terminology 2. Terminology
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be
interpreted as described in RFC2119 [2]. interpreted as described in BCP 14, RFC 2119 [2].
Throughout this document, unless otherwise specified, the acronym Throughout this document, unless otherwise specified, the acronym
DHCP refers to DHCP as specified in RFC 3315. DHCP refers to DHCP as specified in RFC 3315.
This document uses terminology specific to IPv6 and DHCP as defined This document uses terminology specific to IPv6 and DHCP as defined
in section "Terminology" of RFC 3315. in section "Terminology" of RFC 3315.
3. Network Information Service (NIS) Servers Option 3. Network Information Service (NIS) Servers Option
The Network Information Service (NIS) Servers option provides a The Network Information Service (NIS) Servers option provides a list
list of one or more IPv6 addresses of NIS servers available to the of one or more IPv6 addresses of NIS servers available to the client.
client. Clients MUST treat the list of NIS servers as an ordered Clients MUST treat the list of NIS servers as an ordered list. The
list. The server MAY list the NIS servers in the order of server MAY list the NIS servers in the order of preference.
preference.
The format of the Network Information Service Servers option is as The format of the Network Information Service Servers option is 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
skipping to change at page 2, line 40 skipping to change at page 2, line 39
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| NIS server (IPv6 address) | | NIS server (IPv6 address) |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_NIS_SERVERS (tbd) option-code: OPTION_NIS_SERVERS (27)
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
4. Network Information Service V2 (NIS+) Servers Option 4. Network Information Service V2 (NIS+) Servers Option
The Network Information Service V2 (NIS+) Servers option provides The Network Information Service V2 (NIS+) Servers option provides a
a list of one or more IPv6 addresses of NIS+ servers available to list of one or more IPv6 addresses of NIS+ servers available to the
the client. Clients MUST treat the list of NIS+ servers as an client. Clients MUST treat the list of NIS+ servers as an ordered
ordered list. The server MAY list the NIS+ servers in the order of 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 23 skipping to change at page 3, line 26
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| NIS+ server (IPv6 address) | | NIS+ server (IPv6 address) |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_NISP_SERVERS (tbd) option-code: OPTION_NISP_SERVERS (28)
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 (NIS) Domain Name Option 5. Network Information Service (NIS) Domain Name Option
The Network Information Service (NIS) Domain Name option is used The Network Information Service (NIS) Domain Name option is used by
by the server to convey client's NIS Domain Name info to the 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_NIS_DOMAIN_NAME | option-len | | OPTION_NIS_DOMAIN_NAME | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| nis-domain-name | | nis-domain-name |
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_NIS_DOMAIN_NAME (tbd) option-code: OPTION_NIS_DOMAIN_NAME (29)
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
specification [1]. [1].
6. Network Information Service V2 (NIS+) Domain Name Option 6. Network Information Service V2 (NIS+) Domain Name Option
The Network Information Service V2 (NIS+) Domain Name option is The Network Information Service V2 (NIS+) Domain Name option is used
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_NISP_DOMAIN_NAME | option-len | | OPTION_NISP_DOMAIN_NAME | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| nisp-domain-name | | nisp-domain-name |
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_NISP_DOMAIN_NAME (tbd) option-code: OPTION_NISP_DOMAIN_NAME (30)
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
specification [1]. [1].
7. 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:
Advertise, Request, Renew, Rebind, Information-Request and Reply. Solicit, 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.
8. 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.
skipping to change at page 5, line 11 skipping to change at page 5, line 21
intruder DHCPv6 server to cause the DHCPv6 clients to search through intruder DHCPv6 server to cause the DHCPv6 clients to search through
invalid domains for incompletely specified domain names. The results invalid domains for incompletely specified domain names. The results
of these misdirected searches may be used to spoof NIS/NIS+ names. of these misdirected searches may be used to spoof NIS/NIS+ names.
To avoid attacks through these options, the DHCPv6 client SHOULD use To avoid attacks through these options, the DHCPv6 client SHOULD use
authenticated DHCP (see section "Authentication of DHCP messages" in authenticated DHCP (see section "Authentication of DHCP messages" in
the DHCPv6 specification [1]). the DHCPv6 specification [1]).
9. IANA Considerations 9. IANA Considerations
IANA is requested to assign an option code to the following options The IANA has assigned option codes to the following options from the
from the option-code space defined in "DHCPv6 Options" section of the option-code space defined in "DHCPv6 Options" section of the DHCPv6
DHCPv6 specification [1]. specification [1].
Option Name Value Described in Option Name Value Described in
OPTION_NIS_SERVERS tbd Section 3 OPTION_NIS_SERVERS 27 Section 3
OPTION_NISP_SERVERS tbd Section 4 OPTION_NISP_SERVERS 28 Section 4
OPTION_NIS_DOMAIN_NAME tbd Section 5 OPTION_NIS_DOMAIN_NAME 29 Section 5
OPTION_NISP_DOMAIN_NAME tbd Section 6 OPTION_NISP_DOMAIN_NAME 30 Section 6
10. Normative References 10. References
[1] Bound, J., Carney, M., Perkins, C., Lemon, T., Volz, B. and R. 10.1. Normative References
Droms (ed.), "Dynamic Host Configuration Protocol for IPv6
[1] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, C., and
M. Carney, "Dynamic Host Configuration Protocol for IPv6
(DHCPv6)", RFC 3315, July 2003. (DHCPv6)", RFC 3315, July 2003.
[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 10.2. Informative References
[3] Sun Microsystems, "System and Network Administration", [3] Sun Microsystems, "System and Network Administration", March
March 1990. 1990.
[4] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", RFC 2132, March 1997.
Acknowledgements
Thanks to the DHC Working Group for their time and input into the
specification. In particular, thanks to (in alphabetical order)
Bernie Volz, Jim Bound, Margaret Wasserman, Pekka Savola, Ralph
Droms, and Thomas Narten for their thorough review.
Author's Address Author's Address
Vijayabhaskar A Kalusivalingam Vijayabhaskar A Kalusivalingam
Hewlett-Packard STSD-I Cisco Systems (India) Private Limited,
29, Cunningham Road No: 9, Brunton Road,
Bangalore - 560052 Bangalore - 560025
India India
Phone: +91-80-2053085 Phone: +91-80-51036615
E-Mail: vijayak@india.hp.com EMail: vibhaska@cisco.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004).
This document and translations of it may be copied and furnished to This document is subject to the rights, licenses and restrictions
others, and derivative works that comment on or otherwise explain it contained in BCP 78, and except as set forth therein, the authors
or assist in its implementation may be prepared, copied, published retain all their rights.
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be This document and the information contained herein are provided on an
revoked by the Internet Society or its successors or assigns. "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.
This document and the information contained herein is provided on an Intellectual Property
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING The IETF takes no position regarding the validity or scope of any
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION Intellectual Property Rights or other rights that might be claimed to
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF pertain to the implementation or use of the technology described in
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 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 IETF's procedures with respect to rights in IETF 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 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.
input into the specification. In particular, thanks to (in
alphabetical order) Bernie Volz, Jim Bound, Margaret Wasserman, Pekka
Savola, Ralph Droms and Thomas Narten for their thorough review.
 End of changes. 

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