📄 rfc1199.txt
字号:
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 Kirkpatrick Jul 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 companion RFC-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 companion RFC-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 of RFC 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 of RFC 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 of RFC 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 from RFC 1066. [STANDARDS-TRACK]1155 Rose May 90 Structure and Identification of Management Information for TCP/IP-based InternetsThis RFC is a re-release of RFC 1065, with a changed "Status of thisMemo", plus a few minor typographical corrections. The technicalcontent of the document is unchanged from RFC 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 updates RFC 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) in RFC-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 and RFC 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]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -