brian@sdcsvax.UCSD.EDU (Brian Kantor) (10/07/87)
--- to a User-Telnet so that this banner would be displayed on the workstation screen independently of the application software running in the Server-Telnet. 932 Clark Jan 85 A Subnetwork Addressing Scheme This RFC proposes an alternative addressing scheme for subnets which, in most cases, requires no modification to host software whatsoever. The drawbacks of this scheme are that the total number of subnets in any one network are limited, and that modification is required to all gateways. 931 StJohns Jan 85 Authentication Server This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This is the second draft of this proposal (superseding RFC 912) and incorporates a more formal description of the syntax for the request and response dialog, as well as a change to specify the type of user identification returned. 930 Solomon Jan 85 Telnet Terminal Type Option This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet that exchange terminal type information within the Telnet protocol are expected to adopt and implement this standard. Distribution of this memo is unlimited. This standard supersedes RFC 884. The only change is to specify that the TERMINAL-TYPE IS sub-negotiation should be sent only in response to the TERMINAL-TYPE SEND sub-negotiation. Reynolds & Postel [Page 42] RFC 1000 - Request for Comments Reference Guide August 1987 929 Lilienkamp Dec 84 Proposed Host-Front End Protocol The Host-Front End Protocol introduced in RFC 928 is described in detail in this memo. The first order of business is to declare that THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the second order of business is to request that any readers of these documents who are able to do test implementations (a) do so and (b) coordinate their efforts with the author. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. 928 Padlipsky Dec 84 Introduction to Proposed DOD Standard H-FP The broad outline of the Host-Front End Protocol introduced here and described in RFC 929 is the result of the deliberations of a number of experienced H-FP designers, who sat as a committee of the DoD Protocol Standards Technical Panel. It is the intent of the designers that the protocol be subjected to multiple test implementations and probable iteration before being agreed upon as any sort of "standard". Therefore, the first order of business is to declare that THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the second order of business is to request that any readers of these documents who are able to do test implementations (a) do so and (b) coordinate their efforts with the author. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. 927 Anderson Dec 84 TACACS User Identification Telnet Option The following is the description of a Telnet option designed to facilitate double login avoidance. It is intended primarily for TAC connections to target hosts on behalf of TAC users, but it can be used between any two consenting hosts. For example, all hosts at one site (e.g., BBN) can use this option to avoid double login when TELNETing to one another. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. 926 ISO Dec 84 Protocol for Providing the Connectionless-Mode Network Services This note is the draft ISO protocol roughly similar to the DoD Internet Protocol. This document has been prepared by retyping the text of ISO DIS 8473 of May 1984, which is currently undergoing voting within ISO as a Draft International Standard Reynolds & Postel [Page 43] RFC 1000 - Request for Comments Reference Guide August 1987 (DIS). This document is distributed as an RFC for information only. It does not specify a standard for the ARPA-Internet. 925 Postel Oct 84 Multi-LAN Address Resolution The problem of treating a set of local area networks (LANs) as one Internet network has generated some interest and concern. It is inappropriate to give each LAN within a site a distinct ARPA-Internet network number. It is desirable to hide the details of the interconnections between the LANs within a site from people, gateways, and hosts outside the site. The question arises on how to best do this, and even how to do it at all. In RFC 917, Jeffery Mogul makes a case for the use of "explicit subnets" in a multi-LAN environment. The explicit subnet scheme is a call to recursively apply the mechanisms the ARPA-Internet uses to manage networks to the problem of managing LANs within one network. In this note I urge another approach: the use of "transparent subnets" supported by a multi-LAN extension of the Address Resolution Protocol. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. 924 Reynolds Oct 84 Official ARPA-Internet Protocols This RFC has been replaced by RFC 991. 923 Reynolds Oct 84 Assigned Numbers This RFC has been replaced by RFCs 997 and 990. 922 Mogul Oct 84 Broadcasting Internet Datagrams in the Presence of Subnets We propose simple rules for broadcasting Internet datagrams on local networks that support broadcast, for addressing broadcasts, and for how gateways should handle them. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. 921 Postel Oct 84 Domain Name System Implementation Schedule - Revised This memo is a policy statement on the implementation of the Domain Style Naming System in the ARPA-Internet. This memo is an update of RFC 881, and RFC 897. This is an official policy statement of the IAB and the DARPA. The intent of this memo is to detail the schedule for the implementation for the Domain Style Reynolds & Postel [Page 44] RFC 1000 - Request for Comments Reference Guide August 1987 Naming System. The explanation of how this system works is to be found in the references. 920 Postel Oct 84 Domain Requirements This memo states the requirements on establishing a Domain, and introduces the limited set of top level domains. This memo is a policy statement on the requirements of establishing a new domain in the ARPA-Internet and the DARPA research community. This is an official policy statement of the IAB and the DARPA. 919 Mogul Oct 84 Broadcasting Internet Datagrams This RFC proposes simple rules for broadcasting Internet datagrams on local networks that support broadcast, for addressing broadcasts, and for how gateways should handle them. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. 918 Reynolds Oct 84 Post Office Protocol (POP) Updated by RFC 937. 917 Mogul Oct 84 Internet Subnets This memo discusses subnets and proposes procedures for the use of subnets, including approaches to solving the problems that arise, particularly that of routing. A subnet of an Internet network is a logically visible sub-section of a single Internet network. For administrative or technical reasons, many organizations have chosen to divide one Internet network into several subnets, instead of acquiring a set of Internet network numbers. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. 916 Finn Oct 84 Reliable Asynchronous Transfer Protocol (RATP) This paper proposes and specifies a protocol which allows two programs to reliably communicate over a communication link. It ensures that the data entering one end of the link if received arrives at the other end intact and unaltered. The protocol, named RATP, is designed to operate over a full duplex point-to-point connection. It contains some features which tailor it to the RS-232 links now in common use. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. Reynolds & Postel [Page 45] RFC 1000 - Request for Comments Reference Guide August 1987 915 Elvy Dec 84 Network Mail Path Service The network mail path service fills the current need of people to determine mailbox addresses for hosts that are not part of the ARPA-Internet but can be reached by one or more relay hosts that have Unix to Unix Copy (UUCP) mail, CSNET mail, MAILNET mail, BITNET mail, etc. Anyone can use the service if they have TCP/TELENET to one of the hosts with a mail path server. This RFC proposes a new service for the ARPA-Internet community and requests discussion and suggestions for improvements. 914 Farber Sep 84 A Thinwire Protocol This document focuses discussion on the particular problems in the ARPA-Internet of low speed network interconnection with personal computers, and possible methods of solution. None of the proposed solutions in this document are intended as standards for the ARPA-Internet. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to the problems, leading eventually to the adoption of standards. 913 Lottor Sep 84 Simple File Transfer Protocol This memo describes a proposed Simple File Transfer Protocol (SFTP). It fills the need of people wanting a protocol that is more useful than TFTP but easier to implement (and less powerful) than FTP. SFTP supports user access control, file transfers, directory listing, directory changing, file renaming, and deleting. Discussion of this proposal is encouraged, and suggestions for improvements may be sent to the author. 912 StJohns Sep 84 Authentication Service This memo describes a proposed authentication protocol for verifying the identity of a user of a 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. Suggested uses include automatic identification and verification of a user during an FTP session, additional verification of a TAC dial up user, and access verification for a generalized network file server. 911 Kirton Aug 84 EGP Gateway under Berkeley Unix 4.2 This memo describes an implementation of the Exterior Gateway Protocol (EGP) (in that sense it is a status report). The memo also discusses some possible extentions and some design issues (in that sense it is an invitation for further discussion). Reynolds & Postel [Page 46] RFC 1000 - Request for Comments Reference Guide August 1987 910 Forsdick Aug 84 Multimedia Mail Meeting Notes This memo is a report on a meeting about the experimental multimedia mail system (and in a sense a status report on that experiment). The meeting was held at Bolt Beranek and Newman on 23-24 July 1984 to discuss recent progress by groups who are building multimedia mail systems and to discuss a variety of issues related to the further development of multimedia systems. Representatives were present from BBN, ISI, SRI and Linkabit. Distribution of this memo is unlimited. 909 Welles Jul 84 Loader Debugger Protocol The Loader Debugger Protocol (LDP) is an application layer protocol for loading, dumping, and debugging target machines from hosts in a network environment. This RFC specifies a proposed protocol for the ARPA-Internet and DARPA research community, and requests discussion and suggestions for improvements. 908 Velten Jul 84 Reliable Data Protocol The Reliable Data Protocol (RDP) is designed to provide a reliable data transport service for packet-based applications. This RFC specifies a proposed protocol for the ARPA-Internet and DARPA research community, and requests discussion and suggestions for improvemts. 907 Storch Jul 84 Host Access Protocol Specification This document specifies the Host Access Protocol (HAP). Although HAP was originally designed as the network-access level protocol for the DARPA/DCA sponsored Wideband Packet Satellite Network, it is intended that it evolve into a standard interface SATNET and TACNET (aka MATNET) as well as the Wideband Network. HAP is an experimental protocol, and will undergo further revision as new capabilities are added and/or different satellite networks are suported. Implementations of HAP should be performed in coordination with satellite network development and operations personnel. 906 Finlayson Jun 84 Bootstrap Loading Using TFTP It is often convenient to be able to bootstrap a computer system from a communications network. This RFC proposes the use of the IP/TFTP protocol for bootstrap loading in this case. Reynolds & Postel [Page 47] RFC 1000 - Request for Comments Reference Guide August 1987 905 ISO Apr 84 ISO Transport Protocol Specification (ISO DP 8073) This is the current specification of the ISO Transport Protocol. This document is the text of ISO/TC97/SC16/N1576 as corrected by ISO/TC97/SC16/N1695. This is the specification currently being voted on in ISO as a Draft International Standard (DIS). This document is distributed as an RFC for your information only, it does not specify a standard for the ARPA-Internet or DARPA research community. Our thanks to Alex McKenzie of BBN for making this online version available. Please note the size of this document, the file contains 258,729 characters. 904 Mills Apr 84 Exterior Gateway Protocol Formal Specification This is the specification of the Exterior Gateway Protocol (EGP). This memo updates portions of RFC 888 and RFC 827. This RFC specifies an official protocol of the DARPA community for use between gateways of different autonomous systems in the ARPA-Internet. 903 Finlayson Jun 84 A Reverse Address Resolution Protocol This RFC suggests a method for workstations to dynamically find their protocol address (e.g., their Internet Address), when they know only their hardware address (e.g., their attached physical network address). This RFC specifies a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvement. 902 Postel Jul 84 ARPA-Internet Protocol Policy The purpose of this memo is to explain how protocol standards are adopted for the ARPA-Internet and the DARPA research community. There are three important aspects to be discussed: the process, the authority, and the complex relationship between the DARPA community and the DDN community. This memo is a policy statement on how protocols become official standards for the ARPA-Internet and the DARPA research community. This is an official policy statement of the ICCB and the DARPA. 901 Reynolds Jun 84 Official ARPA-Internet Protocols This RFC has been replaced by RFC 991. Reynolds & Postel [Page 48] RFC 1000 - Request for Comments Reference Guide August 1987 900 Reynolds Jun 84 Assigned Numbers This RFC has been replaced by RFCs 997 and 990. 899 Postel Apr 84 Requests For Comments Summary A summary of the Request for Comments documents from RFC 800-898. 898 Hinden Apr 84 Gateway Special Interest Group Meeting Notes This memo is a report on the Gateway Special Interest Group Meeting that was held at ISI on 28 and 29 February 1984. Robert Hinden of BBNCC chaired, and Jon Postel of ISI hosted the meeting. Approximately 35 gateway designers and implementors attended. These notes are based on the recollections of Jon Postel and Mike Muuss. Under each topic area are Jon Postel's brief notes, and additional details from Mike Muuss. This memo is a report on the meeting. No conclusions, decisions, or policy statements are documented in this note. 897 Postel Feb 84 Domain Name System Implementation Schedule This memo is a policy statement on the implementation of the Domain Style Naming System in the ARPA-Internet. This memo is a partial update of RFC 881. The intent of this memo is to detail the schedule for the implementation of the Domain Style Naming System. The names of hosts will be changed to Domain style names. Hosts will begin to use Domain style names on 14-Mar-84, and the use of old style names will be completely phased out before 2-May-84. This applies to both the ARPA research hosts and the DDN operational hosts. This is an official policy statement of the ICCB and the DARPA. 896 Nagle Jan 84 Congestion Control in IP/TCP Internetworks This memo discusses some aspects of congestion control in IP/TCP Internetworks. It is intended to stimulate thought and further discussion of this topic. While some specific suggestions are made for improved congestion control implementation, this memo does not specify any standards. 895 Postel Apr 84 A Standard for the Transmission of IP Datagrams over Experimental Ethernet Networks This RFC specifies a standard method of encapsulating Internet Reynolds & Postel [Page 49] RFC 1000 - Request for Comments Reference Guide August 1987 Protocol (IP) datagrams on an Experimental Ethernet. This RFC specifies a standard protocol for the ARPA-Internet community. 894 Hornig Apr 84 A Standard for the Transmission of IP Datagrams over Ethernet Networks This RFC specifies a standard method of encapsulating Internet Protocol (IP) datagrams on an Ethernet. This RFC specifies a standard protocol for the ARPA-Internet community. 893 Leffler Apr 84 Trailer Encapsulations This RFC discusses the motivation for use of "trailer encapsulations" on local-area networks and describes the implementation of such an encapsulation on various media. This document is for information only. This is NOT an official protocol for the ARPA-Internet community. 892 ISO Dec 83 ISO Transport Protocol Specification This is a draft version of the transport protocol being standardized by the ISO. This version also appeared in the ACM SIGCOMM Computer Communication Review (V.12, N.3-4) July-October 1982. This version is now out of date. 891 Mills Dec 83 DCN Local-Network Protocols This RFC provides a description of the DCN protocols for maintaining connectivity, routing, and clock information in a local network. These procedures may be of interest to the designers and implementers of other local networks. 890 Postel Feb 84 Exterior Gateway Protocol Implementation Schedule This memo is a policy statement on the implementation of the Exterior Gateway Protocol (EGP) in the ARPA-Internet. This is an official policy statement of ICCB and DARPA. After 1-Aug-84 there shall be no dumb gateways in the Internet. Every gateway must be a member of some autonomous system. Some gateway of each autonomous system must exchange routing information with some gateway of the core autonomous system using the Exterior Gateway Protocol. 889 Mills Dec 83 Internet Delay Experiments This memo reports on some measurements of round-trip times in the Internet and suggests some possible improvements to the TCP Reynolds & Postel [Page 50] RFC 1000 - Request for Comments Reference Guide August 1987 retransmission timeout calculation. This memo is both a status report on the ARPA-Internet and advice to TCP implementers. 888 Seamonson Jan 84 "Stub" Exterior Gateway Protocol This RFC describes the Exterior Gateway Protocol (EGP) used to connect Stub Gateways to an Autonomous System of core Gateways. This document specifies the working protocol, and defines an ARPA official protocol. All implementers of Gateways should carefully review this document. 887 Accetta Dec 83 Resource Location Protocol This RFC specifies a draft standard for the ARPA-Internet community. It describes a resource location protocol for use in the ARPA-Internet. It is most useful on networks employing technologies which support some method of broadcast addressing, however it may also be used on other types of networks. For maximum benefit, all hosts which provide significant resources or services to other hosts on the ARPA-Internet should implement this protocol. Hosts failing to implement the Resource Location Protocol risk being ignored by other hosts which are attempting to locate resources on the ARPA-Internet. 886 Rose Dec 83 Proposed Standard for Message Header Munging This RFC specifies a draft standard for the ARPA-Internet community. It describes the rules to be used when transforming mail from the conventions of one message system to those of another message system. In particular, the treatment of header fields, and recipient addresses is specified. 885 Postel Dec 83 Telnet End of Record Option This RFC specifies a standard for the ARPA-Internet community. It specifies a method for marking the end of records in data transmitted on Telnet connections. 884 Solomon Dec 83 Telnet Terminal Type Option This RFC specifies a standard for the ARPA-Internet community. It specifies a method for exchanging terminal type information in the Telnet protocol. Reynolds & Postel [Page 51] RFC 1000 - Request for Comments Reference Guide August 1987 883 Mockapetris Nov 83 Domain Names - Implementation and Specification This RFC discusses the implementation of domain name servers and resolvers, specifies the format of transactions, and discusses the use of domain names in the context of existing mail systems and other network software. 882 Mockapetris Nov 83 Domain Names - Concepts and Facilities This RFC introduces domain style names, their use for DDN/ARPA-Internet mail and host address support, and the protocol and servers used to implement domain name facilities. 881 Postel Nov 83 The Domain Names Plan and Schedule This RFC outlines a plan and schedule for the implementation of domain style names throughout the DDN/ARPA-Internet community. The introduction of domain style names will impact all hosts on the DDN/ARPA-Internet. 880 Reynolds Oct 83 Official Protocols This RFC has been replaced by RFC 991. 879 Postel Nov 83 The TCP Maximum Segment Size and Related Topics This RFC discusses the TCP Maximum Segment Size Option and related topics. The purpose is to clarify some aspects of TCP and its interaction with IP. This memo is a clarification to the TCP specification, and contains information that may be considered as "advice to implementers". 878 Malis Dec 83 The ARPANET 1822L Host Access Protocol This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. The 1822L procedure allows ARPANET hosts to use logical identifiers as well as 1822 physical interface identifiers to address each other. 877 Korb Sep 83 A Standard for the Transmission of IP Datagrams Over Public Data Networks This RFC specifies a standard adopted by CSNET, the VAN gateway, Reynolds & Postel [Page 52] RFC 1000 - Request for Comments Reference Guide August 1987 and other organizations for the transmission of IP datagrams over the X.25-based public data networks. 876 Smallberg Sep 83 Survey of SMTP Implementations This RFC is a survey of implementation status. It does not specify an official protocol, but rather notes the status of implementation of aspects of a protocol. It is expected that the status of the hosts reported on will change. This information must be treated as a snapshot of the state of these implemetations. 875 Padlipsky Sep 82 Gateways, Architectures, and Heffalumps This RFC is a discussion about the role of gateways in an internetwork, especially the problems of translating or mapping protocols between different protocol suites. The discussion notes possible functionality mis-matches, undesirable routing "singularity points", flow control issues, and high cost of translating gateways. Originally published as M82-51 by the MITRE Corporation, Bedford, Massachusetts. 874 Padlipsky Sep 82 A Critique of X.25 This RFC is an analysis of X.25 pointing out some problems in the conceptual model, particularly the conflict between the interface aspects and the end-to-end aspects. The memo also touches on security, and implementation issues. Originally published as M82-50 by the MITRE Corporation, Bedford, Massachusetts. 873 Padlipsky Sep 82 The Illusion of Vendor Support This memo takes issue with the claim that international standards in computer protocols presently provide a basis for low cost vendor supported protocol implementations. Originally published as M82-49 by the MITRE Corporation, Bedford, Massachusetts. 872 Padlipsky Sep 82 TCP-ON-A-LAN This memo attacks the notion that TCP cannot be appropriate for use on a Local Area Network. Originally published as M82-48 by the MITRE Corporation, Bedford Massachusetts. 871 Padlipsky Sep 82 A Perspective on the Arpanet Reference Model This RFC is primarily intended as a perspective on the ARM and points out some of the differences between the ARM and the ISORM Reynolds & Postel [Page 53] RFC 1000 - Request for Comments Reference Guide August 1987 which were expressed by members in NWG general meetings, NWG protocol design committee meetings, the ARPA-Internet Working Group, and private conversations over the intervening years. Originally published as M82-47 by the MITRE Corporation, Bedford, Massachusetts. 870 Reynolds Oct 83 Assigned Numbers This RFC has been replaced by RFCs 997 and 990. 869 Hinden Dec 83 A Host Monitoring Protocol This RFC specifies the Host Monitoring Protocol used to collect information from various types of hosts in the Internet. Designers of Internet communications software are encouraged to consider this protocol as a means of monitoring the behavior of their creations. 868 Postel May 83 Time Protocol This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet that choose to implement a Time Protocol are expected to adopt and implement this standard. This protocol provides a site-independent, machine readable date and time. The Time service sends back to the originating source the time in seconds since midnight on January first 1900. 867 Postel May 83 Daytime Protocol This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet that choose to implement a Daytime Protocol are expected to adopt and implement this standard. The Daytime service simply sends the current date and time as a character string without regard to the input. 866 Postel May 83 Active Users This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet that choose to implement an Active Users Protocol are expected to adopt and implement this standard. The Active Users service simply sends a list of the currently active users on the host without regard to the input. 865 Postel May 83 Quote of the Day Protocol This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet that choose to implement a Quote of the Day Protocol are expected to adopt and implement this standard. Reynolds & Postel [Page 54] RFC 1000 - Request for Comments Reference Guide August 1987 The Quote of the Day service simply sends a short message without regard to the input. 864 Postel May 83 Character Generator Protocol This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet that choose to implement a Character Generator Protocol are expected to adopt and implement this standard. The Character Generator service simply sends data without regard to the input. 863 Postel May 83 Discard Protocol This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet that choose to implement a Discard Protocol are expected to adopt and implement this standard. The Discard service simply throws away any data it receives. 862 Postel May 83 Echo Protocol This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet that choose to implement a Echo Protocol are expected to adopt and implement this standard. The Echo service simply sends back to the originating source any data it receives. 861 Postel May 83 Telnet Extended Options - List Option This Telnet Option provides a mechanism for extending the set of possible options. This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes NIC 16239. 860 Postel May 83 Telnet Timing Mark Option This Telnet Option provides a way to check the roundtrip path between two Telnet modules. This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes NIC 16238. 859 Postel May 83 Telnet Status Option This Telnet Option provides a way to determine the other Telnet module's view of the status of options. This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes RFC 651 (NIC 31154). Reynolds & Postel [Page 55] RFC 1000 - Request for Comments Reference Guide August 1987 858 Postel May 83 Telnet Suppress Go Ahead Option This Telnet Option disables the exchange of go-ahead signals between the Telnet modules. This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes NIC 15392. 857 Postel May 83 Telnet Echo Option This Telnet Option enables remote echoing by the other Telnet module. This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes NIC 15390. 856 Postel May 83 Telnet Binary Transmission This Telnet Option enables a binary data mode between the Telnet modules. This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes NIC 15389. 855 Postel May 83 Telnet Option Specifications This memo specifies the general form for Telnet options and the directions for their specification. This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes RFC 651, NIC 18640. 854 Postel May 83 Telnet Protocol Specifications This is the specification of the Telnet protocol used for remote terminal access in the ARPA-Internet. The purpose of the Telnet Protocol is to provide a fairly general, bi-directional, eight-bit byte oriented communications facility. Its primary goal is to allow a standard method of interfacing terminal devices and terminal-oriented processes to each other. It is envisioned that the protocol may also be used for terminal-terminal communication ("linking") and process-process communication (distributed computation). This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes NIC 18639. 853 Never Issued. Reynolds & Postel [Page 56] RFC 1000 - Request for Comments Reference Guide August 1987 852 Malis Apr 83 The ARPANET Short Blocking Feature This RFC specifies the ARPANET Short Blocking Feature, which will allow ARPANET hosts to optionally shorten the IMP's host blocking timer. This Feature is a replacement of the ARPANET non-blocking host interface, which was never implemented, and will be available to hosts using either the 1822 or 1822L Host Access Protocol. This RFC is also being presented as a solicitation of comments on the Short Blocking Feature, especially from host network software implementers and maintainers. 851 Malis Apr 83 The ARPANET 1822L Host Access Protocol This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. 1822L allows ARPANET hosts to use logical names as well as 1822's physical port locations to address each other. This RFC is also being presented as a solicitation of comments on 1822L, especially from host network software implementers and maintainers. Obsoletes RFC 802. 850 Horton Jun 83 Standard for Interchange of USENET Messages This memo is distributed as an RFC only to make this information easily accessible to researchers in the ARPA-Internet community. It does not specify an Internet standard. This RFC defines the standard format for interchange of Network News articles among USENET sites. It describes the format for articles themselves, and gives partial standards for transmission of news. The news transmission is not entirely standardized in order to give a good deal of flexibility to the individual hosts to choose transmission hardware and software, whether to batch news and so on. 849 Crispin May 83 Suggestions for Improved Host Table Distribution This RFC actually is a request for comments. The issue dealt with is that of a naming registry update procedure, both as exists currently and what could exist in the future. None of the proposed solutions are intended as standards at this time; rather it is hoped that a general consensus will emerge as the appropriate solution, leaving eventually to the adoption of standards. Reynolds & Postel [Page 57] RFC 1000 - Request for Comments Reference Guide August 1987 848 Smallberg Mar 83 Who provides the "Little" TCP Services? This RFC lists those hosts which provide any of these "little" TCP services: The list of hosts were taken from the NIC hostname table of 24-Feb-83. The tests were run on February 23 and 24, and March 3 and 5 from ISI-VAXA.ARPA. 847 Westine Feb 83 Summary of Smallberg Surveys This is a summary of the surveys of Telnet, FTP and Mail (SMTP) servers conducted by David Smallberg in December 1982, January and February 1983 as reported in RFC 832-843, 845-846. This memo extracts the number of hosts that accepted the connection to their server for each of Telnet, FTP, and SMTP, and compares it to the total host in the ARPA-Internet (not counting TACs or ECHOS). 846 Smallberg Feb 83 Who Talks TCP? -- Survey of 22 February 1983 This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 18-Feb-83. The tests were run on 22-Feb-83 from ISI-VAXA.ARPA. 845 Smallberg Feb 83 Who Talks TCP? -- Survey of 15 February 1983 This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 3-Feb-83. The tests were run on 15-Feb-83 from ISI-VAXA.ARPA. 844 Clements Feb 83 Who Talks ICMP, too? Survey of 18 February 1983 This survey determines how many hosts are able to respond to Telnet connections from a user at a class C site. This requires, in addition to IP and TCP, participation in gateway routing via ICMP and handling of Class C addresses. The list of hosts was taken from RFC 843, extracting only those hosts which are listed there as accepting Telnet connection. The tests were run on 18-Feb-83. 843 Smallberg Feb 83 Who Talks TCP? -- Survey of 8 February 1983 This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was Reynolds & Postel [Page 58] RFC 1000 - Request for Comments Reference Guide August 1987 taken from the NIC hostname table of 3-Feb-83. The tests were run on 8-Feb-83 and on 9-Feb-83 from ISI-VAXA.ARPA. 842 Smallberg Feb 83 Who Talks TCP? -- Survey of 1 February 1983 This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 28-Jan-83. The tests were run on 1-Feb-83 and on 2-Feb-83 ISI-VAXA.ARPA. 841 FIPS PUB 98 Jan 83 Specification for Message Format for Computer Based Message Systems This RFC is FIPS 98. The purpose of distributing this document as an RFC is to make it easily accessible to the ARPA research community. This RFC does not specify a standard for the ARPA-Internet. Obsoletes RFC 806. 840 Postel Apr 83 Official Protocols This RFC has been replaced by RFC 991. 839 Smallberg Jan 83 Who Talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 25-Jan-83. 838 Smallberg Jan 83 Who Talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 18-Jan-83. 837 Smallberg Jan 83 Who Talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 11-Jan-83. 836 Smallberg Jan 83 Who Talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was Reynolds & Postel [Page 59] RFC 1000 - Request for Comments Reference Guide August 1987 taken from the NIC hostname table of 20-Dec-82. The tests were run on 4-Jan-83 through 5-Jan-83. 835 Smallberg Dec 82 Who Talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 28-Dec-82 through 5-Jan-83. 834 Smallberg Dec 82 Who Talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 22-Dec-82. 833 Smallberg Dec 82 Who Talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 14-Dec-82. 832 Smallberg Dec 82 Who Talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 7-Dec-82. 831 Braden Dec 82 Backup Access to the European Side of SATNET The purpose of this RFC is to focus discussion on a particular Internet problem: a backup path for software maintenance of the European sector of the Internet, for use when SATNET is partitioned. We propose a mechanism, based upon the Source Routing option of IP, to reach European Internet sites via the VAN Gateway and UCL. This proposal is not intended as a standard at this time. 830 Zaw-Sing Su Oct 82 A Distributed System for Internet Name Service This RFC proposes a distributed name service for ARPA-Internet. Its purpose is to focus discussion on the subject. It is hoped that a general consensus will emerge leading eventually to the adoption of standards. Reynolds & Postel [Page 60] RFC 1000 - Request for Comments Reference Guide August 1987 829 Cerf Oct 82 Packet Satellite Technology Reference Sources This RFC describes briefly the packet satellite technology developed by the Defense Advanced Research Projects Agency and several other participating organizations in the U.K. and Norway and provides a bibliography of relevant papers for researchers interested in experimental and operational experience with this dynamic satellite-sharing technique. 828 Owen Aug 82 Data Communications: IFIP's International "Network" of Experts This RFC is distributed to inform the ARPA-Internet community of the activities of the IFIP technical committee on Data Communications, and to encourage participation in those activities. 827 Rosen Oct 82 Exterior Gateway Protocol (EGP) This RFC is proposed to establish a standard for Gateway to Gateway procedures that allow the Gateways to be mutually suspicious. This document is a DRAFT for that standard. Your comments are strongly encouraged. 826 Plummer Nov 82 An Ethernet Address Resolution Protocol The purpose of this RFC is to present a method of Converting Protocol Addresses (e.g., IP addresses) to Local Network Addresses (e.g., Ethernet addresses). This is an issue of general concern in the ARPA-Internet Community at this time. The method proposed here is presented for your consideration and comment. This is not the specification of an ARPA-Internet Standard. 825 Postel Nov 82 Request for Comments on Requests for Comments This RFC is intended to clarify the status of RFCs and to provide some guidance for the authors of RFCs in the future. It is in a sense a specification for RFCs. 824 MacGregor Aug 82 The Cronus Virtual Local Network The purpose of this note is to describe the CRONUS Virtual Local Network, especially the addressing related features. These features include a method for mapping between Internet Addresses and Local Network addresses. This is a topic of current concern in the ARPA-Internet community. This note is intended to Reynolds & Postel [Page 61] RFC 1000 - Request for Comments Reference Guide August 1987 stimulate discussion. This is not a specification of an ARPA-Internet Standard. 823 Hinden Sep 82 The DARPA Internet Gateway This RFC is a status report on the Internet Gateway developed by BBN. It describes the Internet Gateway as of September 1982. This memo presents detailed descriptions of message formats and gateway procedures, however, this is not an implementation specification, and such details are subject to change. 822 Crocker Aug 82 Standard for the Format of ARPA Internet Text Messages This document revises the specifications in RFC 733, in order to serve the needs of the larger and more complex ARPA-Internet. Some of RFC 733's features failed to gain adequate acceptance. In order to simplify the standard and the software that follows it, these features have been removed. A different addressing scheme is used, to handle the case of internetwork mail; and the concept of re-transmission has been introduced. Obsoletes RFC 733, NIC 41952. 821 Postel Aug 82 Simple Mail Transfer Protocol The objective of Simple Mail Transfer Protocol (SMTP) is to transfer mail reliably and efficiently. SMTP is independent of the particular transmission subsystem and requires only a reliable ordered data stream channel. Obsoletes RFCs 788, 780, 772. 820 Postel Jan 82 Assigned Numbers This RFC is is replaced by RFCs 997 and 990. 819 Zaw-Sing Su Aug 82 The Domain Naming Convention for Internet User Applications This RFC is an attempt to clarify the generalization of the Domain Naming Convention, the Internet Naming Convention, and to explore the implications of its adoption for ARPA-Internet name service and user applications. 818 Postel Nov 82 The Remote User Telnet Service This RFC is the specification of an application protocol. Any host that implements this application level service must follow this protocol. Reynolds & Postel [Page 62] 'ake