1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
|
Network Working Group R. Droms
Request for Comments: 2242 Bucknell University
Category: Standards Track K. Fong
Novell
November 1997
NetWare/IP Domain Name and Information
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (1997). All Rights Reserved.
1.0 Abstract
The Dynamic Host Configuration Protocol (DHCP) [RFC 2131] provides a
framework for passing configuration information to hosts on a TCP/IP
network. DHCP includes options for specific configuration parameters
[RFC 2132]. This document defines options that carry NetWare/IP
domain name and NetWare/IP sub-options to DHCP clients.
1.1 Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC 2119].
1.2 Terminology
This document uses the following terms:
o "DHCP client"
A DHCP client is an Internet host using DHCP to obtain
configuration parameters such as a network address.
Droms & Fong Standards Track [Page 1]
^L
RFC 2242 NetWare/IP Domain Name and Information November 1997
o "DHCP server"
A DHCP server is an Internet host that returns configuration
parameters to DHCP clients.
2. The NetWare/IP Domain Name option
This option code is used to convey the NetWare/IP domain name used by
the NetWare/IP product. The NetWare/IP Domain in the option is an NVT
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 Name
+-----+-----+------+------+------+-----
| 62 | n | c1 | c2 | c3 | ...
+-----+-----+------+------+------+-----
The 'len' field gives the length of the NetWare/IP Domain Name.
3. The NetWare/IP Information option
The NetWare/IP option code will be used to convey all the NetWare/IP
related information except for the NetWare/IP domain name.
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
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
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
sub-option to be present in option 63 encoding. Each of them is
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/IP
information configured.
Droms & Fong Standards Track [Page 2]
^L
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 the
DHCP response packet.
NWIP_EXIST_IN_SNAME_FILE (code 3)
All NetWare/IP information is present in the 'sname' and, if
necessary, 'file' fields of the DHCP response packet. If used, the
following DHCP server behavior is required: within the 'options'
area, option 63 is present with its length field set to 2. The
first byte of the value field is set to NWIP_EXIST_IN_SNAME_FILE
tag and the second byte is set to zero. Both option 62 and option
63 will be placed in the area covered by the sname and file
fields. Option 62 is encoded normally. Option 63 is encoded with
its tag, length and value. The value field does not contain any of
the first four sub-options described herein.
NWIP_EXIST_BUT_TOO_BIG (code 4)
Neither 'options' area nor 'sname' field can accommodate the
NetWare/IP information.
If either NWIP_EXIST_IN_OPTIONS_AREA or NWIP_EXIST_IN_SNAME_FILE
sub-options is set, one or more of the following sub-options may be
present.
NSQ_BROADCAST (code 5)
Length is 1 and a value of 1 or 0. If the value is 1, the client
SHOULD perform a NetWare Nearest Server Query to find out its
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 contains
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 contains
the addresses of n Nearest NetWare/IP servers.
Droms & Fong Standards Track [Page 3]
^L
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 indicating
the number of times a NetWare/IP client should attempt to
communicate with a given DSS server at startup.
AUTORETRY_SECS (code 9)
Length is 1 and the value is a one byte integer value indicating
the amount of delay in seconds in between each NetWare/IP client
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, the
NetWare/IP client SHOULD support NetWare/IP Version 1.1
compatibility. A NetWare/IP client only needs this compatibility
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 field
identifies the Primary Domain SAP/RIP Service server (DSS) for
this NetWare/IP domain. NetWare/IP administration utility uses
this value as Primary DSS server when configuring a secondary DSS
server.
An example of option 63 encoding is provided below.
Code Len NetWare/IP General Info
+-----+-----+----+----+
| 63 | 11 | 2 | 0 |
+-----+-----+----+----+
NWIP_EXIST_IN_OPTIONS_AREA (length 0)
+----+----+----+
| 5 | 1 | 1 |
+----+----+----+
NSQ_BROADCAST_SERVER (length 1)
value is YES
+----+----+------------+
| 7 | 4 | IP address |
+----+----+------------+
NEAREST_NWIP_SERVER (length 4)
value is IP address of server
Droms & Fong Standards Track [Page 4]
^L
RFC 2242 NetWare/IP Domain Name and Information November 1997
4. References
[RFC 854] Postel, J. and J. Reynolds, "Telnet Protocol
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
2131, March 1997.
[RFC 2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", RFC 2132, March 1997.
5. Security considerations
DHCP currently provides no authentication or security mechanisms.
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.
6. Authors' addresses
Ralph Droms
Computer Science Department
323 Dana Engineering
Bucknell University
Lewisburg, PA 17837
Phone: (717) 524-1145
EMail: droms@bucknell.edu
Kester Fong
Information Access Division
Novell Inc.
SJF-8-265
2010 Fortune Dr,
San Jose, CA95131
Phone:(408)-577-8959
EMail: kfong@novell.com
Droms & Fong Standards Track [Page 5]
^L
RFC 2242 NetWare/IP Domain Name and Information November 1997
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.
Droms & Fong Standards Track [Page 6]
^L
|
