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

📄 rfc1060.txt

📁 中、英文RFC文档大全打包下载完全版 .
💻 TXT
📖 第 1 页 / 共 5 页
字号:
Reynolds & Postel                                              [Page 19]RFC 1060                    Assigned Numbers                  March 1990                         IANA ETHERNET ADDRESS BLOCK   The IANA owns an Ethernet address block which may be used for   multicast address asignments or other special purposes.   The address block in IEEE binary is (which is in bit transmission   order):                       0000 0000 0000 0000 0111 1010   In the normal Internet dotted decimal notation this is 0.0.94 since   the bytes are transmitted higher order first and bits within bytes   are transmitted lower order first (see "Data Notation" in the   Introduction).   IEEE CSMA/CD and Token Bus bit transmission order: 00 00 5E   IEEE Token Ring bit transmission order: 00 00 7A   Appearance on the wire (bits transmitted from left to right):       0                           23                            47       |                           |                             |       1000 0000 0000 0000 0111 1010 xxxx xxx0 xxxx xxxx xxxx xxxx       |                                     |       Multicast Bit                         0 = Internet Multicast                                             1 = Assigned by IANA for                                                 other uses   Appearance in memory (bits transmitted right-to-left within octets,   octets transmitted left-to-right):       0                           23                            47       |                           |                             |       0000 0001 0000 0000 0101 1110 0xxx xxxx xxxx xxxx xxxx xxxx               |                     |               Multicast Bit         0 = Internet Multicast                                     1 = Assigned by IANA for other uses   The latter representation corresponds to the Internet standard bit-   order, and is the format that most programmers have to deal with.   Using this representation, the range of Internet Multicast addresses   is:          01-00-5E-00-00-00  to  01-00-5E-7F-FF-FF  in hex, or          1.0.94.0.0.0  to  1.0.94.127.255.255  in dotted decimalReynolds & Postel                                              [Page 20]RFC 1060                    Assigned Numbers                  March 1990                             IP TOS PARAMETERS   This documents the default Type-of-Service values that are currently   recommended for the most important Internet protocols.   There are three binary TOS attributes: low delay, high throughput,   and high reliability; in each case, an attribute bit is turned on to   indicate "better".  The three attributes cannot all be optimized   simultanously, and in fact the TOS algorithms that have been   discussed tend to make "better" values of the attributes mutually   exclusive.  Therefore, the recommended values have at most one bit   on.   Generally, protocols which are involved in direct interaction with a   human should select low delay, while data transfers which may involve   large blocks of data are need high throughput.  Finally, high   reliability is most important for datagram-based Internet management   functions.   Application protocols not included in these tables should be able to   make appropriate choice of low delay (1 0 0) or high throughput (0 1   0).   The following are recommended values for TOS:                  ----- Type-of-Service Value -----                    Low        High         High      Protocol     Delay    Throughput  Reliability      TELNET (1)    1           0           0      FTP        Control     1           0           0        Data (2)    0           1           0      TFTP          1           0           0      SMTP  (3)        Cmd phase   1           0           0        DATA phase  0           1           0      Domain Name Service        UDP Query   1           0           0        TCP Query   0           0           0        Zone Tnsfr  0           1           0      NNTP          0           0           0Reynolds & Postel                                              [Page 21]RFC 1060                    Assigned Numbers                  March 1990      ICMP        Errors      0           0           0        Queries     0           0           0      Any IGP       0           0           1      EGP           0           0           0      SNMP          0           0           1      BOOTP         0           0           0      Notes:      (1)  Includes all interactive user protocols (e.g., rlogin).      (2)  Includes all bulk data transfer protocols (e.g., rcp).      (3)  If the implementation does not support changing the TOS           during the lifetime of the connection, then the recommended           TOS on opening the connection is (0,0,0).Reynolds & Postel                                              [Page 22]RFC 1060                    Assigned Numbers                  March 1990                         IP TIME TO LIVE PARAMETER   The current recommended default TTL for the Internet Protocol (IP)   RFC-791 [45,105] is 32.Reynolds & Postel                                              [Page 23]RFC 1060                    Assigned Numbers                  March 1990                         DOMAIN SYSTEM PARAMETERS   The Internet Domain Naming System (DOMAIN) includes several   parameters.  These are documented in RFC-1034, [81] and RFC-1035   [82].  The CLASS parameter is listed here.  The per CLASS parameters   are defined in separate RFCs as indicated.   Domain System Parameters:      Decimal   Name                                          References      -------   ----                                          ----------            0   Reserved                                           [PM1]            1   Internet (IN)                                   [81,PM1]            2   Unassigned                                         [PM1]            3   Chaos (CH)                                         [PM1]            4   Hessoid (HS)                                       [PM1]      5-65534   Unassigned                                         [PM1]        65535   ReservedReynolds & Postel                                              [Page 24]RFC 1060                    Assigned Numbers                  March 1990                               BOOTP PARAMETERS   The Bootstrap Protocol (BOOTP) RFC-951 [36] describes an IP/UDP   bootstrap protocol (BOOTP) which allows a diskless client machine to   discover its own IP address, the address of a server host, and the   name of a file to be loaded into memory and executed.  The BOOTP   Vendor Information Extensions RFC-1084 [117] proposes an addition to   the Bootstrap Protocol (BOOTP).   Vendor Extensions are listed below:      Tag     Name          Data Length    Meaning          References      ---     ----          -----------    -------          ----------       0      Pad               0          None       1      Subnet Mask       4          Subnet Mask Value       2      Time Zone         4          Time Offset in                                           Seconds from UTC       3      Gateways          N          N/4 Gateway addresses       4      Time Server       N          N/4 Timeserver addresses       5      Name Server       N          N/4 IEN-116 Server addresses       6      Domain Server     N          N/4 DNS Server addresses       7      Log Server        N          N/4 Logging Server addresses       8      Quotes Server     N          N/4 Quotes Server addresses       9      LPR Server        N          N/4 Printer Server addresses      10      Impress Server    N          N/4 Impress Server addresses      11      RLP Server        N          N/4 RLP Server addresses      12      Hostname          N          Hostname string      13      Boot File Size    2          Size of boot file in 512 byte                                           checks      14      Merit Dump File              Client to dump and name                                           the file to dump it to      15-127  Unassigned      128-154 Reserved      255     End               0          NoneReynolds & Postel                                              [Page 25]RFC 1060                    Assigned Numbers                  March 1990                       NETWORK MANAGEMENT PARAMETERS   For the management of hosts and gateways on the Internet a data   structure for the information has been defined.  This data structure   should be used with any of several possible management protocols, such   as the "Simple Network Management Protocol" (SNMP) RFC-1098 [15], or   the "Common Management Information Protocol over TCP" (CMOT) [142].   The data structure is the "Structure and Indentification of Management   Information for TCP/IP-based Internets" (SMI) RFC-1065 [120], and the   "Management Information Base for Network Management of TCP/IP-based   Internets" (MIB) [121].   The SMI includes the provision for parameters or codes to indicate

⌨️ 快捷键说明

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