📄 rfc901.txt
字号:
Finger Protocol (FINGER) ------------------------------------------- STATUS: Elective SPECIFICATION: RFC 742 (in APH) COMMENTS: Provides information on the current or most recent activity of a user. Some extensions have been suggested.Reynolds & Postel [Page 19] Official ARPA-Internet Protocols RFC 901 Some changes are are needed for TCP. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol CONTACT: Postel@USC-ISIF.ARPA WhoIs Protocol (NICNAME) ------------------------------------------- STATUS: Elective SPECIFICATION: RFC 812 (in IPTW) COMMENTS: Accesses the ARPANET Directory database. Provides a way to find out about people, their addresses, phone numbers, organizations, and mailboxes. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol CONTACT: Feinler@SRI-NIC.ARPA Domain Name Protocol (DOMAIN) STATUS: Experimental SPECIFICATION: RFC 881, 882, 883 COMMENTS: OTHER REFERENCES: RFC 897 - Domain Name Implementation Schedule DEPENDENCIES: Transmission Control Protocol CONTACT: Mockapetris@USC-ISIF.ARPAReynolds & Postel [Page 20] Official ARPA-Internet Protocols RFC 901 HOSTNAME Protocol (HOSTNAME) --------------------------------------- STATUS: Elective SPECIFICATION: RFC 811 (in IPTW) COMMENTS: Accesses the Registered Internet Hosts database (HOSTS.TXT). Provides a way to find out about a host in the Internet, its Internet Address, and the protocols it implements. OTHER REFERENCES: RFC 810 - Host Table Specification DEPENDENCIES: Transmission Control Protocol CONTACT: Feinler@SRI-NIC.ARPA Host Name Server Protocol (NAMESERVER) ----------------------------- STATUS: Experimental SPECIFICATION: IEN 116 (in IPTW) COMMENTS: Provides machine oriented procedure for translating a host name to an Internet Address. 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-ISIF.ARPAReynolds & Postel [Page 21] Official ARPA-Internet Protocols RFC 901 CSNET Mailbox Name Server Protocol (CSNET-NS) ---------------------- STATUS: Experimental SPECIFICATION: CS-DN-2 COMMENTS: Provides access to the CSNET data base of users to give information about users names, affiliations, and mailboxes. Please discuss any plans for implementation or use of this protocol with the contact. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol CONTACT: Solomon@UWISC.ARPA Daytime Protocol (DAYTIME) ----------------------------------------- STATUS: Elective SPECIFICATION: RFC 867 COMMENTS: Provides the day and time in ASCII character string. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol or User Datagram Protocol CONTACT: Postel@USC-ISIF.ARPA Time Server Protocol (TIME) ---------------------------------------- STATUS: Recommended SPECIFICATION: RFC 868 COMMENTS: Provides the time as the number of seconds from a specified reference time. OTHER REFERENCES:Reynolds & Postel [Page 22] Official ARPA-Internet Protocols RFC 901 DEPENDENCIES: Transmission Control Protocol or User Datagram Protocol CONTACT: Postel@USC-ISIF.ARPA DCNET Time Server Protocol (CLOCK) --------------------------------- STATUS: Elective SPECIFICATION: RFC 778 COMMENTS: Provides a mechanism for keeping synchronized clocks. OTHER REFERENCES: DEPENDENCIES: Internet Control Message Protocol CONTACT: Mills@USC-ISID.ARPA SUPDUP Protocol (SUPDUP) ------------------------------------------- STATUS: Elective SPECIFICATION: RFC 734 (in APH) COMMENTS: A special Telnet like protocol for display terminals. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol CONTACT: Admin.MRC@SU-SCORE.ARPAReynolds & Postel [Page 23] Official ARPA-Internet Protocols RFC 901 Internet Message Protocol (MPM) ------------------------------------ STATUS: Experimental SPECIFICATION: RFC 759 COMMENTS: This is an experimental multimedia mail transfer protocol. The implementation is called a Message Processing Module or MPM. 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-ISIF.ARPA Post Office Protocol (POP) ----------------------------------------- STATUS: Experimental SPECIFICATION: RFC xxx COMMENTS: This is an experimental procedure for accessing mailbox services from personal workstations. Please discuss any plans for implementation or use of this protocol with the contact. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol CONTACT: Postel@USC-ISIF.ARPAReynolds & Postel [Page 24] Official ARPA-Internet Protocols RFC 901 Network Standard Text Editor (NETED) ------------------------------- STATUS: Elective SPECIFICATION: RFC 569 COMMENTS: Describes a simple line editor which could be provided by every Internet host. OTHER REFERENCES: DEPENDENCIES: CONTACT: Postel@USC-ISIF.ARPAAppendices Assigned Numbers --------------------------------------------------- STATUS: None SPECIFICATION: RFC 900 COMMENTS: Describes the fields of various protocols that are assigned specific values for actual use, and lists the currently assigned values. Issued June 1984, replaces RFC 870, RFC 790 in IPTW, and RFC 820 of January 1983. OTHER REFERENCES: CONTACT: JKReynolds@USC-ISIF.ARPAReynolds & Postel [Page 25] Official ARPA-Internet Protocols RFC 901 Pre-emption -------------------------------------------------------- STATUS: Elective SPECIFICATION: RFC 794 (in IPTW) COMMENTS: Describes how to do pre-emption of TCP connections. OTHER REFERENCES: CONTACT: Postel@USC-ISIF.ARPA 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.ARPA Address Mappings --------------------------------------------------- STATUS: None SPECIFICATION: RFC 796 (in IPTW) COMMENTS: Describes the mapping between Internet Addresses and the addresses of some specific networks. Out of date, needs revision. OTHER REFERENCES: CONTACT: Postel@USC-ISIF.ARPAReynolds & Postel [Page 26] Official ARPA-Internet Protocols RFC 901 Internet Protocol on X.25 Networks --------------------------------- STATUS: Recommended SPECIFICATION: RFC 877 COMMENTS: Describes a standard for the transmission of IP Datagrams over Public Data Networks. OTHER REFERENCES: CONTACT: jtk@PURDUE.ARPA Internet Protocol on DC Networks ----------------------------------- STATUS: Elective SPECIFICATION: RFC 891 COMMENTS: OTHER REFERENCES: RFC 778 - DCNET Internet Clock Service CONTACT: Mills@USC-ISID.ARPA Internet Protocol on Ethernet Networks ----------------------------- STATUS: Recommended SPECIFICATION: RFC 894 COMMENTS: OTHER REFERENCES: RFC 893 CONTACT: Postel@USC-ISIF.ARPAReynolds & Postel [Page 27] Official ARPA-Internet Protocols RFC 901 Internet Protocol on Experimental Ethernet Networks ---------------- STATUS: Recommended SPECIFICATION: RFC 895 COMMENTS: OTHER REFERENCES: CONTACT: Postel@USC-ISIF.ARPA Address Resolution Protocol (ARP) ---------------------------------- STATUS: Recommended SPECIFICATION: RFC 826 COMMENTS: This is a procedure for finding the network hardware address corresponding to an Internet Address. OTHER REFERENCES: CONTACT: Postel@USC-ISIF.ARPAReynolds & Postel [Page 28] ⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -