| |
| RFC 887 | Resource Location Protocol |
| |
| Authors: | M. Accetta. |
| Date: | December 1983 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
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 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 Internet. |
|
| |
| RFC 908 | Reliable Data Protocol |
| |
| Authors: | D. Velten, R.M. Hinden, J. Sax. |
| Date: | July 1984 |
| Formats: | txt pdf |
| Updated by: | RFC 1151 |
| Status: | EXPERIMENTAL |
|
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. |
|
| |
| RFC 909 | Loader Debugger Protocol |
| |
| Authors: | C. Welles, W. Milliken. |
| Date: | July 1984 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
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 improvemts. |
|
| |
| RFC 938 | Internet Reliable Transaction Protocol functional and interface specification |
| |
| Authors: | T. Miller. |
| Date: | February 1985 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This RFC is being distributed to members of the DARPA research community in order to solicit their reactions to the proposals contained in it. While the issues discussed may not be directly relevant to the research problems of the DARPA community, they may be interesting to a number of researchers and implementors. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 998 | NETBLT: A bulk data transfer protocol |
| |
| Authors: | D.D. Clark, M.L. Lambert, L. Zhang. |
| Date: | March 1987 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0969 |
| Status: | EXPERIMENTAL |
|
This document is a description of, and a specification for, the NETBLT protocol. It is a revision of the specification published in RFC-969. NETBLT (NETwork BLock Transfer) is a transport level protocol intended for the rapid transfer of a large quantity of data between computers. It provides a transfer that is reliable and flow controlled, and is designed to provide maximum throughput over a wide variety of networks. Although NETBLT currently runs on top of the Internet Protocol (IP), it should be able to operate on top of any datagram protocol similar in function to IP. This document is published for discussion and comment, and does not constitute a standard. The proposal may change and certain parts of the protocol have not yet been specified; implementation of this document is therefore not advised. Obsoletes RFC-969. |
|
| |
| RFC 1004 | Distributed-protocol authentication scheme |
| |
| Authors: | D.L. Mills. |
| Date: | April 1 1987 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
The purpose of this RFC is to focus discussion on authentication problems in the Internet and possible methods of solution. The proposed solutions this document are not intended as standards for the Internet at this time. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to authentication problems, leading eventually to the adoption of standards. This document suggests mediated access-control and authentication procedures suitable for those cases when an association is to be set up between users belonging to different trust environments. |
|
| |
| RFC 1045 | VMTP: Versatile Message Transaction Protocol: Protocol specification |
| |
| Authors: | D.R. Cheriton. |
| Date: | February 1988 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This memo specifies the Versatile Message Transaction Protocol (VMTP) [Version 0.7 of 19-Feb-88], a transport protocol specifically designed to support the transaction model of communication, as exemplified by remote procedure call (RPC). The full function of VMTP, including support for security, real-time, asynchronous message exchanges, streaming, multicast and idempotency, provides a rich selection to the VMTP user level. Subsettability allows the VMTP module for particular clients and servers to be specialized and simplified to the services actually required. Examples of such simple clients and servers include PROM network bootload programs, network boot servers, data sensors and simple controllers, to mention but a few examples. This RFC describes a protocol proposed as a standard for the Internet community. |
|
| |
| RFC 1075 | Distance Vector Multicast Routing Protocol |
| |
| Authors: | D. Waitzman, C. Partridge, S.E. Deering. |
| Date: | November 1988 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This RFC describes a distance-vector-style routing protocol for routing multicast datagrams through an internet. It is derived from the Routing Information Protocol (RIP), and implements multicasting as described in RFC-1054. This is an experimental protocol, and its implementation is not recommended at this time. |
|
| |
| RFC 1105 | Border Gateway Protocol (BGP) |
| |
| Authors: | K. Lougheed, Y. Rekhter. |
| Date: | June 1989 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1163 |
| Status: | EXPERIMENTAL |
|
This RFC outlines a specific approach for the exchange of network reachability information between Autonomous Systems. Updated by RFCs 1163 and 1164. [STANDARDS-TRACK] |
|
| |
| RFC 1138 | Mapping between X.400(1988) / ISO 10021 and RFC 822 |
| |
|
|
Ths RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This memo updates RFCs 822, 987, and 1026. |
|
| |
| RFC 1143 | The Q Method of Implementing TELNET Option Negotiation |
| |
| Authors: | D.J. Bernstein. |
| Date: | February 1990 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This is RFC discusses an implementation approach to option negotiation in the Telnet protocol (RFC 854). It does not propose any changes to the TELNET protocol. Rather, it discusses the implementation of the protocol of one feature, only. This is not a protocol specification. This is an experimental method of implementing a protocol. |
|
| |
| RFC 1145 | TCP alternate checksum options |
| |
| Authors: | J. Zweig, C. Partridge. |
| Date: | February 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1146 |
| Status: | EXPERIMENTAL |
|
This memo is suggests a pair of TCP options to allow use of alternate data checksum algorithms in the TCP header. The use of these options is experimental, and not recommended for production use. |
|
| |
| RFC 1146 | TCP alternate checksum options |
| |
| Authors: | J. Zweig, C. Partridge. |
| Date: | March 1990 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1145 |
| Status: | EXPERIMENTAL |
|
This memo is suggests a pair of TCP options to allow use of alternate data checksum algorithms in the TCP header. The use of these options is experimental, and not recommended for production use. Note: This RFC corrects errors introduced in the editing process in RFC 1145. |
|
| |
| RFC 1148 | Mapping between X.400(1988) / ISO 10021 and RFC 822 |
| |
|
|
This RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This edition includes material lost in editing. |
|
| |
| RFC 1149 | Standard for the transmission of IP datagrams on avian carriers |
| |
| Authors: | D. Waitzman. |
| Date: | April 1 1990 |
| Formats: | txt pdf |
| Updated by: | RFC 2549 |
| Status: | EXPERIMENTAL |
|
This memo describes an experimental method for the encapsulation of IP datagrams in avian carriers. This specification is primarily useful in Metropolitan Area Networks. This is an experimental, not recommended standard. |
|
| |
| RFC 1151 | Version 2 of the Reliable Data Protocol (RDP) |
| |
| Authors: | C. Partridge, R.M. Hinden. |
| Date: | April 1 1990 |
| Formats: | txt pdf |
| Updates: | RFC 0908 |
| Status: | EXPERIMENTAL |
|
This RFC suggests several updates to the specification of the Reliable Data Protocol (RDP) in RFC-908 based on experience with the protocol. This revised version of the protocol is experimental. |
|
| |
| RFC 1153 | Digest message format |
| |
| Authors: | F.J. Wancho. |
| Date: | April 1 1990 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This memo describes the de facto standard Digest Message Format. This is an elective experimental protocol. |
|
| |
| RFC 1154 | Encoding header field for internet messages |
| |
| Authors: | D. Robinson, R. Ullmann. |
| Date: | April 1 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1505 |
| Status: | EXPERIMENTAL |
|
This RFC proposes an elective experimental Encoding header field to permit the mailing of multi-part, multi-structured messages. The use of Encoding updates RFC 1049 (Content-Type), and is a suggested update to RFCs 1113, 1114, and 1115 (Privacy Enhancement). |
|
| |
| RFC 1159 | Message Send Protocol |
| |
| Authors: | R. Nelson. |
| Date: | June 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1312 |
| Status: | EXPERIMENTAL |
|
This RFC suggests an Experimental Protocol for the Internet community. Hosts on the Internet that choose to implement a Message Send Protocol may experiment with this protocol. |
|
| |
| RFC 1161 | SNMP over OSI |
| |
| Authors: | M.T. Rose. |
| Date: | June 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1418 |
| Status: | EXPERIMENTAL |
|
This memo defines an experimental means for running the Simple Network Management Protocol (SNMP) over OSI transports. This memo does not specify a standard for the Internet community, |
|
| |
| RFC 1162 | Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Management Information Base |
| |
| Authors: | G. Satz. |
| Date: | June 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1238 |
| Status: | EXPERIMENTAL |
|
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. This memo does not specify a standard for the Internet community. |
|
| |
| RFC 1165 | Network Time Protocol (NTP) over the OSI Remote Operations Service |
| |
| Authors: | J. Crowcroft, J.P. Onions. |
| Date: | June 1990 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This memo suggests an Experimental Protocol for the OSI and Internet communities. Hosts in either community, and in particular those on both are encouraged to experiment with this mechanism. |
|
| |
| RFC 1176 | Interactive Mail Access Protocol: Version 2 |
| |
| Authors: | M.R. Crispin. |
| Date: | August 1990 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1064 |
| Status: | EXPERIMENTAL |
|
This RFC suggests a method for personal computers and workstations to dynamically access mail from a mailbox server ("repository"). It obosoletes RFC 1064. This RFC specifies an Experimental Protocol for the Internet community. Discussion and suggestions for improvement are requested. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. |
|
| |
| RFC 1183 | New DNS RR Definitions |
| |
| Authors: | C.F. Everhart, L.A. Mamakos, R. Ullmann, P.V. Mockapetris. |
| Date: | October 1990 |
| Formats: | txt pdf |
| Updates: | RFC 1034, RFC 1035 |
| Updated by: | RFC 5395 |
| Status: | EXPERIMENTAL |
|
This memo defines five new DNS types for experimental purposes. This RFC describes an Experimental Protocol for the Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 1185 | TCP Extension for High-Speed Paths |
| |
| Authors: | V. Jacobson, R.T. Braden, L. Zhang. |
| Date: | October 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1323 |
| Status: | EXPERIMENTAL |
|
This memo describes an Experimental Protocol extension to TCP for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. |
|
| |
| RFC 1187 | Bulk Table Retrieval with the SNMP |
| |
| Authors: | M.T. Rose, K. McCloghrie, J.R. Davin. |
| Date: | October 1990 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This memo reports an interesting family of algorithms for bulk table retrieval using the Simple Network Management Protocol (SNMP). This memo describes an Experimental Protocol for the Internet community, and requests discussion and suggestions for improvements. This memo does not specify a standard for the Internet community. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. |
|
| |
| RFC 1190 | Experimental Internet Stream Protocol: Version 2 (ST-II) |
| |
| Authors: | C. Topolcic. |
| Date: | October 1990 |
| Formats: | txt pdf |
| Obsoletes: | IEN 119 |
| Obsoleted by: | RFC 1819 |
| Status: | EXPERIMENTAL |
|
This memo defines a revised version of the Internet Stream Protocol, originally defined in IEN-119 [8], based on results from experiments with the original version, and subsequent requests, discussion, and suggestions for improvements. This is a Limited-Use Experimental Protocol. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. |
|
| |
| RFC 1204 | Message Posting Protocol (MPP) |
| |
| Authors: | S. Yeh, D. Lee. |
| Date: | February 1991 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This memo describes a protocol for posting messages from workstations (e.g., PCs) to a mail service host. This RFC specifies an Experimental Protocol for the Internet community. It does not specify any standard. |
|
| |
| RFC 1224 | Techniques for managing asynchronously generated alerts |
| |
| Authors: | L. Steinberg. |
| Date: | May 1991 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This RFC explores mechanisms to prevent a remotely managed entity from burdening a manager or network with an unexpected amount of network management information, and to ensure delivery of "important" information. The focus is on controlling the flow of asynchronously generated information, and not how the information is generated. |
|
| |
| RFC 1226 | Internet protocol encapsulation of AX.25 frames |
| |
| Authors: | B. Kantor. |
| Date: | May 1991 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This memo describes a method for the encapsulation of AX.25 (the Amateur Packet-Radio Link-Layer Protocol) frames within IP packets. This technique is an Experimental Protocol for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1228 | SNMP-DPI: Simple Network Management Protocol Distributed Program Interface |
| |
| Authors: | G. Carpenter, B. Wijnen. |
| Date: | May 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1592 |
| Status: | EXPERIMENTAL |
|
This RFC describes a protocol that International Business Machines Corporation (IBM) has been implementing in most of its SNMP agents to allow dynamic extension of supported MIBs. This is an Experimental Protocol for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1235 | Coherent File Distribution Protocol |
| |
| Authors: | J. Ioannidis, G. Maguire. |
| Date: | June 1991 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This memo describes the Coherent File Distribution Protocol (CFDP). This is an Experimental Protocol for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1238 | CLNS MIB for use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) |
| |
| Authors: | G. Satz. |
| Date: | June 1991 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1162 |
| Status: | EXPERIMENTAL |
|
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. This is an Experimental Protocol for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1241 | Scheme for an internet encapsulation protocol: Version 1 |
| |
| Authors: | R.A. Woodburn, D.L. Mills. |
| Date: | July 1991 |
| Formats: | txt pdf ps |
| Status: | EXPERIMENTAL |
|
This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1279 | X.500 and Domains |
| |
| Authors: | S.E. Hardcastle-Kille. |
| Date: | November 1991 |
| Formats: | txt ps pdf |
| Status: | EXPERIMENTAL |
|
This RFCconsiders X.500 in relation to Internet and UK Domains.A basic model of X.500 providing a higher level and more descriptive naming structure is emphasised. In addition, a mapping of domains onto X.500 is proposed, which gives a range of new management and user facilities over and above those currently available. This specification proposes an experimental new mechanism to access and manage domain information on the Internet and in the UK Academic Community. There is no current intention to provide an operational replacement for DNS. |
|
| |
| RFC 1283 | SNMP over OSI |
| |
| Authors: | M. Rose. |
| Date: | December 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1418 |
| Status: | EXPERIMENTAL |
|
This memo describes mappings from the SNMP onto both the COTS and the CLTS. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet Standard. |
|
| |
| RFC 1307 | Dynamically Switched Link Control Protocol |
| |
| Authors: | J. Young, A. Nicholson. |
| Date: | March 1992 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This memo describes an experimental protocol developed by a project team at Cray Research, Inc., in implementing support for circuit- switched T3 services. The protocol is used for the control of network connections external to a host, but known to the host. It is documented here for the benefit of others who may wish to perform further research.
While working with circuit-switched T3 networks, developers at CrayResearch, Inc., defined a model wherein a host would generate control messages for a network switch. This work is described in RFC 1306,"Experiences Supporting By-Request Circuit-Switched T3 Networks". In order to simplify the model it was decided that the inconsistencies of switch control should be hidden from the host generating the control messages. To that end, a protocol was defined and implemented. This RFC documents the Dynamically Switched LinkControl Protocol (DSLCP), which is used for creation and control of downstream network links by a host. |
|
| |
| RFC 1312 | Message Send Protocol 2 |
| |
| Authors: | R. Nelson, G. Arnold. |
| Date: | April 1992 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1159 |
| Status: | EXPERIMENTAL |
|
The Message Send Protocol is used to send a short message to a given user on a given terminal on a given host. This memo defines an Experimental Protocol for the Internet community. |
|
| |
| RFC 1339 | Remote Mail Checking Protocol |
| |
| Authors: | S. Dorner, P. Resnick. |
| Date: | June 1992 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This RFC defines a protocol to provide a mail checking service to be used between a client and server pair. Typically, a small program on a client workstation would use the protocol to query a server in order to find out whether new mail has arrived for a specified user. |
|
| |
| RFC 1348 | DNS NSAP RRs |
| |
|
|
This RFC defines the format of two new Resource Records (RRs) for the Domain Name System (DNS), and reserves corresponding DNS type mnemonic and numerical codes. This memo defines an Experimental Protocol for the Internet community. |
|
| |
| RFC 1383 | An Experiment in DNS Based IP Routing |
| |
| Authors: | C. Huitema. |
| Date: | December 1992 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
Potential solutions to the routing explosion. This memo defines an Experimental Protocol for the Internet community. |
|
| |
| RFC 1393 | Traceroute Using an IP Option |
| |
| Authors: | G. Malkin. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
Traceroute serves as a valuable network debugging tool. The way in which it is currently implemented has the advantage of being automatically supported by all of the routers. It's two problems are the number of packets it generates and the amount of time it takes to run.
This document specifies a new IP option and ICMP message type which duplicates the functionality of the existing traceroute method while generating fewer packets and completing in a shorter time. |
|
| |
| RFC 1405 | Mapping between X.400(1984/1988) and Mail-11 (DECnet mail) |
| |
| Authors: | C. Allocchio. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2162 |
| Status: | EXPERIMENTAL |
|
This document describes a set of mappings which will enable inter working between systems operating the CCITT X.400 ( 1984 / 1988 )Recommendations on Message Handling Systems, and systems running theMail-11 (also known as DECnet mail) protocol. The specifications are valid within DECnet Phase IV addressing and routing scheme.
The complete scenario of X.400 / RFC822 / Mail-11 is also considered, in order to cover the possible complex cases arising in multiple gateway translations.
This document covers mainly the O/R address to DECnet from/to address mapping (and vice versa); other mappings are based on RFC 1327 and its eventual future updates.
This is a combined effort of COSINE S2.2, the RARE MSG Working Group, and the IETF X.400 Ops Working Group. |
|
| |
| RFC 1409 | Telnet Authentication Option |
| |
| Authors: | D. Borman, Ed.. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1416 |
| Status: | EXPERIMENTAL |
|
This memo defines an Experimental Protocol for the Internet community. |
|
| |
| RFC 1411 | Telnet Authentication: Kerberos Version 4 |
| |
| Authors: | D. Borman, Ed.. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This memo defines an Experimental Protocol for the Internet community. |
|
| |
| RFC 1412 | Telnet Authentication: SPX |
| |
| Authors: | K. Alagappan. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This memo defines an Experimental Protocol for the Internet community. |
|
| |
| RFC 1416 | Telnet Authentication Option |
| |
| Authors: | D. Borman, Ed.. |
| Date: | February 1993 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1409 |
| Obsoleted by: | RFC 2941 |
| Status: | EXPERIMENTAL |
|
This RFC 1416 replaces RFC 1409, which has an important typographical error in the example on page 6 (one occurance of "REPLY" should be "IS"). This memo defines an Experimental Protocol for the Internet community. |
|
| |
| RFC 1433 | Directed ARP |
| |
| Authors: | J. Garrett, J. Hagan, J. Wong. |
| Date: | March 1993 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
A router with an interface to two IP networks via the same link level interface could observe that the two IP networks share the same link level network, and could advertise that information to hosts (viaICMP Redirects) and routers (via dynamic routing protocols).However, a host or router on only one of the IP networks could not use that information to communicate directly with hosts and routers on the other IP network unless it could resolve IP addresses on the"foreign" IP network to their corresponding link level addresses.Directed ARP is a dynamic address resolution procedure that enables hosts and routers to resolve advertised potential next-hop IP addresses on foreign IP networks to their associated link level addresses. |
|
| |
| RFC 1440 | SIFT/UFT: Sender-Initiated/Unsolicited File Transfer |
| |
| Authors: | R. Troth. |
| Date: | July 1993 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This document describes a Sender-Initiated File Transfer (SIFT) protocol, also commonly called Unsolicited File Transfer (UFT) protocol. This memo defines an Experimental Protocol for the Internet community. |
|
| |
| RFC 1455 | Physical Link Security Type of Service |
| |
| Authors: | D. Eastlake 3rd. |
| Date: | May 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2474 |
| Status: | EXPERIMENTAL |
|
This RFC documents an experimental protocol providing a Type ofService (TOS) to request maximum physical link security. This is an addition to the types of service enumerated in RFC 1349: Type ofService in the Internet Protocol Suite. The new TOS requests the network to provide what protection it can against surreptitious observation by outside agents of traffic so labeled. The purpose is protection against traffic analysis and as an additional possible level of data confidentiality. This TOS is consistent with all other defined types of service for IP version 4 in that it is based on link level characteristics and will not provide any particular guaranteed level of service. |
|
| |
| RFC 1459 | Internet Relay Chat Protocol |
| |
|
|
The IRC protocol was developed over the last 4 years since it was first implemented as a means for users on a BBS to chat amongst themselves. Now it supports a world-wide network of servers and clients, and is stringing to cope with growth. Over the past 2 years, the average number of users connected to the main IRC network has grown by a factor of 10.
The IRC protocol is a text-based protocol, with the simplest client being any socket program capable of connecting to the server. |
|
| |
| RFC 1464 | Using the Domain Name System To Store Arbitrary String Attributes |
| |
| Authors: | R. Rosenbaum. |
| Date: | May 1993 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
While the Domain Name System (DNS) [2,3] is generally used to store predefined types of information (e.g., addresses of hosts), it is possible to use it to store information that has not been previously classified.
This paper describes a simple means to associate arbitrary string information (ASCII text) with attributes that have not been defined by the DNS. It uses DNS TXT resource records to store the information. It requires no change to current DNS implementations. |
|
| |
| RFC 1465 | Routing Coordination for X.400 MHS Services Within a Multi Protocol / Multi Network Environment Table Format V3 for Static Routing |
| |
| Authors: | D. Eppenberger. |
| Date: | May 1993 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This document proposes short term solutions for maintaining and distributing routing information and shows how messages can travel over different networks by using multi stack MTAs as relays. This memo defines an Experimental Protocol for the Internet community. |
|
| |
| RFC 1475 | TP/IX: The Next Internet |
| |
| Authors: | R. Ullmann. |
| Date: | June 1993 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
The first version of this memo, describing a possible next generation of Internet protocols, was written by the present author in the summer and fall of 1989, and circulated informally, including to theIESG, in December 1989. A further informal note on the addressing, called "Toasternet Part II", was circulated on the IETF mail list during March of 1992. |
|
| |
| RFC 1476 | RAP: Internet Route Access Protocol |
| |
| Authors: | R. Ullmann. |
| Date: | June 1993 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This RFC describes an open distance vector routing protocol for use at all levels of the internet, from isolated LANs to the major routers of an international commercial network provider. |
|
| |
| RFC 1486 | An Experiment in Remote Printing |
| |
| Authors: | M. Rose, C. Malamud. |
| Date: | July 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1528, RFC 1529 |
| Status: | EXPERIMENTAL |
|
This memo describes a technique for "remote printing" using the Internet mail infrastructure. In particular, this memo focuses on the case in which remote printers are connected to the international telephone network. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1505 | Encoding Header Field for Internet Messages |
| |
| Authors: | A. Costanzo, D. Robinson, R. Ullmann. |
| Date: | August 1993 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1154 |
| Status: | EXPERIMENTAL |
|
This document expands upon the elective experimental Encoding header field which permits the mailing of multi-part, multi-structured messages. It replaces RFC 1154 [1]. |
|
| |
| RFC 1507 | DASS - Distributed Authentication Security Service |
| |
| Authors: | C. Kaufman. |
| Date: | September 1993 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
The goal of DASS is to provide authentication services in a distributed environment which are both more secure and easier to use than existing mechanisms. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1528 | Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures |
| |
| Authors: | C. Malamud, M. Rose. |
| Date: | October 1993 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1486 |
| Status: | EXPERIMENTAL |
|
This memo describes a technique for "remote printing" using the Internet mail infrastructure. In particular, this memo focuses on the case in which remote printers are connected to the international telephone network. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1545 | FTP Operation Over Big Address Records (FOOBAR) |
| |
| Authors: | D. Piscitello. |
| Date: | November 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1639 |
| Status: | EXPERIMENTAL |
|
This paper describes a convention for specifying longer addresses in the PORT command. |
|
| |
| RFC 1561 | Use of ISO CLNP in TUBA Environments |
| |
| Authors: | D. Piscitello. |
| Date: | December 1993 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This memo specifies a profile of the ISO/IEC 8473 Connectionless-modeNetwork Layer Protocol (CLNP, [1]) for use in conjunction with RFC1347, TCP/UDP over Bigger Addresses (TUBA, [2]). It describes the use of CLNP to provide the lower-level service expected byTransmission Control Protocol (TCP, [3]) and User Datagram Protocol(UDP, [4]). CLNP provides essentially the same datagram service asInternet Protocol (IP, [5]), but offers a means of conveying bigger network addresses (with additional structure, to aid routing).
While the protocols offer nearly the same services, IP and CLNP are not identical. This document describes a means of preserving the semantics of IP information that is absent from CLNP while preserving consistency between the use of CLNP in Internet and OSI environments.This maximizes the use of already-deployed CLNP implementations. |
|
| |
| RFC 1592 | Simple Network Management Protocol Distributed Protocol Interface Version 2.0 |
| |
| Authors: | B. Wijnen, G. Carpenter, K. Curran, A. Sehgal, G. Waters. |
| Date: | March 1994 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1228 |
| Status: | EXPERIMENTAL |
|
This RFC describes version 2.0 of a protocol that International Business Machines Corporation (IBM) has been implementing in most of its SNMP agents to allow dynamic extension of supported MIBs. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. |
|
| |
| RFC 1608 | Representing IP Information in the X.500 Directory |
| |
| Authors: | T. Johannsen, G. Mansfield, M. Kosters, S. Sataluri. |
| Date: | March 1994 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This document describes the objects necessary to include information about IP networks and IP numbers in the X.500 Directory. It extends the work "Charting networks in the X.500 Directory" [1] where a general framework is presented for representing networks in theDirectory by applying it to IP networks. This application of theDirectory is intended to support the work of IP network assigning authorities, NICs, as well as other applications looking for a mapping of IP numbers to data of related networks. Furthermore,Autonomous Systems and related routing policy information can be represented in the Directory along with their relationship to networks and organizations. |
|
| |
| RFC 1609 | Charting Networks in the X.500 Directory |
| |
| Authors: | G. Mansfield, T. Johannsen, M. Knopper. |
| Date: | March 1994 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
There is a need for a framework wherein the infrastructural and service related information about communication networks can be made accessible from all places and at all times in a reasonably efficient manner and with reasonable accuracy. This document presents a model in which a communication network with all its related details and descriptions can be represented in the X.500 Directory. Schemas of objects and their attributes which may be used for this purpose are presented. The model envisages physical objects and several logical abstractions of the physical objects. |
|
| |
| RFC 1637 | DNS NSAP Resource Records |
| |
| Authors: | B. Manning, R. Colella. |
| Date: | June 1994 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1348 |
| Obsoleted by: | RFC 1706 |
| Status: | EXPERIMENTAL |
|
The Internet is moving towards the deployment of an OSI lower layers infrastructure. This infrastructure comprises the connectionless network protocol (CLNP) and supporting routing protocols. Also required as part of this infrastructure is support in the Domain NameSystem (DNS) for mapping between names and NSAP addresses.
This document defines the format of one new Resource Record (RR) for the DNS for domain name-to-NSAP mapping. The RR may be used with anyNSAP address format. This document supercedes RFC 1348.
NSAP-to-name translation is accomplished through use of the PTR RR(see STD 13, RFC 1035 for a description of the PTR RR). This paper describes how PTR RRs are used to support this translation. |
|
| |
| RFC 1639 | FTP Operation Over Big Address Records (FOOBAR) |
| |
| Authors: | D. Piscitello. |
| Date: | June 1994 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1545 |
| Status: | EXPERIMENTAL |
|
This paper describes a convention for specifying address families other than the default Internet address family in FTP commands and replies. |
|
| |
| RFC 1641 | Using Unicode with MIME |
| |
| Authors: | D. Goldsmith, M. Davis. |
| Date: | July 1994 |
| Formats: | txt pdf ps |
| Status: | EXPERIMENTAL |
|
The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993(E) jointly define a 16 bit character set (hereafter referred to asUnicode) which encompasses most of the world's writing systems.However, Internet mail (STD 11, RFC 822) currently supports only 7- bit US ASCII as a character set. MIME (RFC 1521 and RFC 1522) extendsInternet mail to support different media types and character sets, and thus could support Unicode in mail messages. MIME neither definesUnicode as a permitted character set nor specifies how it would be encoded, although it does provide for the registration of additional character sets over time.
This document specifies the usage of Unicode within MIME. |
|
| |
| RFC 1642 | UTF-7 - A Mail-Safe Transformation Format of Unicode |
| |
| Authors: | D. Goldsmith, M. Davis. |
| Date: | July 1994 |
| Formats: | txt pdf ps |
| Obsoleted by: | RFC 2152 |
| Status: | EXPERIMENTAL |
|
The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993(E) jointly define a 16 bit character set (hereafter referred to asUnicode) which encompasses most of the world's writing systems.However, Internet mail (STD 11, RFC 822) currently supports only 7- bit US ASCII as a character set. MIME (RFC 1521 and RFC 1522) extendsInternet mail to support different media types and character sets, and thus could support Unicode in mail messages. MIME neither definesUnicode as a permitted character set nor specifies how it would be encoded, although it does provide for the registration of additional character sets over time.
This document describes a new transformation format of Unicode that contains only 7-bit ASCII characters and is intended to be readable by humans in the limiting case that the document consists of characters from the US-ASCII repertoire. It also specifies how this transformation format is used in the context of RFC 1521, RFC 1522, and the document "Using Unicode with MIME". |
|
| |
| RFC 1644 | T/TCP -- TCP Extensions for Transactions Functional Specification |
| |
| Authors: | R. Braden. |
| Date: | July 1994 |
| Formats: | txt pdf |
| Updates: | RFC 1379 |
| Status: | EXPERIMENTAL |
|
This memo specifies T/TCP, an experimental TCP extension for efficient transaction-oriented (request/response) service. This backwards-compatible extension could fill the gap between the current connection-oriented TCP and the datagram-based UDP.
This work was supported in part by the National Science Foundation under Grant Number NCR-8922231. |
|
| |
| RFC 1664 | Using the Internet DNS to Distribute RFC1327 Mail Address Mapping Tables |
| |
| Authors: | C. Allocchio, A. Bonito, B. Cole, S. Giordano, R. Hagens. |
| Date: | August 1994 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2163 |
| Status: | EXPERIMENTAL |
|
This memo defines how to store in the Internet Domain Name System the mapping information needed by e-mail gateways and other tools to mapRFC822 domain names into X.400 O/R names and vice versa. Mapping information can be managed in a distributed rather than a centralised way. Gateways located on Internet hosts can retrieve the mapping information querying the DNS instead of having fixed tables which need to be centrally updated and distributed. This memo is a joint effort of X400 operation working group (x400ops) and RARE Mail andMessaging working group (WG-MSG). |
|
| |
| RFC 1693 | An Extension to TCP : Partial Order Service |
| |
| Authors: | T. Connolly, P. Amer, P. Conrad. |
| Date: | November 1994 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This RFC introduces a new transport mechanism for TCP based upon partial ordering. The aim is to present the concepts of partial ordering and promote discussions on its usefulness in network communications. Distribution of this memo is unlimited. |
|
| |
| RFC 1712 | DNS Encoding of Geographical Location |
| |
| Authors: | C. Farrell, M. Schulze, S. Pleitner, D. Baldoni. |
| Date: | November 1994 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This document defines the format of a new Resource Record (RR) for the Domain Naming System (DNS), and reserves a corresponding DNS type mnemonic and numerical code. This definition deals with associating geographical host location mappings to host names within a domain.The data shown in this document is fictitious and does not necessarily reflect the real Internet. |
|
| |
| RFC 1735 | NBMA Address Resolution Protocol (NARP) |
| |
| Authors: | J. Heinanen, R. Govindan. |
| Date: | December 1994 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This document describes the NBMA Address Resolution Protocol (NARP).NARP can be used by a source terminal (host or router) connected to aNon-Broadcast, Multi-Access link layer (NBMA) network to find out theNBMA addresses of the a destination terminal provided that the destination terminal is connected to the same NBMA network. Although this document focuses on NARP in the context of IP, the technique is applicable to other network layer protocols as well. This RFC is a product of the Routing over Large Clouds Working Group of the IETF. |
|
| |
| RFC 1756 | Remote Write Protocol - Version 1.0 |
| |
| Authors: | T. Rinne. |
| Date: | January 1995 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This document describes a simple Remote Write Protocol (RWP). This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. |
|
| |
| RFC 1765 | OSPF Database Overflow |
| |
| Authors: | J. Moy. |
| Date: | March 1995 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
Proper operation of the OSPF protocol requires that all OSPF routers maintain an identical copy of the OSPF link-state database. However, when the size of the link-state database becomes very large, some routers may be unable to keep the entire database due to resource shortages; we term this "database overflow". When database overflow is anticipated, the routers with limited resources can be accommodated by configuring OSPF stub areas and NSSAs. This memo details a way of gracefully handling unanticipated database overflows.
This memo is a product of the OSPF Working Group. Please send comments to ospf@gated.cornell.edu. |
|
| |
| RFC 1768 | Host Group Extensions for CLNP Multicasting |
| |
| Authors: | D. Marlow. |
| Date: | March 1995 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This memo documents work performed in the TUBA (TCP/UDP over BiggerAddresses) working group of IPng area prior to the July 1994 decision to utilize SIPP-16 as the basis for IPng. The TUBA group worked on extending the Internet Protocol suite by the use of ISO 8473 (CLNP) and its related routing protocols. This memo describes multicast extensions to CLNP and its related routing protocols for Internet multicast use. Publication of this memo does not imply acceptance by any IETF Working Group for the ideas expressed within.
This memo provides a specification for multicast extensions to theCLNP protocol similar to those provided to IP by RFC1112. These extensions are intended to provide the mechanisms needed by a host for multicasting in a CLNP based Internet. This memo covers addressing extensions to the CLNP addressing structure, extensions to the CLNP protocol and extensions to the ES-IS protocol. An appendix discusses the differences between IP multicast and the CLNP multicast approach provided in this memo. |
|
| |
| RFC 1788 | ICMP Domain Name Messages |
| |
| Authors: | W. Simpson. |
| Date: | April 1995 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
This document specifies ICMP messages for learning the FullyQualified Domain Name associated with an IP address. |
|
| |
| RFC 1791 | TCP And UDP Over IPX Networks With Fixed Path MTU |
| |
| Authors: | T. Sung. |
| Date: | April 1995 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
TCP/IPX allows TCP/IP applications to run over IPX networks by letting TCP and UDP run over IPX. And this memo specifies the packet format and operational procedures for running TCP and UDP over IPX. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind. |
|
| |
| RFC 1792 | TCP/IPX Connection Mib Specification |
| |
| Authors: | T. Sung. |
| Date: | April 1995 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
New MIB objects, tcpIpxConnTable, udpIpxTable, tcpUnspecConnTable and udpUnspecTable are presented in this paper, to be used in place of tcpConnTable and udpListenerTable when TCP and UDP are running over IPX. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind. |
|
| |
| RFC 1797 | Class A Subnet Experiment |
| |
| Authors: | Internet Assigned Numbers Authority (IANA). |
| Date: | April 1995 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
There appears to be some interest in experimenting with subnetting the class A addresses. It is suggested that conducting an experiment now to identify and fix any software that does not properly handle subnetted class A addresses would be useful and important. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind. |
|
| |
| RFC 1801 | MHS use of the X.500 Directory to support MHS Routing |
| |
| Authors: | S. Kille. |
| Date: | June 1995 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
The key problem in routing is to map from an O/R Address onto an MTA (next hop). This shall be an MTA which in some sense is "nearer" to the destination UA. This is done repeatedly until the message can be directly delivered to the recipient UA. This memo defines an Experimental Protocol for the Internet community. |
|
| |
| RFC 1804 | Schema Publishing in X.500 Directory |
| |
| Authors: | G. Mansfield, P. Rajeev, S. Raghavan, T. Howes. |
| Date: | June 1995 |
| Formats: | txt pdf |
| Status: | EXPERIMENTAL |
|
The X.500 directory provides a powerful mechanism for storing and retrieving information about objects of interest. To interpret the information stored in the directory, the schema must be known to all the components of the directory. Presently, there are no means other than ftp to distribute schema information across the Internet. This is proving to be a severe constraint as the Directory is growing.This document presents a solution to the schema distribution problem using the existing mechanisms of the directory. A naming scheme for naming schema objects and a meta-schema for storing schema objects is presented. The procedures for fetching unknown schema from the directory at runtime are described. |
|
| |
| RFC 1806 | Communicating Presentation Information in Internet Messages: The Content-Disposition Header |
| |
| Authors: | R. Troost, S. Dorner. |
| Date: | June 1995 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2183 |
| Status: | EXPERIMENTAL |
|
This memo provides a mechanism whereby messages conforming to the[RFC 1521] ("MIME") specification can convey presentational information. It specifies a new "Content-Disposition" header, optional and valid for any [RFC 1521] entity ("message" or "body part"). Two values for this header are described in this memo; one for the ordinary linear presentation of the body part, and another to facilitate the use of mail to transfer files. It is expected that more values will be defined in the future, and procedures are defined for extending this set of values.
This document is intended as an extension to [RFC 1521]. As such, the reader is assumed to be familiar with [RFC 1521], and [RFC 822]. The information presented herein supplements but does not replace that found in those documents. |
|
| |
| RFC 1819 | Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+ |
| |
| Authors: | L. Delgrossi, L. Berger, Eds.. |
| Date: | August 1995 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1190, IEN 119 |
| Status: | EXPERIMENTAL |
|
This memo contains a revised specification of the Internet STreamProtocol Version 2 (ST2). ST2 is an experimental resource reservation protocol intended to provide end-to-end real-time guarantees over an internet. It allows applications to build multi-destination simplex data streams with a desired quality of service. The revised version of ST2 specified in this memo is called ST2+.
This specification is a product of the STream Protocol Working Group of the Internet Engineering Task Force. |
|
| |
| RFC 1830 | SMTP Service Extensions for Transmission of Large and Binary MIME Messages |
| |
| Authors: | G. Vaudreuil. |
| Date: | August 1995 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 3030 |
| Status: | EXPERIMENTAL |
|
This memo defines two extensions to the SMTP service. The first service enables a SMTP client and server to negotiate the use of an alternate DATA command "BDAT" for efficiently sending large MIME messages. The second extension takes advantage of the BDAT command to permit the negotiated sending of unencoded binary data. This memo defines an Experimental Protocol for the Internet community. |
|
| |
| RFC 1836 | Representing the O/R Address hierarchy in the X.500 Directory Information Tree |
| |
| Authors: | S. Kille. |
| Date: | August 1995 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2294 |
| Status: | EXPERIMENTAL |
|
This document defines a representation of the O/R Address hierarchy in the Directory Information Tree [6, 1]. This is useful for a range of purposes, including: |
|
| |
| RFC 1837 | Representing Tables and Subtrees in the X.500 Directory |
| |
| Authors: | S. Kille. |
| Date: | August 1995 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2293 |
| Status: | EXPERIMENTAL |
|
This document defines techniques for representing two types of information mapping in the OSI Directory [1].
1. Mapping from a key to a value (or set of values), as might be done in a table lookup.
2. Mapping from a distinguished name to an associated value (or values), where the values are not defined by the owner of the entry. This is achieved by use of a directory subtree.
These techniques were developed for supporting MHS use of Directory[2], but are specified separately as they have more general applicability. |
|
| |
| RFC 1838 | Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses |
| |
| Authors: | S. Kille. |
| Date: | August 1995 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2164 |
| Status: | EXPERIMENTAL |
|
This document defines how to use directory to support the mapping between X.400 O/R Addresses and mailboxes defined in RFC 1327 [2]. |
|
| |
| RFC 1845 | SMTP Service Extension for Checkpoint/Restart |
| |
| Authors: | D. Crocker, N. Freed, A. Cargille. |
| Date: | September 1995 |
| Formats: | txt |
| |
