ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzakg_5.4.0.1/rzakgconceptoptions.xml

<?xml:stylesheet version="1.0" encoding="utf-8"?>
<?xml:stylesheet type="text/xsl" href="../rzahg/icdyntable.xsl"?>
<TABLE xmlns="x-schema:rzakgconceptoptions-schema.xml">
<TITLE>DHCP options lookup</TITLE>
<TH col="TD1">
Option number
</TH>
<TH col="TD2">
Option
</TH>
<TH col="TD3">
Description
</TH>
<TR><TD1 valign="top" width="11.224489795918368%">1</TD1><TD2 valign="top" width="17.346938775510203%">Subnet mask</TD2><TD3 valign="top" width="71.42857142857143%">The subnet mask option specifies the client's subnet
mask as per RFC 950. If both the subnet mask and the router option are specified
in a DHCP reply, the subnet mask option must be first.<p>The code for the
subnet mask option is 1, and its length is 4 octets.</p>
<br clear="none"></br><img src="rzakg530.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">2</TD1><TD2 valign="top" width="17.346938775510203%">Time offset</TD2><TD3 valign="top" width="71.42857142857143%">The time offset field specifies the offset of the client's
subnet in seconds from Coordinated Universal Time (UTC). The offset is expressed
as a two's complement 32-bit integer. A positive offset indicates a location
east of the zero meridian and a negative offset indicates a location west
of the zero meridian.<p>The code for the time offset option is 2, and its
length is 4 octets.</p>
<br clear="none"></br><img src="rzakg531.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">3</TD1><TD2 valign="top" width="17.346938775510203%">Router</TD2><TD3 valign="top" width="71.42857142857143%">The router option specifies a list of IP addresses for
routers on the client's subnet. Routers should be listed in order of preference.<p>The
code for the router option is 3. The minimum length for the router option
is 4 octets, and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg511.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">4</TD1><TD2 valign="top" width="17.346938775510203%">Time server</TD2><TD3 valign="top" width="71.42857142857143%">The time server option specifies a list of RFC 868 time
servers available to the client. Servers should be listed in order of preference.<p>The
code for the time server option is 4. The minimum length for this option is
4 octets, and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg512.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">5</TD1><TD2 valign="top" width="17.346938775510203%">Name server</TD2><TD3 valign="top" width="71.42857142857143%">The name server option specifies a list of IEN 116 name
servers available to the client. Servers should be listed in order of preference.<p>The
code for the name server option is 5. The minimum length for this option is
4 octets, and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg513.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">6</TD1><TD2 valign="top" width="17.346938775510203%">Domain Name Server</TD2><TD3 valign="top" width="71.42857142857143%">The domain name server option specifies a list of Domain
Name System (STD 13, RFC 1035) name servers available to the client. Servers
should be listed in order of preference.<p>The code for the domain name server
option is 6. The minimum length for this option is 4 octets, and the length
must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg514.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">7</TD1><TD2 valign="top" width="17.346938775510203%">Log server</TD2><TD3 valign="top" width="71.42857142857143%">The log server option specifies a list of MIT-LCS UDP
log servers available to the client. Servers should be listed in order of
preference.<p>The code for the log server option is 7. The minimum length
for this option is 4 octets, and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg515.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">8</TD1><TD2 valign="top" width="17.346938775510203%">Cookie server</TD2><TD3 valign="top" width="71.42857142857143%">The cookie server option specifies a list of RFC 865
cookie servers available to the client. Servers should be listed in order
of preference.<p>The code for the cookie server option is 8. The minimum length
for this option is 4 octets, and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg516.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">9</TD1><TD2 valign="top" width="17.346938775510203%">LPR server</TD2><TD3 valign="top" width="71.42857142857143%">The LPR server option specifies a list of RFC 1179 line
printer servers available to the client. Servers should be listed in order
of preference.<p>The code for the LPR server option is 9. The minimum length
for this option is 4 octets, and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg517.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">10</TD1><TD2 valign="top" width="17.346938775510203%">Impress server</TD2><TD3 valign="top" width="71.42857142857143%">The Impress server option specifies a list of Imagen
Impress servers available to the client. Servers should be listed in order
of preference.<p>The code for the Impress server option is 10. The minimum
length for this option is 4 octets, and the length must always be a multiple
of 4.</p>
<br clear="none"></br><img src="rzakg518.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">11</TD1><TD2 valign="top" width="17.346938775510203%">Resource location server</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies a list of RFC 887 Resource Location
servers available to the client. Servers should be listed in order of preference.<p>The
code for this option is 11. The minimum length for this option is 4 octets,
and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg519.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">12</TD1><TD2 valign="top" width="17.346938775510203%">Host name</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the name of the client. The name
might or might not be qualified with the local domain name (see section 3.17
for the preferred way to retrieve the domain name). See RFC 1035 for character
set restrictions.<p>The code for this option is 12, and its minimum length
is 1.</p>
<br clear="none"></br><img src="rzakg520.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">13</TD1><TD2 valign="top" width="17.346938775510203%">Boot file size</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the length in 512-octet blocks
of the default boot image for the client. The file length is specified as
an unsigned 16-bit integer.<p>The code for this option is 13, and its length
is 2.</p>
<br clear="none"></br><img src="rzakg541.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">14</TD1><TD2 valign="top" width="17.346938775510203%">Merit dump file</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the path-name of a file to which
the client's core image should be dumped in the event the client crashes.
The path is formatted as a character string consisting of characters from
the NVT ASCII character set.<p>The code for this option is 14. Its minimum
length is 1.</p>
<br clear="none"></br><img src="rzakg521.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">15</TD1><TD2 valign="top" width="17.346938775510203%">Domain name</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the domain name that client should
use when resolving hostnames through the Domain Name System.<p>The code for
this option is 15. Its minimum length is 1.</p>
<br clear="none"></br><img src="rzakg522.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">16</TD1><TD2 valign="top" width="17.346938775510203%">Swap server</TD2><TD3 valign="top" width="71.42857142857143%">This specifies the IP address of the client's swap server.<p>The
code for this option is 16, and its length is 4.</p>
<br clear="none"></br><img src="rzakg523.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">17</TD1><TD2 valign="top" width="17.346938775510203%">Root path</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the path-name that contains the
client's root disk. The path is formatted as a character string consisting
of characters from the NVT ASCII character set.<p>The code for this option
is 17. Its minimum length is 1.</p>
<br clear="none"></br><img src="rzakg524.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">18</TD1><TD2 valign="top" width="17.346938775510203%">Extensions path</TD2><TD3 valign="top" width="71.42857142857143%">A string to specify a file, retrievable via TFTP, which
contains information which can be interpreted in the same way as the 64-octet
vendor-extension field within the BOOTP response, with the following exceptions: <ul><li>The length of the file is unconstrained</li>
<li>All references to Tag 18 (that is, instances of the BOOTP
Extensions Path field) within the file are ignored.</li>
</ul>
<p>The code for this option is 18. Its minimum length is 1.</p>
<br clear="none"></br><img src="rzakg525.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">19</TD1><TD2 valign="top" width="17.346938775510203%">IP forwarding</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies whether the client should configure
its IP layer for packet forwarding. A value of 0 means disable IP forwarding,
and a value of 1 means enable IP forwarding.<p>The code for this option is
19, and its length is 1.</p>
<br clear="none"></br><img src="rzakg544.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">20</TD1><TD2 valign="top" width="17.346938775510203%">Non-Local source routing</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies whether the client should configure
its IP layer to allow forwarding of datagrams with non-local source routes.
A value of 0 means disallow forwarding of such datagrams, and a value of 1
means allow forwarding.<p>The code for this option is 20, and its length is
1.</p>
<br clear="none"></br><img src="rzakg545.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">21</TD1><TD2 valign="top" width="17.346938775510203%">Policy filter</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies policy filters for non-local source
routing. The filters consist of a list of IP addresses and masks which specify
destination/mask pairs with which to filter incoming source routes.<p>Any
source routed datagram whose next-hop address does not match one of the filters
should be discarded by the client.</p>
<p>The code for this option is 21. The
minimum length of this option is 8, and the length must be a multiple of 8.</p>
<br clear="none"></br><img src="rzakg510.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">22</TD1><TD2 valign="top" width="17.346938775510203%">Maximum datagram reassembly size</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the maximum size datagram that
the client should be prepared to reassemble. The size is specified as a 16-bit
unsigned integer. The minimum value legal value is 576.<p>The code for this
option is 22, and its length is 2.</p>
<br clear="none"></br><img src="rzakg542.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">23</TD1><TD2 valign="top" width="17.346938775510203%">Default IP time to live</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the default time-to-live that
the client should use on outgoing datagrams. The TTL is specified as an octet
with a value between 1 and 255.<p>The code for this option is 23, and its
length is 1.</p>
<br clear="none"></br><img src="rzakg546.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">24</TD1><TD2 valign="top" width="17.346938775510203%">Path MTU aging timeout</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the timeout (in seconds) to use
when aging Path MTU values discovered by the mechanism defined in RFC 1191.
The timeout is specified as a 32-bit unsigned integer.<p>The code for this
option is 24, and its length is 4.</p>
<br clear="none"></br><img src="rzakg532.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">25</TD1><TD2 valign="top" width="17.346938775510203%">Path MTU plateau table</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies a table of MTU sizes to use when
performing Path MTU Discovery as defined in RFC 1191. The table is formatted
as a list of 16-bit unsigned integers, ordered from smallest to largest. The
minimum MTU value cannot be smaller than 68.<p>The code for this option is
25. Its minimum length is 2, and the length must be a multiple of 2.</p>
<br clear="none"></br><img src="rzakg526.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">26</TD1><TD2 valign="top" width="17.346938775510203%">Interface MTU</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the MTU to use on this interface.
The MTU is specified as a 16-bit unsigned integer. The minimum legal value
for the MTU is 68.<p>The code for this option is 26, and its length is 2.</p>
<br clear="none"></br><img src="rzakg543.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">27</TD1><TD2 valign="top" width="17.346938775510203%">All subnets are local</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies whether the client can assume
that all subnets of the IP network to which the client is connected use the
same MTU as the subnet of that network to which the client is directly connected.
A value of 1 indicates that all subnets share the same MTU. A value of 0 means
that the client should assume that some subnets of the directly connected
network might have smaller MTUs.<p>The code for this option is 27, and its
length is 1.</p>
<br clear="none"></br><img src="rzakg547.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">28</TD1><TD2 valign="top" width="17.346938775510203%">Broadcast address</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the broadcast address in use on
the client's subnet. Legal values for broadcast addresses are specified in
section 3.2.1.3 of RFC 2132.<p>The code for this option is 28, and its length
is 4.</p>
<br clear="none"></br><img src="rzakg533.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">29</TD1><TD2 valign="top" width="17.346938775510203%">Perform mask discovery</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies whether the client should perform
subnet mask discovery using ICMP. A value of 0 indicates that the client should
not perform mask discovery. A value of 1 means that the client should perform
mask discovery.<p>The code for this option is 29, and its length is 1.</p>
<br clear="none"></br><img src="rzakg548.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">30</TD1><TD2 valign="top" width="17.346938775510203%">Mask supplier</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies whether the client should respond
to subnet mask requests using ICMP. A value of 0 indicates that the client
should not respond. A value of 1 means that the client should respond.<p>The
code for this option is 30, and its length is 1.</p>
<br clear="none"></br><img src="rzakg549.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">31</TD1><TD2 valign="top" width="17.346938775510203%">Perform router discovery</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies whether the client should solicit
routers using the Router Discovery mechanism defined in RFC 1256. A value
of 0 indicates that the client should not perform router discovery. A value
of 1 means that the client should perform router discovery.<p>The code for
this option is 31, and its length is 1.</p>
<br clear="none"></br><img src="rzakg550.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">32</TD1><TD2 valign="top" width="17.346938775510203%">Router solicitation address option</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the address to which the client
should transmit router solicitation requests.<p>The code for this option is
32, and its length is 4.</p>
<br clear="none"></br><img src="rzakg534.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">33</TD1><TD2 valign="top" width="17.346938775510203%">Static route</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies a list of static routes that the
client should install in its routing cache. If multiple routes to the same
destination are specified, they are listed in descending order of priority.<p>The
routes consist of a list of IP address pairs. The first address is the destination
address, and the second address is the router for the destination.</p>
<p>The
default route (0.0.0.0) is an illegal destination for a static route.</p>
<p>The
code for this option is 33. The minimum length of this option is 8, and the
length must be a multiple of 8.</p>
<br clear="none"></br><img src="rzakg509.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">34</TD1><TD2 valign="top" width="17.346938775510203%">Trailer encapsulation</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies whether the client should negotiate
the use of trailers (RFC 893) when using the ARP protocol. A value of 0 indicates
that the client should not attempt to use trailers. A value of 1 means that
the client should attempt to use trailers.<p>The code for this option is 34,
and its length is 1.</p>
<br clear="none"></br><img src="rzakg573.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">35</TD1><TD2 valign="top" width="17.346938775510203%">ARP cache timeout</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the timeout in seconds for ARP
cache entries. The time is specified as a 32-bit unsigned integer.<p>The code
for this option is 35, and its length is 4.</p>
<br clear="none"></br><img src="rzakg535.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">36</TD1><TD2 valign="top" width="17.346938775510203%">Ethernet encapsulation</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies whether the client should use
Ethernet Version 2 (RFC 894) or IEEE 802.3 (RFC 1042) encapsulation if the
interface is an Ethernet. A value of 0 indicates that the client should use
RFC 894 encapsulation. A value of 1 means that the client should use RFC 1042
encapsulation.<p>The code for this option is 36, and its length is 1.</p>
<br clear="none"></br><img src="rzakg551.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">37</TD1><TD2 valign="top" width="17.346938775510203%">TCP default TTL</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the default TTL that the client
should use when sending TCP segments. The value is represented as an 8-bit
unsigned integer. The minimum value is 1.<p>The code for this option is 37,
and its length is 1.</p>
<br clear="none"></br><img src="rzakg552.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">38</TD1><TD2 valign="top" width="17.346938775510203%">TCP keep-alive interval</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the interval (in seconds) that
the client TCP should wait before sending a keepalive message on a TCP connection.
The time is specified as a 32-bit unsigned integer. A value of zero indicates
that the client should not generate keepalive messages on connections unless
specifically requested by an application.<p>The code for this option is 38,
and its length is 4.</p>
<br clear="none"></br><img src="rzakg536.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">39</TD1><TD2 valign="top" width="17.346938775510203%">TCP keep-alive garbage</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the whether the client should
send TCP keepalive messages with a octet of garbage for compatibility with
older implementations. A value of 0 indicates that a garbage octet should
not be sent. A value of 1 indicates that a garbage octet should be sent.<p>The
code for this option is 39, and its length is 1.</p>
<br clear="none"></br><img src="rzakg553.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">40</TD1><TD2 valign="top" width="17.346938775510203%">Network information service domain</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the name of the client's NIS domain.
The domain is formatted as a character string consisting of characters from
the NVT ASCII character set.<p>The code for this option is 40. Its minimum
length is 1.</p>
<br clear="none"></br><img alt="" src="rzakg540.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">41</TD1><TD2 valign="top" width="17.346938775510203%">Network information servers</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies a list of IP addresses indicating
NIS servers available to the client. Servers should be listed in order of
preference.<p>The code for this option is 41. Its minimum length is 4, and
the length must be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg556.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">42</TD1><TD2 valign="top" width="17.346938775510203%">Network time protocol servers option</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies a list of IP addresses indicating
NTP servers available to the client. Servers should be listed in order of
preference.<p>The code for this option is 42. Its minimum length is 4, and
the length must be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg557.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">44</TD1><TD2 valign="top" width="17.346938775510203%">NetBIOS over TCP/IP name server</TD2><TD3 valign="top" width="71.42857142857143%">The NetBIOS name server (NBNS) option specifies a list
of RFC 1001/1002 NBNS name servers listed in order of preference.<p>The code
for this option is 44. The minimum length of the option is 4 octets, and the
length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg558.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">45</TD1><TD2 valign="top" width="17.346938775510203%">NetBIOS over TCP/IP datagram distribution server</TD2><TD3 valign="top" width="71.42857142857143%">The NetBIOS datagram distribution server (NBDD) option
specifies a list of RFC 1001/1002 NBDD servers listed in order of preference.<p>The
code for this option is 45. The minimum length of the option is 4 octets,
and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg559.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">46</TD1><TD2 valign="top" width="17.346938775510203%">NetBIOS over TCP/IP node type</TD2><TD3 valign="top" width="71.42857142857143%">The NetBIOS node type option allows NetBIOS over TCP/IP
clients which are configurable to be configured as described in RFC 1001/1002.
The value is specified as a single octet which identifies the client type
as follows:<br clear="none"></br><img src="rzakg554.gif"></img><br clear="none"></br><p>In the
above chart, the notation '0x' indicates a number in base-16 (hexadecimal).</p>
<p>The
code for this option is 46. The length of this option is always 1.</p>
<br clear="none"></br><img src="rzakg555.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">47</TD1><TD2 valign="top" width="17.346938775510203%">NetBIOS over TCP/IP scope</TD2><TD3 valign="top" width="71.42857142857143%">The NetBIOS scope option specifies the NetBIOS over
TCP/IP scope parameter for the client as specified in RFC 1001/1002.<p>The
code for this option is 47. The minimum length of this option is 1.</p>
<br clear="none"></br><img src="rzakg528.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">48</TD1><TD2 valign="top" width="17.346938775510203%">X Window System Font server</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies a list of X Window System Font
servers available to the client. Servers should be listed in order of preference.<p>The
code for this option is 48. The minimum length of this option is 4 octets,
and the length must be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg560.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">49</TD1><TD2 valign="top" width="17.346938775510203%">X Window System display manager</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies a list of IP addresses of systems
that are running the X Window System Display Manager and are available to
the client.<p>Addresses should be listed in order of preference.</p>
<p>The
code for the this option is 49. The minimum length of this option is 4, and
the length must be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg561.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">51</TD1><TD2 valign="top" width="17.346938775510203%">IP address lease time</TD2><TD3 valign="top" width="71.42857142857143%">This option is used in a client request (DHCPDISCOVER
or DHCPREQUEST) to allow the client to request a lease time for the IP address.
In a server reply (DHCPOFFER), a DHCP server uses this option to specify the
lease time it is willing to offer.<p>The time is in units of seconds, and
is specified as a 32-bit unsigned integer.</p>
<p>The code for this option
is 51, and its length is 4.</p>
<br clear="none"></br><img src="rzakg537.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">58</TD1><TD2 valign="top" width="17.346938775510203%">Renewal (T1) time value</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the time interval from address
assignment until the client transitions to the RENEWING state.<p>The value
is in units of seconds, and is specified as a 32-bit unsigned integer.</p>
<p>The
code for this option is 58, and its length is 4.</p>
<br clear="none"></br><img src="rzakg538.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">59</TD1><TD2 valign="top" width="17.346938775510203%">Rebinding (T2) time value option</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the time interval from address
assignment until the client transitions to the REBINDING state.<p>The value
is in units of seconds, and is specified as a 32-bit unsigned integer.</p>
<p>The
code for this option is 59, and its length is 4.</p>
<br clear="none"></br><img src="rzakg539.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">62</TD1><TD2 valign="top" width="17.346938775510203%">NetWare/IP domain name</TD2><TD3 valign="top" width="71.42857142857143%">Specifies the Netware/IP domain name.</TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">63</TD1><TD2 valign="top" width="17.346938775510203%">NetWare/IP</TD2><TD3 valign="top" width="71.42857142857143%">Specifies the NetWare sub-options you want. The range
is 1 to 255. Use option 62 to specify the NetWare/IP domain name.</TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">64</TD1><TD2 valign="top" width="17.346938775510203%">NIS domain name</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies the name of the client's NIS+
domain. The domain is formatted as a character string consisting of characters
from the NVT ASCII character set.<p>The code for this option is 64. Its minimum
length is 1.</p>
<br clear="none"></br><img src="rzakg527.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">65</TD1><TD2 valign="top" width="17.346938775510203%">NIS servers</TD2><TD3 valign="top" width="71.42857142857143%"><p>This option specifies a list of IP addresses indicating
NIS+ servers available to the client. Servers should be listed in order of
preference.</p>
<p>The code for this option is 65. Its minimum length is 4,
and the length must be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg562.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">66</TD1><TD2 valign="top" width="17.346938775510203%">Server name</TD2><TD3 valign="top" width="71.42857142857143%">This option is used to identify a TFTP server when the
'sname' field in the DHCP header has been used for DHCP options.<p>The code
for this option is 66, and its minimum length is 1.</p>
<br clear="none"></br><img src="rzakg571.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">67</TD1><TD2 valign="top" width="17.346938775510203%">Boot file name</TD2><TD3 valign="top" width="71.42857142857143%">This option is used to identify a bootfile when the
'file' field in the DHCP header has been used for DHCP options.<p>The code
for this option is 67, and its minimum length is 1.</p>
<br clear="none"></br><img src="rzakg572.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">68</TD1><TD2 valign="top" width="17.346938775510203%">Home address</TD2><TD3 valign="top" width="71.42857142857143%">This option specifies a list of IP addresses indicating
mobile IP home agents available to the client. Agents should be listed in
order of preference.<p>The code for this option is 68. Its minimum length
is 0 (indicating no home agents are available) and the length must be a multiple
of 4. It is expected that the usual length will be four octets, containing
a single home agent's address.</p>
<br clear="none"></br><img src="rzakg529.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">69</TD1><TD2 valign="top" width="17.346938775510203%">SMTP servers</TD2><TD3 valign="top" width="71.42857142857143%">The SMTP server option specifies a list of SMTP servers
available to the client. Servers should be listed in order of preference.<p>The
code for the SMTP server option is 69. The minimum length for this option
is 4 octets, and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg563.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">70</TD1><TD2 valign="top" width="17.346938775510203%">POP3 server</TD2><TD3 valign="top" width="71.42857142857143%"><p>The POP3 server option specifies a list of POP3 available
to the client. Servers should be listed in order of preference.</p>
<p>The
code for the POP3 server option is 70. The minimum length for this option
is 4 octets, and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg564.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">71</TD1><TD2 valign="top" width="17.346938775510203%">NNTP server</TD2><TD3 valign="top" width="71.42857142857143%">The NNTP server option specifies a list of NNTP available
to the client. Servers should be listed in order of preference.<p>The code
for the NNTP server option is 71. The minimum length for this option is 4
octets, and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg565.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">72</TD1><TD2 valign="top" width="17.346938775510203%">WWW server</TD2><TD3 valign="top" width="71.42857142857143%">The WWW server option specifies a list of WWW available
to the client. Servers should be listed in order of preference.<p>The code
for the WWW server option is 72. The minimum length for this option is 4 octets,
and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg566.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">73</TD1><TD2 valign="top" width="17.346938775510203%">Finger server</TD2><TD3 valign="top" width="71.42857142857143%">The Finger server option specifies a list of Finger
available to the client. Servers should be listed in order of preference.<p>The
code for the Finger server option is 73. The minimum length for this option
is 4 octets, and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg567.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">74</TD1><TD2 valign="top" width="17.346938775510203%">IRC server</TD2><TD3 valign="top" width="71.42857142857143%">The IRC server option specifies a list of IRC available
to the client. Servers should be listed in order of preference.<p>The code
for the IRC server option is 74. The minimum length for this option is 4 octets,
and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg568.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">75</TD1><TD2 valign="top" width="17.346938775510203%">StreetTalk server</TD2><TD3 valign="top" width="71.42857142857143%">The StreetTalk server option specifies a list of StreetTalk
servers available to the client. Servers should be listed in order of preference.<p>The
code for the StreetTalk server option is 75. The minimum length for this option
is 4 octets, and the length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg569.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">76</TD1><TD2 valign="top" width="17.346938775510203%">STDA server</TD2><TD3 valign="top" width="71.42857142857143%">The StreetTalk Directory Assistance (STDA) server option
specifies a list of STDA servers available to the client. Servers should be
listed in order of preference.<p>The code for the StreetTalk Directory Assistance
server option is 76. The minimum length for this option is 4 octets, and the
length must always be a multiple of 4.</p>
<br clear="none"></br><img src="rzakg570.gif"></img><br clear="none"></br></TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">77</TD1><TD2 valign="top" width="17.346938775510203%">User class</TD2><TD3 valign="top" width="71.42857142857143%">Specifies the class name of which the host is a member.
You must have previously defined this class to the DHCP server during DHCP
server configuration.</TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">78</TD1><TD2 valign="top" width="17.346938775510203%">Directory agent</TD2><TD3 valign="top" width="71.42857142857143%">Specifies the IP address of the directory agent if clients
use Service Location Protocol to transact messages.</TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">79</TD1><TD2 valign="top" width="17.346938775510203%">Service scope</TD2><TD3 valign="top" width="71.42857142857143%">Specifies the scope of the directory agent that uses
Service Location Protocol to respond to service request messages.</TD3></TR>
<TR><TD1 valign="top" width="11.224489795918368%">80</TD1><TD2 valign="top" width="17.346938775510203%">Naming authority</TD2><TD3 valign="top" width="71.42857142857143%">Specifies the naming authority for the directory agent
if clients use Service Location Protocol to transact messages. The naming
authority specifies the syntax for schemes that are used in URLs.</TD3></TR>
</TABLE>