Internet Documents RFCs RFCs All Documents STDs Internet Standards Documents BCPs Best Current Practice Documents FYIs Informational Documents

RFC 35	Network Meeting
	Authors: S.D. Crocker. Date: March 1970 Formats: txt pdf Status: INFORMATIONAL
RFC 96	An Interactive Network Experiment to Study Modes of Access the Network Information Center
	Authors: R.W. Watson. Date: February 1971 Formats: txt pdf Status: INFORMATIONAL
RFC 699	Request For Comments summary notes: 600-699
	Authors: J. Postel, J. Vernon. Date: November 1982 Formats: txt pdf Status: INFORMATIONAL
RFC 800	Request For Comments summary notes: 700-799
	Authors: J. Postel, J. Vernon. Date: November 1982 Formats: txt pdf Status: INFORMATIONAL This RFC is a slightly annotated list of the 100 RFCs from RFC 700 through RFC 799. This is a status report on these RFCs.
RFC 899	Request For Comments summary notes: 800-899
	Authors: J. Postel, A. Westine. Date: May 1984 Formats: txt pdf Status: INFORMATIONAL
RFC 1012	Bibliography of Request For Comments 1 through 999
	Authors: J.K. Reynolds, J. Postel. Date: June 1987 Formats: txt pdf Status: INFORMATIONAL This RFC is a reference guide for the Internet community which provides a bibliographic summary of the Request for Comments numbers 1 through 999 issued between the years 1969-1987.
RFC 1056	PCMAIL: A distributed mail system for personal computers
	Authors: M.L. Lambert. Date: June 1988 Formats: txt pdf Obsoletes: RFC 0993 Status: INFORMATIONAL This memo is a discussion of the Pcmail workstation based distributed mail system. It is identical to the discussion in RFC-993, save that a new, much simpler mail transport protocol is described. The new transport protocol is the result of continued research into ease of protocol implementation and use issues.
RFC 1057	RPC: Remote Procedure Call Protocol specification: Version 2
	Authors: Sun Microsystems. Date: June 1988 Formats: txt pdf Obsoletes: RFC 1050 Status: INFORMATIONAL This RFC describes a standard that Sun Microsystems and others are using, and is one we wish to propose for the Internet's consideration. This memo is not an Internet standard at this time.
RFC 1094	NFS: Network File System Protocol specification
	Authors: B. Nowicki. Date: March 1989 Formats: txt pdf Also: RFC 1813 Status: INFORMATIONAL This RFC describes a protocol that Sun Microsystems, Inc., and others are using. A new version of the protocol is under development, but others may benefit from the descriptions of the current protocol, and discussion of some of the design issues.
RFC 1099	Request for Comments Summary: RFC Numbers 1000-1099
	Authors: J. Reynolds. Date: December 1991 Formats: txt pdf Status: INFORMATIONAL
RFC 1107	Plan for Internet directory services
	Authors: K.R. Sollins. Date: July 1989 Formats: txt pdf Status: INFORMATIONAL This memo proposes a program to develop a directory service for the Internet. It reports the results of a meeting held in February 1989, which was convened to review requirements and options for such a service. This proposal is offered for comment, and does not represent a committed research activity of the Internet community.
RFC 1111	Request for comments on Request for Comments: Instructions to RFC authors
	Authors: J. Postel. Date: August 1989 Formats: txt pdf Obsoletes: RFC 0825 Obsoleted by: RFC 1543, RFC 2223 Status: INFORMATIONAL This RFC specifies a standard for the Internet community. Authors of RFCs are expected to adopt and implement this standard.
RFC 1117	Internet numbers
	Authors: S. Romano, M.K. Stahl, M. Recker. Date: August 1989 Formats: txt pdf Obsoletes: RFC 1062, RFC 1020, RFC 0997 Obsoleted by: RFC 1166 Status: INFORMATIONAL This memo is an official status report on the network numbers and the autonomous system numbers used in the Internet community.
RFC 1118	Hitchhikers guide to the Internet
	Authors: E. Krol. Date: September 1989 Formats: txt pdf Status: INFORMATIONAL This RFC is being distributed to members of the Internet community in order to make available some "hints" which will allow new network participants to understand how the direction of the Internet is set, how to acquire online information and how to be a good Internet neighbor. While the information discussed may not be relevant to the research problems of the Internet, it may be interesting to a number of researchers and implementors. No standards are defined or specified in this memo.
RFC 1120	Internet Activities Board
	Authors: V. Cerf. Date: September 1989 Formats: txt pdf Obsoleted by: RFC 1160 Status: INFORMATIONAL This RFC provides a history and description of the Internet Activities Board (IAB) and its subsidiary organizations. This memo is for informational use and does not constitute a standard.
RFC 1121	Act one - the poems
	Authors: J. Postel, L. Kleinrock, V.G. Cerf, B. Boehm. Date: September 1989 Formats: txt pdf Status: INFORMATIONAL This RFC presents a collection of poems that were presented at "Act One", a symposium held partially in celebration of the 20th anniversary of the ARPANET.
RFC 1127	Perspective on the Host Requirements RFCs
	Authors: R.T. Braden. Date: October 1989 Formats: txt pdf Status: INFORMATIONAL This RFC is for information only; it does not constitute a standard, draft standard, or proposed standard, and it does not define a protocol.
RFC 1129	Internet Time Synchronization: The Network Time Protocol
	Authors: D.L. Mills. Date: October 1989 Formats: txt pdf ps Also: RFC 1119 Status: INFORMATIONAL This memo describes the Network Time Protocol (NTP) designed to distribute time information in a large, diverse internet system operating at speeds from mundane to lightwave. It uses a returnable- time architecture in which a distributed subnet of time servers operating in a self-organizing, hierarchical, master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute time information within a network via local routing algorithms and time daemons. The architectures, algorithms and protocols which have evolved to NTP over several years of implementation and refinement are described in this paper. The synchronization subnet which has been in regular operation in the Internet for the last several years is described along with performance data which shows that timekeeping accuracy throughout most portions of the Internet can be ordinarily maintained to within a few tens of milliseconds, even in cases of failure or disruption of clocks, time servers or networks. This memo describes the Network Time Protocol in RFC-1119.
RFC 1133	Routing between the NSFNET and the DDN
	Authors: J.Y. Yu, H.W. Braun. Date: November 1989 Formats: txt pdf Status: INFORMATIONAL This document is a case study of the implementation of routing between the NSFNET and the DDN components (the MILNET and the ARPANET). We hope that it can be used to expand towards interconnection of other Administrative Domains. We would welcome discussion and suggestions about the methods employed for the interconnections. No standards are specified in this memo.
RFC 1135	Helminthiasis of the Internet
	Authors: J.K. Reynolds. Date: December 1989 Formats: txt pdf Status: INFORMATIONAL This memo takes a look back at the helminthiasis (infestation with, or disease caused by parasitic worms) of the Internet that was unleashed the evening of 2 November 1988. This RFC provides information about an event that occurred in the life of the Internet. This memo does not specify any standard. This document provides a glimpse at the infection, its festering, and cure. The impact of the worm on the Internet community, ethics statements, the role of the news media, crime in the computer world, and future prevention is discussed. A documentation review presents four publications that describe in detail this particular parasitic computer program. Reference and bibliography sections are also included.
RFC 1136	Administrative Domains and Routing Domains: A model for routing in the Internet
	Authors: S. Hares, D. Katz. Date: December 1989 Formats: txt pdf Status: INFORMATIONAL This RFC proposes a model for describing routing within the Internet. The model is an adaptation of the "OSI Routeing Framework". This memo does not specify an Internet standard.
RFC 1141	Incremental updating of the Internet checksum
	Authors: T. Mallory, A. Kullberg. Date: January 1990 Formats: txt pdf Updates: RFC 1071 Updated by: RFC 1624 Status: INFORMATIONAL This memo correctly describes the incremental update procedure for use with the standard Internet checksum. It is intended to replace the description of Incremental Update in RFC 1071. This is not a standard but rather, an implementation technique.
RFC 1142	OSI IS-IS Intra-domain Routing Protocol
	Authors: D. Oran, Ed.. Date: February 1990 Formats: txt pdf ps Status: INFORMATIONAL This RFC is a republication of ISO DP 10589 as a service to the Internet community. This is not an Internet standard.
RFC 1147	FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices
	Authors: R.H. Stine. Date: April 1990 Formats: txt pdf ps Obsoleted by: RFC 1470 Status: INFORMATIONAL The goal of this FYI memo is to provide practical information to site administrators and network managers. This memo provides information for the Internet community. It does not specify any standard. It is not a statement of IAB policy or recommendations. [Also FYI 2.] This catalog contains descriptions of several tools available to assist network managers in debugging and maintaining TCP/IP internets and interconnected communications resources. Entries in the catalog tell what a tool does, how it works, and how it can be obtained.
RFC 1152	Workshop report: Internet research steering group workshop on very-high-speed networks
	Authors: C. Partridge. Date: April 1990 Formats: txt pdf Status: INFORMATIONAL This memo is a report on a workshop sponsored by the Internet Research Steering Group. This memo is for information only. This RFC does not specify an Internet standard.
RFC 1160	Internet Activities Board
	Authors: V. Cerf. Date: May 1990 Formats: txt pdf Obsoletes: RFC 1120 Status: INFORMATIONAL This RFC provides a history and description of the Internet Activities Board (IAB) and its subsidiary organizations. This memo is for informational use and does not constitute a standard. This is a revision of RFC 1120.
RFC 1166	Internet numbers
	Authors: S. Kirkpatrick, M.K. Stahl, M. Recker. Date: July 1990 Formats: txt pdf Obsoletes: RFC 1117, RFC 1062, RFC 1020 Updated by: RFC 5737 Status: INFORMATIONAL This memo is a status report on the network numbers and autonomous system numbers used in the Internet community.
RFC 1167	Thoughts on the National Research and Education Network
	Authors: V.G. Cerf. Date: July 1990 Formats: txt pdf Status: INFORMATIONAL The memo provides a brief outline of a National Research and Education Network (NREN). This memo provides information for the Internet community. It does not specify any standard. It is not a statement of IAB policy or recommendations.
RFC 1168	Intermail and Commercial Mail Relay services
	Authors: A. Westine, A.L. DeSchon, J. Postel, C.E. Ward. Date: July 1990 Formats: txt pdf ps Status: INFORMATIONAL This RFC discusses the history and evolution of the Intermail and Commercial mail systems. The problems encountered in operating a store-and-forward mail relay between commercial systems such as Telemail, MCI Mail and Dialcom are also discussed. This RFC provides information for the Internet community, and does not specify any standard.
RFC 1169	Explaining the role of GOSIP
	Authors: V.G. Cerf, K.L. Mills. Date: August 1990 Formats: txt pdf Status: INFORMATIONAL This informational RFC represents the official view of the Internet Activities Board (IAB), after coordination with the Federal Networking Council (FNC). This RFC does not specify a standard.
RFC 1170	Public key standards and licenses
	Authors: R.B. Fougner. Date: January 1991 Formats: txt pdf Status: INFORMATIONAL This RFC is a public statement by Public Key Partners regarding Public Key Standards and Licenses. This memo is for informational use only, and does not constitute an Internet standard.
RFC 1173	Responsibilities of host and network managers: A summary of the "oral tradition" of the Internet
	Authors: J. VanBokkelen. Date: August 1990 Formats: txt pdf Status: INFORMATIONAL This informational RFC describes the conventions to be followed by those in charge of networks and hosts in the Internet. It is a summary of the "oral tradition" of the Internet on this subject. [RFC Editor's note: This memo is a contribution by the author of his view of these conventions. It is expected that this RFC will provide a basis for the development of official policies in the future.] These conventions may be supplemented or amended by the policies of specific local and regional components of the Internet. This RFC does not specify a standard, or a policy of the IAB.
RFC 1174	IAB recommended policy on distributing internet identifier assignment and IAB recommended policy change to internet "connected" status
	Authors: V.G. Cerf. Date: August 1990 Formats: txt pdf Status: INFORMATIONAL This informational RFC represents the official view of the Internet Activities Board (IAB), and describes the recommended policies and procedures on distributing Internet identifier assignments and dropping the connected status requirement. This RFC does not specify a standard.
RFC 1175	FYI on where to start: A bibliography of internetworking information
	Authors: K.L. Bowers, T.L. LaQuey, J.K. Reynolds, K. Roubicek, M.K. Stahl, A. Yuan. Date: August 1990 Formats: txt pdf Also: FYI 0003 Status: INFORMATIONAL The intent of this bibliography is to offer a representative collection of resources of information that will help the reader become familiar with the concepts of internetworking. It is meant to be a starting place for further research. There are references to other sources of information for those users wishing to pursue, in greater depth, the issues and complexities of the current networking environment.
RFC 1177	FYI on Questions and Answers: Answers to commonly asked "new internet user" questions
	Authors: G.S. Malkin, A.N. Marine, J.K. Reynolds. Date: August 1990 Formats: txt pdf Obsoleted by: RFC 1206 Status: INFORMATIONAL This FYI RFC is one of three FYI's called, "Questions and Answers" (Q/A), produced by the User Services Working Group (USWG) of the Internet Engineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard. [Also FYI 4.]
RFC 1178	Choosing a name for your computer
	Authors: D. Libes. Date: August 1990 Formats: txt pdf Also: FYI 0005 Status: INFORMATIONAL In order to easily distinguish between multiple computers, we give them names. Experience has taught us that it is as easy to choose bad names as it is to choose good ones. This essay presents guidelines for deciding what makes a name good or bad. Keywords: domain name system, naming conventions, computer administration, computer network management
RFC 1179	Line printer daemon protocol
	Authors: L. McLaughlin. Date: August 1990 Formats: txt pdf Status: INFORMATIONAL This RFC describes an existing print server protocol widely used on the Internet for communicating between line printer daemons (both clients and servers). This memo is for informational purposes only, and does not specify an Internet standard. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol.
RFC 1180	TCP/IP tutorial
	Authors: T.J. Socolofsky, C.J. Kale. Date: January 1991 Formats: txt pdf Status: INFORMATIONAL This RFC is a tutorial on the TCP-IP protocol suite, focusing particularly on the steps in forwarding an IP datagram from source host to destination host through a router. It does not specify an Internet standard.
RFC 1181	RIPE Terms of Reference
	Authors: R. Blokzijl. Date: September 1990 Formats: txt pdf Status: INFORMATIONAL This RFC describes the Terms of Reference of RIPE (Reseaux IP Europeens), the cooperation of European IP networks. This memo provides information for the Internet community. It does not specify any standard.
RFC 1186	MD4 Message Digest Algorithm
	Authors: R.L. Rivest. Date: October 1990 Formats: txt pdf Obsoleted by: RFC 1320 Status: INFORMATIONAL This RFC is the specification of the MD4 Digest Algorithm. If you are going to implement MD4, it is suggested you do it this way. This memo is for informational use and does not constitute a standard.
RFC 1192	Commercialization of the Internet summary report
	Authors: B. Kahin. Date: November 1990 Formats: txt pdf Status: INFORMATIONAL This memo is based on a workshop held by the Science, Technology and Public Policy Program of the John F. Kennedy School of Government, Harvard University, March 1-3, 1990. This memo provides information for the Internet community. It does not specify any standard.
RFC 1193	Client requirements for real-time communication services
	Authors: D. Ferrari. Date: November 1990 Formats: txt pdf Status: INFORMATIONAL A real-time communication service provides its clients with the ability to specify their performance requirements and to obtain guarantees about the satisfaction of those requirements. In this paper, we propose a set of performance specifications that seem appropriate for such services; they include various types of delay bounds, throughput bounds, and reliability bounds. We also describe other requirements and desirable properties from a client's viewpoint, and the ways in which each requirement is to be translated to make it suitable for lower levels in the protocol hierarchy.Finally, we present some examples of requirements specification, and discuss some of the possible objections to our approach. This research has been supported in part by AT&T Bell Laboratories, the University of California under a MICRO grant, and theInternational Computer Science Institute. The views and conclusions in this document are those of the author and should not be interpreted as representing official policies, either expressed or implied, of any of the sponsoring organizations.
RFC 1197	Using ODA for translating multimedia information
	Authors: M. Sherman. Date: December 1990 Formats: txt pdf Status: INFORMATIONAL The purpose of this RFC is to inform implementors of multimedia systems about our experiences using ISO 8613: Office Document Architecture (ODA). Because ODA is being proposed as an encoding format for use in multimedia mail and file exchange, implementors wishing to use ODA in an open systems environment may profit from our experiences. This memo provides information for the Internet community. It does not specify any standard.
RFC 1198	FYI on the X window system
	Authors: R.W. Scheifler. Date: January 1991 Formats: txt pdf Also: FYI 0006 Status: INFORMATIONAL This FYI RFC provides pointers to the published standards of the MIT X Consortium. This memo provides information for the Internet community. It does not specify any Internet standard.
RFC 1199	Request for Comments Summary Notes: 1100-1199
	Authors: J. Reynolds. Date: December 1991 Formats: txt pdf Status: INFORMATIONAL
RFC 1202	Directory Assistance service
	Authors: M.T. Rose. Date: February 1991 Formats: txt pdf Status: INFORMATIONAL This document defines a mechanism by which a user-interface may access a textual DAP-like interface over a TCP/IP connection. This is a local mechanism. This memo provides information for the Internet community. It does not specify any standard.
RFC 1205	5250 Telnet interface
	Authors: P. Chmielewski. Date: February 1991 Formats: txt pdf Updated by: RFC 2877 Status: INFORMATIONAL This RFC is being distributed in order to document the interface to the IBM 5250 Telnet implementation. This memo provides information for the Internet community. It does not specify any standard.
RFC 1206	FYI on Questions and Answers: Answers to commonly asked "new Internet user" questions
	Authors: G.S. Malkin, A.N. Marine. Date: February 1991 Formats: txt pdf Obsoletes: RFC 1177 Obsoleted by: RFC 1325 Status: INFORMATIONAL This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard. [FYI 4]
RFC 1207	FYI on Questions and Answers: Answers to commonly asked "experienced Internet user" questions
	Authors: G.S. Malkin, A.N. Marine, J.K. Reynolds. Date: February 1991 Formats: txt pdf Also: FYI 0007 Status: INFORMATIONAL This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A), produced by the User Services Working Group of the Internet Engineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard.
RFC 1208	A Glossary of Networking Terms
	Authors: O.J. Jacobsen, D.C. Lynch. Date: March 1991 Formats: txt pdf Status: INFORMATIONAL This RFC is a glossary adapted from "The INTEROP Pocket Glossary of Networking Terms" distributed at Interop '90. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1210	Network and infrastructure user requirements for transatlantic research collaboration: Brussels, July 16-18, and Washington July 24-25, 1990
	Authors: V.G. Cerf, P.T. Kirstein, B. Randell. Date: March 1991 Formats: txt pdf Status: INFORMATIONAL This report summarises user requirements for networking and related infrastructure facilities needed to enable effective cooperation between US and European research teams participating in the plannedESPRIT-DARPA/NSF programme of collaborative research in InformationScience and Technology. It analyses the problems and disparities of the current facilities, and suggests appropriate one and three year targets for improvements. It proposes a number of initial actions aimed at achieving these targets. Finally, the workshop has identified a non-exhaustive set of important issues upon which support of future research will depend. These issues could be studied in the short term, with the aim of initiating a programme of joint research in collaboration technology within the next year.
RFC 1211	Problems with the maintenance of large mailing lists
	Authors: A. Westine, J. Postel. Date: March 1991 Formats: txt pdf Status: INFORMATIONAL This RFC discusses problems with maintaining large mailing lists, especially the processing of error reports. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1215	Convention for defining traps for use with the SNMP
	Authors: M.T. Rose. Date: March 1991 Formats: txt pdf Status: INFORMATIONAL This memo suggests a straight-forward approach towards defining traps used with the SNMP. This memo provides information for the Internet community. It does not specify any standard.
RFC 1216	Gigabit network economics and paradigm shifts
	Authors: P. Richard, P. Kynikos. Date: April 1 1991 Formats: txt pdf Status: INFORMATIONAL This memo proposes a new standard paradigm for the Internet Activities Board (IAB) standardization track. [STANDARDS-TRACK]
RFC 1217	Memo from the Consortium for Slow Commotion Research (CSCR)
	Authors: V.G. Cerf. Date: April 1 1991 Formats: txt pdf Status: INFORMATIONAL This RFC is in response to RFC 1216, "Gigabit Network Economics and Paradigm Shifts". This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1218	Naming scheme for c=US
	Authors: North American Directory Forum. Date: April 1991 Formats: txt pdf Obsoleted by: RFC 1255, RFC 1417 Status: INFORMATIONAL This RFC is a near-verbatim copy of a document, known as NADF-123, which has been produced by the North American Directory Forum (NADF). As a part of its charter, the NADF must reach agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1219	On the assignment of subnet numbers
	Authors: P.F. Tsuchiya. Date: April 1991 Formats: txt pdf Status: INFORMATIONAL This memo suggests a new procedure for assigning subnet numbers. Use of this assignment technique within a network would be a purely local matter, and would not effect other networks. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1221	Host Access Protocol (HAP) specification: Version 2
	Authors: W. Edmond. Date: April 1991 Formats: txt pdf Updates: RFC 0907 Status: INFORMATIONAL This memo describes the Host Access Protocol implemented in the Terrestrial Wideband Network (TWBNET). This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1222	Advancing the NSFNET routing architecture
	Authors: H.W. Braun, Y. Rekhter. Date: May 1991 Formats: txt pdf Status: INFORMATIONAL This RFC suggests improvements in the NSFNET routing architecture to accommodate a more flexible interface to the Backbone clients. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1223	OSI CLNS and LLC1 protocols on Network Systems HYPERchannel
	Authors: J.M. Halpern. Date: May 1991 Formats: txt pdf Status: INFORMATIONAL The intent of this document is to provide a complete discussion of the protocols and techniques used to transmit OSI CLNS and LLC1 datagrams (and any associated higher level protocols) on Network Systems Corporation's HYPERchannel equipment.This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1236	IP to X.121 address mapping for DDN
	Authors: L. Morales, P. Hasse. Date: June 1991 Formats: txt pdf Status: INFORMATIONAL This memo defines a standard way of converting IP addresses to CCITT X.121 addresses and is the recommended standard for use on the Internet, specifically for the Defense Data Network (DDN). This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1242	Benchmarking Terminology for Network Interconnection Devices
	Authors: S. Bradner. Date: July 1991 Formats: txt pdf Updated by: RFC 6201 Status: INFORMATIONAL This memo discusses and defines a number of terms that are used in describing performance benchmarking tests and the results of such tests. The terms defined in this memo will be used in additional memos to define specific benchmarking tests and the suggested format to be used in reporting the results of each of the tests. This memo is a product of the Benchmarking Methodology Working Group (BMWG) of the Internet Engineering Task Force (IETF).
RFC 1244	Site Security Handbook
	Authors: J.P. Holbrook, J.K. Reynolds. Date: July 1991 Formats: txt pdf Obsoleted by: RFC 2196 Status: INFORMATIONAL This FYI RFC is a first attempt at providing Internet users guidance on how to deal with security issues in the Internet. This FYI RFC provides information for the Internet community. It does not specify an Internet standard. [FYI 8]
RFC 1245	OSPF Protocol Analysis
	Authors: J. Moy. Date: July 1991 Formats: txt pdf ps Also: RFC 1247, RFC 1246 Status: INFORMATIONAL This report attempts to summarize the key features of OSPF V2. It also attempts to analyze how the protocol will perform and scale in the Internet. This memo provides information for the Internet community. It does not specify any Internet standard.
RFC 1246	Experience with the OSPF Protocol
	Authors: J. Moy. Date: July 1991 Formats: txt pdf ps Also: RFC 1247, RFC 1245 Status: INFORMATIONAL This report documents experience with OSPF V2. This includes reports on interoperability testing, field experience, simulations and the current state of OSPF implementations. This memo provides information for the Internet community. It does not specify any Internet standard.
RFC 1249	DIXIE Protocol Specification
	Authors: T. Howes, M. Smith, B. Beecher. Date: August 1991 Formats: txt pdf Also: RFC 1202 Status: INFORMATIONAL This RFC defines a mechanism by which TCP/UDP based clients can access OSI Directory Service without the overhead of the ISO transport and presentation protocols required to implement full-blown DAP. This memo provides information for the Internet community. It does not specify any standard.
RFC 1251	Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members
	Authors: G. Malkin. Date: August 1991 Formats: txt pdf Obsoleted by: RFC 1336 Status: INFORMATIONAL This FYI RFC contains biographical information about members of the Internet Activities Board (IAB), the Internet Engineering Steering Group (IESG) of the Internet Engineering Task Force (IETF), and the the Internet Research Steering Group (IRSG) of the Internet Research Task Force (IRTF). This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 9]
RFC 1254	Gateway Congestion Control Survey
	Authors: A. Mankin, K. Ramakrishnan. Date: August 1991 Formats: txt pdf Status: INFORMATIONAL The growth of network intensive Internet applications has made gateway congestion control a high priority. The IETF Performance andCongestion Control Working Group surveyed and reviewed gateway congestion control and avoidance approaches. The purpose of this paper is to present our review of the congestion control approaches, as a way of encouraging new discussion and experimentation. Included in the survey are Source Quench, Random Drop, Congestion Indication(DEC Bit), and Fair Queueing. The task remains for Internet implementors to determine and agree on the most effective mechanisms for controlling gateway congestion.
RFC 1255	A Naming Scheme for c=US
	Authors: The North American Directory Forum. Date: September 1991 Formats: txt pdf Obsoletes: RFC 1218 Obsoleted by: RFC 1417 Status: INFORMATIONAL This memo documents the NADF's agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1257	Isochronous applications do not require jitter-controlled networks
	Authors: C. Partridge. Date: September 1991 Formats: txt pdf Status: INFORMATIONAL This memo argues that jitter control is not required for networks to support isochronous applications. A network providing bandwidth and bounds delay is sufficient. The implications for gigabit internetworking protocols are briefly considered.
RFC 1258	BSD Rlogin
	Authors: B. Kantor. Date: September 1991 Formats: txt pdf Obsoleted by: RFC 1282 Status: INFORMATIONAL The rlogin facility provides a remote-echoed, locally flow-controlled virtual terminal with proper flushing of output.This memo documents an existing protocol and common implementation that is extensively used on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1259	Building the open road: The NREN as test-bed for the national public network
	Authors: M. Kapor. Date: September 1991 Formats: txt pdf Status: INFORMATIONAL This memo discusses the background and importance of NREN. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1261	Transition of Nic Services
	Authors: S. Williamson, L. Nobile. Date: September 1991 Formats: txt pdf Status: INFORMATIONAL This memo outlines the transition of NIC Services. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1262	Guidelines for Internet Measurement Activities
	Authors: V.G. Cerf. Date: October 1991 Formats: txt pdf Status: INFORMATIONAL This RFC represents IAB guidance for researchers considering measurement experiments on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1263	TCP Extensions Considered Harmful
	Authors: S. O'Malley, L.L. Peterson. Date: October 1991 Formats: txt pdf Status: INFORMATIONAL This RFC comments on recent proposals to extend TCP. It argues that the backward compatible extensions proposed in RFC's 1072 and 1185 should not be pursued, and proposes an alternative way to evolve theInternet protocol suite. Its purpose is to stimulate discussion in the Internet community.
RFC 1265	BGP Protocol Analysis
	Authors: Y. Rekhter. Date: October 1991 Formats: txt pdf Status: INFORMATIONAL This report summarizes the key feature of BGP, and analyzes the protocol with respect to scaling and performance. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1266	Experience with the BGP Protocol
	Authors: Y. Rekhter. Date: October 1991 Formats: txt pdf Status: INFORMATIONAL The purpose of this memo is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by Border Gateway Protocol (BGP). This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1270	SNMP Communications Services
	Authors: F. Kastenholz. Date: October 1991 Formats: txt pdf Status: INFORMATIONAL This document discusses various issues to be considered when determining the underlying communications services to be used by an SNMP implementation. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1272	Internet Accounting: Background
	Authors: C. Mills, D. Hirsh, G.R. Ruth. Date: November 1991 Formats: txt pdf Status: INFORMATIONAL This document provides background information for the "Internet Accounting Architecture". This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1273	Measurement Study of Changes in Service-Level Reachability in the Global TCP/IP Internet: Goals, Experimental Design, Implementation, and Policy Considerations
	Authors: M.F. Schwartz. Date: November 1991 Formats: txt pdf Status: INFORMATIONAL In this report we discuss plans to carry out a longitudinal measurement study of changes in service-level reachability in the global TCP/IP Internet. We overview our experimental design, considerations of network and remote site load, mechanisms used to control the measurement collection process, and network appropriate use and privacy issues, including our efforts to inform sites measured by this study. A list of references and information on how to contact the Principal Investigator are included.
RFC 1275	Replication Requirements to provide an Internet Directory using X.500
	Authors: S.E. Hardcastle-Kille. Date: November 1991 Formats: txt pdf ps Status: INFORMATIONAL This RFCconsiders certain deficiencies of the 1988 X.500 standard, which need to be addressed before an effective openInternet Directory can be established using these protocols and services [CCI88]. The only areas considered are primary problems, to which solutions must be found before a pilot can be deployed. This RFCconcerns itself with deficiencies which can only be addressed by use of additional protocol or procedures for distributed operation.
RFC 1278	A string encoding of Presentation Address
	Authors: S.E. Hardcastle-Kille. Date: November 1991 Formats: txt ps pdf Status: INFORMATIONAL There are a number of environments where a simple string encoding of Presentation Address is desirable. This specification defines such a representation.
RFC 1281	Guidelines for the Secure Operation of the Internet
	Authors: R. Pethia, S. Crocker, B. Fraser. Date: November 1991 Formats: txt pdf Status: INFORMATIONAL The purpose of this document is to provide a set of guidelines to aid in the secure operation of the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1282	BSD Rlogin
	Authors: B. Kantor. Date: December 1991 Formats: txt pdf Obsoletes: RFC 1258 Status: INFORMATIONAL This memo documents an existing protocol and common implementation that is extensively used on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1287	Towards the Future Internet Architecture
	Authors: D. Clark, L. Chapin, V. Cerf, R. Braden, R. Hobby. Date: December 1991 Formats: txt pdf Status: INFORMATIONAL This informational RFC discusses important directions for possible future evolution of the Internet architecture, and suggests steps towards the desired goals. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1290	There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places
	Authors: J. Martin. Date: December 1991 Formats: txt pdf Obsoleted by: RFC 1402 Status: INFORMATIONAL This document was presented at the 1991 ACM SIGUCCS User ServicesConference. It appears here in its updated form. There is a wealth of information on the network. In fact, so much information, that you could spend your entire life browsing. This paper will present some of the "gold nuggets" of information and file repositories on the network that could be of use to end users. The ultimate goal is to make the route to these sources of information invisible to the user. At present, this is not easy to do. I will explain some of the techniques that can be used to make these nuggets easier to pick up so that we can all be richer.
RFC 1291	Mid-Level Networks Potential Technical Services
	Authors: V. Aggarwal. Date: December 1991 Formats: txt ps pdf Status: INFORMATIONAL This document proposes a set of technical services that each Internet mid-level network can offer within the mid-level network itself and and to its peer networks. The term "mid-level" is used as a generic term to represent all regional and similar networks, which, due to continuous evolutions and transitions, can no longer be termed"regional" [MAN]. It discusses the pros and cons of offering these services, as well as areas in which mid-level networks can work together. A large portion of the ideas stem from discussions at the IETFOperational Statistics (OPstat), User Connectivity Problems (UCP) andNetwork Joint Management (NJM) working groups.
RFC 1292	A Catalog of Available X.500 Implementations
	Authors: R. Lang, R. Wright. Date: January 1992 Formats: txt pdf Obsoleted by: RFC 1632 Status: INFORMATIONAL The goal of this document is to provide information regarding the availability and capability of implementations of X.500. Comments and critiques of this document, and new or updated descriptions ofX.500 implementations are welcome. Send them to the DirectoryInformation Services Infrastructure (DISI) Working Group(disi@merit.edu) or to the editors.
RFC 1295	User Bill of Rights for entries and listings in the Public Directory
	Authors: The North American Directory Forum. Date: January 1992 Formats: txt pdf Obsoleted by: RFC 1417 Status: INFORMATIONAL This RFC is a near-verbatim copy of a document, known as NADF-265, which has been produced by the North American Directory Forum (NADF). User Bill of Rights for entries and listings in the Public Directory The mission of the North American Directory Forum is to provide interconnected electronic directories which empower users with unprecedented access to public information. To address significant security and privacy issues, the North American Directory Forum introduces the following "User Bill of Rights" for entries in thePublic Directory. As a user, you have: I. The right not to be listed. II. The right to have you or your agent informed when your entry is created. III. The right to examine your entry. IV. The right to correct inaccurate information in your entry. V. The right to remove specific information from your entry. VI. The right to be assured that your listing in thePublic Directory will comply with US or Canadian law regulating privacy or access information. VII. The right to expect timely fulfillment of these rights.
RFC 1296	Internet Growth (1981-1991)
	Authors: M. Lottor. Date: January 1992 Formats: txt pdf Status: INFORMATIONAL This document illustrates the growth of the Internet by examination of entries in the Domain Name System (DNS) and pre-DNS host tables.DNS entries are collected by a program called ZONE, which searches the Internet and retrieves data from all known domains. Pre-DNS host table data were retrieved from system archive tapes. Various statistics are presented on the number of hosts and domains.
RFC 1297	NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist ("NOC TT REQUIREMENTS")
	Authors: D. Johnson. Date: January 1992 Formats: txt pdf Status: INFORMATIONAL Professional quality handling of network problems requires some kind of problem tracking system, herein referred to as a "trouble ticket" system. A basic trouble ticket system acts like a hospital chart, coordinating the work of multiple people who may need to work on the problem. Once the basic trouble ticket system is in place, however, there are many extensions that can aid Network Operations efficiency.Information in the tickets can be used to produce statistical reports. Operator efficiency and accuracy may be increased by automating trouble ticket entry with information from the networkAlert system. The Alert system may be used to monitor trouble ticket progress. Trouble tickets may be also used to communicate network health information between NOCs, to telcom vendors, and to other internal sales and engineering audiences. This document explores competing uses, architectures, and desirable features of integrated internal trouble ticket systems for Network and other Operations Centers.
RFC 1298	SNMP over IPX
	Authors: R. Wormley, S. Bostock. Date: February 1992 Formats: txt pdf Obsoleted by: RFC 1420 Status: INFORMATIONAL This memo defines a convention for encapsulating Simple NetworkManagement Protocol (SNMP) [1] packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol [2].
RFC 1299	Summary of 1200-1299
	Authors: M. Kennedy. Date: January 1997 Formats: txt pdf Status: INFORMATIONAL
RFC 1300	Remembrances of Things Past
	Authors: S. Greenfield. Date: February 1992 Formats: txt pdf Status: INFORMATIONAL Poem. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1301	Multicast Transport Protocol
	Authors: S. Armstrong, A. Freier, K. Marzullo. Date: February 1992 Formats: txt pdf Status: INFORMATIONAL This memo describes a protocol for reliable transport that utilizes the multicast capability of applicable lower layer networking architectures. The transport definition permits an arbitrary number of transport providers to perform realtime collaborations without requiring networking clients (aka, applications) to possess detailed knowledge of the population or geographical dispersion of the participating members. It is not network architectural specific, but does implicitly require some form of multicasting (or broadcasting) at the data link level, as well as some means of communicating that capability up through the layers to the transport. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1302	Building a Network Information Services Infrastructure
	Authors: D. Sitzler, P. Smith, A. Marine. Date: February 1992 Formats: txt pdf Also: FYI 0012 Status: INFORMATIONAL This FYI RFC document is intended for existing Internet NetworkInformation Center (NIC) personnel, people interested in establishing a new NIC, Internet Network Operations Centers (NOCs), and funding agencies interested in contributing to user support facilities. The document strives to: - Define a basic set of essential services that NetworkInformation Centers (NICs) will provide to Internet users, including new mechanisms that will facilitate the timely dissemination of information to the Internet community and encourage cooperation among NICs. - Describe existing NIC services as an aid to Internet users and as a model for organizations establishing new NICs.
RFC 1303	A Convention for Describing SNMP-based Agents
	Authors: K. McCloghrie, M. Rose. Date: February 1992 Formats: txt pdf Also: RFC 1155, RFC 1212, RFC 1213, RFC 1157 Status: INFORMATIONAL This memo suggests a straight-forward approach towards describingSNMP-based agents.
RFC 1306	Experiences Supporting By-Request Circuit-Switched T3 Networks
	Authors: A. Nicholson, J. Young. Date: March 1992 Formats: txt pdf Status: INFORMATIONAL This memo describes the experiences of a project team at CrayResearch, Inc., in implementing support for circuit-switched T3 services. While the issues discussed may not be directly relevant to the research problems of the Internet, they may be interesting to a number of researchers and implementers. Developers at Cray Research, Inc. were presented with an opportunity to use a circuit-switched T3 network for wide area networking. They devised an architectural model for using this new resource. This involves activating the circuit-switched connection when an application program engages in a bulk data transfer, and releasing the connection when the transfer is complete. Three software implementations for this feature have been tested, and the results documented here. A variety of issues are involved, and further research is necessary. Network users are beginning to recognize the value of this service, and are planning to make use of by-request circuit-switched networks. A standard method of access will be needed to ensure interoperability among vendors of circuit- switched network support products.
RFC 1308	Executive Introduction to Directory Services Using the X.500 Protocol
	Authors: C. Weider, J. Reynolds. Date: March 1992 Formats: txt pdf Also: FYI 0013 Status: INFORMATIONAL This document is an Executive Introduction to Directory Services using the X.500 protocol. It briefly discusses the deficiencies in currently deployed Internet Directory Services, and then illustrates the solutions provided by X.500. This FYI RFC is a product of the Directory Information Services(pilot) Infrastructure Working Group (DISI). A combined effort of the User Services and the OSI Integration Areas of the InternetEngineering Task Force (IETF).
RFC 1309	Technical Overview of Directory Services Using the X.500 Protocol
	Authors: C. Weider, J. Reynolds, S. Heker. Date: March 1992 Formats: txt pdf Also: FYI 0014 Status: INFORMATIONAL This document is an overview of the X.500 standard for people not familiar with the technology. It compares and contrasts DirectoryServices based on X.500 with several of the other Directory services currently in use in the Internet. This paper also describes the status of the standard and provides references for further information on X.500 implementations and technical information. A primary purpose of this paper is to illustrate the vast functionality of the X.500 protocol and to show how it can be used to provide a global directory for human use, and can support other applications which would benefit from directory services, such as main programs. This FYI RFC is a product of the Directory Information Services(pilot) Infrastructure Working Group (DISI). A combined effort of the User Services and the OSI Integration Areas of the InternetEngineering Task Force (IETF).
RFC 1310	The Internet Standards Process
	Authors: L. Chapin. Date: March 1992 Formats: txt pdf Obsoleted by: RFC 1602 Status: INFORMATIONAL This memo documents the process currently used for the standardization of Internet protocols and procedures. [STANDARDS-TRACK]
RFC 1311	Introduction to the STD Notes
	Authors: J. Postel. Date: March 1992 Formats: txt pdf Status: INFORMATIONAL The STDs are a subseries of notes within the RFC series that are the Internet standards. The intent is to identify clearly for the Internet community those RFCs which document Internet standards. [STANDARDS- TRACK]
RFC 1313	Today's Programming for KRFC AM 1313 Internet Talk Radio
	Authors: C. Partridge. Date: April 1 1992 Formats: txt pdf Status: INFORMATIONAL Hi and welcome to KRFC Internet Talk Radio, your place on the AM dial for lively talk and just-breaking news on internetworking. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1321	The MD5 Message-Digest Algorithm
	Authors: R. Rivest. Date: April 1992 Formats: txt pdf Updated by: RFC 6151 Status: INFORMATIONAL This document describes the MD5 message-digest algorithm. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1322	A Unified Approach to Inter-Domain Routing
	Authors: D. Estrin, Y. Rekhter, S. Hotz. Date: May 1992 Formats: txt pdf Status: INFORMATIONAL This memo is an informational RFC which outlines one potential approach for inter-domain routing in future global internets. The focus is on scalability to very large networks and functionality, as well as scalability, to support routing in an environment of heterogeneous services, requirements, and route selection criteria. Note: The work of D. Estrin and S. Hotz was supported by the NationalScience Foundation under contract number NCR-9011279, with matching funds from GTE Laboratories. The work of Y. Rekhter was supported by the Defense Advanced Research Projects Agency, under contractDABT63-91-C-0019. Views and conclusions expressed in this paper are not necessarily those of the Defense Advanced Research ProjectsAgency and National Science Foundation.
RFC 1324	A Discussion on Computer Network Conferencing
	Authors: D. Reed. Date: May 1992 Formats: txt pdf Status: INFORMATIONAL This memo is intended to make more people aware of the present developments in the Computer Conferencing field as well as put forward ideas on what should be done to formalize this work so that there is a common standard for programmers and others who are involved in this field to work with. It is also the intention of this memo to stimulate the computer community and generate some useful discussion about the merits of this field.
RFC 1325	FYI on Questions and Answers Answers to Commonly asked "New Internet User" Questions
	Authors: G. Malkin, A. Marine. Date: May 1992 Formats: txt pdf Obsoletes: RFC 1206 Obsoleted by: RFC 1594 Status: INFORMATIONAL This FYI RFC is one of two FYI's called, "Questions and Answers"(Q/A), produced by the User Services Working Group of the InternetEngineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet.
RFC 1326	Mutual Encapsulation Considered Dangerous
	Authors: P. Tsuchiya. Date: May 1992 Formats: txt pdf Status: INFORMATIONAL This memo describes a packet explosion problem that can occur with mutual encapsulation of protocols (A encapsulates B and B encapsulates A).
RFC 1329	Thoughts on Address Resolution for Dual MAC FDDI Networks
	Authors: P. Kuehn. Date: May 1992 Formats: txt pdf Updated by: RFC 5494 Status: INFORMATIONAL In this document an idea is submitted how IP and ARP can be used on inhomogeneous FDDI networks (FDDI networks with single MAC and dual MAC stations) by introducing a new protocol layer in the protocol suite of the dual MAC stations. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1330	Recommendations for the Phase I Deployment of OSI Directory Services (X.500) and OSI Message Handling Services (X.400) within the ESNET Community
	Authors: ESCC X.500/X.400 Task Force, ESnet Site Coordinating Comittee (ESCC), Energy Sciences Network (ESnet). Date: May 1992 Formats: txt pdf Status: INFORMATIONAL This RFC is a near verbatim copy of the whitepaper produced by the ESnet Site Coordinating Committee's X.500/X.400 Task Force. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1335	A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space Exhaustion
	Authors: Z. Wang, J. Crowcroft. Date: May 1992 Formats: txt pdf Status: INFORMATIONAL This RFC presents a solution to problem of address space exhaustion in the Internet. It proposes a two-tier address structure for theInternet. This is an "idea" paper and discussion is strongly encouraged.
RFC 1336	Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members
	Authors: G. Malkin. Date: May 1992 Formats: txt pdf Obsoletes: RFC 1251 Also: FYI 0009 Status: INFORMATIONAL This FYI RFC contains biographical information about members of theInternet Activities Board (IAB), the Internet Engineering SteeringGroup (IESG) of the Internet Engineering Task Force (IETF), and the the Internet Research Steering Group (IRSG) of the Internet ResearchTask Force (IRTF).
RFC 1337	TIME-WAIT Assassination Hazards in TCP
	Authors: R. Braden. Date: May 1992 Formats: txt pdf Status: INFORMATIONAL This note describes some theoretically-possible failure modes for TCP connections and discusses possible remedies. In particular, one very simple fix is identified.
RFC 1338	Supernetting: an Address Assignment and Aggregation Strategy
	Authors: V. Fuller, T. Li, J. Yu, K. Varadhan. Date: June 1992 Formats: txt pdf Obsoleted by: RFC 1519 Status: INFORMATIONAL This memo discusses strategies for address assignment of the existingIP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers run by transit routing domain providers.
RFC 1343	A User Agent Configuration Mechanism for Multimedia Mail Format Information
	Authors: N. Borenstein. Date: June 1992 Formats: txt pdf ps Status: INFORMATIONAL This memo suggests a file format to be used to inform multiple mail reading user agent programs about the locally-installed facilities for handling mail in various formats. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1344	Implications of MIME for Internet Mail Gateways
	Authors: N. Borenstein. Date: June 1992 Formats: txt pdf ps Status: INFORMATIONAL While MIME was carefully designed so that it does not require any changes to Internet electronic message transport facilities, there are several ways in which message transport systems may want to take advantage of MIME. These opportunities are the subject of this memo. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1345	Character Mnemonics and Character Sets
	Authors: K. Simonsen. Date: June 1992 Formats: txt pdf Status: INFORMATIONAL This memo lists a selection of characters and their presence in some coded character sets. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1346	Resource Allocation, Control, and Accounting for the Use of Network Resources
	Authors: P. Jones. Date: June 1992 Formats: txt pdf Status: INFORMATIONAL The purpose of this RFC is to focus discussion on particular challenges in large service networks in general, and the International IP Internet in particular. No solution discussed in this document is intended as a standard. Rather, it is hoped that a general consensus will emerge as to the appropriate solutions, leading eventually to the adoption of standards. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1347	TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing
	Authors: R. Callon. Date: June 1992 Formats: txt pdf ps Status: INFORMATIONAL This paper describes a simple proposal which provides a long-term solution to Internet addressing, routing, and scaling. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1355	Privacy and Accuracy Issues in Network Information Center Databases
	Authors: J. Curran, A. Marine. Date: August 1992 Formats: txt pdf Also: FYI 0015 Status: INFORMATIONAL This document provides a set of guidelines for the administration and operation of public Network Information Center (NIC) databases. The purpose is to formalize procedures for the responsible handling of the personal and organizational information maintained by NICs in publically accessible databases, and to improve the accuracy and accessibility of such data where appropriate.
RFC 1357	A Format for E-mailing Bibliographic Records
	Authors: D. Cohen. Date: July 1992 Formats: txt pdf Obsoleted by: RFC 1807 Status: INFORMATIONAL This memo defines a format for E-mailing bibliographic records of technical reports. It is intended to accelerate the dissemination of information about new Computer Science Technical Reports (CS-TR).
RFC 1358	Charter of the Internet Architecture Board (IAB)
	Authors: L. Chapin. Date: August 1992 Formats: txt pdf Obsoleted by: RFC 1601 Status: INFORMATIONAL The Internet Architecture Board (IAB) shall be constituted and shall operate as a technical advisory group of the Internet Society. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1359	Connecting to the Internet - What Connecting Institutions Should Anticipate
	Authors: ACM SIGUCCS. Date: August 1992 Formats: txt pdf Also: FYI 0016 Status: INFORMATIONAL This FYI RFC outlines the major issues an institution should consider in the decision and implementation of a campus connection to theInternet. In order to provide clarity to the reader, some specific information has been detailed. In doing so, the document has been directed toward U.S. academic institutions that have not yet connected to theInternet. However, the issues for which specific information has been provided can be generalized for any organization that wishes to participate in the world-wide Internet community. It will be necessary for those organizations to obtain the correct and detailed information from their local or national IP service providers. In addition, this document may be used as an evaluation checklist for organizations that are currently connected. Readers are expected to have general familiarity with networking concepts and terminology.
RFC 1361	Simple Network Time Protocol (SNTP)
	Authors: D. Mills. Date: August 1992 Formats: txt pdf Obsoleted by: RFC 1769 Also: RFC 1305 Status: INFORMATIONAL This memorandum describes the Simple Network Time Protocol (SNTP), which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. SNTP can be used when the ultimate performance of the full NTP implementation described inRFC-1305 is not needed or justified. It involves no change to the current or previous NTP specification versions or known implementations, but rather a clarification of certain design features of NTP which allow operation in a simple, stateless RPC mode with accuracy and reliability expectations similar to the UDP/TIME protocol described in RFC-868. This memorandum does not obsolete or update any RFC. A working knowledge of RFC-1305 is not required for an implementation of SNTP.
RFC 1362	Novell IPX over Various WAN Media (IPXWAN)
	Authors: M. Allen. Date: September 1992 Formats: txt pdf Obsoleted by: RFC 1634 Status: INFORMATIONAL This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocolNovell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks.
RFC 1363	A Proposed Flow Specification
	Authors: C. Partridge. Date: September 1992 Formats: txt pdf Status: INFORMATIONAL A flow specification (or "flow spec") is a data structure used by internetwork hosts to request special services of the internetwork, often guarantees about how the internetwork will handle some of the hosts' traffic. In the future, hosts are expected to have to request such services on behalf of distributed applications such as multimedia conferencing. The flow specification defined in this memo is intended for information and possible experimentation (i.e., experimental use by consenting routers and applications only). This RFC is a product of the Internet Research Task Force (IRTF).
RFC 1365	An IP Address Extension Proposal
	Authors: K. Siyan. Date: September 1992 Formats: txt pdf Status: INFORMATIONAL This RFC suggests an extension to the IP protocol to solve the shortage of IP address problem, and requests discussion and suggestions for improvements.
RFC 1366	Guidelines for Management of IP Address Space
	Authors: E. Gerich. Date: October 1992 Formats: txt pdf Obsoleted by: RFC 1466 Status: INFORMATIONAL This document has been reviewed by the Federal Engineering Task Force(FEPG) on behalf of the Federal Networking Council (FNC), the co- chairs of the International Engineering Planning Group (IEPG), and the Reseaux IP Europeens (RIPE). There was general consensus by those groups to support the recommendations proposed in this document for management of the IP address space.
RFC 1367	Schedule for IP Address Space Management Guidelines
	Authors: C. Topolcic. Date: October 1992 Formats: txt pdf Obsoleted by: RFC 1467 Status: INFORMATIONAL This memo suggests a schedule for the implementation of the IP network number allocation plan described in RFC 1366. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1369	Implementation Notes and Experience for the Internet Ethernet MIB
	Authors: F. Kastenholz. Date: October 1992 Formats: txt pdf Status: INFORMATIONAL This document reflects the currently known status of 11 different implementations of the MIB by 7 different vendors on 7 different Ethernet interface chips. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1371	Choosing a Common IGP for the IP Internet
	Authors: P. Gross. Date: October 1992 Formats: txt pdf Status: INFORMATIONAL This memo presents motivation, rationale and other surrounding background information leading to the IESG's recommendation to theIAB for a single "common IGP" for the IP portions of the Internet. In this memo, the term "common IGP" is defined, the need for a commonIGP is explained, the relation of this issue to other ongoingInternet Engineering Task Force (IETF) routing protocol development is provided, and the relation of this issue to the goal for multi- protocol integration in the Internet is explored. Finally, a specific IGP is recommended as the "common IGP" for IP portions of the Internet -- the Open Shortest Path First (OSPF) routing protocol. The goal of this recommendation is for all vendors of Internet IP routers to make OSPF available as one of the IGP's provided with their routers.
RFC 1373	Portable DUAs
	Authors: T. Tignor. Date: October 1992 Formats: txt pdf Status: INFORMATIONAL This document comes in two parts. The first part is for regular people who wish to set up their own DUAs (Directory User Interfaces) to access the Directory. The second part is for ISODE-maintainers wishing to provide portable DUAs to users. This part gives instructions in a similar but longer, step-by-step format. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1375	Suggestion for New Classes of IP Addresses
	Authors: P. Robinson. Date: October 1992 Formats: txt pdf Status: INFORMATIONAL This RFC suggests a change in the method of specifying the IP address to add new classes of networks to be called F, G, H, and K, to reduce the amount of wasted address space, and to increase the available IP address number space, especially for smaller organizations or classes of connectors that do not need or do not want a full Class C IP address.
RFC 1380	IESG Deliberations on Routing and Addressing
	Authors: P. Gross, P. Almquist. Date: November 1992 Formats: txt pdf Status: INFORMATIONAL This memo summarizes issues surrounding the routing and addressing scaling problems in the IP architecture, and it provides a brief background of the ROAD group and related activities in the InternetEngineering Task Force (IETF). It also provides a preliminary report of the Internet EngineeringSteering Group (IESG) deliberations on how these routing and addressing issues should be pursued in the Internet ArchitectureBoard (IAB)/IETF.
RFC 1384	Naming Guidelines for Directory Pilots
	Authors: P. Barker, S.E. Hardcastle-Kille. Date: January 1993 Formats: txt pdf ps Obsoleted by: RFC 1617, RTR_0011 Status: INFORMATIONAL Deployment of a Directory will benefit from following certain guidelines. This document defines a number of naming guidelines.Alignment to these guidelines is recommended for directory pilots.
RFC 1385	EIP: The Extended Internet Protocol
	Authors: Z. Wang. Date: November 1992 Formats: txt pdf Status: INFORMATIONAL EIP can substantially reduce the amount of modifications needed to the current Internet systems and greatly ease the difficulties of transition. This is an "idea" paper and discussion is strongly encouraged on Big-Internet@munnari.oz.au. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1386	The US Domain
	Authors: A. Cooper, J. Postel. Date: December 1992 Formats: txt pdf Obsoleted by: RFC 1480 Status: INFORMATIONAL This is a description of the US Top Level Domains on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1387	RIP Version 2 Protocol Analysis
	Authors: G. Malkin. Date: January 1993 Formats: txt pdf Obsoleted by: RFC 1721 Status: INFORMATIONAL As required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience.
RFC 1391	The Tao of the IETF: A Guide for New Attendees of the Internet Engineering Task Force
	Authors: G. Malkin. Date: January 1993 Formats: txt pdf Obsoleted by: RFC 1539 Status: INFORMATIONAL Over the last two years, the attendance at Internet Engineering TaskForce (IETF) Plenary meetings has grown phenomenally. Approximately38% of the attendees are new to the IETF at each meeting. About 33% of those go on to become regular attendees. When the meetings were smaller, it wasn't very difficult for a newcomer to get to know people and get into the swing of things. Today, however, a newcomer meets many more new people, some previously known only as the authors of Request For Comments (RFC) documents or thought provoking email messages. The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This will give them a warm, fuzzy feeling and enable them to make the meeting more productive for everyone. This FYI will also provide the mundane bits of information which everyone who attends an IETF meeting should know.
RFC 1392	Internet Users' Glossary
	Authors: G. Malkin, T. LaQuey Parker. Date: January 1993 Formats: txt pdf Obsoleted by: RFC 1983 Status: INFORMATIONAL There are many networking glossaries in existence. This glossary concentrates on terms which are specific to the Internet. Naturally, there are entries for some basic terms and acronyms because other entries refer to them.
RFC 1394	Relationship of Telex Answerback Codes to Internet Domains
	Authors: P. Robinson. Date: January 1993 Formats: txt pdf Status: INFORMATIONAL This RFC gives the list, as best known, of all common Internet domains and the conversion between specific country telex answerback codes and Internet country domain identifiers. It also lists the telex code and international dialing code, wherever it is available.It will also list major Internet "Public" E-Mail addresses. This list is designed to show the corresponding codes for Fax and voice messages, telex country codes, telex answerbacks and Internet domains. It is an attempt to place all of the information into one list and all the connections for each country.
RFC 1396	The Process for Organization of Internet Standards Working Group (POISED)
	Authors: S. Crocker. Date: January 1993 Formats: txt pdf Status: INFORMATIONAL This report provides a summary of the POISED Working Group (WG), starting from the events leading to the formation of the WG to the end of 1992. Necessarily, this synopsis represents my own perception, particularly for the "prehistory" period. Quite a few people hold strong views about both the overall sequence and specific events. My intent here is to convey as neutral a point of view as possible.
RFC 1399	Summary of 1300-1399
	Authors: J. Elliott. Date: January 1997 Formats: txt pdf Status: INFORMATIONAL
RFC 1400	Transition and Modernization of the Internet Registration Service
	Authors: S. Williamson. Date: March 1993 Formats: txt pdf Status: INFORMATIONAL As a result of the NREN NIS award by National Science Foundation, non- DDN registration services will soon be transferred from the DDN NIC to the new Internet Registration Service, which is a part of an entity referred to as the InterNIC. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1401	Correspondence between the IAB and DISA on the use of DNS
	Authors: Internet Architecture Board. Date: January 1993 Formats: txt pdf Status: INFORMATIONAL This memo reproduces three letters exchanged between the InternetActivities Board (IAB) and the Defense Information Systems Agency(DISA) regarding the importance of using the Domain Name System (DNS) throughout the Internet, and phasing out the use of older host name to address tables, such as "hosts.txt".
RFC 1402	There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places
	Authors: J. Martin. Date: January 1993 Formats: txt pdf Obsoletes: RFC 1290 Also: FYI 0010 Status: INFORMATIONAL A wealth of information exists on the network. In fact, there is so much information that you could spend your entire life browsing. This paper will present some of the "gold nuggets" of information and file repositories on the network that could be useful. The ultimate goal is to make the route to these sources of information invisible to you. At present, this is not easy to do. I will explain some of the techniques that can be used to make these nuggets easier to pick up so that we all can be richer.
RFC 1404	A Model for Common Operational Statistics
	Authors: B. Stockman. Date: January 1993 Formats: txt pdf Obsoleted by: RFC 1857 Status: INFORMATIONAL This memo describes a model for operational statistics in theInternet. It gives recommendations for metrics, measurements, polling periods, storage formats and presentation formats.
RFC 1417	NADF Standing Documents: A Brief Overview
	Authors: The North American Directory Forum. Date: February 1993 Formats: txt pdf Obsoletes: RFC 1295, RFC 1255, RFC 1218 Obsoleted by: RFC 1758 Status: INFORMATIONAL The purpose of this document is to provide a brief overview of the NADF's Standing Document series. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1428	Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME
	Authors: G. Vaudreuil. Date: February 1993 Formats: txt pdf Status: INFORMATIONAL Protocols for extending SMTP to pass 8bit characters have been defined [3] [4]. These protocols require that messages transported by the extended SMTP are to be encoded in MIME [1] [2]. Before work began on these protocols, several SMTP implementations adopted ad-hoc mechanisms for sending 8bit data. It is desirable for the extendedSMTP environment and these ad hoc mechanisms interoperate. This document outlines the problems in this environment and an approach to minimizing the cost of transition from current usage of non-MIME 8bit messages to MIME.
RFC 1429	Listserv Distribute Protocol
	Authors: E. Thomas. Date: February 1993 Formats: txt pdf Status: INFORMATIONAL This memo specifies a subset of the distribution protocol used by theBITNET LISTSERV to deliver mail messages to large amounts of recipients. This protocol, known as DISTRIBUTE, optimizes the distribution by sending a single copy of the message over heavily loaded links, insofar as topological information is available to guide such decisions, and reduces the average turnaround time for large mailing lists to 5-15 minutes on the average. This memo describes a simple interface allowing non-BITNET mailing list exploders (or other bulk-delivery scripts) to take advantage of this service by letting the BITNET distribution network take care of the delivery.
RFC 1430	A Strategic Plan for Deploying an Internet X.500 Directory Service
	Authors: S. Hardcastle-Kille, E. Huizer, V. Cerf, R. Hobby, S. Kent. Date: February 1993 Formats: txt pdf Status: INFORMATIONAL There are a number of reasons why a new Internet Directory Service is required. This document describes an overall strategy for deploying a Directory Service on the Internet, based on the OSI X.500 DirectoryService. It then describes in more detail the initial steps which need to be taken in order to achieve these goals, and how work already undertaken by Internet Engineering Task Force Working Groups(IETF WGs) is working towards these goals.
RFC 1431	DUA Metrics (OSI-DS 33 (v2))
	Authors: P. Barker. Date: February 1993 Formats: txt pdf Status: INFORMATIONAL This RFC is being distributed to members of the Internet 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 Internet, they may be interesting to a number of researchers and implementers. This document defines a set of criteria by which a DUA implementation, or more precisely a Directory user interface, may be judged. Particular issues covered include terminal requirements; style of interface; target user; default object classes and attribute types; use of DAP; error handling. The focus of the note is on"white pages" DUAs: this is a reflection of the current information base. Nevertheless much of the document will be applicable to DUAs developed for other types of Directory usage. Please send comments to the author or to the discussion group <osi- ds@CS.UCL.AC.UK&rt;.
RFC 1432	Recent Internet Books
	Authors: J. Quarterman. Date: March 1993 Formats: txt pdf Status: INFORMATIONAL This article originally appeared in Volume 2 Number 12, (December1992) of Matrix News, the monthly newsletter of Matrix Information and Directory Services, Inc. (MIDS).
RFC 1434	Data Link Switching: Switch-to-Switch Protocol
	Authors: R. Dixon, D. Kushi. Date: March 1993 Formats: txt pdf ps Obsoleted by: RFC 1795 Status: INFORMATIONAL This RFC describes IBM's support of Data Link Switching over TCP/IP.The RFC is being distributed to members of the Internet 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 Internet, they may be interesting to a number of researchers and implementors. Any questions or comments relative to the contents of this RFC should be sent to the following Internet address: dlsw@ralvma.vnet.ibm.com.
RFC 1435	IESG Advice from Experience with Path MTU Discovery
	Authors: S. Knowles. Date: March 1993 Formats: txt pdf Status: INFORMATIONAL In the course of reviewing the MTU Discovery protocol for possible elevation to Draft Standard, a specific operational problem was uncovered. The problem results from the optional suppression of ICMP messages implemented in some routers. This memo outlines a modification to this practice to allow the correct functioning of MTUDiscovery.
RFC 1436	The Internet Gopher Protocol (a distributed document search and retrieval protocol)
	Authors: F. Anklesaria, M. McCahill, P. Lindner, D. Johnson, D. Torrey, B. Albert. Date: March 1993 Formats: txt pdf Status: INFORMATIONAL The Internet Gopher protocol is designed for distributed document search and retrieval. This document describes the protocol, lists some of the implementations currently available, and has an overview of how to implement new client and server applications. This document is adapted from the basic Internet Gopher protocol document first issued by the Microcomputer Center at the University ofMinnesota in 1991.
RFC 1437	The Extension of MIME Content-Types to a New Medium
	Authors: N. Borenstein, M. Linimon. Date: April 1 1993 Formats: txt pdf Status: INFORMATIONAL A previous document, RFC 1341, defines a format and general framework for the representation of a wide variety of data types in Internet mail. This document defines one particular type of MIME data, the matter-transport/sentient-life-form type. The matter- transport/sentient-life-form MIME type is intended to facilitate the wider interoperation of electronic mail messages that include entire sentient life forms, such as human beings. Other informally proposed subtypes, such as "non-sentient-life-form","non-sentient-non-life-form", and the orthogonally necessary but nevertheless puzzling "sentient-non-life-form", are not described in this memo.
RFC 1438	Internet Engineering Task Force Statements Of Boredom (SOBs)
	Authors: A. Lyman Chapin, C. Huitema. Date: April 1 1993 Formats: txt pdf Status: INFORMATIONAL This document creates a new subseries of RFCs, entitled, IETF Statements Of Boredom (SOBs). This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1439	The Uniqueness of Unique Identifiers
	Authors: C. Finseth. Date: March 1993 Formats: txt pdf Status: INFORMATIONAL This RFC provides information that may be useful when selecting a method to use for assigning unique identifiers to people.
RFC 1453	A Comment on Packet Video Remote Conferencing and the Transport/Network Layers
	Authors: W. Chimiak. Date: April 1993 Formats: txt pdf Status: INFORMATIONAL The new generation of multimedia applications demands new features and new mechanisms for proper performance. ATM technology has moved from concept to reality, delivering very high bandwidths and new capabilities to the data link layer user. In an effort to anticipate the high bandwidth-delay data link layer, Delta-t [Delta-t], NETBLT[RFC 988], and VMTP [RFC 1045] were developed. The excellent insights and mechanisms pioneered by the creators of these experimental Internet protocols were used in the design of XpressTransfer Protocol (XTP) [XTP92] with the goal of eventually delivering ATM bandwidths to a user process. This RFC is a vehicle to inform the Internet community about XTP as it benefits from pastInternet activity and targets general-purpose applications and multimedia applications with the emerging ATM networks in mind.
RFC 1454	Comparison of Proposals for Next Version of IP
	Authors: T. Dixon. Date: May 1993 Formats: txt pdf Status: INFORMATIONAL This is a slightly edited reprint of RARE Technical Report(RTC(93)004). The following is a brief summary of the characteristics of the three main proposals for replacing the current Internet Protocol. It is not intended to be exhaustive or definitive (a brief bibliography at the end points to sources of more information), but to serve as input to the European discussions on these proposals, to be co-ordinated byRARE and RIPE. It should be recognised that the proposals are themselves "moving targets", and in so far as this paper is accurate at all, it reflects the position at the 25th IETF meeting inWashington, DC. Comments from Ross Callon and Paul Tsuchiya on the original draft have been incorporated. Note that for a time the term"IPv7" was use to mean the eventual next version of IP, but that the same term was closely associated with a particilar proposal, so the term "IPng" is now used to identify the eventual next generation ofIP. The paper begins with a "generic" discussion of the mechanisms for solving problems and achieving particular goals, before discussing the proposals invidually.
RFC 1456	Conventions for Encoding the Vietnamese Language VISCII: VIetnamese Standard Code for Information Interchange VIQR: VIetnamese Quoted-Readable Specification
	Authors: Vietnamese Standardization Working Group. Date: May 1993 Formats: txt pdf Status: INFORMATIONAL This document provides information to the Internet community on the currently used conventions for encoding Vietnamese characters into7-bit US ASCII and in an 8-bit form. These conventions are widely used by the overseas Vietnamese who are on the Internet and are active in USENET. This document only provides information and specifies no level of standard.
RFC 1457	Security Label Framework for the Internet
	Authors: R. Housley. Date: May 1993 Formats: txt pdf Status: INFORMATIONAL This memo presents a security labeling framework for the Internet. The framework is intended to help protocol designers determine what, if any, security labeling should be supported by their protocols. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1458	Requirements for Multicast Protocols
	Authors: R. Braudes, S. Zabele. Date: May 1993 Formats: txt pdf Status: INFORMATIONAL This memo discusses some of these unresolved issues, and provides a high-level design for a new multicast transport protocol, group address and membership authority, and modifications to existing routing protocols. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1462	FYI on "What is the Internet?"
	Authors: E. Krol, E. Hoffman. Date: May 1993 Formats: txt pdf Also: FYI 0020 Status: INFORMATIONAL This FYI RFC answers the question, "What is the Internet?" and is produced by the User Services Working Group of the InternetEngineering Task Force (IETF). Containing a modified chapter from EdKrol's 1992 book, "The Whole Internet User's Guide and Catalog," the paper covers the Internet's definition, history, administration, protocols, financing, and current issues such as growth, commercialization, and privatization.
RFC 1463	FYI on Introducing the Internet-- A Short Bibliography of Introductory Internetworking Readings
	Authors: E. Hoffman, L. Jackson. Date: May 1993 Formats: txt pdf Also: FYI 0019 Status: INFORMATIONAL This bibliography offers a short list of recent information resources that will help the network novice become familiar with the Internet, including its associated networks, resources, protocols, and history.This FYI RFC includes references to free sources of information available on-line as well as traditional publications. A short section at the end includes information for accessing the on-line files. This FYI is intentionally brief so it can be easily used as a handout by user services personnel.
RFC 1466	Guidelines for Management of IP Address Space
	Authors: E. Gerich. Date: May 1993 Formats: txt pdf Obsoletes: RFC 1366 Obsoleted by: RFC 2050 Status: INFORMATIONAL This document has been reviewed by the Federal Engineering PlanningGroup (FEPG) on behalf of the Federal Networking Council (FNC), the co-chairs of the Intercontinental Engineering Planning Group (IEPG), and the Reseaux IP Europeens (RIPE). There was general consensus by those groups to support the recommendations proposed in this document for management of the IP address space.
RFC 1468	Japanese Character Encoding for Internet Messages
	Authors: J. Murai, M. Crispin, E. van der Poel. Date: June 1993 Formats: txt pdf Status: INFORMATIONAL This document describes the encoding used in electronic mail [RFC822] and network news [RFC1036] messages in several Japanese networks. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1470	FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices
	Authors: R. Enger, J. Reynolds. Date: June 1993 Formats: txt pdf Obsoletes: RFC 1147 Also: FYI 0002 Status: INFORMATIONAL The goal of this FYI memo is to provide an update to FYI 2, RFC 1147[1], which provided practical information to site administrators and network managers. New and/or updated tools are listed in this RFC.Additonal descriptions are welcome, and should be sent to: noctools- entries@merit.edu.
RFC 1477	IDPR as a Proposed Standard
	Authors: M. Steenstrup. Date: July 1993 Formats: txt pdf Status: INFORMATIONAL This document contains a discussion of inter-domain policy routing (IDPR), including an overview of functionality and a discussion of experiments. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1480	The US Domain
	Authors: A. Cooper, J. Postel. Date: June 1993 Formats: txt pdf Obsoletes: RFC 1386 Status: INFORMATIONAL This is a description of the US Top Level Domains on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1489	Registration of a Cyrillic Character Set
	Authors: A. Chernov. Date: July 1993 Formats: txt pdf Status: INFORMATIONAL Though the proposed character set "koi8-r" is not currently an international standard, there is very large user community (including Relcom Net) supporting it. Factually, "koi8-r" is de-facto standard for Unix and global network applications in the former Soviet Union. This is the reason the Society of Unix User Groups (SUUG) believes "koi8-r" should be registered. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1491	A Survey of Advanced Usages of X.500
	Authors: C. Weider, R. Wright. Date: July 1993 Formats: txt pdf Also: FYI 0021 Status: INFORMATIONAL This document is the result of a survey asking people to detail their advanced usages of X.500. It is intended to show how various organizations are using X.500 in ways which extend the view of X.500 as a "White Pages" service. This RFC is a product of the IntegratedDirectory Services Working Group of the Application and User ServicesAreas of the IETF.
RFC 1492	An Access Control Protocol, Sometimes Called TACACS
	Authors: C. Finseth. Date: July 1993 Formats: txt pdf Status: INFORMATIONAL This RFC documents the extended TACACS protocol use by the Cisco Systems terminal servers. This same protocol is used by the University of Minnesota's distributed authentication system. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1498	On the Naming and Binding of Network Destinations
	Authors: J. Saltzer. Date: August 1993 Formats: txt pdf Status: INFORMATIONAL This brief paper offers a perspective on the subject of names of destinations in data communication networks. It suggests two ideas:First, it is helpful to distinguish among four different kinds of objects that may be named as the destination of a packet in a network. Second, the operating system concept of binding is a useful way to describe the relations among the four kinds of objects. To illustrate the usefulness of this approach, the paper interprets some more subtle and confusing properties of two real-world network systems for naming destinations.
RFC 1499	Summary of 1400-1499
	Authors: J. Elliott. Date: January 1997 Formats: txt pdf Status: INFORMATIONAL
RFC 1501	OS/2 User Group
	Authors: E. Brunsen. Date: August 1993 Formats: txt pdf Status: INFORMATIONAL Memo soliciting reactions to the proposal of a OS/2 User Group. This memo provides information for the Internet community. This memo does not specify an IAB standard of any kind.
RFC 1503	Algorithms for Automating Administration in SNMPv2 Managers
	Authors: K. McCloghrie, M. Rose. Date: August 1993 Formats: txt pdf Status: INFORMATIONAL When a user invokes an SNMPv2 management application, it may be desirable for the user to specify the minimum amount of information necessary to establish and maintain SNMPv2 communications. This memo suggests an approach to achieve this goal. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1504	Appletalk Update-Based Routing Protocol: Enhanced Appletalk Routing
	Authors: A. Oppenheimer. Date: August 1993 Formats: txt pdf Status: INFORMATIONAL This document provides detailed information about the AppleTalk Update- based Routing Protocol (AURP) and wide area routing. AURP provides wide area routing enhancements to the AppleTalk routing protocols and is fully compatible with AppleTalk Phase 2. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1506	A Tutorial on Gatewaying between X.400 and Internet Mail
	Authors: J. Houttuin. Date: August 1993 Formats: txt pdf Status: INFORMATIONAL This tutorial was produced especially to help new gateway managers find their way into the complicated subject of mail gatewaying according to RFC 1327. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1511	Common Authentication Technology Overview
	Authors: J. Linn. Date: September 1993 Formats: txt pdf Status: INFORMATIONAL This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1523	The text/enriched MIME Content-type
	Authors: N. Borenstein. Date: September 1993 Formats: txt pdf Obsoleted by: RFC 1563, RFC 1896 Status: INFORMATIONAL MIME [RFC-1341, RFC-1521] defines a format and general framework for the representation of a wide variety of data types in Internet mail.This document defines one particular type of MIME data, the text/enriched type, a refinement of the "text/richtext" type defined in RFC 1341. The text/enriched MIME type is intended to facilitate the wider interoperation of simple enriched text across a wide variety of hardware and software platforms.
RFC 1524	A User Agent Configuration Mechanism For Multimedia Mail Format Information
	Authors: N. Borenstein. Date: September 1993 Formats: txt pdf Status: INFORMATIONAL This memo suggests a file format to be used to inform multiple mail reading user agent programs about the locally-installed facilities for handling mail in various formats. The mechanism is explicitly designed to work with mail systems based Internet mail as defined byRFC's 821 (STD 10), 822 (STD 11), 934, 1049 (STD 11), 1113, and theMultipurpose Internet Mail Extensions, known as MIME. However, with some extensions it could probably be made to work for X.400-based mail systems as well. The format and mechanism are proposed in a manner that is generally operating-system independent. However, certain implementation details will inevitably reflect operating system differences, some of which will have to be handled in a uniform manner for each operating system. This memo makes such situations explicit, and, in an appendix, suggests a standard behavior under the UNIX operating system.
RFC 1526	Assignment of System Identifiers for TUBA/CLNP Hosts
	Authors: D. Piscitello. Date: September 1993 Formats: txt pdf Status: INFORMATIONAL This document describes conventions whereby the system identifier portion of an RFC 1237 style NSAP address may be guaranteed uniqueness within a routing domain for the purpose of autoconfiguration in TUBA/CLNP internets. The mechanism is extensible and can provide a basis for assigning system identifiers in a globally unique fashion.
RFC 1527	What Should We Plan Given the Dilemma of the Network?
	Authors: G. Cook. Date: September 1993 Formats: txt pdf Status: INFORMATIONAL Early last year, as the concluding effort of an 18 month appointment at the US Congress Office of Technology Assessment (OTA), I drafted a potential policy framework for Congressional action on the NationalResearch and Education Network (NREN). The Internet community needs to be asking what the most important policy issues facing the network are. And given agreement on any particular set of policy issues, the next thing we should be asking is, what would be some of the political choices that would follow forCongress to make? It is unfortunate that this was never officially done for or by theCongress by OTA. What we have as a result is network policy making being carried out now by the Science Subcommittee on the House side in consultation with a relatively small group of interested parties.The debate seems to be more focused on preserving turf than on any sweeping understanding of what the legislation is doing. That is unfortunate. In the hope that it may contain some useful ideas, I offer a shortened version of the suggested policy draft as information for the Internet community.
RFC 1529	Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Administrative Policies
	Authors: C. Malamud, M. Rose. Date: October 1993 Formats: txt pdf Obsoletes: RFC 1486 Status: INFORMATIONAL This document defines the administrative policies for the operation of remote printer facilities within the context of the tpc.int subdomain. The document describes different approaches to resource recovery for remote printer server sites and includes discussions of issues pertaining to auditing, security, and denial of access. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1530	Principles of Operation for the TPC.INT Subdomain: General Principles and Policy
	Authors: C. Malamud, M. Rose. Date: October 1993 Formats: txt pdf Status: INFORMATIONAL This document defines the initial principles of operation for the tpc.int subdomain, a collection of service listings accessible over the Internet infrastructure through an administered namespace contained within the Domain Name System [1,2]. This document is informational and applies only to those Internet sites that choose to register themselves within the tpc.int subdomain. The tpc.int subdomain is organized as a cooperative of the sites that provide access within the context of the subdomain.Policy for the subdomain is set by a board responsible to the cooperative. The primary purpose of the tpc.int subdomain is to provide transparent mapping between general-purpose computers on the Internet and special-purpose devices directly connected to the telephone network. Initially, a remote printing service is defined [3,4] which ties together G3-compatible facsimile devices on the telephone network with users of electronic mail in the Internet and associated message-handling domains connected to the Internet by application- layer gateways. It should be noted that remote printer gateways have long been technically feasible and have become an integral part of many individual networks. The tpc.int subdomain integrates individual sites into a common namespace, transforming remote printing from a single-site, value-added service into an integral transparent service in the global Internet.
RFC 1535	A Security Problem and Proposed Correction With Widely Deployed DNS Software
	Authors: E. Gavron. Date: October 1993 Formats: txt pdf Status: INFORMATIONAL This document discusses a flaw in some of the currently distributed name resolver clients. The flaw exposes a security weakness related to the search heuristic invoked by these same resolvers when users provide a partial domain name, and which is easy to exploit (although not by the masses). This document points out the flaw, a case in point, and a solution.
RFC 1536	Common DNS Implementation Errors and Suggested Fixes
	Authors: A. Kumar, J. Postel, C. Neuman, P. Danzig, S. Miller. Date: October 1993 Formats: txt pdf Status: INFORMATIONAL This memo describes common errors seen in DNS implementations and suggests some fixes. Where applicable, violations of recommendations from STD 13, RFC 1034 and STD 13, RFC 1035 are mentioned. The memo also describes, where relevant, the algorithms followed in BIND(versions 4.8.3 and 4.9 which the authors referred to) to serve as an example.
RFC 1537	Common DNS Data File Configuration Errors
	Authors: P. Beertema. Date: October 1993 Formats: txt pdf Obsoleted by: RFC 1912 Status: INFORMATIONAL This memo describes errors often found in DNS data files. It points out common mistakes system administrators tend to make and why they often go unnoticed for long periods of time.
RFC 1538	Advanced SNA/IP : A Simple SNA Transport Protocol
	Authors: W. Behl, B. Sterling, W. Teskey. Date: October 1993 Formats: txt pdf Status: INFORMATIONAL This RFC provides information for the Internet community about a method for establishing and maintaining SNA sessions over an IP internet. While the issues discussed may not be directly relevant to the research problems of the Internet, they may be interesting to a number of researchers and implementors. Any questions or comments relative to the contents of this RFC may be sent to the followingInternet address: snaip@mcdata.com.
RFC 1539	The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force
	Authors: G. Malkin. Date: October 1993 Formats: txt pdf Obsoletes: RFC 1391 Obsoleted by: RFC 1718 Status: INFORMATIONAL Over the last two years, the attendance at Internet Engineering TaskForce (IETF) Plenary meetings has grown phenomenally. Approximately38% of the attendees are new to the IETF at each meeting. About 33% of those go on to become regular attendees. When the meetings were smaller, it wasn't very difficult for a newcomer to get to know people and get into the swing of things. Today, however, a newcomer meets many more new people, some previously known only as the authors of Request For Comments (RFC) documents or thought provoking email messages. The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This will give them a warm, fuzzy feeling and enable them to make the meeting more productive for everyone. This FYI will also provide the mundane bits of information which everyone who attends an IETF meeting should know.
RFC 1543	Instructions to RFC Authors
	Authors: J. Postel. Date: October 1993 Formats: txt pdf Obsoletes: RFC 1111, RFC 0825 Obsoleted by: RFC 2223 Status: INFORMATIONAL This Request for Comments (RFC) provides information about the preparation of RFCs, and certain policies relating to the publication of RFCs. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1546	Host Anycasting Service
	Authors: C. Partridge, T. Mendez, W. Milliken. Date: November 1993 Formats: txt pdf Status: INFORMATIONAL This RFC describes an internet anycasting service for IP. The primary purpose of this memo is to establish the semantics of an anycasting service within an IP internet. Insofar as is possible, this memo tries to be agnostic about how the service is actually provided by the internetwork. This memo describes an experimental service and does not propose a protocol. This memo is produced by the Internet Research Task Force (IRTF).
RFC 1547	Requirements for an Internet Standard Point-to-Point Protocol
	Authors: D. Perkins. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL This document discusses the evaluation criteria for an InternetStandard Data Link Layer protocol to be used with point-to-point links. Although many industry standard protocols and ad hoc protocols already exist for the data link layer, none are both complete and sufficiently versatile to be accepted as an InternetStandard. In preparation to designing such a protocol, the features necessary to qualify a point-to-point protocol as an InternetStandard are discussed in detail. An analysis of the strengths and weaknesses of several existing protocols on the basis of these requirements demonstrates the failure of each to address key issues. Historical Note: This was the design requirements document datedJune 1989, which was followed for RFC-1134 through the present.It is now published for completeness and future guidance.
RFC 1550	IP: Next Generation (IPng) White Paper Solicitation
	Authors: S. Bradner, A. Mankin. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL This memo solicits white papers on topics related to the IPng requirements and selection criteria. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1551	Novell IPX Over Various WAN Media (IPXWAN)
	Authors: M. Allen. Date: December 1993 Formats: txt pdf Obsoleted by: RFC 1634 Status: INFORMATIONAL This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocolNovell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This document supercedes RFC 1362 and adds capability forUnnumbered RIP links, On-demand statically routed links and client to router connectivity.
RFC 1554	ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP
	Authors: M. Ohta, K. Handa. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL This memo describes a text encoding scheme: "ISO-2022-JP-2", which is used experimentally for electronic mail [RFC822] and network news [RFC1036] messages in several Japanese networks. The encoding is a multilingual extension of "ISO-2022-JP", the existing encoding for Japanese [2022JP]. The encoding is supported by an Emacs based multilingual text editor: MULE [MULE]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1555	Hebrew Character Encoding for Internet Messages
	Authors: H. Nussbacher, Y. Bourvine. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL This document describes the encoding used in electronic mail [RFC822] for transferring Hebrew. The standard devised makes use of MIME[RFC1521] and ISO-8859-8.
RFC 1556	Handling of Bi-directional Texts in MIME
	Authors: H. Nussbacher. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL This document describes the format and syntax of the "direction" keyword to be used with bi-directional texts in MIME.
RFC 1557	Korean Character Encoding for Internet Messages
	Authors: U. Choi, K. Chon, H. Park. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL This document describes the encoding method being used to represent Korean characters in both header and body part of the Internet mail messages [RFC822]. This encoding method was specified in 1991, and has since then been used. It has now widely being used in Korean IP networks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1558	A String Representation of LDAP Search Filters
	Authors: T. Howes. Date: December 1993 Formats: txt pdf Obsoleted by: RFC 1960 Status: INFORMATIONAL The Lightweight Directory Access Protocol (LDAP) [1] defines a network representation of a search filter transmitted to an LDAP server. Some applications may find it useful to have a common way of representing these search filters in a human-readable form. This document defines a human-readable string format for representing LDAP search filters.
RFC 1560	The MultiProtocol Internet
	Authors: B. Leiner, Y. Rekhter. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL This document was prepared by the authors on behalf of the InternetArchitecture Board (IAB). It is offered by the IAB to stimulate discussion. There has recently been considerable discussion on two topics:MultiProtocol approaches in the Internet and the selection of a next generation Internet Protocol. This document suggests a strawman position for goals and approaches for the IETF/IESG/IAB in these areas. It takes the view that these two topics are related, and proposes directions for the IETF/IESG/IAB to pursue. In particular, it recommends that the IETF/IESG/IAB should continue to be a force for consensus on a single protocol suite and internet layer protocol. The IETF/IESG/IAB should: - maintain its focus on the TCP/IP protocol suite, - work to select a single next-generation internet protocol and develop mechanisms to aid in transition from the current IPv4, and - continue to explore mechanisms to interoperate and share resources with other protocol suites within the Internet.
RFC 1562	Naming Guidelines for the AARNet X.500 Directory Service
	Authors: G. Michaelson, M. Prior. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL AARNet is a member network of the global Internet and participates in the global Internet X.500 based Directory Service. A number of RFC's have been issued that make recommendations that alter or supplement the OSI/ETU standards for X.500 [1]. In general, these RFCs will be followed by the AARNet Directory Service. However, in certain cases we wish to align ourselves with our national ISO body (StandardsAustralia) rather than the Internet where they conflict. In naming, we have chosen to align ourselves with Standards Australia and this document notes the difference in our approach to the Internet guidelines suggested in RFC 1384 [2].
RFC 1563	The text/enriched MIME Content-type
	Authors: N. Borenstein. Date: January 1994 Formats: txt pdf ps Obsoletes: RFC 1523 Obsoleted by: RFC 1896 Status: INFORMATIONAL MIME [RFC-1341, RFC-1521] defines a format and general framework for the representation of a wide variety of data types in Internet mail.This document defines one particular type of MIME data, the text/enriched type, a refinement of the "text/richtext" type defined in RFC 1341. The text/enriched MIME type is intended to facilitate the wider interoperation of simple enriched text across a wide variety of hardware and software platforms.
RFC 1564	DSA Metrics (OSI-DS 34 (v3))
	Authors: P. Barker, R. Hedberg. Date: January 1994 Formats: txt pdf Status: INFORMATIONAL This document defines a set of criteria by which a DSA implementation may be judged. Particular issues covered include conformance to standards; performance; demonstrated interoperability. The intention is that the replies to the questions posed provide a fairly full description of a DSA. Some of the questions will yield answers which are purely descriptive; others, however, are intended to elicit answers which give some measure of the utility of the DSA. The marks awarded for a DSA in each particular area should give a good indication of the DSA's capabilities, and its suitability for particular uses. Please send comments to the authors or to the discussion group<osi-ds@CS.UCL.AC.UK&rt;.
RFC 1568	Simple Network Paging Protocol - Version 1(b)
	Authors: A. Gwinn. Date: January 1994 Formats: txt pdf Obsoleted by: RFC 1645 Status: INFORMATIONAL This RFC suggests a simple way for delivering both alphanumeric and numeric pages (one-way) to radio paging terminals. Gateways supporting this protocol, as well as SMTP, have been in use for several months in one nationwide paging firm. One other paging firm is in the process of adopting it. Earlier versions of this specification were reviewed by IESG members and the IETF's "822 Extensions" Working Group. They preferred an alternate strategy, as discussed under "Relationship to Other IETFWork", below.
RFC 1569	Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures
	Authors: M. Rose. Date: January 1994 Formats: txt pdf Obsoleted by: RFC 1703 Status: INFORMATIONAL This memo describes a technique for radio paging using the Internet mail infrastructure. In particular, this memo focuses on the case in which radio pagers are identified via the international telephone network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1571	Telnet Environment Option Interoperability Issues
	Authors: D. Borman. Date: January 1994 Formats: txt pdf Updates: RFC 1408 Status: INFORMATIONAL This document describes a method for allowing implementors to ensure that their implementation of the Environment option will be interoperable with as many other implementations as possible, by providing a set of heuristics that can be used to help identify which definitions for VAR and VALUE are being used by the other side of the connection. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1574	Essential Tools for the OSI Internet
	Authors: S. Hares, C. Wittbrodt. Date: February 1994 Formats: txt pdf Obsoletes: RFC 1139 Status: INFORMATIONAL This document specifies the following three necessary tools to debug problems in the deployment and maintenance of networks using ISO 8473(CLNP): - ping or OSI Echo function- traceroute function which uses the OSI Echo function- routing table dump function These CLNS tools are the basics required for hosts and routers forCLNS network support. It is intended that this document specify the most basic support level required for CLNS hosts and routers. To support some of the needed tools (ping and traceroute) this memo specifies the mechanism specified in RFC 1575 [3].
RFC 1576	TN3270 Current Practices
	Authors: J. Penner. Date: January 1994 Formats: txt pdf Status: INFORMATIONAL This document describes the existing implementation of transferring3270 display terminal data using currently available telnet capabilities. The name traditionally associated with this implementation is TN3270. Information is provided to aid in the implementation of TN3270 servers as well as client terminal emulators. The following areas pertaining to TN3270 implementations are covered in this document: 1. the telnet options negotiated to transition from a NVT ASCII state to a TN3270 state ready to process incoming 3270 data stream commands 2. the method for sending and receiving 3270 data 3. the method of handling some special keys known as SYSREQ andATTN using current available telnet commands 4. the events that will transition a TN3270 session back to an NVT session
RFC 1578	FYI on Questions and Answers - Answers to Commonly Asked "Primary and Secondary School Internet User" Questions
	Authors: J. Sellers. Date: February 1994 Formats: txt pdf Obsoleted by: RFC 1941 Status: INFORMATIONAL The goal of this FYI RFC, produced by the Internet School Networking(ISN) group in the User Services Area of the Internet EngineeringTask Force (IETF), is to document the questions most commonly asked about the Internet by those in the primary and secondary school community, and to provide pointers to sources which answer those questions. It is directed at educators, school media specialists, and school administrators who are recently connected to the Internet, who are accessing the Internet via dial-up or another means which is not a direct connection, or who are considering an Internet connection as a resource for their schools.
RFC 1579	Firewall-Friendly FTP
	Authors: S. Bellovin. Date: February 1994 Formats: txt pdf Status: INFORMATIONAL This memo describes a suggested change to the behavior of FTP client programs. No protocol modifications are required, though we outline some that might be useful.
RFC 1580	Guide to Network Resource Tools
	Authors: EARN Staff. Date: March 1994 Formats: txt pdf Also: FYI 0023 Status: INFORMATIONAL The purpose of this guide is to supply the basic information that anyone on the network needs to try out and begin using tools. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. [FYI 23]
RFC 1581	Protocol Analysis for Extensions to RIP to Support Demand Circuits
	Authors: G. Meyer. Date: February 1994 Formats: txt pdf Status: INFORMATIONAL As required by Routing Protocol Criteria [1], this report documents the key features of Routing over Demand Circuits on Wide AreaNetworks - RIP [2] and the current implementation experience.
RFC 1585	MOSPF: Analysis and Experience
	Authors: J. Moy. Date: March 1994 Formats: txt pdf Status: INFORMATIONAL This memo documents how the MOSPF protocol satisfies the requirements imposed on Internet routing protocols by "Internet Engineering TaskForce internet routing protocol standardization criteria" ([RFC1264]). Please send comments to mospf@gated.cornell.edu.
RFC 1586	Guidelines for Running OSPF Over Frame Relay Networks
	Authors: O. deSouza, M. Rodrigues. Date: March 1994 Formats: txt pdf Status: INFORMATIONAL This memo specifies guidelines for implementors and users of the OpenShortest Path First (OSPF) routing protocol to bring about improvements in how the protocol runs over frame relay networks. We show how to configure frame relay interfaces in a way that obviates the "full-mesh" connectivity required by current OSPF implementations. This allows for simpler, more economic network designs. These guidelines do not require any protocol changes; they only provide recommendations for how OSPF should be implemented and configured to use frame relay networks efficiently.
RFC 1588	White Pages Meeting Report
	Authors: J. Postel, C. Anderson. Date: February 1994 Formats: txt pdf Status: INFORMATIONAL This report describes the results of a meeting held at the November IETF (Internet Engineering Task Force) in Houston, TX, on November 2, 1993, to discuss the future of and approaches to a white pages directory services for the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1589	A Kernel Model for Precision Timekeeping
	Authors: D. Mills. Date: March 1994 Formats: txt pdf Status: INFORMATIONAL This memorandum describes an engineering model which implements a precision time-of-day function for a generic operating system. The model is based on the principles of disciplined oscillators and phase-lock loops (PLL) often found in the engineering literature. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1590	Media Type Registration Procedure
	Authors: J. Postel. Date: March 1994 Formats: txt pdf Obsoleted by: RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049 Updates: RFC 1521 Status: INFORMATIONAL Several protocols allow the use of data representing different"media" such as text, images, audio, and video, and within such media different encoding styles, such as (in video) jpeg, gif, ief, and tiff. The Multimedia Internet Message Extensions (MIME) protocol [1] defined several initial types of multimedia data objects, and a procedure for registering additional types with the Internet AssignedNumbers Authority (IANA). Several questions have been raised about the requirements and administrative procedure for registering MIME content-type and subtypes, and the use of these Media Types for other applications. This document addresses these issues and specifies a procedure for the registration of new Media Types (content- type/subtypes). It also generalizes the scope of use of these MediaTypes to make it appropriate to use the same registrations and specifications with other applications.
RFC 1591	Domain Name System Structure and Delegation
	Authors: J. Postel. Date: March 1994 Formats: txt pdf Status: INFORMATIONAL This memo provides some information on the structure of the names in the Domain Name System (DNS), specifically the top-level domain names; and on the administration of domains. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1593	SNA APPN Node MIB
	Authors: W. McKenzie, J. Cheng. Date: March 1994 Formats: txt pdf Status: INFORMATIONAL This RFC describes IBM's SNMP support for SNA Advanced Peer-to-PeerNetworking (APPN) nodes.
RFC 1594	FYI on Questions and Answers - Answers to Commonly asked "New Internet User" Questions
	Authors: A. Marine, J. Reynolds, G. Malkin. Date: March 1994 Formats: txt pdf Obsoletes: RFC 1325 Obsoleted by: RFC 2664 Status: INFORMATIONAL This FYI RFC is one of two FYI's called, "Questions and Answers"(Q/A), produced by the User Services Working Group of the InternetEngineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet.
RFC 1597	Address Allocation for Private Internets
	Authors: Y. Rekhter, B. Moskowitz, D. Karrenberg, G. de Groot. Date: March 1994 Formats: txt pdf Obsoleted by: RFC 1918 Status: INFORMATIONAL This RFC describes methods to preserve IP address space by not allocating globally unique IP addresses to hosts private to an enterprise while still permitting full network layer connectivity between all hosts inside an enterprise as well as between all public hosts of different enterprises. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1599	Summary of 1500-1599
	Authors: M. Kennedy. Date: January 1997 Formats: txt pdf Status: INFORMATIONAL
RFC 1601	Charter of the Internet Architecture Board (IAB)
	Authors: C. Huitema. Date: March 1994 Formats: txt pdf Obsoletes: RFC 1358 Obsoleted by: RFC 2850 Status: INFORMATIONAL This memo documents the composition, selection, roles, and organization of the Internet Architecture Board and its subsidiary organizations.
RFC 1602	The Internet Standards Process -- Revision 2
	Authors: Internet Architecture Board, Internet Engineering Steering Group. Date: March 1994 Formats: txt pdf Obsoletes: RFC 1310 Obsoleted by: RFC 2026 Updated by: RFC 1871 Status: INFORMATIONAL This document is a revision of RFC 1310, which defined the official procedures for creating and documenting Internet Standards. This revision (revision 2) includes the following major changes: (a) The new management structure arising from the POISED WorkingGroup is reflected. These changes were agreed to by the IETF plenary and by the IAB and IESG in November 1992 and accepted by the ISOC Board of Trustees at their December 1992 meeting. (b) Prototype status is added to the non-standards track maturity levels (Section 2.4.1). (c) The Intellectual Property Rights section is completely revised, in accordance with legal advice. Section 5 of this document replaces Sections 5 and 6 of RFC-1310. The new section 5 has been reviewed by legal counsel to the Internet Society. (d) An appeals procedure is added (Section 3.6). (e) The wording of sections 1 and 1.2 has been changed to clarify the relationships that exist between the Internet Society and the IAB, the IESG, the IETF, and the Internet Standards process. (f) An Appendix B has been added, listing the contact points for theRFC editor, the IANA, the IESG, the IAB and the ISOC. The"future issues" are now listed in Appendix C.
RFC 1603	IETF Working Group Guidelines and Procedures
	Authors: E. Huizer, D. Crocker. Date: March 1994 Formats: txt pdf Obsoleted by: RFC 2418 Updated by: RFC 1871 Status: INFORMATIONAL The Internet Engineering Task Force (IETF) has responsibility for developing and reviewing specifications intended as InternetStandards. IETF activities are organized into working groups (WGs).This document describes the guidelines and procedures for formation and operation of IETF working groups. It describes the formal relationship between IETF participants WG and the InternetEngineering Steering Group (IESG). The basic duties of IETF participants, including WG Chair and IESG Area Directors are defined.
RFC 1605	SONET to Sonnet Translation
	Authors: W. Shakespeare. Date: April 1 1994 Formats: txt pdf Status: INFORMATIONAL Because Synchronous Optical Network (SONET) transmits data in frames of bytes, it is fairly easy to envision ways to compress SONET frames to yield higher bandwidth over a given fiber optic link. This memo describes a particular method, SONET Over Novel English Translation(SONNET).
RFC 1606	A Historical Perspective On The Usage Of IP Version 9
	Authors: J. Onions. Date: April 1 1994 Formats: txt pdf Status: INFORMATIONAL This paper reviews the usages of the old IP version protocol. It considers some of its successes and its failures.
RFC 1607	A VIEW FROM THE 21ST CENTURY
	Authors: V. Cerf. Date: April 1 1994 Formats: txt pdf Status: INFORMATIONAL This document is a composition of letters discussing a possible future. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1613	cisco Systems X.25 over TCP (XOT)
	Authors: J. Forster, G. Satz, G. Glick, R. Day. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL This memo documents a method of sending X.25 packets over IP internets by encapsulating the X.25 Packet Level in TCP packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1614	Network Access to Multimedia Information
	Authors: C. Adie. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL This report summarises the requirements of research and academic network users for network access to multimedia information. It does this by investigating some of the projects planned or currently underway in the community. Existing information systems such asGopher, WAIS and World-Wide Web are examined from the point of view of multimedia support, and some interesting hypermedia systems emerging from the research community are also studied. Relevant existing and developing standards in this area are discussed. The report identifies the gaps between the capabilities of currentlydeployed systems and the user requirements, and proposes further work centred on the World-Wide Web system to rectify this. The report is in some places very detailed, so it is preceded by an extended summary, which outlines the findings of the report.
RFC 1615	Migrating from X.400(84) to X.400(88)
	Authors: J. Houttuin, J. Craigie. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL This document compares X.400(88) to X.400(84) and describes what problems can be anticipated in the migration, especially considering the migration from the existing X.400(84) infrastructure created by the COSINE MHS project to an X.400(88) infrastructure. It not only describes the technical complications, but also the effect the transition will have on the end users, especially concerning interworking between end users of the 84 and the 88 services.
RFC 1616	X.400(1988) for the Academic and Research Community in Europe
	Authors: RARE WG-MSG Task Force 88, E. Huizer, J. Romaguera, Eds.. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL The report documents the results of a task force on X.400(1988) deployment of the RARE Mails and Messaging Work Group during the period from November 1992 until October 1993. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1617	Naming and Structuring Guidelines for X.500 Directory Pilots
	Authors: P. Barker, S. Kille, T. Lenggenhager. Date: May 1994 Formats: txt pdf Obsoletes: RFC 1384 Status: INFORMATIONAL Deployment of a Directory will benefit from following certain guidelines. This document defines a number of naming and structuring guidelines focused on White Pages usage. Alignment to these guidelines is recommended for directory pilots. The final version of this document will replace RFC 1384.
RFC 1620	Internet Architecture Extensions for Shared Media
	Authors: B. Braden, J. Postel, Y. Rekhter. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL The original Internet architecture assumed that each network is labeled with a single IP network number. This assumption may be violated for shared media, including "large public data networks"(LPDNs). The architecture still works if this assumption is violated, but it does not have a means to prevent multiple host- router and router-router hops through the shared medium. This memo discusses alternative approaches to extending the Internet architecture to eliminate some or all unnecessary hops.
RFC 1621	Pip Near-term Architecture
	Authors: P. Francis. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL Pip is an internet protocol intended as the replacement for IP version 4. Pip is a general purpose internet protocol, designed to evolve to all forseeable internet protocol requirements. This specification describes the routing and addressing architecture for near-term Pip deployment. We say near-term only because Pip is designed with evolution in mind, so other architectures are expected in the future. This document, however, makes no reference to such future architectures.
RFC 1622	Pip Header Processing
	Authors: P. Francis. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL Pip is an internet protocol intended as the replacement for IP version 4. Pip is a general purpose internet protocol, designed to handle all forseeable internet protocol requirements. This specification defines the Pip header processing for Routers andHosts.
RFC 1624	Computation of the Internet Checksum via Incremental Update
	Authors: A. Rijsinghani, Ed.. Date: May 1994 Formats: txt pdf Updates: RFC 1141 Status: INFORMATIONAL This memo describes an updated technique for incremental computation of the standard Internet checksum. It updates the method described in RFC 1141.
RFC 1625	WAIS over Z39.50-1988
	Authors: M. St. Pierre, J. Fullton, K. Gamiel, J. Goldman, B. Kahle, J. Kunze, H. Morris, F. Schiettecatte. Date: June 1994 Formats: txt pdf Status: INFORMATIONAL The purpose of this memo is to initiate a discussion for a migration path of the WAIS technology from Z39.50-1988 Information Retrieval Service Definitions and Protocol Specification for Library Applications [1] to Z39.50-1992 [2] and then to Z39.50-1994 [3]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1627	Network 10 Considered Harmful (Some Practices Shouldn't be Codified)
	Authors: E. Lear, E. Fair, D. Crocker, T. Kessler. Date: July 1994 Formats: txt pdf Obsoleted by: RFC 1918 Status: INFORMATIONAL This document restates the arguments for maintaining a unique address space. Concerns for Internet architecture and operations, as well as IETF procedure, are explored. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1628	UPS Management Information Base
	Authors: J. Case, Ed.. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing uninterruptible power supply (UPS) systems. [STANDARDS-TRACK]
RFC 1630	Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web
	Authors: T. Berners-Lee. Date: June 1994 Formats: txt pdf Status: INFORMATIONAL This document defines the syntax used by the World-Wide Web initiative to encode the names and addresses of objects on the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1631	The IP Network Address Translator (NAT)
	Authors: K. Egevang, P. Francis. Date: May 1994 Formats: txt pdf Obsoleted by: RFC 3022 Status: INFORMATIONAL The two most compelling problems facing the IP Internet are IP address depletion and scaling in routing. Long-term and short-term solutions to these problems are being developed. The short-term solution is CIDR (Classless InterDomain Routing). The long-term solutions consist of various proposals for new internet protocols with larger addresses. It is possible that CIDR will not be adequate to maintain the IPInternet until the long-term solutions are in place. This memo proposes another short-term solution, address reuse, that complementsCIDR or even makes it unnecessary. The address reuse solution is to place Network Address Translators (NAT) at the borders of stub domains. Each NAT box has a table consisting of pairs of local IP addresses and globally unique addresses. The IP addresses inside the stub domain are not globally unique. They are reused in other domains, thus solving the address depletion problem. The globally unique IP addresses are assigned according to current CIDR address allocation schemes. CIDR solves the scaling problem. The main advantage of NAT is that it can be installed without changes to routers or hosts. This memo presents a preliminary design for NAT, and discusses its pros and cons.
RFC 1632	A Revised Catalog of Available X.500 Implementations
	Authors: A. Getchell, S. Sataluri, Eds.. Date: May 1994 Formats: txt pdf Obsoletes: RFC 1292 Obsoleted by: RFC 2116 Status: INFORMATIONAL This document is the result of a survey that gathered new or updated descriptions of currently available implementations of X.500, including commercial products and openly available offerings. This document is a revision of RFC 1292. We contacted each contributor inRFC 1292 and requested an update and published the survey template in several mailing lists and obtained new product descriptions. This document contains detailed description of twenty six (26) X.500 implementations - DSAs, DUAs, and DUA interfaces.
RFC 1633	Integrated Services in the Internet Architecture: an Overview
	Authors: R. Braden, D. Clark, S. Shenker. Date: June 1994 Formats: txt pdf ps Status: INFORMATIONAL This memo discusses a proposed extension to the Internet architecture and protocols to provide integrated services, i.e., to support real- time as well as the current non-real-time service of IP. This extension is necessary to meet the growing need for real-time service for a variety of new applications, including teleconferencing, remote seminars, telescience, and distributed simulation. This memo represents the direct product of recent work by Dave Clark,Scott Shenker, Lixia Zhang, Deborah Estrin, Sugih Jamin, JohnWroclawski, Shai Herzog, and Bob Braden, and indirectly draws upon the work of many others.
RFC 1634	Novell IPX Over Various WAN Media (IPXWAN)
	Authors: M. Allen. Date: May 1994 Formats: txt pdf Obsoletes: RFC 1551, RFC 1362 Status: INFORMATIONAL This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocolNovell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This document supercedes RFC 1362 and RFC 1551. The changes from RFC 1551 are to correct a problem in the wording when anRFC 1362 router talks to an RFC 1551 router and to allow numbers to be specified in a Router Name.
RFC 1635	How to Use Anonymous FTP
	Authors: P. Deutsch, A. Emtage, A. Marine. Date: May 1994 Formats: txt pdf Also: FYI 0024 Status: INFORMATIONAL This document provides information for the novice Internet user about using the File Transfer Protocol (FTP). It explains what FTP is, what anonymous FTP is, and what an anonymous FTP archive site is. It shows a sample anonymous FTP session. It also discusses common ways files are packaged for efficient storage and transmission.
RFC 1636	Report of IAB Workshop on Security in the Internet Architecture - February 8-10, 1994
	Authors: R. Braden, D. Clark, S. Crocker, C. Huitema. Date: June 1994 Formats: txt pdf Status: INFORMATIONAL This document is a report on an Internet architecture workshop, initiated by the IAB and held at USC Information Sciences Institute on February 8-10, 1994. This workshop generally focused on security issues in the Internet architecture. This document should be regarded as a set of working notes containing ideas about security that were developed by Internet experts in a broad spectrum of areas, including routing, mobility, realtime service, and provider requirements, as well as security. It contains some significant diversity of opinions on some important issues.This memo is offered as one input in the process of developing viable security mechanisms and procedures for the Internet.
RFC 1640	The Process for Organization of Internet Standards Working Group (POISED)
	Authors: S. Crocker. Date: June 1994 Formats: txt pdf Status: INFORMATIONAL This report, originally prepared in January 1993 provides a summary of the POISED WG, starting from the events leading to the formation of the WG to the end of 1992. Necessarily, this synopsis represents my own perception, particularly for the "prehistory" period. Quite a few people hold strong views about both the overall sequence and specific events. My intent here is to convey as neutral a point of view as possible.
RFC 1645	Simple Network Paging Protocol - Version 2
	Authors: A. Gwinn. Date: July 1994 Formats: txt pdf Obsoletes: RFC 1568 Obsoleted by: RFC 1861 Status: INFORMATIONAL This RFC suggests a simple way for delivering both alphanumeric and numeric pages (one-way) to radio paging terminals. Gateways supporting this protocol, as well as SMTP, have been in use for several months for nationwide paging and messaging. In addition, email filters and SNPP client software for Unix and Windows are available at no cost. Please contact the author for more information. Earlier versions of this specification were reviewed by IESG members and the "822 Extensions" Working Group. They preferred an alternate strategy, as discussed under "Relationship to Other IETF Work", below.
RFC 1646	TN3270 Extensions for LUname and Printer Selection
	Authors: C. Graves, T. Butts, M. Angel. Date: July 1994 Formats: txt pdf Status: INFORMATIONAL This document describes protocol extensions to TN3270. There are two extensions outlined in this document. The first defines a way by which a TN3270 client can request a specific device (LUname) from aTN3270 server. The second extension specifies how a TN3270 printer device can be requested by a TN3270 client and the manner in which the 3270 printer status information can be sent to the TN3270 server.Discussions and suggestions for improvements to these enhancements should be sent to the TN3270E Working Group mailing listTN3270E@list.nih.gov . These extensions will be called TN3287 in this document. This information is being provided to members of theInternet community that want to support the 3287 data stream within the TELNET protocol.
RFC 1649	Operational Requirements for X.400 Management Domains in the GO-MHS Community
	Authors: R. Hagens, A. Hansen. Date: July 1994 Formats: txt pdf Status: INFORMATIONAL The goal of this document is to unite regionally operated X.400 services on the various continents into one GO-MHS Community (as seen from an end-user's point of view). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1656	BGP-4 Protocol Document Roadmap and Implementation Experience
	Authors: P. Traina. Date: July 1994 Formats: txt pdf Obsoleted by: RFC 1773 Status: INFORMATIONAL Border Gateway Protocol v4 (BGP-4) [1] is an inter-Autonomous System routing protocol. It is built on experience gained with BGP as defined in RFC-1267 [2] and BGP usage in the connected Internet as described in RFC-1268 [3]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1667	Modeling and Simulation Requirements for IPng
	Authors: S. Symington, D. Wood, M. Pullen. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1668	Unified Routing Requirements for IPng
	Authors: D. Estrin, T. Li, Y. Rekhter. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1669	Market Viability as a IPng Criteria
	Authors: J. Curran. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1670	Input to IPng Engineering Considerations
	Authors: D. Heagerty. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1671	IPng White Paper on Transition and Other Considerations
	Authors: B. Carpenter. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1672	Accounting Requirements for IPng
	Authors: N. Brownlee. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1673	Electric Power Research Institute Comments on IPng
	Authors: R. Skelton. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1674	A Cellular Industry View of IPng
	Authors: M. Taylor. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This memo is a response to RFC 1550, "IP: Next Generation (IPng)White Paper Solicitation". The statements in this paper are intended as input to the technical discussions within IETF, and do not represent any endorsement or commitment on the part of the cellular industry, the Cellular Digital Packet Data (CDPD) consortium of service providers or any of its constituent companies.
RFC 1675	Security Concerns for IPng
	Authors: S. Bellovin. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1676	INFN Requirements for an IPng
	Authors: A. Ghiselli, D. Salomoni, C. Vistoli. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This white paper is sent by INFN network team, the Italian NationalInstitute for nuclear physics, whose network, named INFNet, is a nationwide network founded to provide the access to existing national and international HEP laboratory and to facilitate communications between the researchers. With this paper we would like to emphasize the key points that we would to consider if charged with IPng plan.We do not really expect to add original items to the selection, but we think that it could be useful to submit the opinions and ideas that come from our network experience.
RFC 1677	Tactical Radio Frequency Communication Requirements for IPng
	Authors: B. Adamson. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1678	IPng Requirements of Large Corporate Networks
	Authors: E. Britton, J. Tavs. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list. This draft summarizes some of the requirements of large corporate networks for the next generation of the Internet protcol suite.
RFC 1679	HPN Working Group Input to the IPng Requirements Solicitation
	Authors: D. Green, P. Irey, D. Marlow, K. O'Donoghue. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1680	IPng Support for ATM Services
	Authors: C. Brazdziunas. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1681	On Many Addresses per Host
	Authors: S. Bellovin. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1682	IPng BSD Host Implementation Analysis
	Authors: J. Bound. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1683	Multiprotocol Interoperability In IPng
	Authors: R. Clark, M. Ammar, K. Calvert. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1684	Introduction to White Pages Services based on X.500
	Authors: P. Jurg. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document aims at organisations who are using local and global electronic communication on a day to day basis and for whom using an electronic White Pages Service is therefore indispensable. The document provides an introduction to the international ITU-T(formerly CCITT) X.500 and ISO 9594 standard, which is particularly suited for providing an integrated local and global electronic WhitePages Service. In addition a short overview of the experience gained from theParadise X.500 pilot is given. References to more detailed information are included. The document should be useful for managers of the above mentioned organisations who need to get the necessary executive commitment for making the address information of their organisation available by means of X.500.
RFC 1685	Writing X.400 O/R Names
	Authors: H. Alvestrand. Date: August 1994 Formats: txt pdf Also: RTR_0012 Status: INFORMATIONAL There is a need for human beings who use X.400 systems to be able to write down O/R names in a uniform way. This memo is a discussion of this topic. This memo provides information for the Internet Community. It does not specify an Internet Standard of any kind.
RFC 1686	IPng Requirements: A Cable Television Industry Viewpoint
	Authors: M. Vecchi. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. The statements in this paper are intended as input to the technical discussions within IETF, and do not represent any endorsement or commitment on the part of the cable television industry or any of its companies. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1687	A Large Corporate User's View of IPng
	Authors: E. Fleischman. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1688	IPng Mobility Considerations
	Authors: W. Simpson. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IPng Area in response to RFC 1550.Publication of this document does not imply acceptance by the IPngArea of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list. This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP.
RFC 1689	A Status Report on Networked Information Retrieval: Tools and Groups
	Authors: J. Foster, Ed.. Date: August 1994 Formats: txt pdf Also: FYI 0025 Status: INFORMATIONAL The purpose of this report is to increase the awareness of NetworkedInformation Retrieval by bringing together in one place information about the various networked information retrieval tools, their developers, interested organisations, and other activities that relate to the production, dissemination, and support of NIR tools.NIR Tools covered include Archie, WAIS, gopher and World Wide Web.
RFC 1690	Introducing the Internet Engineering and Planning Group (IEPG)
	Authors: G. Huston. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This memo introduces the IEPG to the Internet Community. The IEPG is an Internet Service Operators' forum, intended to assist ServiceOperators to coordinate in operational aspects of managing Internet services.
RFC 1691	The Document Architecture for the Cornell Digital Library
	Authors: W. Turner. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This memo defines an architecture for the storage and retrieval of the digital representations for books, journals, photographic images, etc., which are collected in a large organized digital library. Two unique features of this architecture are the ability to generate reference documents and the ability to create multiple views of a document.
RFC 1698	Octet Sequences for Upper-Layer OSI to Support Basic Communications Applications
	Authors: P. Furniss. Date: October 1994 Formats: txt pdf Status: INFORMATIONAL This document states particular octet sequences that comprise the OSI upper-layer protocols (Session, Presentation and ACSE) when used to support applications with "basic communications requirements". These include OSI application protocols such as X.400 P7 and DirectoryAccess Protocol, and "migrant" protocols, originally defined for use over other transports. As well as the octet sequences which are the supporting layer headers(and trailers) around the application data, this document includes some tutorial material on the OSI upper layers. An implementation that sends the octet sequences given here, and interprets the equivalent protocol received, will be able to interwork with an implementation based on the base standard, when both are being used to support an appropriate application protocol.
RFC 1699	Summary of 1600-1699
	Authors: J. Elliott. Date: January 1997 Formats: txt pdf Status: INFORMATIONAL
RFC 1701	Generic Routing Encapsulation (GRE)
	Authors: S. Hanks, T. Li, D. Farinacci, P. Traina. Date: October 1994 Formats: txt pdf Status: INFORMATIONAL This document specifies a protocol for performing encapsulation of an arbitrary network layer protocol over another arbitrary network layer protocol.
RFC 1702	Generic Routing Encapsulation over IPv4 networks
	Authors: S. Hanks, T. Li, D. Farinacci, P. Traina. Date: October 1994 Formats: txt pdf Status: INFORMATIONAL This memo addresses the case of using IP as the delivery protocol or the payload protocol and the special case of IP as both the delivery and payload. This memo also describes using IP addresses and autonomous system numbers as part of a GRE source route. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1703	Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures
	Authors: M. Rose. Date: October 1994 Formats: txt pdf Obsoletes: RFC 1569 Status: INFORMATIONAL This memo describes a technique for radio paging using the Internet mail infrastructure. In particular, this memo focuses on the case in which radio pagers are identified via the international telephone network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1704	On Internet Authentication
	Authors: N. Haller, R. Atkinson. Date: October 1994 Formats: txt pdf Status: INFORMATIONAL This document describes a spectrum of authentication technologies and provides suggestions to protocol developers on what kinds of authentication might be suitable for some kinds of protocols and applications used in the Internet. This document provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1705	Six Virtual Inches to the Left: The Problem with IPng
	Authors: R. Carlson, D. Ficarella. Date: October 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1706	DNS NSAP Resource Records
	Authors: B. Manning, R. Colella. Date: October 1994 Formats: txt pdf Obsoletes: RFC 1637 Status: INFORMATIONAL OSI lower layer protocols, comprising the connectionless network protocol (CLNP) and supporting routing protocols, are deployed in some parts of the global Internet. Maintenance and debugging of CLNP connectivity is greatly aided by support in the Domain Name System(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. 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. This document obsoletes RFC 1348 and RFC 1637.
RFC 1707	CATNIP: Common Architecture for the Internet
	Authors: M. McGovern, R. Ullmann. Date: October 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550 Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1708	NTP PICS PROFORMA - For the Network Time Protocol Version 3
	Authors: D. Gowin. Date: October 1994 Formats: txt pdf Status: INFORMATIONAL This RFC describes a PICS Proforma translated into an Internet acceptable form. The Original document was developed according toISO 9646 for conformance test purposes. This document is intended for both developers and users of the NTP (Network Time Protocol).This document contains specific information and performance characteristics for the use of NTP within the context of Internet usage. It is suggested, that users wishing to use the synchronization capabilities of the Internet abide by the characteristics set within this document. For more information please contact Dr. David Mills at Mills@udel.edu or review RFC 1305 for more information.
RFC 1709	K-12 Internetworking Guidelines
	Authors: J. Gargano, D. Wasley. Date: November 1994 Formats: txt pdf ps Also: FYI 0026 Status: INFORMATIONAL The K-12 community traditionally has not had this level of staffing available for telecommunications planning. This document is intended to bridge that gap and provides a recommended technical direction, an introduction to the role the Internet now plays in K-12 education and technical guidelines for building a campus data communications infrastructure that provides internetworking services and connections to the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1710	Simple Internet Protocol Plus White Paper
	Authors: R. Hinden. Date: October 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the author and/or the sipp@sunroof.eng.sun.com mailing list.
RFC 1711	Classifications in E-mail Routing
	Authors: J. Houttuin. Date: October 1994 Formats: txt pdf Status: INFORMATIONAL This paper presents a classification for e-mail routing issues. It clearly defines commonly used terminology such as static routing, store-and-forward routing, source routing and others. Real life examples show which routing options are used in existing projects. The goal is to define all terminology in one reference paper. This will also help relatively new mail system managers to understand the issues and make the right choices. The reader is expected to already have a solid understanding of general networking terminology. In this paper, the word Message Transfer Agent (MTA) is used to describe a routing entity, which can be an X.400 MTA, a UNIX mailer, or any other piece of software performing mail routing functions. AnMTA processes the so called envelope information of a message. The term User Agent (UA) is used to describe a piece of software performing user related mail functions. It processes the contents of a message's envelope, i.e., the header fields and body parts.
RFC 1713	Tools for DNS debugging
	Authors: A. Romao. Date: November 1994 Formats: txt pdf Also: FYI 0027 Status: INFORMATIONAL Although widely used (and most of the times unnoticed), DNS (DomainName System) is too much overlooked, in the sense that people, especially administrators, tend to ignore possible anomalies as long as applications that need name-to-address mapping continue to work.This document presents some tools available for domain administrators to detect and correct those anomalies.
RFC 1714	Referral Whois Protocol (RWhois)
	Authors: S. Williamson, M. Kosters. Date: November 1994 Formats: txt pdf ps Obsoleted by: RFC 2167 Status: INFORMATIONAL This memo describes version 1.0 of the client/server interaction ofRWhois. RWhois provides a distributed system for the display of hierarchical information. This system is hierarchical by design, allowing for the reduction of a query, and the referral of the user closer to the maintainer of the information.
RFC 1715	The H Ratio for Address Assignment Efficiency
	Authors: C. Huitema. Date: November 1994 Formats: txt pdf Updated by: RFC 3194 Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the author and/or the sipp@sunroof.eng.sun.com mailing list.
RFC 1716	Towards Requirements for IP Routers
	Authors: P. Almquist, F. Kastenholz. Date: November 1994 Formats: txt pdf Obsoleted by: RFC 1812 Status: INFORMATIONAL The goal of this work is to replace RFC-1009, Requirements for Internet Gateways ([INTRO:1]) with a new document. It defines and discusses requirements for devices which perform the network layer forwarding function of the Internet protocol suite. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1718	The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force
	Authors: IETF Secretariat, G. Malkin. Date: November 1994 Formats: txt pdf Obsoletes: RFC 1539 Obsoleted by: RFC 3160 Status: INFORMATIONAL Over the last two years, the attendance at Internet Engineering TaskForce (IETF) plenary meetings has grown phenomenally. Approximately one third of the attendees are new to the IETF at each meeting, and many of those go on to become regular attendees. When the meetings were smaller, it wasn't very difficult for a newcomer to get into the swing of things. Today, however, a newcomer meets many more new people, some previously known only as the authors of documents or thought provoking e-mail messages. The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This will give them a warm, fuzzy feeling and enable them to make the meeting more productive for everyone. This FYI will also provide the mundane bits of information which everyone who attends an IETF meeting should know.
RFC 1719	A Direction for IPng
	Authors: P. Gross. Date: December 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IPng Area in response to RFC 1550.Publication of this document does not imply acceptance by the IPngArea of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list. This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP.
RFC 1721	RIP Version 2 Protocol Analysis
	Authors: G. Malkin. Date: November 1994 Formats: txt pdf Obsoletes: RFC 1387 Status: INFORMATIONAL As required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience. This report is a prerequisite to advancing RIP-2 on the standards track.
RFC 1726	Technical Criteria for Choosing IP The Next Generation (IPng)
	Authors: C. Partridge, F. Kastenholz. Date: December 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IPng Area in response to RFC 1550.Publication of this document does not imply acceptance by the IPngArea of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list. This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP.
RFC 1727	A Vision of an Integrated Internet Information Service
	Authors: C. Weider, P. Deutsch. Date: December 1994 Formats: txt pdf Status: INFORMATIONAL This paper lays out a vision of how Internet information services might be integrated over the next few years, and discusses in some detail what steps will be needed to achieve this integration.
RFC 1728	Resource Transponders
	Authors: C. Weider. Date: December 1994 Formats: txt pdf Status: INFORMATIONAL Although a number of systems have been created in the last several years to provide resource location and navigation on the Internet, the information contained in these systems must be maintained and updated by hand. This paper describes an automatic mechanism, the resource transponder, for maintaining resource location information.
RFC 1729	Using the Z39.50 Information Retrieval Protocol
	Authors: C. Lynch. Date: December 1994 Formats: txt pdf Status: INFORMATIONAL This memo describes an approach to the implementation of the ANSI/NISO Z39.50-1992 Standard for Information Retrieval in the TCP/IP environment which is currently in wide use by the Z39.50 implementor community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1732	IMAP4 Compatibility with IMAP2 and IMAP2bis
	Authors: M. Crispin. Date: December 1994 Formats: txt pdf Status: INFORMATIONAL This is a summary of hints and recommendations to enable an IMAP4 implementation to interoperate with implementations that conform to earlier specifications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1733	Distributed Electronic Mail Models in IMAP4
	Authors: M. Crispin. Date: December 1994 Formats: txt pdf Status: INFORMATIONAL There are three fundamental models of client/server email: offline, online, and disconnected use. IMAP4 can be used in any one of these three models. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1736	Functional Recommendations for Internet Resource Locators
	Authors: J. Kunze. Date: February 1995 Formats: txt pdf Status: INFORMATIONAL This document specifies a minimum set of requirements for Internet resource locators, which convey location and access information for resources. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1737	Functional Requirements for Uniform Resource Names
	Authors: K. Sollins, L. Masinter. Date: December 1994 Formats: txt pdf Status: INFORMATIONAL This document specifies a minimum set of requirements for a kind of Internet resource identifier known as Uniform Resource Names (URNs). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1739	A Primer On Internet and TCP/IP Tools
	Authors: G. Kessler, S. Shepard. Date: December 1994 Formats: txt pdf Obsoleted by: RFC 2151 Status: INFORMATIONAL This memo is an introductory guide to some of the TCP/IP and Internet tools and utilities that allow users to access the wide variety of information on the network, from determining if a particular host is up to viewing a multimedia thesis on foreign policy. It also describes discussion lists accessible from the Internet, ways to obtain Internet documents, and resources that help users weave their way through the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1741	MIME Content Type for BinHex Encoded Files
	Authors: P. Faltstrom, D. Crocker, E. Fair. Date: December 1994 Formats: txt pdf Status: INFORMATIONAL This memo describes the format to use when sending BinHex4.0 files via MIME [BORE93]. The format is compatible with existing mechanisms for distributing Macintosh files. Only when available software and/or user practice dictates, should this method be employed. It is recommended to use application/applefile [FALT94] for maximum interoperability.
RFC 1744	Observations on the Management of the Internet Address Space
	Authors: G. Huston. Date: December 1994 Formats: txt pdf Status: INFORMATIONAL This memo examines some of the issues associated with the current management practices of the Internet IPv4 address space, and examines the potential outcomes of these practices as the unallocated address pool shrinks in size. Possible modifications to the management practices are examined, and potential outcomes considered. Some general conclusions are drawn, and the relevance of these conclusions to the matter of formulation of address management policies for IPv6 are noted.
RFC 1746	Ways to Define User Expectations
	Authors: B. Manning, D. Perkins. Date: December 1994 Formats: txt pdf Status: INFORMATIONAL This paper covers basic fundamentals that must be understood when one defines, interprets, or implements methods to control user expectations on or over the Internet.
RFC 1750	Randomness Recommendations for Security
	Authors: D. Eastlake 3rd, S. Crocker, J. Schiller. Date: December 1994 Formats: txt pdf Obsoleted by: RFC 4086 Status: INFORMATIONAL Security systems today are built on increasingly strong cryptographic algorithms that foil pattern analysis attempts. However, the security of these systems is dependent on generating secret quantities for passwords, cryptographic keys, and similar quantities. The use of pseudo-random processes to generate secret quantities can result in pseudo-security. The sophisticated attacker of these security systems may find it easier to reproduce the environment that produced the secret quantities, searching the resulting small set of possibilities, than to locate the quantities in the whole of the number space. Choosing random quantities to foil a resourceful and motivated adversary is surprisingly difficult. This paper points out many pitfalls in using traditional pseudo-random number generation techniques for choosing such quantities. It recommends the use of truly random hardware techniques and shows that the existing hardware on many systems can be used for this purpose. It provides suggestions to ameliorate the problem when a hardware solution is not available. And it gives examples of how large such quantities need to be for some particular applications.
RFC 1751	A Convention for Human-Readable 128-bit Keys
	Authors: D. McDonald. Date: December 1994 Formats: txt pdf Status: INFORMATIONAL This memo proposes a convention for use with Internet applications & protocols using 128-bit cryptographic keys. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1753	IPng Technical Requirements Of the Nimrod Routing and Addressing Architecture
	Authors: N. Chiappa. Date: December 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list. This document presents the requirements that the Nimrod routing and addressing architecture has upon the internetwork layer protocol. To be most useful to Nimrod, any protocol selected as the IPng should satisfy these requirements. Also presented is some background information, consisting of i) information about architectural and design principles which might apply to the design of a new internetworking layer, and ii) some details of the logic and reasoning behind particular requirements.
RFC 1754	IP over ATM Working Group's Recommendations for the ATM Forum's Multiprotocol BOF Version 1
	Authors: M. Laubach. Date: January 1995 Formats: txt pdf Status: INFORMATIONAL This document represents an initial list of requirements submitted to the ATM Forum's Multiprotocol BOF for the operation of IP over ATM networks as determined by the IETF IP over ATM Working Group and other working groups. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1758	NADF Standing Documents: A Brief Overview
	Authors: The North American Directory Forum. Date: February 1995 Formats: txt pdf Obsoletes: RFC 1417 Status: INFORMATIONAL The purpose of this document is to provide a brief overview of the NADF's Standing Document series. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1760	The S/KEY One-Time Password System
	Authors: N. Haller. Date: February 1995 Formats: txt pdf Status: INFORMATIONAL This document describes the S/KEY* One-Time Password system as released for public use by Bellcore and as described in reference[3]. A reference implementation and documentation are available by anonymous ftp from ftp.bellcore.com in the directories pub/nmh/...
RFC 1761	Snoop Version 2 Packet Capture File Format
	Authors: B. Callaghan, R. Gilligan. Date: February 1995 Formats: txt pdf Status: INFORMATIONAL This paper describes the file format used by "snoop", a packet monitoring and capture program developed by Sun. This paper is provided so that people can write compatible programs to generate and interpret snoop packet capture files.
RFC 1769	Simple Network Time Protocol (SNTP)
	Authors: D. Mills. Date: March 1995 Formats: txt pdf Obsoletes: RFC 1361 Obsoleted by: RFC 2030, RFC 4330 Status: INFORMATIONAL This memorandum describes the Simple Network Time Protocol (SNTP), which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. SNTP can be used when the ultimate performance of the full NTP implementation described inRFC-1305 is not needed or justified. It can operate in both unicast modes (point to point) and broadcast modes (point to multipoint). It can also operate in IP multicast mode where this service is available. SNTP involves no change to the current or previous NTP specification versions or known implementations, but rather a clarification of certain design features of NTP which allow operation in a simple, stateless remote-procedure call (RPC) mode with accuracy and reliability expectations similar to the UDP/TIME protocol described in RFC-868. This memorandum obsoletes RFC-1361 of the same title. Its purpose is to explain the protocol model for operation in broadcast mode, to provide additional clarification in some places and to correct a few typographical errors. A working knowledge of the NTP Version 3 specification RFC-1305 is not required for an implementation of SNTP.Distribution of this memorandum is unlimited.
RFC 1770	IPv4 Option for Sender Directed Multi-Destination Delivery
	Authors: C. Graff. Date: March 1995 Formats: txt pdf Status: INFORMATIONAL This memo defines an IPv4 option to provide a sender directed multi- destination delivery mechanism called Selective Directed BroadcastMode (SDBM). The SDBM provides unreliable UDP delivery to a set ofIP addresses included in the option field of an IPv4 datagram. Data reliability if required will be provided by the application layer.This approach was developed to support sender directed multi- destination delivery to sparsely populated groups with no additional control traffic. This approach will find application in the extremely bandwidth constrained tactical military environment, as well as in some commercial applications requiring sender control of data delivery.
RFC 1773	Experience with the BGP-4 protocol
	Authors: P. Traina. Date: March 1995 Formats: txt pdf Obsoletes: RFC 1656 Status: INFORMATIONAL The purpose of this memo is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by Border Gateway Protocol version 4 (BGP-4). This report documents experience with BGP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1774	BGP-4 Protocol Analysis
	Authors: P. Traina, Ed.. Date: March 1995 Formats: txt pdf Status: INFORMATIONAL The purpose of this report is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by the Border Gateway Protocol version 4 (BGP-4). This report summarizes the key features of BGP, and analyzes the protocol with respect to scaling and performance. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1775	To Be "On" the Internet
	Authors: D. Crocker. Date: March 1995 Formats: txt pdf Status: INFORMATIONAL The Internet permits different levels of access for consumers and providers of service. The nature of those differences is quite important in the capabilities They afford. Hence, it is appropriate to provide terminology that distinguishes among the range, so that the Internet community can gain some clarity when distinguishing whether a user (or an organization) is "on" the Internet. This document suggests four terms, for distinguishing the major classes of access.
RFC 1776	The Address is the Message
	Authors: S. Crocker. Date: April 1 1995 Formats: txt pdf Status: INFORMATIONAL Declaring that the address is the message, the IPng WG has selected a packet format which includes 1696 bytes of address space. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1785	TFTP Option Negotiation Analysis
	Authors: G. Malkin, A. Harkin. Date: March 1995 Formats: txt pdf Updates: RFC 1350 Status: INFORMATIONAL The TFTP option negotiation mechanism, proposed in [1], is a backward-compatible extension to the TFTP protocol, defined in [2].It allows file transfer options to be negotiated prior to the transfer using a mechanism which is consistent with TFTP's RequestPacket format. The mechanism is kept simple by enforcing a request- respond-acknowledge sequence, similar to the lock-step approach taken by TFTP itself. This document was written to allay concerns that the presence of options in a TFTP Request packet might cause pathological behavior on servers which do not support TFTP option negotiation.
RFC 1786	Representation of IP Routing Policies in a Routing Registry (ripe-81++)
	Authors: T. Bates, E. Gerich, L. Joncheray, J-M. Jouanigot, D. Karrenberg, M. Terpstra, J. Yu. Date: March 1995 Formats: txt pdf Status: INFORMATIONAL This document was originally published as a RIPE document known as ripe-181 but is also being published as an Informational RFC to reach a larger audience than its original scope. It has received community wide interest and acknowledgment throughout the Internet service provider community and will be used as the basic starting point for future work on Internet Routing Registries and routing policy representation. It can also be referred to as ripe-81++. This document is an update to the original `ripe-81'[1] proposal for representing and storing routing polices within the RIPE database. It incorporates several extensions proposed by Merit Inc.[2] and gives details of a generalized IP routing policy representation to be used by all Internet routing registries. It acts as both tutorial and provides details of database objects and attributes that use and make up a routing registry.
RFC 1787	Routing in a Multi-provider Internet
	Authors: Y. Rekhter. Date: April 1995 Formats: txt pdf Status: INFORMATIONAL This document was prepared by the author on behalf of the InternetArchitecture Board (IAB). It is offered by the IAB to stimulate discussion. Over the past few years the Internet has undergone significant changes. Among them is the emergence of multiple Network ServiceProviders, where resources that provide Internet-wide IP connectivity(routers, links) are controlled by different organizations. This document presents some of the issues related to network layer routing in a multi-provider Internet, and specifically to the unicast routing.
RFC 1789	INETPhone: Telephone Services and Servers on Internet
	Authors: C. Yang. Date: April 1995 Formats: txt pdf Status: INFORMATIONAL INETPhone is a true telephone service through the Internet. It integrates the local telephone networks and the Internet usingINETPhone servers. Thus a long distance call can be split into two local calls and an Internet connection, which is transparent to end users. Such a phone service through Internet will be a major step towards integrated services on Internet. In order to support theINETPhone and lay down the ground rules of the service, a scheme of"open partnership" is proposed, so that the entire Internet community can have the equal opportunity and benefits from the INETPhone service.
RFC 1790	An Agreement between the Internet Society and Sun Microsystems, Inc
	Authors: in the Matter of ONC RPC and XDR Protocols. V. Cerf. Date: April 1995 Formats: txt pdf Status: INFORMATIONAL This RFC is an official public record of an agreement between SUN Microsystems and the Internet Society. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
RFC 1794	DNS Support for Load Balancing
	Authors: T. Brisco. Date: April 1995 Formats: txt pdf Status: INFORMATIONAL This RFC is meant to first chronicle a foray into the IETF DNS Working Group, discuss other possible alternatives to provide/simulate load balancing support for DNS, and to provide an ultimate, flexible solution for providing DNS support for balancing loads of many types. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1795	Data Link Switching: Switch-to-Switch Protocol AIW DLSw RIG: DLSw Closed Pages, DLSw Standard Version 1
	Authors: L. Wells, Chair, A. Bartky, Ed.. Date: April 1995 Formats: txt pdf Obsoletes: RFC 1434 Status: INFORMATIONAL This RFC describes use of Data Link Switching over TCP/IP. The RFC is being distributed to members of the Internet 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 Internet, they may be interesting to a number of researchers and Implementers. This RFC was created as a joint effort of the Advanced Peer-to-PeerNetworking (APPN) Implementers Workshop (AIW) Data Link Switching(DLSw) Related Interest Group (RIG). The APPN Implementers Workshop is a group sponsored by IBM and consists of representatives of member companies implementing current and future IBM Networking interoperable products. The DLSw Related Interest Group was formed in this forum in order to produce a single version of the Switch toSwitch Protocol (SSP) which could be implemented by all vendors, which would fix documentation problems with the existing RFC 1434, and which would enhance and evolve the protocol to add new functions and features. This document is based on RFC 1434. This document contains significant changes to RFC 1434 and therefore obsoletes that document. Any questions or comments relative to the contents of this RFC should be sent to the following Internet address: aiw-dlsw@networking.raleigh.ibm.com. NOTE 1: This is a widely subscribed mailing list and messages sent to this address will be sent to all members of the DLSw mailing list.For specific questions relating to subscribing to the AIW and any of it's working groups send email to: appn@vnet.ibm.com Information regarding all of the AIW working groups and the work they are producing can be obtained by copying, via anonymous ftp, the file aiwinfo.psbin or aiwinfo.txt from the Internet host networking.raleigh.ibm.com, located in directory aiw. NOTE 2: These mailing lists and addresses are subject to change.
RFC 1796	Not All RFCs are Standards
	Authors: C. Huitema, J. Postel, S. Crocker. Date: April 1995 Formats: txt pdf Status: INFORMATIONAL This document discusses the relationship of the Request for Comments(RFCs) notes to Internet Standards.
RFC 1799	Request for Comments Summary RFC Numbers 1700-1799
	Authors: M. Kennedy. Date: January 1997 Formats: txt pdf Status: INFORMATIONAL
RFC 1802	Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 Routing
	Authors: H. Alvestrand, K. Jordan, S. Langlois, J. Romaguera. Date: June 1995 Formats: txt pdf Status: INFORMATIONAL The Internet X.400 community (i.e., GO-MHS) currently lacks a distributed mechanism providing dynamic updating and management of message routing information. The IETF MHS-DS Working Group has specified an approach for X.400 Message Handling Systems to perform message routing using OSI Directory Services. The MHS-DS approach has been successfully tested in a number of local environments. This memo describes a proposed Internet Pilot Project that seeks to prove the MHS-DS approach on a larger scale. The results of this pilot will then be used to draw up recommendations for a global deployment.
RFC 1803	Recommendations for an X.500 Production Directory Service
	Authors: R. Wright, A. Getchell, T. Howes, S. Sataluri, P. Yee, W. Yeong. Date: June 1995 Formats: txt pdf Status: INFORMATIONAL This document contains a set of basic recommendations for a country- level X.500 DSA. These recommendations can only be considered a starting point in the quest to create a global production qualityX.500 infrastructure. For there to be a true "production quality"X.500 infrastructure more work must be done, including a transition from the 1988 X.500 (plus some Internet extensions) to the 1993 X.500 standard (including the '93 replication and knowledge model). This document does not discuss this transition.
RFC 1805	Location-Independent Data/Software Integrity Protocol
	Authors: A. Rubin. Date: June 1995 Formats: txt pdf Status: INFORMATIONAL This memo describes a protocol for adding integrity assurance to files that are distributed across the Internet. This protocol is intended for the distribution of software, data, documents, and any other file that is subject to malicious modification. The protocol described here is intended to provide assurances of integrity and time. A trusted third party is required.
RFC 1807	A Format for Bibliographic Records
	Authors: R. Lasher, D. Cohen. Date: June 1995 Formats: txt pdf Obsoletes: RFC 1357 Status: INFORMATIONAL This RFC defines a format for bibliographic records describing technical reports. This format is used by the Cornell UniversityDienst protocol and the Stanford University SIFT system. The original RFC (RFC 1357) was written by D. Cohen, ISI, July 1992.This is a revision of RFC 1357. New fields include handle, other_access, keyword, and withdraw.
RFC 1809	Using the Flow Label Field in IPv6
	Authors: C. Partridge. Date: June 1995 Formats: txt pdf Status: INFORMATIONAL The purpose of this memo is to distill various opinions and suggestions of the End-to-End Research Group regarding the handling of Flow Labels into a set of suggestions for IPv6. This memo is for information purposes only and is not one of the IPv6 specifications.Distribution of this memo is unlimited.
RFC 1810	Report on MD5 Performance
	Authors: J. Touch. Date: June 1995 Formats: txt pdf Status: INFORMATIONAL MD5 is an authentication algorithm, which has been proposed as the default authentication option in IPv6. When enabled, the MD5 algorithm operates over the entire data packet, including header.This RFC addresses how fast MD5 can be implemented in software and hardware, and whether it supports currently available IP bandwidth.MD5 can be implemented in existing hardware technology at 256 Mbps, and in software at 87 Mbps. These rates cannot support current IP rates, e.g., 100 Mbps TCP and 130 Mbps UDP over ATM. If MD5 cannot support existing network bandwidth using existing technology, it will not scale as network speeds increase in the future. This RFC is intended to alert the IP community about the performance limitations of MD5, and to suggest that alternatives be considered for use in high speed IP implementations.
RFC 1811	U.S
	Authors: Government Internet Domain Names. Federal Networking Council. Date: June 1995 Formats: txt pdf Obsoleted by: RFC 1816 Status: INFORMATIONAL This document describes the registration policies for the top-level domain ".GOV". Thus far, Federal Agencies and their subsidiaries have registered without any guidance. This has resulted in multiple registrations for Federal Agencies and naming schemes that do not facilitate responsiveness to the public. This document fixes this by restricting registrations to coincide with the approved structure of the US government. The document cited, FIPS 95-1, provides a standard recognized structure into which domain registrations for top-level domains. The IANA requires that an organization/country apply for and get a 2 letter code from ISO/ITU (e.g., US for UnitedStates) for additional top-level registration. As a side effect, this reduces the number of .GOV level registrations and reduces the workload on the Internic.
RFC 1813	NFS Version 3 Protocol Specification
	Authors: B. Callaghan, B. Pawlowski, P. Staubach. Date: June 1995 Formats: txt pdf Also: RFC 1094 Status: INFORMATIONAL This paper describes the NFS version 3 protocol. This paper is provided so that people can write compatible implementations.
RFC 1814	Unique Addresses are Good
	Authors: E. Gerich. Date: June 1995 Formats: txt pdf Status: INFORMATIONAL The IAB suggests that while RFC 1597 establishes reserved IP address space for the use of private networks which are isolated and will remain isolated from the Internet, any enterprise which anticipates external connectivity to the Internet should apply for a globally unique address from an Internet registry or service provider.
RFC 1815	Character Sets ISO-10646 and ISO-10646-J-1
	Authors: M. Ohta. Date: July 1995 Formats: txt pdf Status: INFORMATIONAL Though the ISO character set standard of ISO 10646 is specified reasonably well about European characters, it is not so useful in an fully internationalized environment. For the practical use of ISO 10646, a lot of external profiling such as restriction of characters, restriction of combination of characters and addition of language information is necessary. This memo provides information on such profiling, along with charset names to each profiled instance. Though all the effort is done to make the resulting charset as useful10646 based charset as possible, the result is not so good. So, the charsets defined in this memo are only for reference purpose and its use for practical purpose is strongly discouraged.
RFC 1816	U.S
	Authors: Government Internet Domain Names. Federal Networking Council. Date: August 1995 Formats: txt pdf Obsoletes: RFC 1811 Obsoleted by: RFC 2146 Status: INFORMATIONAL This memo provides an update and clarification to RFC 1811. This document describes the registration policies for the top-level domain".GOV". Thus far, Federal Agencies and their subsidiaries have registered without any guidance. This has resulted in multiple registrations for Federal Agencies and naming schemes that do not facilitate responsiveness to the public. This document fixes this by restricting registrations to coincide with the approved structure of the US government. The document cited, FIPS 95-1, provides a standard recognized structure into which domain registrations for.GOV can be fit. This policy is exactly comparable to that for the top-level domains. The IANA requires that an organization/country apply for and get a 2 letter code from ISO/ITU (e.g., US for UnitedStates) for additional top-level registration. As a side effect, this reduces the number of .GOV level registrations and reduces the workload on the Internic.
RFC 1820	Multimedia E-mail (MIME) User Agent Checklist
	Authors: E. Huizer. Date: August 1995 Formats: txt pdf Obsoleted by: RFC 1844 Status: INFORMATIONAL This document presents a checklist to facilitate evaluation of MIME capable User Agents. Access to a MIME test-responder, that generates test-messages is described.
RFC 1821	Integration of Real-time Services in an IP-ATM Network Architecture
	Authors: M. Borden, E. Crawley, B. Davie, S. Batsell. Date: August 1995 Formats: txt pdf Status: INFORMATIONAL The IETF is currently developing an integrated service model which is designed to support real-time services on the Internet.Concurrently, the ATM Forum is developing Asynchronous Transfer Mode networking which similarly provides real-time networking support. The use of ATM in the Internet as a link layer protocol is already occurring, and both the IETF and the ATM Forum are producing specifications for IP over ATM. The purpose of this paper is to provide a clear statement of what issues need to be addressed in interfacing the IP integrated services environment with an ATM service environment so as to create a seamless interface between the two in support of end users desiring real-time networking services.
RFC 1822	A Grant of Rights to Use a Specific IBM patent with Photuris
	Authors: J. Lowe. Date: August 1995 Formats: txt pdf Status: INFORMATIONAL This Request for Comments records a grant by IBM Corporation to permit the conditional free use of one of its patents. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1823	The LDAP Application Program Interface
	Authors: T. Howes, M. Smith. Date: August 1995 Formats: txt pdf Status: INFORMATIONAL This document defines a C language application program interface to the lightweight directory access protocol (LDAP). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1824	The Exponential Security System TESS: An Identity-Based Cryptographic Protocol for Authenticated Key-Exchange (E.I.S.S.-Report 1995/4)
	Authors: H. Danisch. Date: August 1995 Formats: txt pdf Status: INFORMATIONAL This informational RFC describes the basic mechanisms and functions of an identity based system for the secure authenticated exchange of cryptographic keys, the generation of signatures, and the authentic distribution of public keys.
RFC 1834	Whois and Network Information Lookup Service, Whois++
	Authors: J. Gargano, K. Weiss. Date: August 1995 Formats: txt pdf Status: INFORMATIONAL This memo describes new features for WHOIS. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1841	PPP Network Control Protocol for LAN Extension
	Authors: J. Chapman, D. Coli, A. Harvey, B. Jensen, K. Rowett. Date: September 1995 Formats: txt pdf Status: INFORMATIONAL Telecommunications infrastructure is improving to offer higher bandwidth connections at lower cost. Access to the network is changing from modems to more intelligent devices. This informationalRFC discusses a PPP Network Control Protocol for one such intelligent device. The protocol is the LAN extension interface protocol.
RFC 1842	ASCII Printable Characters-Based Chinese Character Encoding for Internet Messages
	Authors: Y. Wei, Y. Zhang, J. Li, J. Ding, Y. Jiang. Date: August 1995 Formats: txt pdf Status: INFORMATIONAL This document describes the encoding used in electronic mail [RFC822] and network news [RFC1036] messages over the Internet. The 7-bit representation of GB 2312 Chinese text was specified by Fung Fung Lee of Stanford University [Lee89] and implemented in various software packages under different platforms (see appendix for a partial list of the available software packages that support this encoding method). It is further tested and used in the usenet newsgroups alt.chinese.text and chinese.* as well as various other network forums with considerable success. Future extensions of this encoding method can accommodate additional GB character sets and other east asian language character sets [Wei94]. The name given to this encoding is "HZ-GB-2312", which is intended to be used in the "charset" parameter field of MIME headers (see [MIME1] and [MIME2]).
RFC 1843	HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and ASCII characters
	Authors: F. Lee. Date: August 1995 Formats: txt pdf Status: INFORMATIONAL The content of this memo is identical to an article of the same title written by the author on September 4, 1989. In this memo, GB stands for GB2312-80. Note that the title is kept only for historical reasons. HZ has been widely used for purposes other than "file exchange".
RFC 1844	Multimedia E-mail (MIME) User Agent Checklist
	Authors: E. Huizer. Date: August 1995 Formats: txt pdf Obsoletes: RFC 1820 Status: INFORMATIONAL This document presents a checklist to facilitate evaluation of MIME capable User Agents. Access to a MIME test-responder, that generates test-messages is described.
RFC 1853	IP in IP Tunneling
	Authors: W. Simpson. Date: October 1995 Formats: txt pdf Status: INFORMATIONAL This document discusses implementation techniques for using IPProtocol/Payload number 4 Encapsulation for tunneling with IPSecurity and other protocols.
RFC 1855	Netiquette Guidelines
	Authors: S. Hambridge. Date: October 1995 Formats: txt pdf Also: FYI 0028 Status: INFORMATIONAL This document provides a minimum set of guidelines for NetworkEtiquette (Netiquette) which organizations may take and adapt for their own use. As such, it is deliberately written in a bulleted format to make adaptation easier and to make any particular item easy(or easier) to find. It also functions as a minimum set of guidelines for individuals, both users and administrators. This memo is the product of the Responsible Use of the Network (RUN) WorkingGroup of the IETF.
RFC 1856	The Opstat Client-Server Model for Statistics Retrieval
	Authors: H. Clark. Date: September 1995 Formats: txt pdf Status: INFORMATIONAL Network administrators gather data related to the performance, utilization, usability and growth of their data network. The amount of raw data gathered is usually quite large, typically ranging somewhere between several megabytes to several gigabytes of data each month. Few (if any) tools exist today for the sharing of that raw data among network operators or between a network service provider(NSP) and its customers. This document defines a model and protocol for a set of tools which could be used by NSPs and Network OperationCenters (NOCs) to share data among themselves and with customers.
RFC 1857	A Model for Common Operational Statistics
	Authors: M. Lambert. Date: October 1995 Formats: txt pdf Obsoletes: RFC 1404 Status: INFORMATIONAL This memo describes a model for operational statistics in theInternet. It gives recommendations for metrics, measurements, polling periods and presentation formats and defines a format for the exchange of operational statistics.
RFC 1858	Security Considerations for IP Fragment Filtering
	Authors: G. Ziemba, D. Reed, P. Traina. Date: October 1995 Formats: txt pdf Updated by: RFC 3128 Status: INFORMATIONAL IP fragmentation can be used to disguise TCP packets from IP filters used in routers and hosts. This document describes two methods of attack as well as remedies to prevent them.
RFC 1859	ISO Transport Class 2 Non-use of Explicit Flow Control over TCP RFC1006 extension
	Authors: Y. Pouffary. Date: October 1995 Formats: txt pdf Status: INFORMATIONAL This document is an extension to STD35, RFC1006, a standard for the Internet community. The document does not duplicate the protocol definitions contained in RFC1006 and in International Standard ISO 8073. It supplements that information with the description of how to implement ISO Transport Class 2 Non-use of Explicit Flow Control on top of TCP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1860	Variable Length Subnet Table For IPv4
	Authors: T. Pummill, B. Manning. Date: October 1995 Fo