📄 rfc1199.txt
字号:
Network Working Group J. ReynoldsRequest for Comments: 1199 ISI December 1991 Request for Comments Summary RFC Numbers 1100-1199Status of This Memo This RFC is a slightly annotated list of the 100 RFCs from RFC 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 on RFC 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 on RFC 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 obsoletes RFC 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"). Itobosoletes RFC 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
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -