draft-ietf-dhc-dhcpv6-opt-nisconfig-01.txt   draft-ietf-dhc-dhcpv6-opt-nisconfig-02.txt 
Network Working Group A.K. Vijayabhaskar Network Working Group A.K. Vijayabhaskar
Internet-Draft Hewlett-Packard Internet-Draft Hewlett-Packard
Expires: November 10, 2002 10 May 2002 Expires: August 26, 2003 26 Feb 2003
NIS Configuration Options for DHCPv6 NIS Configuration Options for DHCPv6
draft-ietf-dhc-dhcpv6-opt-nisconfig-01.txt draft-ietf-dhc-dhcpv6-opt-nisconfig-02.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. 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 August 17, 2002. This Internet-Draft will expire on August 26, 2003.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). 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 NIS-related configuration
information in DHCPv6: NIS Servers, NIS+ Servers, NIS Client Domain information in DHCPv6: NIS Servers, NIS+ Servers, NIS Client Domain
Name, NIS+ Client Domain name. Name, NIS+ Client Domain name.
1. Introduction 1. Introduction
This document describes four options for configuration information This document describes four options for configuration information
related to Network Information Service (NIS) in DHCPv6 [2]. related to Network Information Service (NIS) in DHCPv6 [1].
2. Requirements 2. Requirements
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, when they appear in this
document, are to be interpreted as described in RFC 2119 [1] document, are to be interpreted as described in RFC 2119 [2]
3. Terminology 3. Terminology
This document uses terminology specific to IPv6 and DHCPv6 as defined This document uses terminology specific to IPv6 and DHCPv6 as defined
in section "Terminology" of the DHCP specification. in section "Terminology" of the DHCP specification.
4. Network Information Service (NIS) Servers option 4. Network Information Service (NIS) Servers option
The Network Information Service Servers option provides a list of The Network Information Service Servers option provides a list of
one or more IP addresses of NIS servers available to the client. The one or more IP addresses of NIS servers available to the client. The
skipping to change at page 3, line 54 skipping to change at page 3, line 54
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 [2]. specification [1].
7. Network Information Service V2 (NIS+) Domain Name option 7. 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 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
skipping to change at page 4, line 29 skipping to change at page 4, line 29
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 [2]. specification [1].
8. Appearance of these option 8. Appearance of these option
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 appear only in the following messages: Solicit, options MUST appear only in the following messages: Solicit,
Advertise, Request, Confirm, Renew, Rebind, Information-Request, Advertise, Request, Confirm, Renew, Rebind, Information-Request and
Reply. Reply.
The option number for these options MAY appear in the Option Request
Option [1] in the following messages: Solicit, Request, Confirm, Renew,
Rebind, Information-Request and Reconfigure.
9. Security Considerations 9. 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 DHCP server to assign invalid NIS options may be used by an intruder DHCP server to assign invalid NIS
parameters, resulting in clients unable to use NIS. parameters, resulting in clients unable to use NIS.
To avoid attacks through these options, the DHCP client SHOULD use To avoid attacks through these options, the DHCP client SHOULD use
authenticated DHCP (see section "Authentication of DHCP messages" authenticated DHCP (see section "Authentication of DHCP messages"
in the DHCPv6 specification [2]). in the DHCPv6 specification [1]).
10. IANA Considerations 10. IANA Considerations
IANA is requested to assign an option code to these options from the IANA is requested to assign an option code to these options from the
option-code space defined in section "DHCPv6 Options" of the DHCPv6 option-code space defined in section "DHCPv6 Options" of the DHCPv6
specification [2]. specification [1].
References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 11. Normative References
Levels", BCP 14, RFC 2119, March 1997.
[2] 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)", draft-ietf-dhc-dhcpv6-23 (work in progress), February (DHCPv6)", draft-ietf-dhc-dhcpv6-28 (work in progress), November
2002. 2002.
12. Informative References
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
Author's Addresses Author's Addresses
Vijayabhaskar A K Vijayabhaskar A K
Hewlett-Packard ESD-I Hewlett-Packard ESD-I
29, Cunningham Road 29, Cunningham Road
Bangalore - 560052 Bangalore - 560052
India India
Phone: +91-80-2051424 Phone: +91-80-2053085
EMail: vijayak@india.hp.com E-Mail: vijayak@india.hp.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). 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
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
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 Jim Bound and input into the specification. In particular, thanks to Jim Bound and
Ralph Droms for their thorough review. Ralph Droms and Bernie Volz 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/