📄 rfc991.txt
字号:
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. This protocol is now abandoned in favor of the DOMAIN protocol. Further implementations of this protocol are not advised. Please discuss any plans for implementation or use of this protocol with the contact. OTHER REFERENCES:Reynolds & Postel [Page 28] RFC 991 November 1986Official ARPA-Internet Protocols DEPENDENCIES: User Datagram Protocol CONTACT: Postel@ISI.EDU CSNET Mailbox Name Server Protocol ---------------------- (CSNET-NS) STATUS: Experimental SPECIFICATION: CS-DN-2 (in DPH) 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@WISC.EDU Daytime Protocol ----------------------------------------- (DAYTIME) STATUS: Elective SPECIFICATION: RFC 867 (in DPH) COMMENTS: Provides the day and time in ASCII character string. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol or User Datagram Protocol CONTACT: Postel@ISI.EDUReynolds & Postel [Page 29] RFC 991 November 1986Official ARPA-Internet Protocols Network Time Protocol ---------------------------------------- (NTP) STATUS: Experimental SPECIFICATION: RFC 958 COMMENTS: A proposed protocol for synchronizing a set of network clocks using a set of distributed clients and servers. Please discuss any plans for implementation or use of this protocol with the contact. OTHER REFERENCES: RFC 778, RFC 891, RFC 956, and RFC 957. DEPENDENCIES: User Datagram Protocol CONTACT: Mills@ISI.EDU Time Server Protocol ---------------------------------------- (TIME) STATUS: Elective SPECIFICATION: RFC 868 (in DPH) COMMENTS: Provides the time as the number of seconds from a specified reference time. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol or User Datagram Protocol CONTACT: Postel@ISI.EDUReynolds & Postel [Page 30] RFC 991 November 1986Official ARPA-Internet Protocols DCNET Time Server Protocol --------------------------------- (CLOCK) STATUS: Experimental SPECIFICATION: RFC 778 COMMENTS: Provides a mechanism for keeping synchronized clocks. Please discuss any plans for implementation or use of this protocol with the contact. OTHER REFERENCES: DEPENDENCIES: Internet Control Message Protocol CONTACT: Mills@ISI.EDU SUPDUP Protocol ------------------------------------------- (SUPDUP) STATUS: Elective SPECIFICATION: RFC 734 (in DPH) COMMENTS: A special Telnet like protocol for display terminals. OTHER REFERENCES: DEPENDENCIES: Transmission Control Protocol CONTACT: Crispin@SU-SCORE.STANFORD.EDUReynolds & Postel [Page 31] RFC 991 November 1986Official ARPA-Internet Protocols Internet Message Protocol ------------------------------------ (MPM) STATUS: Experimental SPECIFICATION: RFC 759 (in DPH) 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@ISI.EDU Post Office Protocol - Version 2 ---------------------------- (POP2) STATUS: Experimental SPECIFICATION: RFC 937 (in DPH) COMMENTS: The intent of the Post Office Protocol - Version 2 (POP2) is to allow a user's workstation to access mail from a mailbox server. It is expected that mail will be posted from the workstation to the mailbox server via the Simple Mail Transfer Protocol (SMTP). Please discuss any plans for implementation or use of this protocol with the contact. OTHER REFERENCES: Obsoletes RFC 918 DEPENDENCIES: Transmission Control Protocol CONTACT: JKReynolds@ISI.EDUReynolds & Postel [Page 32] RFC 991 November 1986Official ARPA-Internet Protocols Network Standard Text Editor ------------------------------- (NETED) STATUS: Elective SPECIFICATION: RFC 569 (in DPH) COMMENTS: Describes a simple line editor which could be provided by every Internet host. OTHER REFERENCES: DEPENDENCIES: CONTACT: Postel@ISI.EDU Authentication Service -------------------------------------- (AUTH) STATUS: Experimental SPECIFICATION: RFC 931 COMMENTS: This server provides a means to determine the identity of a user of a particular TCP connection. Given a TCP port number pair, it returns a character string which identifies the owner of that connection on the server's system. Please discuss any plans for implementation or use of this protocol with the contact. OTHER REFERENCES: Supercedes RFC 912 DEPENDENCIES: Transmission Control Protocol CONTACT: StJohns@SRI-NIC.ARPAReynolds & Postel [Page 33] RFC 991 November 1986Official ARPA-Internet Protocols Bootstrap Protocol ----------------------------------------- (BOOTP) STATUS: Experimental SPECIFICATION: RFC 951 COMMENTS: This proposed protocol provides an IP/UDP bootstrap protocol 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. Please discuss any plans for implementation or use of this protocol with the contact. OTHER REFERENCES: DEPENDENCIES: Internet Protocol, User Datagram Protocol CONTACT: Croft@SUMEX-AIM.STANFORD.EDUReynolds & Postel [Page 34] RFC 991 November 1986Official ARPA-Internet ProtocolsAPPENDICES Assigned Numbers --------------------------------------------------- STATUS: None SPECIFICATION: RFC 990 COMMENTS: Describes the fields of various protocols that are assigned specific values for actual use, and lists the currently assigned values. Issued November 1986, replaces RFC 960, RFC 790 in IPTW, and RFC 943. OTHER REFERENCES: CONTACT: JKReynolds@ISI.EDU Pre-emption -------------------------------------------------------- STATUS: Elective SPECIFICATION: RFC 794 (in DPH) COMMENTS: Describes how to do pre-emption of TCP connections. OTHER REFERENCES: CONTACT: Postel@ISI.EDUReynolds & Postel [Page 35] RFC 991 November 1986Official ARPA-Internet Protocols Service Mappings --------------------------------------------------- STATUS: None SPECIFICATION: RFC 795 (in DPH) 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@ISI.EDU Address Mappings --------------------------------------------------- STATUS: None SPECIFICATION: RFC 796 (in DPH) COMMENTS: Describes the mapping between Internet Addresses and the addresses of some specific networks. Out of date, needs revision. OTHER REFERENCES: CONTACT: Postel@ISI.EDU Document Formats --------------------------------------------------- STATUS: None SPECIFICATION: RFC 678 (in DPH) COMMENTS: Describes standard format rules for several types of documents. OTHER REFERENCES: CONTACT: Postel@ISI.EDUReynolds & Postel [Page 36] RFC 991 November 1986Official ARPA-Internet Protocols Bitmap Formats ----------------------------------------------------- STATUS: None SPECIFICATION: RFC 797 (in DPH) COMMENTS: Describes a standard format for bitmap data. OTHER REFERENCES: CONTACT: Postel@ISI.EDU Facsimile Formats -------------------------------------------------- STATUS: None SPECIFICATION: RFC 804 COMMENTS: Describes a standard format for facsimile data. OTHER REFERENCES: RFC 769 (in DPH) CONTACT: Postel@ISI.EDU Host-Front End Protocol ------------------------------------- (HFEP) STATUS: Experimental SPECIFICATION: RFC 929 COMMENTS: Please discuss any plans for implementation or use of this protocol with the contact. OTHER REFERENCES: RFC 928 DEPENDENCIES:⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -