Movatterモバイル変換

Network Working Group                                         M. KennedyRequest for Comments: 1299                                           ISICategory: Informational                                     January 1997Request for Comments Summary                         RFC Numbers 1200-1299Status of This Memo   This RFC is a slightly annotated list of the 100 RFCs fromRFC 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-KilleNov 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-KilleNov 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-KilleNov 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-KilleNov 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-KilleNov 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   SchwartzNov 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   WaldbusserNov 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   KastenholzOct 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 ProtocolThe 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'MalleyOct 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   WilliamsonSept 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   PartridgeSept 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    MalkinAug 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   HolbrookJul 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   WaldbusserJul 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   ReynoldsJun 91    Reassignment of Experimental MIBs to                           Standard MIBsThis memo specifically updatesRFC 1229,RFC 1230,RFC 1231,RFC 1232andRFC 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   IoannidisJun 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   McCloghrieMay 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 specifyan Internet standard.1226   Kantor May 91   Internet Protocol Encapsulation of AX.25 FrameThis memo describes a method for the encapsulation of AX.25 (the AmateurPacket-Radio Link-Layer Protocol) frames within IP packets.  Thistechnique is an Experimental Protocol for the Internet community.  Itdoes not specify an Internet standard.1225  Rose   May 91   Post Office Protocol - Version 3This memo suggests a simple method for workstations to dynamicallyaccess mail from a mailbox server.  [STANDARDS-TRACK]1224  SteinbergMay 91  Techniques for Managing Asynchronously                         Generated AlertsThis memo defines common mechanisms for managing asynchronously producedalerts in a manner consistent with current network management protocols.This memo specifies an Experimental Protocol for the Internet community.It does not specify an Internet standard.Kennedy                      Informational                     [Page 14]

RFC 1299                  Summary of 1200-1299              January 19971223  HalpernMay 91   OSI CLNS and LLC1 Protocols on Network Systems                        HYPERchannelThe intent of this document is to provide a complete discussion of theprotocols and techniques used to transmit OSI CLNS and LLC1 datagrams(and any associated higher level protocols) on Network SystemsCorporation's HYPERchannel equipment.This memo provides information forthe Internet community.  It does not specify an Internet standard.1222    Braun       May 91   Advancing the NSFNET Routing ArchitectureThis RFC suggests improvements in the NSFNET routing architecture toaccommodate a more flexible interface to the Backbone clients.  Thismemo provides information for the Internet community.  It does notspecify an Internet standard.1221     Edmond    Apr 91   Host Access Protocol (HAP) Specification                              - Version 2This memo describes the Host Access Protocol implemented in theTerrestrial Wideband Network (TWBNET). This memo provides informationfor the Internet community.  It does not specify an Internet standard.1220     Baker     Apr 91   Point-to-Point Protocol Extensions                              for BridgingThis document defines an extension of the Internet Point-to-PointProtocol (PPP) described inRFC 1171, targeting the use of Point-to-Point lines for Remote Bridging. [STANDARDS-TRACK]1219    Tsuchiya   Apr 91   On the Assignment of Subnet NumbersThis memo suggests a new procedure for assigning subnet numbers.  Use ofthis assignment technique within a network would be a purely localmatter, and would not effect other networks. This memo providesinformation for the Internet community.  It does not specify an Internetstandard.Kennedy                      Informational                     [Page 15]

RFC 1299                  Summary of 1200-1299              January 19971218    N.A.D.F.  Apr 91  A Naming Scheme for c=USThis RFC is a near-verbatim copy of a document, known as NADF-123, whichhas been produced by the North American Directory Forum (NADF). As apart of its charter, the NADF must reach agreement as to how entries arenamed in the public portions of the North American Directory. This memoprovides information for the Internet community.  It does not specify anInternet standard.1217   Cerf      Apr 91   Memo from the Consortium for Slow                            Commotion Research (CSCR)This RFC is in response toRFC 1216, "Gigabit Network Economics andParadigm Shifts".  This memo provides information for the Internetcommunity. It does not specify an Internet standard.1216  P.R.A.I.   Apr 91  Gigabit Network Economics and Paradigm ShiftsThis memo proposes a new standard paradigm for the Internet ActivitiesBoard (IAB) standardization track. [STANDARDS-TRACK]1215  Rose       Mar 91  A Convention for Defining Traps                           for use with the SNMPThis memo suggests a straight-forward approach towards defining trapsused with the SNMP. This memo provides information for the Internetcommunity.  It does not specify any standard.1214  Labarre    Apr 91  OSI Internet Management: Management                           Information BaseThis RFC documents a MIB for use with CMIP, either over pure OSI stacksor with the CMIP over TCP specification.  It redefines objects comprisedby the second revision of the Management Information Base for NetworkManagement of TCP/IP-based internets: MIB-II so as to conform to the OSIstructure of management information. [STANDARDS-TRACK]Kennedy                      Informational                     [Page 16]

RFC 1299                  Summary of 1200-1299              January 19971213   McCloghrieMar 91  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. [STANDARDS-TRACK]1212   Rose     Mar 91   Concise MIB DefinitionsThis memo describes a straight-forward approach toward producingconcise, yet descriptive, MIB modules. This memo defines a format forproducing MIB modules. [STANDARDS-TRACK]1211  Westine   Mar 91    Problems with the Maintenance of Large                            Mailing ListsThis RFC discusses problems with maintaining large mailing lists,especially the processing of error reports.  This memo providesinformation for the Internet community.  It does not specify an Internetstandard.1210   Cerf    Mar 91    Network and Infrastructure User                           Requirements for Transatlantic Research                           CollaborationThis report complements a shorter printed version which appeared in asummary report of all the committees which met in Brussels andWashington last July, 1990.  This memo provides information for theInternet community.  It does not specify an Internet standard.1209   Piscitello Mar 91  The Transmission of IP Datagrams over the                            SMDS ServiceThis memo defines a protocol for the transmission of IP and ARP packetsover a Switched Multi-megabit Data Service Network configured as alogical IP subnetwork. [STANDARDS-TRACK]Kennedy                      Informational                     [Page 17]

RFC 1299                  Summary of 1200-1299              January 19971208   Jacobsen   Mar 91  A Glossary of Networking TermsThis RFC is a glossary adapted from "The INTEROP Pocket Glossary ofNetworking Terms" distributed at Interop '90.  This memo providesinformation for the Internet community.  It does not specify an Internetstandard.1207   Malkin    Feb 91   FYI on Questions and Answers                            Answers to Commonly asked "Experienced                            Internet User" QuestionsThis FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A),produced by the User Services Working Group of the Internet EngineeringTask Force (IETF).  The goal is to document the most commonly askedquestions and answers in the Internet. This memo provides informationfor the Internet community.  It does not specify any standard.1206   Malkin    Feb 91   FYI on Questions and Answers                            Answers to Commonly asked "New                            Internet User" QuestionsThis FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A).The goal is to document the most commonly asked questions and answers inthe Internet. This memo provides information for the Internet community.It does not specify any standard. [FYI 4]1205   ChmielewskiFeb 91  5250 Telnet InterfaceThis RFC is being distributed in order to document the interface to theIBM 5250 Telnet implementation. This memo provides information for theInternet community.  It does not specify any standard.1204   Yeh       Feb 91   Message Posting Protocol (MPP)This memo describes a protocol for posting messages from workstations(e.g., PCs) to a mail service host.  This RFC specifies an ExperimentalProtocol for the Internet community. It does not specify any standard.Kennedy                      Informational                     [Page 18]

RFC 1299                  Summary of 1200-1299              January 19971203   Rice     Feb 91    Interactive Mail Access Protocol                            - Version 3This RFC suggests a method for workstations to access mail dynamicallyfrom a mailbox server ("repository"). The following document is amodified version ofRFC 1064, the definition of the IMAP2 protocol. ThisRFC specifies an Experimental Protocol for the Internet community. Itdoes not specify any standard.1202   Rose     Feb 91    Directory Assistance ServiceThis document defines a mechanism by which a user-interface may access atextual DAP-like interface over a TCP/IP connection.  This is a localmechanism.  This memo provides information for the Internet community.It does not specify any standard.1201   Provan  Feb 91     Transmitting IP Traffic over ARCNET                            NetworksThis memo defines a protocol for the transmission of IP and ARP packetsover the ARCnet Local Area Network.This memo specifies a method ofencapsulating Internet Protocol (IP) and Address Resolution Protocol(ARP) datagrams for transmission across ARCNET using the "ARCNET PacketHeader Definition Standard". [STANDARDS-TRACK]1200   IAB    Apr 91      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.Kennedy                      Informational                     [Page 19]

RFC 1299                  Summary of 1200-1299              January 1997Security Considerations   Security issues are not discussed in this memo.Author's Address   Mary Kennedy   University of Southern California   Information Sciences Institute   4676 Admiralty Way   Marina del Rey, CA 90292   Phone:  (310) 822-1511   EMail:  MKENNEDY@ISI.EDUKennedy                      Informational                     [Page 20]