📄 rfc1299.txt
字号:
The purpose of this memo is to document how the requirements foradvancing a routing protocol to Draft Standard have been satisfied byBorder Gateway Protocol (BGP). This memo provides information for theInternet community. It does not specify an Internet standard.1265 Rekhter Oct 91 BGP Protocol AnalysisThis report summarizes the key feature of BGP, and analyzes the protocolwith respect to scaling and performance. This memo provides informationfor the Internet community. It does not specify an Internet standard.Kennedy Informational [Page 7]RFC 1299 Summary of 1200-1299 January 19971264 Hinden Oct 91 Internet Engineering Task Force Internet Routing Protocol Standardization CriteriaThis informational RFC presents procedures for creating and documentingInternet standards on routing protocols. These procedures have beenestablished by the Internet Activities Board (IAB) in consultation withthe Internet Engineering Steering Group (IESG). This memo providesinformation for the Internet community. It does not specifiy an Internetstandard.1263 O'Malley Oct 91 TCP Extensions Considered HarmfulThis RFC comments on recent proposals to extend TCP. It argues that thebackward compatible extensions proposed in RFC's 1072 and 1185 shouldnot be pursued, and proposes an alternative way to evolve the Internetprotocol suite. This memo provides information for the Internetcommunity. It does not specify an Internet standard.1262 IAB Oct 91 Guidelines for Internet Measurement ActivitiesThis RFC represents IAB guidance for researchers considering measurementexperiments on the Internet. This memo provides information for theInternet community. It does not specify an Internet standard.1261 Williamson Sept 91 Transition of NIC ServicesThis memo outlines the transition of NIC Services. This memo providesinformation for the Internet community. It does not specify an Internetstandard.1260 Never issued.1259 Kapor Sept 91 Building The Open Road: The NREN As Test-Bed For The National Public NetworkThis memo discusses the background and importance of NREN. This memoprovides information for the Internet community. It does not specify anInternet standard.Kennedy Informational [Page 8]RFC 1299 Summary of 1200-1299 January 19971258 Kantor Sept 91 BSD RloginThe rlogin facility provides a remote-echoed, locally flow-controlledvirtual terminal with proper flushing of output.This memo documents anexisting protocol and common implementation that is extensively used onthe Internet. This memo provides information for the Internetcommunity. It does not specify an Internet standard.1257 Partridge Sept 91 Isochronous Applications Do Not Require Jitter-Controlled NetworksThis memo argues that jitter control is not required for networks tosupport isochronous applications. This memo provides information for theInternet community. It does not specify an Internet standard.1256 Deering Sept 91 ICMP Router Discovery MessagesThis document specifies an extension of the Internet Control MessageProtocol (ICMP) to enable hosts attached to multicast or broadcastnetworks to discover the IP addresses of their neighboring routers.[STANDARDS-TRACK]1255 N.A.D.F. Sept 91 A Naming Scheme for c=USThis memo documents the NADF's agreement as to how entries are named inthe public portions of the North American Directory. This memo providesinformation for the Internet community. It does not specify an Internetstandard.1254 Mankin Aug 91 Gateway Congestion Control SurveyThe purpose of this paper is to present a review of the congestioncontrol approaches, as a way of encouraging new discussion andexperimentation. Included in the survey are Source Quench, Random Drop,Congestion Indication (DEC Bit), and Fair Queueing.1253 Baker Aug 91 OSPF Version 2 Management Information BaseThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets. Inparticular, it defines objects for managing OSPF Version 2. [STANDARDS-TRACK]Kennedy Informational [Page 9]RFC 1299 Summary of 1200-1299 January 19971252 Baker Aug 91 OSPF Version 2 Management Information BaseThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets. Inparticular, it defines objects for managing OSPF Version 2. [STANDARDS-TRACK]1251 Malkin Aug 91 Who's Who in the Internet Biographies of IAB, IESG and IRSG MembersThis FYI RFC contains biographical information about members of theInternet Activities Board (IAB), the Internet Engineering Steering Group(IESG) of the Internet Engineering Task Force (IETF), and the theInternet Research Steering Group (IRSG) of the Internet Research TaskForce (IRTF). This memo provides information for the Internet community.It does not specify an Internet standard. [FYI 9]1250 IAB Aug 91 IAB Official Protocol StandardsThis memo describes the state of standardization of protocols used inthe Internet as determined by the Internet Activities Board (IAB). Thismemo provides information for the Internet community. It does notspecify an Internet standard.1249 Howes Aug 91 DIXIE Protocol SpecificationThis RFC defines a mechanism by which TCP/UDP based clients can accessOSI Directory Service without the overhead of the ISO transport andpresentation protocols required to implement full-blown DAP. This memoprovides information for the Internet community. It does not specifyany standard.1248 Baker Jul 91 OSPF Version 2 Management Information BaseThis memo defines an experimental portion of the Management InformationBase (MIB) for use with network management protocols in TCP/IP-basedinternets. In particular, it defines objects for managing OSPF Version2. [STANDARDS-TRACK]1247 Moy Jul 91 OSPF Version 2This memo documents version 2 of the OSPF protocol. OSPF is a link-state based routing protocol. [STANDARDS-TRACK]Kennedy Informational [Page 10]RFC 1299 Summary of 1200-1299 January 19971246 Moy Jul 91 Experience with the OSPF protocolThis report documents experience with OSPF V2. This includes reports oninteroperability testing, field experience, simulations and the currentstate of OSPF implementations. This memo provides information for theInternet community. It does not specify any Internet standard.1245 Moy Jul 91 OSPF protocol analysisThis report attempts to summarize the key features of OSPF V2. It alsoattempts to analyze how the protocol will perform and scale in theInternet. This memo provides information for the Internet community. Itdoes not specify any Internet standard.1244 Holbrook Jul 91 Site Security HandbookThis FYI RFC is a first attempt at providing Internet users guidance onhow to deal with security issues in the Internet. This FYI RFC providesinformation for the Internet community. It does not specify an Internetstandard. [FYI 8]1243 Waldbusser Jul 91 AppleTalk Management Information BaseThis memo defines objects for managing AppleTalk objects for use withthe SNMP protocol. [STANDARDS-TRACK]1242 Bradner Jul 91 Benchmarking Terminology for Network Interconnection DevicesThis memo discusses and defines a number of terms that are used indescribing performance benchmarking tests and the results of such tests.This memo provides information for the Internet community. It does notspecify an Internet standard.1241 Woodburn Jul 91 A Scheme for an Internet Encapsulation Protocol: Version 1This memo defines an Experimental Protocol for the Internet community.It does not specify an Internet standard.Kennedy Informational [Page 11]RFC 1299 Summary of 1200-1299 January 19971240 Shue Jun 91 OSI Connectionless Transport Services on top of UDP Version: 1This document describes a protocol for running OSI Connectionlessservice on UDP. [STANDARDS-TRACK]1239 Reynolds Jun 91 Reassignment of Experimental MIBs to Standard MIBsThis memo specifically updates RFC 1229, RFC 1230, RFC 1231, RFC 1232and RFC 1233 with new codes. [STANDARDS-TRACK]1238 Satz Jun 91 CLNS MIB for use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542)This memo defines an experimental portion of the Management InformationBase (MIB) for use with network management protocols in TCP/IP-basedinternets. This is an Experimental Protocol for the Internet community.It does not specify an Internet standard.1237 Colella Jul 91 Guidelines for OSI NSAP Allocation in the InternetThis paper provides guidelines for allocating NSAPs in theInternet.[STANDARDS-TRACK]1236 Morales Jun 91 IP to X.121 Address Mapping for DDN A Model for Routing in the InternetThis memo defines a standard way of converting IP addresses to CCITTX.121 addresses and is the recommended standard for use on the Internet,specifically for the Defense Data Network (DDN). This memo providesinformation for the Internet community. It does not specify an Internetstandard.1235 Ioannidis Jun 91 The Coherent File Distribution ProtocolThis memo describes the Coherent File Distribution Protocol (CFDP).This is an Experimental Protocol for the Internet community. It does notspecify an Internet standard.Kennedy Informational [Page 12]RFC 1299 Summary of 1200-1299 January 19971234 Provan Jun 91 Tunneling IPX Traffic through IP NetworksThis memo describes a method of encapsulating IPX datagrams within UDPpackets so that IPX traffic can travel across an IP internet.[STANDARDS-TRACK]1233 Cox May 91 Definitions of Managed Objects for the DS3 Interface TypeThis memo defines objects for managing DS3 Interface objects for usewith the SNMP protocol. [STANDARDS-TRACK]1234 Baker May 91 Definitions of Managed Objects for the DS1 Interface TypeThis memo defines objects for managing DS1 Interface objects for usewith the SNMP protocol. [STANDARDS-TRACK]1231 McCloghrie May 91 IEEE 802.5 Token Ring MIBThis memo defines an experimental portion of the Management InformationBase (MIB) for use with network management protocols in TCP/IP-basedinternets. In particular, this memo defines managed objects used formanaging subnetworks which use the IEEE 802.5 Token Ring technologydescribed in 802.5 Token Ring Access Method and Physical LayerSpecifications, IEEE Standard 802.5-1989. [STANDARDS-TRACK]1230 McCloghrie May 91 IEEE 802.4 Token Bus MIBThis memo defines an experimental portion of the Management InformationBase (MIB) for use with network management protocols in TCP/IP-basedinternets. In particular, this memo defines managed objects used formanaging subnetworks which use the IEEE 802.4 Token Bus technologydescribed in 802.4 Token-Passing Bus Access Method and Physical LayerSpecifications, IEEE Standard 802.4. [STANDARDS-TRACK]1229 McCloghrie May 91 Extensions to the Generic-Interface MIBThis RFC contains definitions of managed objects used as experimentalextensions to the generic interfaces structure of MIB-II. [STANDARDS-TRACK]Kennedy Informational [Page 13]RFC 1299 Summary of 1200-1299 January 19971228 Carpenter May 91 Simple Network Management Protocol Distributed Program InterfaceThis RFC describes a protocol that International Business MachinesCorporation (IBM) has been implementing in most of its SNMP agents toallow dynamic extension of supported MIBs. This is an ExperimentalProtocol for the Internet community. It does not specify an Internetstandard.1227 Rose May 91 SNMP MUX Protocol and MIBThis memo suggests a mechanism by which a user process may associateitself with the local SNMP agent on a host, in order to implementportions of the MIB. This mechanism would be local to the host.This isan Experimental Protocol for the Internet community. It does not specify
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -