| Digital UNIX | ||
|---|---|---|
| Prev | Appendix A. Conformance to Internet Host Requirements | Next |
RFC 1122 covers requirements for communication protocols for the data link, internetworking, and transport layers of host Internet software. RFC 1123 covers requirements for the application and support protocols for Internet host software.
This section contains tables that list and briefly describe the RFCs that Digital UNIX was validated against and that are referenced in the Host Requirement RFCs. Additionally, Table A-8 and Table A-9 list the total must/must not level requirements explicitly stated by the Host Requirements RFCs.
Table A-1 lists the RFCs that RFC 1122 references for the link layer. For a discussion of link layer requirements, see Chapter 2 of RFC 1122.
Table A-1. Referenced RFCs for the Link Layer
| Referenced RFC[a] | Description |
|---|---|
| RFC 1042: Internet Protocol on IEEE 802 (IP-IEEE) | Specifies a standard method of encapsulating the IP datagrams and ARP requests and replies on IEEE 802 Networks. |
| RFC 894: Internet Protocol on Ethernet Networks (IP-E) | Specifies a standard method of encapsulating IP datagrams on an Ethernet. |
| RFC 826: Address Resolution Protocol (ARP) | Presents a method for converting protocol addresses (IP addresses) to local network addresses (Ethernet addresses). |
| Notes: a. Digital UNIX is also validated against the following RFCs that are not referenced in RFC 1122:
| |
[a] Digital UNIX is also validated against the following RFCs that are not referenced in RFC 1122:
RFC 1103: Transmission of IP over FDDI (IP-FDDI)
RFC 1055: A Nonstandard for Transmission of IP Datagrams Over Serial Lines: SLIP
Table A-2 lists the RFCs that RFC 1122 references for the Internet layer. For a discussion of Internet layer requirements, see Chapter 3 of RFC 1122.
Table A-2. Referenced RFCs for the Internet Layer
| Referenced RFC | Description |
|---|---|
| RFC 1112: Host Extensions for IP Multicasting (IGMP) | Specifies the extensions required of a host implementation of the IP to support multicasting. |
| RFC 1009: [a] Requirements for Internet Gateways | Documents the requirements for IP routers connected to the Internet. |
| RFC 950: Internet Standard Subnetting Procedures | Discusses standards for subnet addressing within internet networks. |
| RFC 792: Internet Control Message Protocol (ICMP) | Describes a protocol for exchanging informational and error messages between hosts, or between gateways and hosts. |
| RFC 791: Internet Protocol (IP) | Specifies an unreliable connectionless protocol for the delivery of datagrams between systems. |
| Notes: a. RFC 1009: Requirements for Internet Gateways references the Exterior Gateway Protocol (EGP) and the Routing Information Protocol (RIP). The EGP is described in RFC 904 and the RIP is described in RFC 1058. | |
[a] RFC 1009: Requirements for Internet Gateways references the Exterior Gateway Protocol (EGP) and the Routing Information Protocol (RIP). The EGP is described in RFC 904 and the RIP is described in RFC 1058.
Table A-3 lists the RFCs that RFC 1122 references for the transport layer. For a discussion of transport layer requirements for UDP and TCP, see Chapter 4 of RFC 1122.
Table A-3. Referenced RFCs for the Transport Layer
| Referenced RFC | Description |
|---|---|
| RFC 793: Transmission Control Protocol (TCP) | Specifies a connection-oriented reliable protocol for the delivery of stream data between ports. |
| RFC 768: User Datagram Protocol (UDP) | Defines an unreliable connectionless protocol for the delivery of data between ports. |
Table A-4 lists the RFCs that RFC 1123 references for the TELNET protocol. For a discussion of TELNET protocol requirements, see Chapter 3 of RFC 1123.
Table A-4. Referenced RFCs for the TELNET Protocol
| Referenced RFC | Description |
|---|---|
| RFC 1184 [a] Telnet Linemode Option | Describes terminal character processing on the client side of a Telnet connection. |
| RFC 1091: Telnet Terminal Type Option | Specifies a standard for hosts on the Internet that exchange terminal type information within the Telnet protocol. |
| RFC 1080: Telnet Remote Flow Control Option | Specifies a standard for hosts on the Internet that use remote flow control within the Telnet protocol. |
| RFC 1079: Telnet Terminal Speed Option | Specifies a standard for hosts on the Internet that exchange terminal speed information within the Telnet protocol. |
| RFC 1073: Telnet Window Size Option | Describes Telnet options that allow a client to convey window size to a Telnet server. |
| RFC 861: Telnet Extended Options List | Describes an extended Telnet option that allows an additional 256 Telnet options. |
| RFC 860: Telnet Timing Mark Option | Provides a mechanism for a user or process at one end of a Telnet connection to be sure that previously transmitted data has been completely processed, printed, discarded, or otherwise disposed of. |
| RFC 859: Telnet Status Option | Allows one end of a Telnet connection to verify the current status of Telnet options (for example, echoing) as viewed by the other end of the connection. |
| RFC 858: Telnet Suppress Go Ahead (SGA) Option | Allows a full duplex connection between a full duplex terminal and a host optimized to handle full duplex terminals to suppress the transmission of GO AHEADS. |
| RFC 857: Telnet Echo Option | Allows the two ends of a Telnet connection to agree on NVT keyboard characters. |
| RFC 856: Telnet Binary Option | Provides the option of binary transmission in a natural way for Telnet connections to INTERPRET the characters transmitted over a Telnet connection as binary data. |
| RFC 855: Telnet Option Specification | Specifies a method of option code assignment and standards for documenting options for the Telnet protocol. |
| RFC 854: Telnet Protocol Specification | Provides a general, bidirectional, 8-bit byte-oriented communications facility whose primary goal is to allow a standard method of interfacing terminal devices and terminal-oriented processes to each other. |
| RFC 736: Telnet SUPDUP Option | Allows a host to provide SUPDUP service on the normal Telnet socket (27 octal) instead of 137 (octal) which is the normal SUPDUP ICP socket. |
| RFC 734: SUPDUP Protocol | Describes a highly efficient display Telnet protocol |
| RFC 732: Data Entry Terminal Option | Describes the DET option to Telnet. The DET option uses five classes of subcommands: 1) to establish the requirements and capabilities of the application and the terminal, 2) to format the screen, and to control the 3) edit, 4) erasure, and 5) transmission functions. |
| Notes: a. RFC 1184: Telnet Linemode Option renders RFC 1116: Telnet Linemode Option obsolete, and it references RFC 885: TELNET End of Record Option. | |
[a] RFC 1184: Telnet Linemode Option renders RFC 1116: Telnet Linemode Option obsolete, and it references RFC 885: TELNET End of Record Option.
Table A-5 lists the RFCs that RFC 1123 references for the file transfer protocols FTP and TFTP. For a discussion of file transfer protocol requirements, see Chapter 4 of RFC 1123.
Table A-5. Referenced RFCs for the File Transfer Protocols
| Protocol | Referenced RFC | Description |
|---|---|---|
| FTP | RFC 959: File Transfer Protocol (FTP) | Specifies a protocol whose objectives are: 1) to promote sharing of files (computer programs and/or data), 2) to encourage indirect or implicit (via programs) use of remote computers, 3) to shield a user from variations in file storage systems among hosts, and 4) to transfer data reliably and efficiently. |
| RFC 678: Standard File Formats | Specifies standard formats for files and describes the expected final form for printed copies of such files. | |
| TFTP | RFC 1350 [a] The TFTP Protocol | Describes a very simple protocol used to transfer files in which each nonterminal packet is acknowledged separately. |
| Notes: a. RFC 1350: The TFTP Protocol renders RFC 783: The TFTP Protocol obsolete. | ||
[a] RFC 1350: The TFTP Protocol renders RFC 783: The TFTP Protocol obsolete.
Table A-6 lists the RFCs that RFC 1123 references for the SMTP protocol. For a discussion of SMTP protocol requirements, see Chapter 5 of RFC 1123.
Table A-6. Referenced RFCs for the SMTP Protocol
| Referenced RFC | Description |
|---|---|
| RFC 1049: A Content-Type Field for Internet Messages | Specifies additions to the Internet Mail Protocol, RFC-822, for the Internet community. |
| RFC 1047: Duplicate Messages and SMTP | Examines a synchronization problem in the SMTP that can cause a message to be delivered multiple times. |
| RFC 974: Mail Routing and the Domain System | Describes how mail systems on the Internet are expected to route messages based on information from the domain system described in RFCs 882, 883, and 973. |
| RFC 822: Standard for the Format of ARPA Internet Text Messages | Specifies a syntax for text messages that are sent among computer users within the framework of electronic mail. |
| RFC 821: Simple Mail Transfer Protocol (SMTP) | Describes a protocol designed to be independent of the particular transmission subsystem and that requires only a reliable ordered data stream channel to transfer mail reliably and efficiently. |
Table A-7 lists the RFCs that RFC 1123 references for the Domain Name System, Host Initialization, and Remote Management support services. For a discussion of Domain Name System, Host Initialization, and Remote Management requirements, see Chapter 6 of RFC 1123.
Table A-7. Referenced RFCs for the Support Services
| Service | Referenced RFC | Description |
|---|---|---|
| Domain Name System | RFC 1035: Domain Names - Implementation and Specification | Describes the details of the domain system and protocol. Assumes that the reader is familiar with the concepts discussed in a companion RFC, Domain Names - Concepts and Facilities. |
| RFC 1034: Domain Names - Concepts and Facilities | Introduces the Domain Name System (DNS). | |
| RFC 974: Mail Routing and the Domain System | Describes how mail systems on the Internet are expected to route messages based on information from the domain system described in RFCs 882, 883, and 973. | |
| Host Initialization | RFC 903: A Reverse Address Resolution Protocol | Describes a link-layer protocol that allows a host to find its IP address. |
| Network Management | RFC 1213: [a]Management Information Base for Network Management of TCP/IP-based internets: MIB II | Defines the second version of the Management Information Base (MIB-II) for use with network management protocols in TCP/IP- based Internets. |
| RFC 1157: [b]A Simple Network Management Protocol (SNMP) | Defines a simple protocol by which management information for a network element can be inspected or altered by logically remote users. | |
| Notes: a. Digital UNIX is validated against RFC 1213: Management Information Base for Network Management of TCP/IP-based Internets: MIB-II. RFC 1123 references RFC 1066: Management Information Base for Network Management of TCP/IP-based Internets. RFC 1158 renders both RFC 1066 and RFC 1156: Management Information Base for Network Management of TCP/IP-based Internets obsolete. RFC 1213, in turn, renders RFC 1158 obsolete. b. RFC 1157: A Simple Network Management Protocol (SNMP) supercedes RFC 1098: A Simple Network Management Protocol (SNMP), which is referenced in RFC 1123. | ||
[a] Digital UNIX is validated against RFC 1213: Management Information Base for Network Management of TCP/IP-based Internets: MIB-II. RFC 1123 references RFC 1066: Management Information Base for Network Management of TCP/IP-based Internets. RFC 1158 renders both RFC 1066 and RFC 1156: Management Information Base for Network Management of TCP/IP-based Internets obsolete. RFC 1213, in turn, renders RFC 1158 obsolete.
[b] RFC 1157: A Simple Network Management Protocol (SNMP) supercedes RFC 1098: A Simple Network Management Protocol (SNMP), which is referenced in RFC 1123.
Table A-8 summarizes the must/must not level requirements, per layer, explicitly stated by RFC 1122.
Table A-8. Total must/must not Requirements in RFC 1122
| Link Layer | Internet Layer | Transport Layer |
|---|---|---|
| 10 | 92 | 79 |
| (7 must, 3 must not) | (80 must, 12 must not) | (74 must, 5 must not) |
Table A-9 summarizes the must/must not level requirements explicitly stated by RFC 1123.
Table A-9. Total must/must not Requirements in RFC 1123
| General Requirements | TELNET Protocol | File Transfer Protocols | SMTP Protocol | DNS Protocol |
|---|---|---|---|---|
| 9 | 24 | 50 | 41 | 33 |
| (9 must) | (22 must, 2 must not) | (46 must, 4 must not) | (32 must, 9 must not) | (29 must, 4 must not) |
| Prev | Home | Next |
| Conformance to Internet Host Requirements | Up | Configuring Digital UNIX to Conditionally Comply to the Host Requirements RFCs |