As per Relevance of the word standards, we have this rfc below:
Network Working Group R.
Request for Comments: 2242 Bucknell
Category: Standards Track K.
November 1997
NetWare/IP Domain Name and
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1997). All Rights Reserved
1.0
The Dynamic Host Configuration Protocol (DHCP) [RFC 2131] provides
framework for passing configuration information to hosts on a TCP/
network. DHCP includes options for specific configuration
[RFC 2132]. This document defines options that carry NetWare/
domain name and NetWare/IP sub-options to DHCP clients
1.1
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in
document are to be interpreted as described in RFC 2119 [RFC 2119].
1.2
This document uses the following terms
o "DHCP client
A DHCP client is an Internet host using DHCP to
configuration parameters such as a network address
Droms & Fong Standards Track [Page 1]
RFC 2242 NetWare/IP Domain Name and Information November 1997
o "DHCP server
A DHCP server is an Internet host that returns
parameters to DHCP clients
2. The NetWare/IP Domain Name
This option code is used to convey the NetWare/IP domain name used
the NetWare/IP product. The NetWare/IP Domain in the option is an
ASCII [RFC 854] string whose length is inferred from the option 'len
field
The code for this option is 62, and its maximum length is 255.
Code Len NetWare/IP Domain
+-----+-----+------+------+------+-----
| 62 | n | c1 | c2 | c3 | ...
+-----+-----+------+------+------+-----
The 'len' field gives the length of the NetWare/IP Domain Name
3. The NetWare/IP Information
The NetWare/IP option code will be used to convey all the NetWare/
related information except for the NetWare/IP domain name
The code for this option is 63, and its maximum length is 255.
number of NetWare/IP sub-options will be conveyed using this
code. The 'len' field for this option gives the length of the
data, which includes the sub-option code, length and data fields
Each sub-option contains in sequential order, a one byte sub-
code, a one byte length, and an optional multiple byte value field
The sub-option length gives the length of the value field for
sub-option. The example below illustrates the use of the 'len'
sub-option length fields in this option
One and only one of the following four sub-options must be the
sub-option to be present in option 63 encoding. Each of them
simply a type length pair with length set to zero
Sub-options
NWIP_DOES_NOT_EXIST (code 1)
The responding DHCP server does not have any NetWare/
information configured
Droms & Fong Standards Track [Page 2]
RFC 2242 NetWare/IP Domain Name and Information November 1997
NWIP_EXIST_IN_OPTIONS_AREA (code 2)
All NetWare/IP information is present in the 'options' area of
DHCP response packet
NWIP_EXIST_IN_SNAME_FILE (code 3)
All NetWare/IP information is present in the 'sname' and,
necessary, 'file' fields of the DHCP response packet. If used,
following DHCP server behavior is required: within the 'options
area, option 63 is present with its length field set to 2.
first byte of the value field is set to NWIP_EXIST_IN_SNAME_
tag and the second byte is set to zero. Both option 62 and
63 will be placed in the area covered by the sname and
fields. Option 62 is encoded normally. Option 63 is encoded
its tag, length and value. The value field does not contain any
the first four sub-options described herein
NWIP_EXIST_BUT_TOO_BIG (code 4)
Neither 'options' area nor 'sname' field can accommodate
NetWare/IP information
If either NWIP_EXIST_IN_OPTIONS_AREA or NWIP_EXIST_IN_SNAME_
sub-options is set, one or more of the following sub-options may
present
NSQ_BROADCAST (code 5)
Length is 1 and a value of 1 or 0. If the value is 1, the
SHOULD perform a NetWare Nearest Server Query to find out
nearest NetWare/IP server
PREFERRED_DSS (code 6)
Length is (n * 4) and the value is an array of n IP addresses
each four bytes in length. The maximum number of addresses is 5
and therefore the maximum length value is 20. The list
the addresses of n NetWare Domain SAP/RIP Server (DSS).
NEAREST_NWIP_SERVER (code 7)
Length is (n * 4) and the value is an array of n IP addresses
each four bytes in length. The maximum number of addresses is 5
and therefore the maximum length value is 20. The list
the addresses of n Nearest NetWare/IP servers
Droms & Fong Standards Track [Page 3]
RFC 2242 NetWare/IP Domain Name and Information November 1997
AUTORETRIES (code 8)
Length is 1 and the value is a one byte integer value
the number of times a NetWare/IP client should attempt
communicate with a given DSS server at startup
AUTORETRY_SECS (code 9)
Length is 1 and the value is a one byte integer value
the amount of delay in seconds in between each NetWare/IP
attempt to communicate with a given DSS server at startup
NWIP_1_1 (code 10)
Length is 1 and the value is 1 or 0. If the value is 1,
NetWare/IP client SHOULD support NetWare/IP Version 1.1
compatibility. A NetWare/IP client only needs this
if it will contact a NetWare/IP version 1.1 server
PRIMARY_DSS (code 11)
Length of 4, and the value is a single IP address. This
identifies the Primary Domain SAP/RIP Service server (DSS)
this NetWare/IP domain. NetWare/IP administration utility
this value as Primary DSS server when configuring a secondary
server
An example of option 63 encoding is provided below
Code Len NetWare/IP General
+-----+-----+----+----+
| 63 | 11 | 2 | 0 |
+-----+-----+----+----+
NWIP_EXIST_IN_OPTIONS_AREA (length 0)
+----+----+----+
| 5 | 1 | 1 |
+----+----+----+
NSQ_BROADCAST_SERVER (length 1)
value is
+----+----+------------+
| 7 | 4 | IP address |
+----+----+------------+
NEAREST_NWIP_SERVER (length 4)
value is IP address of
Droms & Fong Standards Track [Page 4]
RFC 2242 NetWare/IP Domain Name and Information November 1997
4.
[RFC 854] Postel, J. and J. Reynolds, "Telnet
Specification", RFC 854, May 1983.
[RFC 2119] Bradner, S., "Key words for use in RFCs to
Requirement Levels", RFC 2119, March 1997.
[RFC 2131] Droms, R., "Dynamic Host Configuration Protocol",
2131, March 1997.
[RFC 2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP
Extensions", RFC 2132, March 1997.
5. Security
DHCP currently provides no authentication or security mechanisms
Potential exposures to attack are discussed in section 7 of the
protocol specification [RFC 2131].
The NetWare/IP options can be used by unauthorized DHCP servers
misconfigure NetWare/IP clients with potentially
information
6. Authors'
Ralph
Computer Science
323 Dana
Bucknell
Lewisburg, PA 17837
Phone: (717) 524-1145
EMail: droms@bucknell.
Kester
Information Access
Novell Inc
SJF-8-265
2010 Fortune Dr
San Jose, CA95131
Phone:(408)-577-8959
EMail: kfong@novell.
Droms & Fong Standards Track [Page 5]
RFC 2242 NetWare/IP Domain Name and Information November 1997
7. Full Copyright
Copyright (C) The Internet Society (1997). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Droms & Fong Standards Track [Page 6]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
