draft-ietf-dhc-netware-options-00.txt   rfc2242.txt 
Network Working Group R. Droms Network Working Group R. Droms
INTERNET DRAFT Bucknell University Request for Comments: 2242 Bucknell University
K. Fong Category: Standards Track K. Fong
Novell Novell
July 1997 November 1997
Expires January 1998
Netware/IP Domain Name and Information NetWare/IP Domain Name and Information
<draft-ietf-dhc-netware-options-00.txt>
Status of this memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document specifies an Internet standards track protocol for the
documents of the Internet Engineering Task Force (IETF), its areas, Internet community, and requests discussion and suggestions for
and its working groups. Note that other groups may also distribute improvements. Please refer to the current edition of the "Internet
working documents as Internet-Drafts. Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Internet-Drafts are draft documents valid for a maximum of six months Copyright Notice
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.''
To learn the current status of any Internet-Draft, please check the Copyright (C) The Internet Society (1997). All Rights Reserved.
``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast).
1.0 Abstract 1.0 Abstract
The Dynamic Host Configuration Protocol (DHCP) [RFC 2131] provides a The Dynamic Host Configuration Protocol (DHCP) [RFC 2131] provides a
framework for passing configuration information to hosts on a TCP/IP framework for passing configuration information to hosts on a TCP/IP
network. DHCP includes options for specific configuration parameters network. DHCP includes options for specific configuration parameters
[RFC 2132]. This document defines options that carry Netware/IP [RFC 2132]. This document defines options that carry NetWare/IP
domain name and Netware/IP sub-options to DHCP clients. domain name and NetWare/IP sub-options to DHCP clients.
1.1 Requirements 1.1 Requirements
Throughout this document, the words that are used to define the The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
significance of particular requirements are capitalized. These words "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this
are: document are to be interpreted as described in RFC 2119 [RFC 2119].
o "MUST"
This word or the adjective "REQUIRED" means that the
item is an absolute requirement of this specification.
o "MUST NOT"
This phrase means that the item is an absolute prohibition
of this specification.
o "SHOULD"
This word or the adjective "RECOMMENDED" means that there
may exist valid reasons in particular circumstances to ignore
this item, but the full implications should be understood and
the case carefully weighed before choosing a different course.
o "SHOULD NOT"
This phrase means that there may exist valid reasons in
particular circumstances when the listed behavior is acceptable
or even useful, but the full implications should be understood
and the case carefully weighed before implementing any behavior
described with this label.
o "MAY"
This word or the adjective "OPTIONAL" means that this item is
truly optional. One vendor may choose to include the item
because a particular marketplace requires it or because it
enhances the product, for example; another vendor may omit the
same item.
1.2 Terminology 1.2 Terminology
This document uses the following terms: This document uses the following terms:
o "DHCP client" o "DHCP client"
A DHCP client is an Internet host using DHCP to obtain A DHCP client is an Internet host using DHCP to obtain
configuration parameters such as a network address. configuration parameters such as a network address.
skipping to change at page 3, line 14 skipping to change at page 2, line 24
ASCII [RFC 854] string whose length is inferred from the option 'len' ASCII [RFC 854] string whose length is inferred from the option 'len'
field. field.
The code for this option is 62, and its maximum length is 255. The code for this option is 62, and its maximum length is 255.
Code Len NetWare/IP Domain Name Code Len NetWare/IP Domain Name
+-----+-----+------+------+------+----- +-----+-----+------+------+------+-----
| 62 | n | c1 | c2 | c3 | ... | 62 | n | c1 | c2 | c3 | ...
+-----+-----+------+------+------+----- +-----+-----+------+------+------+-----
The 'len' field gives the length of the NetWare/IP Domain Name.
3. The NetWare/IP Information option 3. The NetWare/IP Information option
The NetWare/IP option code will be used to convey all the NetWare/IP The NetWare/IP option code will be used to convey all the NetWare/IP
related information except for the NetWare/IP domain name. related information except for the NetWare/IP domain name.
The code for this option is 63, and its maximum length is 255. A The code for this option is 63, and its maximum length is 255. A
number of NetWare/IP sub-options will be conveyed using this option number of NetWare/IP sub-options will be conveyed using this option
code. code. The 'len' field for this option gives the length of the option
data, which includes the sub-option code, length and data fields.
Each sub-option contains in sequential order, a one byte sub-option Each sub-option contains in sequential order, a one byte sub-option
code, a one byte length, and an optional multiple byte value field. code, a one byte length, and an optional multiple byte value field.
The sub-option length gives the length of the value field for the
sub-option. The example below illustrates the use of the 'len' and
sub-option length fields in this option.
One and only one of the following four sub-options must be the first One and only one of the following four sub-options must be the first
sub-option to be present in option 63 encoding. Each of them is sub-option to be present in option 63 encoding. Each of them is
simply a type length pair with length set to zero. simply a type length pair with length set to zero.
Sub-options: Sub-options:
NWIP_DOES_NOTE_EXIST (code 1) NWIP_DOES_NOT_EXIST (code 1)
The responding DHCP server does not have any NetWare/IP The responding DHCP server does not have any NetWare/IP
information configured. information configured.
NWIP_EXIST_IN_OPTIONS_AREA (code 2) NWIP_EXIST_IN_OPTIONS_AREA (code 2)
All NetWare/IP information is present in the 'options' area of the All NetWare/IP information is present in the 'options' area of the
DHCP response packet. DHCP response packet.
NWIP_EXIST_IN_SNAME_FILE (code 3) NWIP_EXIST_IN_SNAME_FILE (code 3)
skipping to change at page 5, line 41 skipping to change at page 5, line 10
| 7 | 4 | IP address | | 7 | 4 | IP address |
+----+----+------------+ +----+----+------------+
NEAREST_NWIP_SERVER (length 4) NEAREST_NWIP_SERVER (length 4)
value is IP address of server value is IP address of server
4. References 4. References
[RFC 854] Postel, J. and J. Reynolds, "Telnet Protocol [RFC 854] Postel, J. and J. Reynolds, "Telnet Protocol
Specification", RFC 854, May 1983. Specification", RFC 854, May 1983.
[RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997.
[RFC 2131] Droms, R., "Dynamic Host Configuration Protocol", RFC [RFC 2131] Droms, R., "Dynamic Host Configuration Protocol", RFC
2131, March 1997. 2131, March 1997.
[RFC 2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor [RFC 2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", RFC 2132. Extensions", RFC 2132, March 1997.
5. Security considerations 5. Security considerations
These options can be used by unauthorized DHCP servers to DHCP currently provides no authentication or security mechanisms.
misconfigure Netware/IP clients with potentially disruptive Potential exposures to attack are discussed in section 7 of the DHCP
protocol specification [RFC 2131].
The NetWare/IP options can be used by unauthorized DHCP servers to
misconfigure NetWare/IP clients with potentially disruptive
information. information.
6. Authors' addresses 6. Authors' addresses
Ralph Droms Ralph Droms
Computer Science Department Computer Science Department
323 Dana Engineering 323 Dana Engineering
Bucknell University Bucknell University
Lewisburg, PA 17837 Lewisburg, PA 17837
skipping to change at line 259 skipping to change at page 6, line 4
Kester Fong Kester Fong
Information Access Division Information Access Division
Novell Inc. Novell Inc.
SJF-8-265 SJF-8-265
2010 Fortune Dr, 2010 Fortune Dr,
San Jose, CA95131 San Jose, CA95131
Phone:(408)-577-8959 Phone:(408)-577-8959
EMail: kfong@novell.com EMail: kfong@novell.com
7. Full Copyright Statement
Copyright (C) The Internet Society (1997). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
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
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS 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.
 End of changes. 17 change blocks. 
63 lines changed or deleted 35 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/