📄 rfc840.txt
字号:
OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol or User Datagram Protocol CONTACT: Postel@USC-ISIF Discard Protocol STATUS: Elective SPECIFICATION: RFC 348 COMMENTS: This specification should be revised for use with TCP and reissued. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol or User Datagram Protocol CONTACT: Postel@USC-ISIFPostel [Page 16] RFC 840 April 1983 Official Protocols Character Generator Protocol STATUS: Elective SPECIFICATION: RFC 429 COMMENTS: This specification should be revised for use with TCP and reissued. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol or User Datagram Protocol CONTACT: Postel@USC-ISIF Quote of the Day Protocol STATUS: Elective SPECIFICATION: RFC xxx COMMENTS: Open a connection to this server, it sends you a quote (as a character string), and closes the connection. This should be described in an RFC. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol or User Datagram Protocol CONTACT: Postel@USC-ISIF Active Users Protocol STATUS: Elective SPECIFICATION: RFC xxx COMMENTS: Open a connection to this server, it sends you a list of the currently logged in users (as a character string), and closes the connection. This should be described in an RFC.Postel [Page 17] RFC 840 April 1983 Official Protocols OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol or User Datagram Protocol CONTACT: Postel@USC-ISIF Finger Protocol STATUS: Elective SPECIFICATION: RFC 742 (in APH) COMMENTS: Some extensions have been suggested. Some changes are are needed for TCP. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol CONTACT: Postel@USC-ISIF NICNAME Protocol STATUS: Elective SPECIFICATION: RFC 812 (in IPTW) COMMENTS: Accesses the ARPANET Directory database. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol CONTACT: Feinler@SRI-NICPostel [Page 18] RFC 840 April 1983 Official Protocols HOSTNAME Protocol STATUS: Elective SPECIFICATION: RFC 811 (in IPTW) COMMENTS: Accesses the Registered Internet Hosts database (HOSTS.TXT). OTHER REFERENCES: RFC 810 - Host Table Specification DEPENDENCIES: Transmission Control Protocol CONTACT: Feinler@SRI-NIC Host Name Server Protocol STATUS: Experimental SPECIFICATION: IEN 116 (in IPTW) COMMENTS: This specification has significant problems: 1) The name syntax is out of date. 2) The protocol details are ambiguous, in particular, the length octet either does or doesn't include itself and the op code. 3) The extensions are not supported by any known implementation. Work is in progress on a significant revision. Further implementations of this protocol are not advised. Please discuss any plans for implementation or use of this protocol with the contact. OTHER REFERENCES: DEPENDENCIES: User Datagram Protocol CONTACT: Postel@USC-ISIFPostel [Page 19] RFC 840 April 1983 Official Protocols CSNET Mailbox Name Server Protocol STATUS: Experimental SPECIFICATION: CS-DN-2 COMMENTS: Please discuss any plans for implementation or use of this protocol with the contact. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol CONTACT: Solomon@UWISC Daytime Protocol STATUS: Elective SPECIFICATION: RFC xxx COMMENTS: Open a connection to this server, it sends you the date and time (as a character string), and closes the connection. This should be described in an RFC. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol or User Datagram Protocol CONTACT: Postel@USC-ISIF Time Server Protocol STATUS: Recommended SPECIFICATION: IEN 142 COMMENTS: Open a connection to this server, it sends you the date and time (as a 32-bit number), and closes the connection. Or send a user datagram and it send back a datagram containing the date and time (as a 32-bit number).Postel [Page 20] RFC 840 April 1983 Official Protocols No known problems. Specification should be reissued as an RFC. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol or User Datagram Protocol CONTACT: Postel@USC-ISIF DCNET Time Server Protocol (Internet Clock Service) STATUS: Elective SPECIFICATION: RFC 778 COMMENTS: OTHER REFERENCES: DEPENDENCIES: Internet Control Message Protocol CONTACT: Mills@LINKABIT-DCN6 SUPDUP Protocol STATUS: Elective SPECIFICATION: RFC 734 (in APH) COMMENTS: OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol CONTACT: Admin.MRC@SU-SCORE Internet Message Protocol (MPM) STATUS: Experimental SPECIFICATION: RFC 753 COMMENTS: This is an experimental multimedia mail transfer protocol. The implementation is called a Message Processing Module or MPM.Postel [Page 21] RFC 840 April 1983 Official Protocols Please discuss any plans for implementation or use of this protocol with the contact. OTHER REFERENCES: RFC 767 - Structured Document Formats DEPENDENCIES: Transmission Control Protocol CONTACT: Postel@USC-ISIFAppendices Assigned Numbers STATUS: None SPECIFICATION: RFC 820 COMMENTS: Describes the fields of various protocols that are assigned specific values for actual use, and lists the currently assigned values. Issued January 1983, replaces RFC 790 in IPTW. OTHER REFERENCES: CONTACT: Postel@USC-ISIF Pre-emption STATUS: Elective SPECIFICATION: RFC 794 (in IPTW) COMMENTS: Describes how to do pre-emption of TCP connections. OTHER REFERENCES: CONTACT: Postel@USC-ISIFPostel [Page 22] RFC 840 April 1983 Official Protocols Service Mappings STATUS: None SPECIFICATION: RFC 795 (in IPTW) COMMENTS: Describes the mapping of the IP type of service field onto the parameters of some specific networks. Out of date, needs revision. OTHER REFERENCES: CONTACT: Postel@USC-ISIF Address Mappings STATUS: None SPECIFICATION: RFC 796 (in IPTW) COMMENTS: Describes the mapping of the IP address field onto the address field of some specific networks. Out of date, needs revision. OTHER REFERENCES: CONTACT: Postel@USC-ISIFPostel [Page 23] ⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -