📄 rfc1299.txt
字号:
Network Working Group M. KennedyRequest for Comments: 1299 ISICategory: Informational January 1997 Request for Comments Summary RFC Numbers 1200-1299Status of This Memo This RFC is a slightly annotated list of the 100 RFCs from RFC 1200 through RFCs 1299. This is a status report on these RFCs. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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 "Internet 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--- ------ ---- -----1299 Kennedy Jan 97 Requests For Comments SummaryThis memo.1298 Wormley Feb 92 SNMP over IPXThis memo defines a convention for encapsulating Simple NetworkManagement Protocol (SNMP) packets over the transport mechanism providedvia the Internetwork Packet Exchange (IPX) protocol. This memo providesinformation for the Internet community. It does not specify an Internetstandard.Kennedy Informational [Page 1]RFC 1299 Summary of 1200-1299 January 19971297 Johnson Jan 92 NOC Internal Integrated Trouble Ticket System Functional Specification WishlistThis document explores competing uses, architectures, and desirablefeatures of integrated internal trouble ticket systems for Network andother Operations Centers. This memo provides information for theInternet community. It does not specify an Internet standard.1296 Lottor Jan 92 Internet Growth (1981-1991)This document illustrates the growth of the Internet by examination ofentries in the Domain Name System (DNS) and pre-DNS host tables. Thismemo provides information for the Internet community. It does notspecify an Internet standard.1295 N.A.D.F. Jan 92 User Bill of Rights for entries and listings in the Public DirectoryThis RFC is a near-verbatim copy of a document, known as NADF-265, whichhas been produced by the North American Directory Forum (NADF). Thismemo provides information for the Internet community. It does notspecify an Internet standard.1294 Bradley Jan 92 Multiprotocol Interconnect over Frame RelayThis memo describes an encapsulation method for carrying networkinterconnect traffic over a Frame Relay backbone. It covers aspects ofboth Bridging and Routing. [STANDARDS-TRACK]1293 Bradley Jan 92 Inverse Address Resolution ProtocolThis memo describes additions to ARP that will allow a station torequest a protocol address corresponding to a given hardware address.[STANDARDS-TRACK]Kennedy Informational [Page 2]RFC 1299 Summary of 1200-1299 January 19971292 Lang Jan 92 A Catalog of Available X.500 ImplementationsThe goal of this document is to provide information regarding theavailability and capability of implementations of X.500. This memoprovides information for the Internet community. It does not specify anInternet standard.1291 Aggarwal Dec 91 Mid-Level Networks Potential Technical ServicesThis document proposes a set of technical services that each Internetmid-level network can offer within the mid-level network itself and andto its peer networks. This RFC provides information for the Internetcommunity. It does not specify an Internet standard.1290 Martin Dec 91 There's Gold in them thar Networks! or Searching for Treasure in all the Wrong PlacesThis paper will present some of the "gold nuggets" of information andfile repositories on the network that could be of use to end users. ThisRFC provides information for the Internet community. It does not specifyan Internet standard.1289 Saperia Dec 91 DECnet Phase IV MIB ExtensionsThis memo is an extension to the SNMP MIB. This memo defines a set ofDECnet Phase IV extensions that have been created for the Internet MIB.[STANDARDS-TRACK]1288 Zimmerman Dec 91 The Finger User Informational ProtocolThis memo describes the Finger user information protocol.This is asimple protocol which provides an interface to a remote user informationprogram. [STANDARDS-TRACK]1287 Clark Dec 91 Towards the Future Internet ArchitectureThis informational RFC discusses important directions for possiblefuture evolution of the Internet architecture, and suggests stepstowards the desired goals. This memo provides information for theInternet community. It does not specify an Internet standard.Kennedy Informational [Page 3]RFC 1299 Summary of 1200-1299 January 19971286 Decker Dec 91 Definitions of Managed Objects for BridgesThis 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 bridges based on the IEEE802.1d draft standard between Local Area Network (LAN) segments. Thismemo is an extension to the SNMP MIB. [STANDARDS-TRACK]1285 Case Jan 92 FDDI 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 devices which implement theFDDI. [STANDARDS-TRACK]1284 Cook Dec 91 Definitions of Managed Objects for the Ethernet-like Interface TypesThis 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 ethernet-like objects.[STANDARDS-TRACK]1283 Rose Dec 91 SNMP over OSIThis memo describes mappings from the SNMP onto both the COTS and theCLTS. This memo defines an Experimental Protocol for the Internetcommunity. It does not specify an Internet Standard.1282 Kantor Dec 91 BSD RloginThis memo documents an existing protocol and common implementation thatis extensively used on the Internet. This memo provides information forthe Internet community. It does not specify an Internet standard.1281 Pethia Nov 91 Guidelines for the Secure Operation of the InternetThe purpose of this document is to provide a set of guidelines to aid inthe secure operation of the Internet. This memo provides information forthe Internet community. It does not specify an Internet standard.Kennedy Informational [Page 4]RFC 1299 Summary of 1200-1299 January 19971280 IAB Mar 92 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.1279 Hardcastle-Kille Nov 91 X.500 and DomainsThis RFC considers X.500 in relation to Internet and UK Domains. Thismemo defines an Experimental Protocol for the Internet community. Itdoes not specify an Internet standard.1278 Hardcastle-Kille Nov 91 A string encoding of Presentation AddressThere are a number of environments where a simple string encoding ofPresentation Address is desirable. This specification defines such arepresentation. This memo provides information for the Internetcommunity. It does not specify an Internet standard.1277 Hardcastle-Kille Nov 91 Encoding Network Addresses to support operation over non-OSI lower layersThis document defines a new network address format, and rules for usingsome existing network address formats. [STANDARDS-TRACK]1276 Hardcastle-Kille Nov 91 Replication and Distributed Operations extensions to provide an Internet Directory using X.500Some requirements on extensions to X.500 are described in theRFC[HK91b], in order to build an Internet Directory using X.500(1988).This document specifies a set of solutions to the problems raised.[STANDARDS-TRACK]Kennedy Informational [Page 5]RFC 1299 Summary of 1200-1299 January 19971275 Hardcastle-Kille Nov 91 Replication Requirements to provide an Internet Directory using X.500This RFC considers certain deficiencies of the 1988 X.500 standard,which need to be addressed before an effective open Internet Directorycan be established using these protocols and services [CCI88]. This memoprovides information for the Internet community. It does not specify anInternet standard.1274 Barker Nov 91 The COSINE and Internet X.500 SchemaThis document suggests an X.500 Directory Schema, or NamingArchitecture, for use in the COSINE and Internet X.500 pilots.[STANDARDS-TRACK]1273 Schwartz Nov 91 A Measurement Study of Changes in Service-Level Reachability in the Global TCP/IP Internet: Goals, Experimental Design, Implementation, and Policy ConsiderationsThis memo describes plans to carry out a longitudinal measurement studyof changes in service-level reachability in the global TCP/IP Internet.This memo provides information for the Internet community. It does notspecify an Internet standard.1272 Mills Nov 91 Internet Accounting: BackgroundThis document provides background information for the "InternetAccounting Architecture". This memo provides information for theInternet community. It does not specify an Internet standard.1271 Waldbusser Nov 91 Remote Network Monitoring 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 remote network monitoringdevices. [STANDARDS-TRACK]Kennedy Informational [Page 6]RFC 1299 Summary of 1200-1299 January 19971270 Kastenholz Oct 91 SNMP Communications ServicesThis document discusses various issues to be considered when determiningthe underlying communications services to be used by an SNMPimplementation. This memo provides information for the Internetcommunity. It does not specify an Internet standard.1269 Willis Oct 91 Definitions of Managed Objects for the Border Gateway Protocol (Version 3)This 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 the Border Gateway Protocol.[STANDARDS-TRACK]1268 Rekhter Oct 91 Application of the Border Gateway Protocol in the InternetThis document describes the usage of the BGP in the Internet.[STANDARDS-TRACK]1267 Lougheed Oct 91 A Border Gateway Protocol 3 (BGP-3)This memo, together with its companion document, "Application of theBorder Gateway Protocol in the Internet", define an inter-autonomoussystem routing protocol for the Internet. [STANDARDS-TRACK]1266 Rekhter Oct 91 Experience with the BGP Protocol
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -