⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc1533.txt

📁 著名的RFC文档,其中有一些文档是已经翻译成中文的的.
💻 TXT
📖 第 1 页 / 共 4 页
字号:
Network Working Group                                       S. AlexanderRequest for Comments: 1533                      Lachman Technology, Inc.Obsoletes: 1497, 1395, 1084, 1048                               R. DromsCategory: Standards Track                            Bucknell University                                                            October 1993               DHCP Options and BOOTP Vendor ExtensionsStatus of this Memo   This RFC 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" for the standardization state and status   of this protocol.  Distribution of this memo is unlimited.Abstract   The Dynamic Host Configuration Protocol (DHCP) [1] provides a   framework for passing configuration information to hosts on a TCP/IP   network.  Configuration parameters and other control information are   carried in tagged data items that are stored in the "options" field   of the DHCP message.  The data items themselves are also called   "options."   This document specifies the current set of DHCP options.  This   document will be periodically updated as new options are defined.    Each superseding document will include the entire current list of   valid options.   All of the vendor information extensions defined in RFC 1497 [2] may   be used as DHCP options.  The definitions given in RFC 1497 are   included in this document, which supersedes RFC 1497.  All of the   DHCP options defined in this document, except for those specific to   DHCP as defined in section 9, may be used as BOOTP vendor information   extensions.Table of Contents    1.  Introduction ..............................................  2    2.  BOOTP Extension/DHCP Option Field Format ..................  2    3.  RFC 1497 Vendor Extensions ................................  3    4.  IP Layer Parameters per Host .............................. 10    5.  IP Layer Parameters per Interface ........................  13    6.  Link Layer Parameters per Interface ....................... 16    7.  TCP Parameters ............................................ 17    8.  Application and Service Parameters ........................ 18Alexander & Droms                                               [Page 1]RFC 1533        DHCP Options and BOOTP Vendor Extensions    October 1993    9.  DHCP Extensions ........................................... 23   10.  Extensions ................................................ 27   11.  Acknowledgements .......................................... 28   12.  References ................................................ 28   13.  Security Considerations ................................... 19   14.  Authors' Addresses ........................................ 301. Introduction   This document specifies options for use with both the Dynamic Host   Configuration Protocol and the Bootstrap Protocol.   The full description of DHCP packet formats may be found in the DHCP   specification document [1], and the full description of BOOTP packet   formats may be found in the BOOTP specification document [3].  This   document defines the format of information in the last field of DHCP   packets ('options') and of BOOTP packets ('vend').  The remainder of   this section defines a generalized use of this area for giving   information useful to a wide class of machines, operating systems and   configurations. Sites with a single DHCP or BOOTP server that is   shared among heterogeneous clients may choose to define other, site-   specific formats for the use of the 'options' field.   Section 2 of this memo describes the formats of DHCP options and   BOOTP vendor extensions.  Section 3 describes options defined in   previous documents for use with BOOTP (all may also be used with   DHCP).  Sections 4-8 define new options intended for use with both   DHCP and BOOTP. Section 9 defines options used only in DHCP.   References further describing most of the options defined in sections   2-6 can be found in section 12.  The use of the options defined in   section 9 is described in the DHCP specification [1].   Information on registering new options is contained in section 10.2. BOOTP Extension/DHCP Option Field Format   DHCP options have the same format as the BOOTP "vendor extensions"   defined in RFC 1497 [2].  Options may be fixed length or variable   length.  All options begin with a tag octet, which uniquely   identifies the option.  Fixed-length options without data consist of   only a tag octet.  Only options 0 and 255 are fixed length.  All   other options are variable-length with a length octet following the   tag octet.  The value of the length octet does not include the two   octets specifying the tag and length.  The length octet is followed   by "length" octets of data.  In the case of some variable-length   options the length field is a constant but must still be specified.Alexander & Droms                                               [Page 2]RFC 1533        DHCP Options and BOOTP Vendor Extensions    October 1993   Any options defined subsequent to this document should contain a   length octet even if the length is fixed or zero.   All multi-octet quantities are in network byte-order.   When used with BOOTP, the first four octets of the vendor information   field have been assigned to the "magic cookie" (as suggested in RFC   951).  This field identifies the mode in which the succeeding data is   to be interpreted.  The value of the magic cookie is the 4 octet   dotted decimal 99.130.83.99 (or hexadecimal number 63.82.53.63) in   network byte order.   All of the "vendor extensions" defined in RFC 1497 are also DHCP   options.   Option codes 128 to 254 (decimal) are reserved for site-specific   options.   Except for the options in section 9, all options may be used with   either DHCP or BOOTP.   Many of these options have their default values specified in other   documents.  In particular, RFC 1122 [4] specifies default values for   most IP and TCP configuration parameters.3. RFC 1497 Vendor Extensions   This section lists the vendor extensions as defined in RFC 1497.   They are defined here for completeness.3.1. Pad Option   The pad option can be used to cause subsequent fields to align on   word boundaries.   The code for the pad option is 0, and its length is 1 octet.    Code   +-----+   |  0  |   +-----+Alexander & Droms                                               [Page 3]RFC 1533        DHCP Options and BOOTP Vendor Extensions    October 19933.2. End Option   The end option marks the end of valid information in the vendor   field.  Subsequent octets should be filled with pad options.   The code for the end option is 255, and its length is 1 octet.    Code   +-----+   | 255 |   +-----+3.3. Subnet Mask   The subnet mask option specifies the client's subnet mask as per RFC   950 [5].   If both the subnet mask and the router option are specified in a DHCP   reply, the subnet mask option MUST be first.   The code for the subnet mask option is 1, and its length is 4 octets.    Code   Len        Subnet Mask   +-----+-----+-----+-----+-----+-----+   |  1  |  4  |  m1 |  m2 |  m3 |  m4 |   +-----+-----+-----+-----+-----+-----+3.4. Time Offset   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 signed 32-bit integer.   The code for the time offset option is 2, and its length is 4 octets.    Code   Len        Time Offset   +-----+-----+-----+-----+-----+-----+   |  2  |  4  |  n1 |  n2 |  n3 |  n4 |   +-----+-----+-----+-----+-----+-----+Alexander & Droms                                               [Page 4]RFC 1533        DHCP Options and BOOTP Vendor Extensions    October 19933.5. Router Option   The router option specifies a list of IP addresses for routers on the   client's subnet.  Routers SHOULD be listed in order of preference.   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.    Code   Len         Address 1               Address 2   +-----+-----+-----+-----+-----+-----+-----+-----+--   |  3  |  n  |  a1 |  a2 |  a3 |  a4 |  a1 |  a2 |  ...   +-----+-----+-----+-----+-----+-----+-----+-----+--3.6. Time Server Option   The time server option specifies a list of RFC 868 [6] time servers   available to the client.  Servers SHOULD be listed in order of   preference.   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.    Code   Len         Address 1               Address 2   +-----+-----+-----+-----+-----+-----+-----+-----+--   |  4  |  n  |  a1 |  a2 |  a3 |  a4 |  a1 |  a2 |  ...   +-----+-----+-----+-----+-----+-----+-----+-----+--3.7. Name Server Option   The name server option specifies a list of IEN 116 [7] name servers   available to the client.  Servers SHOULD be listed in order of   preference.   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.    Code   Len         Address 1               Address 2   +-----+-----+-----+-----+-----+-----+-----+-----+--   |  5  |  n  |  a1 |  a2 |  a3 |  a4 |  a1 |  a2 |  ...   +-----+-----+-----+-----+-----+-----+-----+-----+--Alexander & Droms                                               [Page 5]RFC 1533        DHCP Options and BOOTP Vendor Extensions    October 19933.8. Domain Name Server Option   The domain name server option specifies a list of Domain Name System   (STD 13, RFC 1035 [8]) name servers available to the client.  Servers   SHOULD be listed in order of preference.   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.    Code   Len         Address 1               Address 2   +-----+-----+-----+-----+-----+-----+-----+-----+--   |  6  |  n  |  a1 |  a2 |  a3 |  a4 |  a1 |  a2 |  ...   +-----+-----+-----+-----+-----+-----+-----+-----+--3.9. Log Server Option   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.   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.    Code   Len         Address 1               Address 2   +-----+-----+-----+-----+-----+-----+-----+-----+--   |  7  |  n  |  a1 |  a2 |  a3 |  a4 |  a1 |  a2 |  ...   +-----+-----+-----+-----+-----+-----+-----+-----+--3.10. Cookie Server Option   The cookie server option specifies a list of RFC 865 [9] cookie   servers available to the client.  Servers SHOULD be listed in order   of preference.   The code for the log server option is 8.  The minimum length for this   option is 4 octets, and the length MUST always be a multiple of 4.    Code   Len         Address 1               Address 2   +-----+-----+-----+-----+-----+-----+-----+-----+--   |  8  |  n  |  a1 |  a2 |  a3 |  a4 |  a1 |  a2 |  ...   +-----+-----+-----+-----+-----+-----+-----+-----+--Alexander & Droms                                               [Page 6]RFC 1533        DHCP Options and BOOTP Vendor Extensions    October 19933.11. LPR Server Option   The LPR server option specifies a list of RFC 1179 [10] line printer   servers available to the client.  Servers SHOULD be listed in order   of preference.   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.    Code   Len         Address 1               Address 2   +-----+-----+-----+-----+-----+-----+-----+-----+--   |  9  |  n  |  a1 |  a2 |  a3 |  a4 |  a1 |  a2 |  ...   +-----+-----+-----+-----+-----+-----+-----+-----+--3.12. Impress Server Option   The Impress server option specifies a list of Imagen Impress servers   available to the client.  Servers SHOULD be listed in order of   preference.   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.    Code   Len         Address 1               Address 2   +-----+-----+-----+-----+-----+-----+-----+-----+--   |  10 |  n  |  a1 |  a2 |  a3 |  a4 |  a1 |  a2 |  ...   +-----+-----+-----+-----+-----+-----+-----+-----+--3.13. Resource Location Server Option   This option specifies a list of RFC 887 [11] Resource Location   servers available to the client.  Servers SHOULD be listed in order   of preference.   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.    Code   Len         Address 1               Address 2   +-----+-----+-----+-----+-----+-----+-----+-----+--   |  11 |  n  |  a1 |  a2 |  a3 |  a4 |  a1 |  a2 |  ...   +-----+-----+-----+-----+-----+-----+-----+-----+--Alexander & Droms                                               [Page 7]RFC 1533        DHCP Options and BOOTP Vendor Extensions    October 19933.14. Host Name Option   This option specifies the name of the client.  The name may or may   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.   The code for this option is 12, and its minimum length is 1.    Code   Len                 Host Name   +-----+-----+-----+-----+-----+-----+-----+-----+--   |  12 |  n  |  h1 |  h2 |  h3 |  h4 |  h5 |  h6 |  ...   +-----+-----+-----+-----+-----+-----+-----+-----+--3.15. Boot File Size Option   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.   The code for this option is 13, and its length is 2.    Code   Len   File Size

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -