Movatterモバイル変換
[0]ホーム
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]
INFORMATIONAL
Network Working Group J. ReynoldsRequest for Comments: 1199 ISI December 1991Request for Comments Summary RFC Numbers 1100-1199Status of This Memo This RFC is a slightly annotated list of the 100 RFCs fromRFC 1100 through RFCs 1199. This is a status report on these RFCs. This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited.Note Many RFCs, but not all, are Proposed Standards, Draft Standards, or Standards. Since the status of these RFCs may change during the standards processing, we note here only that they are on the standards track. Please see the latest edition of "IAB Official Protocol Standards" for the current state and status of these RFCs. In the following, RFCs on the standards track are marked [STANDARDS- TRACK].RFC Author Date Title--- ------ ---- -----1199 Reynolds Dec 91 Requests For Comments SummaryThis memo.1198 Scheifler Jan 91 FYI on the X Window SystemThis FYI RFC provides pointers to the published standards of the MIT XConsortium. This memo provides information for the Internet community.It does not specify any Internet standard.1197 Sherman Dec 90 Using ODA for Translating Multimedia InformationThe purpose of this RFC is to inform implementors of multimedia systemsabout our experiences using ISO 8613: Office Document Architecture(ODA). Because ODA is being proposed as an encoding format for use inmultimedia mail and file exchange, implementors wishing to use ODA in anReynolds [Page 1]
RFC 1199 Summary of 1100-1199 December 1991open systems environment may profit from our experiences. This memoprovides information for the Internet community. It does not specifyany standard.1196 Zimmerman Dec 90 The Finger User Information ProtocolThis memo describes the Finger User Information Protocol. This is asimple protocol which provides an interface to a remote user informationprogram. Based onRFC 742, a description of the original Fingerprotocol, this memo attempts to clarify the expected communicationbetween the two ends of a Finger connection. It also tries not toinvalidate the many existing implementations or add unnecessaryrestrictions to the original protocol definition. This edition correctsand clarifies in a minor way,RFC 1194. [STANDARDS-TRACK]1195 Callon Dec 90 Use of OSI IS-IS for Routing in TCP/IP and Dual EnvironmentsThis memo specifies an integrated routing protocol, based on the OSIIntra-Domain IS-IS Routing Protocol, which may be used as an interiorgateway protocol (IGP) to support TCP/IP as well as OSI. This allows asingle routing protocol to be used to support pure IP environments, pureOSI environments, and dual environments. This specification wasdeveloped by the IS-IS working group of the Internet Engineering TaskForce. [STANDARDS-TRACK]1194 Zimmerman Nov 90 The Finger User Information ProtocolThis memo describes the Finger User Information Protocol. This is asimple protocol which provides an interface to a remote user informationprogram. Based onRFC 742, a description of the original Fingerprotocol, this memo attempts to clarify the expected communicationbetween the two ends of a Finger connection. It also tries not toinvalidate the many existing implementations or add unnecessaryrestrictions to the original protocol definition. [STANDARDS-TRACK]1193 Ferrari Nov 90 Client Requirements for Real-Time Communication ServicesThis memo describes client requirements for real-time communicationservices. This memo provides information for the Internet community,and requests discussion and suggestions for improvements. It does notspecify any standard.Reynolds [Page 2]
RFC 1199 Summary of 1100-1199 December 19911192 Kahin Nov 90 Commercialization of the Internet Summary ReporThis memo is based on a workshop held by the Science, Technology andPublic Policy Program of the John F. Kennedy School of Government,Harvard University, March 1-3, 1990. This memo provides information forthe Internet community. It does not specify any standard.1191 Mogul Nov 90 Path MTU DiscoveryThis memo describes a technique for dynamically discovering the maximumtransmission unit (MTU) of an arbitrary internet path. It specifies asmall change to the way routers generate one type of ICMP message. Fora path that passes through a router that has not been so changed, thistechnique might not discover the correct Path MTU, but it will alwayschoose a Path MTU as accurate as, and in many cases more accurate than,the Path MTU that would be chosen by current practice. [STANDARDS-TRACK]1190 Topolcic Oct 90 Experimental Internet Stream Protocol, Version 2 (ST-II)This memo defines a revised version of the Internet Stream Protocol,originally defined in IEN-119 [8], based on results from experimentswith the original version, and subsequent requests, discussion, andsuggestions for improvements. This is a Limited-Use ExperimentalProtocol. Please refer to the current edition of the "IAB OfficialProtocol Standards" for the standardization state and status of thisprotocol.1189 Warrier Oct 90 The Common Management Information Services and Protocols for the InternetThis memo defines a network management architecture that uses theInternational Organization for Standardization's (ISO) Common ManagementInformation Services/Common Management Information Protocol (CMIS/CMIP)in the Internet. [STANDARDS-TRACK]1188 Katz Oct 90 A Proposed Standard for the Transmission of IP Datagrams over FDDI NetworksThis memo defines a method of encapsulating the Internet Protocol (IP)datagrams and Address Resolution Protocol (ARP) requests and replies onReynolds [Page 3]
RFC 1199 Summary of 1100-1199 December 1991Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK]1187 Rose Oct 90 Bulk Table Retrieval with the SNMPThis memo reports an interesting family of algorithms for bulk tableretrieval using the Simple Network Management Protocol (SNMP). Thismemo describes an Experimental Protocol for the Internet community, andrequests discussion and suggestions for improvements. This memo doesnot specify a standard for the Internet community. Please refer to thecurrent edition of the "IAB Official Protocol Standards" for thestandardization state and status of this protocol.1186 Rivest Oct 90 The MD4 Message Digest AlgorithmThis RFC is the specification of the MD4 Digest Algorithm. If you aregoing to implement MD4, it is suggested you do it this way. This memois for informational use and does not constitute a standard.1185 Jacobson Oct 90 TCP Extension for High-Speed PathsThis memo describes an Experimental Protocol extension to TCP for theInternet community, and requests discussion and suggestions forimprovements. Please refer to the current edition of the "IAB OfficialProtocol Standards" for the standardization state and status of thisprotocol.1184 Borman Oct 90 Telnet Linemode OptionThis RFC specifies a procedure for line at a time terminal interactionbased on the Telnet Protocol. It obsoletesRFC 1116. [STANDARDS-TRACK]1183 Everhart Oct 90 New DNS RR DefinitionsThis memo defines five new DNS types for experimental purposes. ThisRFC describes an Experimental Protocol for the Internet community, andrequests discussion and suggestions for improvements.1182 Never issued.Reynolds [Page 4]
RFC 1199 Summary of 1100-1199 December 19911181 Blokzijl Sep 90 RIPE Terms of ReferenceThis RFC describes the Terms of Reference of RIPE (Reseaux IPEuropeens), the cooperation of European IP networks. This memo providesinformation for the Internet community. It does not specify anystandard.1180 Socolofsky Jan 91 A TCP/IP TutorialThis RFC is a tutorial on the TCP-IP protocol suite, focusingparticularly on the steps in forwarding an IP datagram from source hostto destination host through a router. It does not specify an Internetstandard.1179 McLaughlin Aug 90 Line Printer Daemon ProtocolThis RFC describes an existing print server protocol widely used on theInternet for communicating between line printer daemons (both clientsand servers). This memo is for informational purposes only, and doesnot specify an Internet standard. Please refer to the current editionof the "IAB Official Protocol Standards" for the standardization stateand status of this protocol.1178 Libes Aug 90 Choosing a Name for Your ComputerThis FYI RFC is a republication of a Communications of the ACM articleon guidelines on what to do and what not to do when naming yourcomputer. This memo provides information for the Internet community.It does not specify any standard. [Also FYI 5.]1177 Malkin Aug 90 FYI on Questions and Answers Answers to Commonly asked "New Internet User" QuestionsThis FYI RFC is one of three FYI's called, "Questions and Answers"(Q/A), produced by the User Services Working Group (USWG) of theInternet Engineering Task Force (IETF). The goal is to document themost commonly asked questions and answers in the Internet. This memoprovides information for the Internet community. It does not specifyany standard. [Also FYI 4.]Reynolds [Page 5]
RFC 1199 Summary of 1100-1199 December 19911176 Crispin Aug 90 Interactive Mail Access Protocol - Version 2This RFC suggests a method for personal computers and workstations todynamically access mail from a mailbox server ("repository"). ItobosoletesRFC 1064. This RFC specifies an Experimental Protocol forthe Internet community. Discussion and suggestions for improvement arerequested. Please refer to the current edition of the "IAB OfficialProtocol Standards" for the standardization state and status of thisprotocol.1175 Bowers Aug 90 FYI on Where to Start - A Bibliography of Internetworking InformationThis FYI RFC is a bibliography of information about TCP/IPinternetworking, prepared by the User Services Working Group (USWG) ofthe Internet Engineering Task Force (IETF). This memo providesinformation for the Internet community. It does not specify anystandard. [Also FYI 3.]1174 Cerf Aug 90 IAB Recommended Policy on Distributing Internet Identifier Assignment and IAB Recommended Policy Change to Internet "Connected" StatusThis informational RFC represents the official view of the InternetActivities Board (IAB), and describes the recommended policies andprocedures on distributing Internet identifier assignments and droppingthe connected status requirement. This RFC does not specify a standard.1173 Van Bokkelen Aug 90 Responsibilities of Host and Network Managers: A Summary of the "Oral Tradition" of the InternetThis informational RFC describes the conventions to be followed by thosein 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 theseconventions. It is expected that this RFC will provide a basis for thedevelopment of official policies in the future.] These conventions maybe supplemented or amended by the policies of specific local andregional components of the Internet. This RFC does not specify astandard, or a policy of the IAB.Reynolds [Page 6]
RFC 1199 Summary of 1100-1199 December 19911172 Perkins Jul 90 The Point-to-Point Protocol (PPP) Initial Configuration OptionsThis memo specifies the Point-to-Point Protocol (PPP) InitialConfiguration Options as a Proposed Standard Protocol for the Internetcommunity. When it becomes a full Standard, this protocol will berecommended for all TCP/IP implementations that communicate over seriallinks.1171 Perkins Jul 90 The Point-to-Point Protocol for the Transmission of Multi-Protocol Datagrams Over Point-to-Point LinksThis memo specifies the Point-to-Point Protocol (PPP) as a DraftStandard Protocol for the Internet community. When it becomes a fullStandard, this protocol will be recommended for all TCP/IPimplementations that communicate over serial links.1170 Fougner Jan 91 Public Key Standards and LicensesThis RFC is a public statement by Public Key Partners regarding PublicKey Standards and Licenses. This memo is for informational use only,and does not constitute an Internet standard.1169 Cerf Aug 90 Explaining the Role of GOSIPThis informational RFC represents the official view of the InternetActivities Board (IAB), after coordination with the Federal NetworkingCouncil (FNC). This RFC does not specify a standard.1168 Westine Jul 90 Intermail and Commercial Mail Relay ServicesThis RFC discusses the history and evolution of the Intermail andCommercial mail systems. The problems encountered in operating astore-and-forward mail relay between commercial systems such asTelemail, MCI Mail and Dialcom are also discussed. This RFC providesinformation for the Internet community, and does not specify anystandard.Reynolds [Page 7]
RFC 1199 Summary of 1100-1199 December 19911167 Cerf Jul 90 Thoughts on the National Research and Education NetworkThe memo provides a brief outline of a National Research and EducationNetwork (NREN). This memo provides information for the Internetcommunity. It does not specify any standard. It is not a statement ofIAB policy or recommendations.1166 KirkpatrickJul 90 Internet NumbersThis memo is a status report on the network numbers and autonomoussystem numbers used in the Internet community.1165 Crowcrowft Jun 90 Network Time Protocol (NTP) over the OSI Remote Operations ServiceThis memo suggests an Experimental Protocol for the OSI and Internetcommunities. Hosts in either community, and in particular those on bothare encouraged to experiment with this mechanism.1164 Honig Jun 90 Application of the Border Gateway Protocol in the InternetThis RFC, together with its companionRFC-1163, "A Border GatewayProtocol (BGP)", specify an inter-autonomous system routing protocol forthe Internet. [STANDARDS-TRACK]1163 Lougheed Jun 90 A Border Gateway Protocol (BGP)This RFC, together with its companionRFC-1164, "Application of theBorder Gateway Protocol in the Internet", specify an inter-autonomoussystem routing protocol for the Internet. [STANDARDS-TRACK]1162 Satz Jun 90 Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Management Information BaseThis memo defines an experimental portion of the Management InformationBase (MIB) for use with network management protocols in TCP/IP-basedinternets. This memo does not specify a standard for the Internetcommunity.Reynolds [Page 8]
RFC 1199 Summary of 1100-1199 December 19911161 Rose Jun 90 SNMP over OSIThis memo defines an experimental means for running the Simple NetworkManagement Protocol (SNMP) over OSI transports. This memo does notspecify a standard for the Internet community,1160 Cerf May 90 The Internet Activities BoardThis RFC provides a history and description of the Internet ActivitiesBoard (IAB) and its subsidiary organizations. This memo is forinformational use and does not constitute a standard. This is arevision ofRFC 1120.1159 Nelson Jun 90 Message Send ProtocolThis RFC suggests an Experimental Protocol for the Internet community.Hosts on the Internet that choose to implement a Message Send Protocolmay experiment with this protocol.1158 Rose May 90 Management Information Base for Network Management of TCP/IP-based internets: MIB-IIThis memo defines the second version of the Management Information Base(MIB-II) for use with network management protocols in TCP/IP- basedinternets. In particular, together with its companion memos whichdescribe the structure of management information (RFC 1155) along withthe network management protocol (RFC 1157) for TCP/IP- based internets,these documents provide a simple, workable architecture and system formanaging TCP/IP-based internets and in particular the Internetcommunity.This document on MIB-II incorporates all of the technical content of RFC1156 on MIB-I and extends it, without loss of compatibilty.[STANDARDS-TRACK]1157 Case May 90 A Simple Network Management Protocol (SNMP)This RFC is a re-release ofRFC 1098, with a changed "Status of thisMemo" section plus a few minor typographical corrections. This memodefines a simple protocol by which management information for a networkelement may be inspected or altered by logically remote users.[STANDARDS-TRACK]Reynolds [Page 9]
RFC 1199 Summary of 1100-1199 December 19911156 McCloghrie May 90 Management Information Base for Network Management of TCP/IP-based internetsThis RFC is a re-release ofRFC 1066, with a changed "Status of thisMemo", "IAB Policy Statement", and "Introduction" sections plus a fewminor typographical corrections. The technical content of the documentis unchanged fromRFC 1066. [STANDARDS-TRACK]1155 Rose May 90 Structure and Identification of Management Information for TCP/IP-based InternetsThis RFC is a re-release ofRFC 1065, with a changed "Status of thisMemo", plus a few minor typographical corrections. The technicalcontent of the document is unchanged fromRFC 1065. [STANDARDS-TRACK]1154 Robinson Apr 90 Encoding Header Field for Internet MessagesThis RFC proposes an elective experimental Encoding header field topermit the mailing of multi-part, multi-structured messages.The use of Encoding updatesRFC 1049 (Content-Type), and is a suggestedupdate to RFCs 1113, 1114, and 1115 (Privacy Enhancement).1153 Wancho Apr 90 Digest Message FormatThis memo describes the de facto standard Digest Message Format. Thisis an elective experimental protocol.1152 Partridge Apr 90 Workshop Report: Internet Research Steering GroupWorkshop on Very-High-Speed NetworksThis memo is a report on a workshop sponsored by the Internet ResearchSteering Group. This memo is for information only. This RFC does notspecify an Internet standard.1151 Partridge Apr 90 Version 2 of the Reliable Data Protocol (RDP)This RFC suggests several updates to the specification of the ReliableReynolds [Page 10]
RFC 1199 Summary of 1100-1199 December 1991Data Protocol (RDP) inRFC-908 based on experience with the protocol.This revised version of the protocol is experimental.1150 Malkin Mar 90 F.Y.I on F.Y.I: Introduction to the F.Y.I. NotesThis memo is the first in a new sub-series of RFCs called FYIs (For YourInformation). This memo provides information for the Internetcommunity. It does not specify any standard. [Also FYI 1.]1149 Waitzman Apr 90 A Standard for the Transmission of IP Datagrams on Avian CarriersThis memo describes an experimental method for the encapsulation of IPdatagrams in avian carriers. This specification is primarily useful inMetropolitan Area Networks. This is an experimental, not recommendedstandard.1148 Kille Mar 90 Mapping between X.400(1988) / ISO 10021 andRFC 822This RFC suggests an electronic mail protocol mapping for the Internetcommunity and UK Academic Community, and requests discussion andsuggestions for improvements. This memo does not specify an Internetstandard. This edition includes material lost in editing.1147 Stine Apr 90 FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected DevicesThe goal of this FYI memo is to provide practical information to siteadministrators and network managers. This memo provides information forthe Internet community. It does not specify any standard. It is not astatement of IAB policy or recommendations. [Also FYI 2.] This catalogcontains descriptions of several tools available to assist networkmanagers in debugging and maintaining TCP/IP internets andinterconnected communications resources. Entries in the catalog tellwhat a tool does, how it works, and how it can be obtained.Reynolds [Page 11]
RFC 1199 Summary of 1100-1199 December 19911146 Zweig Mar 90 TCP Alternate Checksum OptionsThis memo is suggests a pair of TCP options to allow use of alternatedata checksum algorithms in the TCP header. The use of these options isexperimental, and not recommended for production use. Note: This RFCcorrects errors introduced in the editing process inRFC 1145.1145 Zweig Feb 90 TCP Alternate Checksum OptionsThis memo is suggests a pair of TCP options to allow use of alternatedata checksum algorithms in the TCP header. The use of these options isexperimental, and not recommended for production use.1144 Jacobson Feb 90 Compressing TCP/IP Headers for Low-Speed Serial LinksThis RFC describes a method for compressing the headers of TCP/IPdatagrams to improve performance over low speed serial links. Themotivation, implementation and performance of the method are described.C code for a sample implementation is given for reference. [STANDARDS-TRACK]1143 Bernstein Feb 90 The Q Method of Implementing TELNET Option NegotiationThis is RFC discusses an implementation approach to option negotiationin the Telnet protocol (RFC 854). It does not propose any changes tothe TELNET protocol. Rather, it discusses the implementation of theprotocol of one feature, only. This is not a protocol specification.This is an experimental method of implementing a protocol.1142 Oran Feb 90 OSI IS-IS Intra-domain Routing ProtocolThis RFC is a republication of ISO DP 10589 as a service to theInternet community. This is not an Internet standard.1141 Mallory Jan 90 Incremental Updating of the Internet ChecksumThis memo correctly describes the incremental update procedure for usewith the standard Internet checksum. It is intended to replace thedescription of Incremental Update inRFC 1071. This is not a standardbut rather, an implementation technique.Reynolds [Page 12]
RFC 1199 Summary of 1100-1199 December 19911140 Postel May 90 IAB Official Protocol StandardsThis memo describes the state of standardization of protocols used inthe Internet as determined by the Internet Activities Board (IAB).This memo is issued quarterly, please be sure the copy you are readingis dated within the last three months. Current copies may be obtainedfrom the Network Information Center or from the Internet AssignedNumbers Authority. Do not use this edition after 31-Aug-90.1139 Hagens Jan 90 An Echo Function for ISO 8473This memo defines an echo function for the connection-less network layerprotocol. Two mechanisms are introduced that may be used to implementthe echo function. The first mechanism is recommended as an interimsolution for the Internet community. The second mechanism will beprogressed to the ANSI X3S3.3 working group for consideration as a workitem.When an ISO standard is adopted that provides functionality similar tothat described by this memo, then this memo will become obsolete andsuperceded by the ISO standard. This memo is not intended to competewith an ISO standard. [STANDARDS-TRACK]1138 Kille Dec 89 Mapping between X.400(1988) / ISO 10021 andRFC 822Ths RFC suggests an electronic mail protocol mapping for the Internetcommunity and UK Academic Community, and requests discussion andsuggestions for improvements. This memo does not specify an Internetstandard. This memo updates RFCs 822, 987, and 1026.1137 Kille Dec 89 Mapping Between FullRFC 822 andRFC 822 with Restricted EncodingThis RFC suggests an electronic mail protocol mapping for the Internetcommunity and UK Academic Community, and requests discussion andsuggestions for improvements. This memo does not specify an Internetstandard.1136 Hares Dec 89 Administrative Domains and Routing Domains A Model for Routing in the InternetThis RFC proposes a model for describing routing within the Internet.Reynolds [Page 13]
RFC 1199 Summary of 1100-1199 December 1991The model is an adaptation of the "OSI Routeing Framework". This memodoes not specify an Internet standard.1135 Reynolds Dec 89 The Helminthiasis of the InternetThis memo takes a look back at the helminthiasis (infestation with, ordisease caused by parasitic worms) of the Internet that was unleashedthe evening of 2 November 1988. This RFC provides information about anevent that occurred in the life of the Internet. This memo does notspecify any standard.This document provides a glimpse at the infection, its festering, andcure. The impact of the worm on the Internet community, ethicsstatements, the role of the news media, crime in the computer world, andfuture prevention is discussed. A documentation review presents fourpublications that describe in detail this particular parasitic computerprogram. Reference and bibliography sections are also included.1134 Perkins Nov 89 The Point-to-Point Protocol: A Proposal for Multi-Protocol Transmission of Datagrams Over Point-to-Point LinksThis proposal is the product of the Point-to-Point Protocol WorkingGroup of the Internet Engineering Task Force (IETF). Comments on thismemo should be submitted to the IETF Point-to-Point Protocol WorkingGroup chair by January 15, 1990. Comments will be reviewed at theFebruary 1990 IETF meeting, with the goal of advancing PPP to draftstandard status. [STANDARDS-TRACK]1133 Yu Nov 89 Routing between the NSFNET and the DDNThis document is a case study of the implementation of routing betweenthe NSFNET and the DDN components (the MILNET and the ARPANET). We hopethat it can be used to expand towards interconnection of otherAdministrative Domains. We would welcome discussion and suggestionsabout the methods employed for the interconnections. No standards arespecified in this memo.1132 McLaughlin Nov 89 A Standard for the Transmission of 802.2 Packets over IPX NetworksThis document specifies a standard method of encapsulating 802.2 packetson networks supporting Novell's Internet Packet Exchange Protocol (IPX).It obsoletes earlier documents detailing the transmission of InternetReynolds [Page 14]
RFC 1199 Summary of 1100-1199 December 1991packets over IPX networks. It differs from these earlier documents inthat it allows for the transmission of multiple network protocols overIPX and for the transmission of packets through IPX bridges.1131 Moy Oct 89 The OSPF SpecificationThis RFC is the specification of the Open Shortest Path First (OSPF)Internet routing protocol. OSPF is in the class of Internal GatewayProtocols (IGPs) for distributing routing information between gatewaysof a single Autonomous System. This routing protocol is based on thelink-state approach (in contrast to the distance-vector approach). Thisspecification was developed by the OSPF Working Group of the InternetEngineering Task Force. [STANDARDS-TRACK]1130 Postel Oct 89 IAB Official Protocol StandardsThis memo describes the state of standardization of protocols used inthe Internet as determined by the Internet Activities Board (IAB).1129 Mills Oct 89 Internet Time Synchronization: the Network Time ProtocolThis memo describes the Network Time Protocol (NTP) designed todistribute time information in a large, diverse internet systemoperating at speeds from mundane to lightwave. It uses a returnable-time architecture in which a distributed subnet of time serversoperating in a self-organizing, hierarchical, master-slave configurationsynchronizes local clocks within the subnet and to national timestandards via wire or radio. The servers can also redistribute timeinformation within a network via local routing algorithms and timedaemons.The architectures, algorithms and protocols which have evolved to NTPover several years of implementation and refinement are described inthis paper. The synchronization subnet which has been in regularoperation in the Internet for the last several years is described alongwith performance data which shows that timekeeping accuracy throughoutmost portions of the Internet can be ordinarily maintained to within afew tens of milliseconds, even in cases of failure or disruption ofclocks, time servers or networks.This memo describes the Network Time Protocol inRFC-1119.Reynolds [Page 15]
RFC 1199 Summary of 1100-1199 December 19911128 Mills Oct 89 Measured Performance of the Network Time Protocol in the Internet SystemThis paper describes a series of experiments involving over 100,000hosts of the Internet system and located in the U.S., Europe and thePacific. The experiments are designed to evaluate the availability,accuracy and reliability of international standard time distributionusing the DARPA/NSF Internet and the Network Time Protocol (NTP), whichis specified inRFC-1119. NTP is designed specifically for use in alarge, diverse internet system operating at speeds from mundane tolightwave. In NTP a distributed subnet of time servers operating in aself-organizing, hierarchical, master-slave configuration exchangeprecision timestamps in order to synchronize subnet clocks to each otherand national time standards via wire or radio.The experiments are designed to locate Internet hosts and gateways thatprovide time by one of three time distribution protocols and evaluatethe accuracy of their indications. For those hosts that support NTP,the experiments determine the distribution of errors and otherstatistics over paths spanning major portions of the globe. Finally,the experiments evaluate the accuracy and reliability of precisiontimekeeping using NTP and typical Internet paths involving DARPA, NSFNETand other agency networks. The experiments demonstrate that timekeepingaccuracy throughout most portions of the Internet can be ordinarilymaintained to within a few tens of milliseconds, even in cases offailure or disruption of clocks, time servers or networks.This memo does not specify a standard.1127 Braden Oct 89 Perspective on Host RequirementsThis RFC is for information only; it does not constitute a standard,draft standard, or proposed standard, and it does not define a protocol.1126 Little Oct 89 Goals and Functional Requirements for Inter-Autonomous System RoutingThis document describes the functional requirements for a routingprotocol to be used between autonomous systems. This document isintended as a necessary precursor to the design of a new inter-autonomous system routing protocol and specifies requirements for theInternet applicable for use with the current DoD IP, the ISO IP, andfuture Internet Protocols. It is intended that these requirements willform the basis for the future development of a new inter-autonomoussystems routing architecture and protocol. This memo does not specify astandard.Reynolds [Page 16]
RFC 1199 Summary of 1100-1199 December 19911125 Estrin Nov 89 Policy Requirements for Inter Administrative Domain RoutingThe purpose of this memo is to focus discussion on particular problemsin the Internet and possible methods of solution. No proposed solutionsin this document are intended as standards for the Internet. Rather, itis hoped that a general consensus will emerge as to the appropriatesolution to such problems, leading eventually to the development andadoption of standards.1124 Leiner Sep 89 Policy Issues in Interconnecting NetworksTo support the activities of the Federal Research Internet CoordinatingCommittee (FRICC) in creating an interconnected set of networks to servethe research community, two workshops were held to address the technicalsupport of policy issues that arise when interconnecting such networks.Held under the suspices of the Internet Activities Board at the requestof the FRICC, and sponsored by NASA through RIACS, the workshopsaddressed the required and feasible technologies and architectures thatcould be used to satisfy the desired policies for interconnection. Thepurpose of this RFC is to report the results of these workshops.1123 Braden Oct 89 Requirements for Internet Hosts -- Application and SupportThis RFC is an official specification for the Internet community. Itincorporates by reference, amends, corrects, and supplements the primaryprotocol standards documents relating to hosts. [STANDARDS-TRACK]1122 Braden Oct 89 Requirements for Internet Hosts -- Communication LayersThis RFC is an official specification for the Internet community. Itincorporates by reference, amends, corrects, and supplements the primaryprotocol standards documents relating to hosts. [STANDARDS-TRACK]1121 Postel Sep 89 Act One - The PoemsThis RFC presents a collection of poems that were presented at "ActOne", a symposium held partially in celebration of the 20th anniversaryof the ARPANET.Reynolds [Page 17]
RFC 1199 Summary of 1100-1199 December 19911120 Cerf Sep 89 The Internet Activities BoardThis RFC provides a history and description of the Internet ActivitiesBoard (IAB) and its subsidiary organizations. This memo is forinformational use and does not constitute a standard.1119 Mills Sep 89 Network Time Protocol (Version 2) Specification and ImplementationThis document describes the Network Time Protocol (NTP), specifies itsformal structure and summarizes information useful for itsimplementation. NTP provides the mechanisms to synchronize time andcoordinate time distribution in a large, diverse internet operating atrates from mundane to lightwave. It uses a returnable-time design inwhich a distributed subnet of time servers operating in a self-organizing, hierarchical-master-slave configuration synchronizes localclocks within the subnet and to national time standards via wire orradio. The servers can also redistribute reference time via localrouting algorithms and time daemons. [STANDARDS-TRACK]1118 Krol Sep 89 The Hitchhikers Guide to the InternetThis RFC is being distributed to members of the Internet community inorder to make available some "hints" which will allow new networkparticipants to understand how the direction of the Internet is set, howto acquire online information and how to be a good Internet neighbor.While the information discussed may not be relevant to the researchproblems of the Internet, it may be interesting to a number ofresearchers and implementors. No standards are defined or specified inthis memo.1117 Romano Aug 89 Internet NumbersThis memo is an official status report on the network numbers and theautonomous system numbers used in the Internet community.1116 Borman Aug 89 Telnet Linemode OptionHosts on the Internet that support Linemode within the Telnet protocolare expected to adopt and implement this protocol. Obsoleted by RFC1184. [STANDARDS-TRACK]Reynolds [Page 18]
RFC 1199 Summary of 1100-1199 December 19911115 Linn Aug 89 Privacy Enhancement for Internet Electronic Mail: Part III -- Algorithms, Modes, and IdentifiersThis RFC provides definitions, references, and citations foralgorithms, usage modes, and associated identifiers used inRFC-1113andRFC-1114 in support of privacy-enhanced electronic mail.[STANDARDS-TRACK]1114 Kent Aug 89 Privacy Enhancement for Internet Electronic Mail: Part II -- Certificate-Based Key ManagementThis RFC specifies the key management aspects of Privacy Enhanced Mail.[STANDARDS-TRACK]1113 Linn Aug 89 Privacy Enhancement for Internet Electronic Mail: Part I -- Message Encipherment and Authentication ProceduresThis RFC specifies features for private electronic mail based onencryption technology. [STANDARDS-TRACK]1112 Deering Aug 89 Host Extensions for IP MulticastingThis memo specifies the extensions required of a host implementation ofthe Internet Protocol (IP) to support multicasting. Recommendedprocedure for IP multicasting in the Internet. This RFC obsoletes RFCs998 and 1054.[STANDARDS-TRACK]1111 Postel Aug 89 Request for Comments on Request for Comments - Instructions to RFC AuthorsThis RFC specifies a standard for the Internet community. Authors ofRFCs are expected to adopt and implement this standard.1110 McKenzie Aug 89 A Problem with the TCP Big Window OptionThis memo comments on the TCP Big Window option described inRFC 1106.Reynolds [Page 19]
RFC 1199 Summary of 1100-1199 December 19911109 Cerf Aug 89 Report of the Second Ad Hoc Network Management Review GroupThis RFC reports an official Internet Activities Board (IAB) policyposition on the treatment of Network Management in the Internet. ThisRFC presents the results and recommendations of the second Ad HocNetwork Management Review on June 12, 1989. The results of the firstsuch meeting were reported inRFC 1052.1108 Kent Nov 91 U.S. Department of Defense Security Options for the Internet ProtocolThis RFC specifies the U.S. Department of Defense Basic SecurityOption and the top-level description of the Extended Security Optionfor use with the Internet Protocol. This RFC obsoletesRFC 1038,"Revised IP Security Option", dated January 1988. [STANDARDS-TRACK]1107 Sollins Jul 89 A Plan for Internet Directory ServicesThis memo proposes a program to develop a directory service for theInternet. It reports the results of a meeting held in February 1989,which was convened to review requirements and options for such aservice. This proposal is offered for comment, and does not represent acommitted research activity of the Internet community.1106 Fox Jun 89 TCP Big Window and Nak OptionsThis memo discusses two extensions to the TCP protocol to provide a moreefficient operation over a network with a high bandwidth*delay product.The extensions described in this document have been implemented andshown to work using resources at NASA. This memo describes anExperimental Protocol, these extensions are not proposed as an Internetstandard, but as a starting point for further research.1105 Lougheed Jun 89 A Border Gateway Protocol (BGP)This RFC outlines a specific approach for the exchange of networkreachability information between Autonomous Systems. Updated by RFCs1163 and 1164.[STANDARDS-TRACK]Reynolds [Page 20]
RFC 1199 Summary of 1100-1199 December 19911104 Braun Jun 89 Models of Policy Based RoutingThe purpose of this RFC is to outline a variety of models for policybased routing. The relative benefits of the different approaches arereviewed. Discussions and comments are explicitly encouraged to movetoward the best policy based routing model that scales well within alarge internetworking environment.1103 Katz Jun 89 A Proposed Standard for the Transmission of IP Datagrams over FDDI NetworksThis RFC specifies a method of encapsulating the Internet Protocol (IP)datagrams and Address Resolution Protocol (ARP) requests and replies onFiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK]1102 Clark May 89 Policy Routing in Internet ProtocolsThe purpose of this RFC is to focus discussion on particular problems inthe Internet and possible methods of solution. No proposed solutions inthis document are intended as standards for the Internet.1101 MockapetrisApr 89 DNS Encoding of Network Names and Other TypesThis RFC proposes two extensions to the Domain Name System: - A specific method for entering and retrieving RRs which map between network names and numbers. - Ideas for a general method for describing mappings between arbitrary identifiers and numbers.The method for mapping between network names and addresses is a proposedstandard, the ideas for a general method are experimental.1100 IAB Apr 89 IAB Official Protocol StandardsThis memo describes the state of standardization of protocols used inthe Internet as determined by the Internet Activities Board (IAB). Anoverview of the standards procedures is presented first, followed bydiscussions of the standardization process and the RFC document series,then the explanation of the terms is presented, the lists of protocolsin each stage of standardization follows, and finally pointers toreferences and contacts for further information.Reynolds [Page 21]
RFC 1199 Summary of 1100-1199 December 1991This memo is issued quarterly, please be sure the copy you are readingis dated within the last three months. Current copies may be obtainedfrom the Network Information Center or from the Internet AssignedNumbers Authority (see the contact information at the end of this memo).Do not use this memo after 31-July-89.Security Considerations Security issues are not discussed in this memo.Author's Address Joyce K. Reynolds University of Southern California Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 Phone: (310) 822-1511 EMail: JKREY@ISI.EDUReynolds [Page 22]
[8]ページ先頭