Movatterモバイル変換

Network Working Group                                        J. ReynoldsRequest for Comments: 1099                                           ISI                                                           December 1991Request for Comments Summary                         RFC Numbers 1000-1099Status of This Memo   This memo is a slightly annotated list of the 100 RFCs fromRFC 1000   through RFCs 1099.  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.RFC     Author       Date      Title---     ------       ----      -----1099    Reynolds   Dec 91    Requests For Comments SummaryThis memo.1098    Case       Apr 89    A Simple Network Management                               Protocol (SNMP)This RFC is a re-release ofRFC 1067, with a changed "Status of thisMemo" section.  This memo defines a simple protocol by which managementinformation for a network element may be inspected or altered bylogically remote users.  In particular, together with its companionmemos which describe the structure of management information along withthe initial management information base, these documents provide asimple, workable architecture and system for managing TCP/IP-basedinternets and in particular the Internet.1097    Miller     Apr 89    Telnet Subliminal-Message OptionThis RFC specifies a standard for the Internet community.  Hosts on theInternet that display subliminal messages within the Telnet protocol areexpected to adopt and implement this standard.1096    Marcy      Mar 89    Telnet X Display Location OptionThis RFC specifies a standard for the Internet community.  Hosts on theInternet that transmit the X display location within the Telnet protocolReynolds                                                        [Page 1]

RFC 1099                  Summary of 1000-1099             December 1991are expected to adopt and implement this standard.1095    Warrier    Apr 89    The Common Management Information                               Services and Protocol over TCP/IP                               (CMOT)This memo defines a network management architecture that uses theInternational Organization for Standardization's (ISO) Common ManagementInformation Services/Common Management Information Protocol (CMIS/CMIP)in a TCP/IP environment.  This architecture provides a means by whichcontrol and monitoring information can be exchanged between a managerand a remote network element.  In particular, this memo defines themeans for implementing the Draft International Standard (DIS) version ofCMIS/CMIP on top of Internet transport protocols for the purpose ofcarrying management information defined in the Internet-standardmanagement information base.  DIS CMIS/CMIP is suitable for deploymentin TCP/IP networks while CMIS/CMIP moves toward becoming anInternational Standard.  Together with the relevant ISO standards andthe companion RFCs that describe the initial structure of managementinformation and management information base, these documents provide thebasis for a comprehensive architecture and system for managing TCP/IP-based internets, and in particular the Internet.1094    Sun        Mar 89    NFS: Network File System                               Protocol SpecificationThis RFC describes a protocol that Sun Microsystems, Inc., and othersare using.  A new version of the protocol is under development, butothers may benefit from the descriptions of the current protocol, anddiscussion of some of the design issues.1093    Braun      Feb 89    The NSFNET Routing ArchitectureThis document describes the routing architecture for the NSFNET centeredaround the new NSFNET Backbone, with specific emphasis on the interfacebetween the backbone and its attached networks.1092    Rekhter    Feb 89    EGP and Policy Based Routing                               in the New NSFNET BackboneThis memo discusses implementation decisions for routing issues in theNSFNET, especially in the NSFNET Backbone.  Of special concern is therestriction of routing information to advertize the best route asestablished by a policy decision.Reynolds                                                        [Page 2]

RFC 1099                  Summary of 1000-1099             December 19911091    VanBokkelenFeb 89    Telnet Terminal-Type OptionThis RFC specifies a standard for the Internet community.  Hosts on theInternet that exchange terminal type information within the Telnetprotocol are expected to adopt and implement this standard.This standard supersedesRFC 930.  A change is made to permit cyclingthrough a list of possible terminal types and selecting the mostappropriate1090    Ullmann    Feb 89    SMTP on X.25This memo proposes a standard for SMTP on the virtual circuit facilityprovided by the X.25 standard of the CCITT.1089    SchoffstallFeb 89    SNMP over EthernetThis memo describes an experimental method by which the Simple NetworkManagement Protocol (SNMP) can be used over Ethernet MAC layer framinginstead of the Internet UDP/IP protocol stack.  This specification isuseful for LAN based network elements that support no higher layerprotocols beyond the MAC sub-layer.1088    McLaughlin Feb 89    A Standard for the Transmission of IP                               Datagrams over NetBIOS NetworksThis document specifies a standard method of encapsulating the InternetProtocol (IP) datagrams on NetBIOS networks.1087    IAB        Jan 89    Ethics and the InternetThis memo is a statement of policy by the Internet Activities Board(IAB) concerning the proper use of the resources of the Internet.1086    Onions     Dec 88    ISO-TP0 bridge between TCP and X.25This memo proposes a standard for the Internet community.  Hosts on theInternet that choose to implement ISO TP0 transport connectivity betweenTCP and X.25 based hosts are expected to experiment with this proposal.TCP port 146 is reserved for this proposal.Reynolds                                                        [Page 3]

RFC 1099                  Summary of 1000-1099             December 19911085    Rose       Dec 88    ISO Presentation Services                               on top of TCP/IP-based internetsRFC 1006 describes a mechanism for providing the ISO transport serviceon top of TCP/IP.  Once this method is applied, one may implement "real"ISO applications on top of TCP/IP-based internets, by simplyimplementing OSI session, presentation, and application services on topof the transport service access point which is provided on top of theTCP.  Although straight-forward, there are some environments in whichthe richness provided by the OSI application layer is desired, but it isnonetheless impractical to implement the underlying OSI infrastructure(i.e., the presentation, session, and transport services on top of theTCP).This memo describes an approach for providing "stream-lined" support ofOSI application services on top of TCP/IP-based internets for suchconstrained environments.  This memo proposes a standard for theInternet community.1084    Reynolds   Dec 88      BOOTP Vendor Information ExtensionsThis RFC is a slight revision and extension ofRFC-1048 by PhilipPrindeville.  This memo will be updated as additional tags are aredefined.  This edition introduces Tag 13 for Boot File Size.  Commentsand suggestions for improvements are sought.1083    IAB        Dec 88      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.This memo is issued quarterly, please be sure the copy you are readingis dated within the last three months.1082    Rose       Nov 88      Post Office Protocol - Version 3                                 Extended Service OfferingsThis memo suggests a simple method for workstations to dynamicallyaccess mail from a discussion group server, as an extension to anearlier memo which dealt with dynamically accessing mail from a mailboxReynolds                                                        [Page 4]

RFC 1099                  Summary of 1000-1099             December 1991server using the Post Office Protocol - Version 3 (POP3).  This RFCspecifies a proposed protocol for the Internet community, and requestsdiscussion and suggestions for improvements.  All of the extensionsdescribed in this memo to the POP3 are OPTIONAL.1081    Rose       Nov 88      Post Office Protocol - Version 3This memo suggests a simple method for workstations to dynamicallyaccess mail from a mailbox server.  This RFC specifies a proposedprotocol for the Internet community, and requests discussion andsuggestions for improvements.1080    Hedrick    Dec 88      Telnet Remote Flow Control OptionThis RFC specifies a standard for the Internet community.  Hosts on theInternet that do remote flow control within the Telnet protocol areexpected to adopt and implement this standard.1079    Hedrick    Dec 88      Telnet Terminal Speed OptionThis RFC specifies a standard for the Internet community.  Hosts on theInternet that exchange terminal speed information within the Telnetprotocol are expected to adopt and implement this standard.1078    Lottor     Nov 88      TCP Port Service Multiplexer (TCPMUX)This RFC proposes an Internet standard which can be used by future TCPservices instead of using 'well-known ports'.1077    Leiner     Nov 88      Critical Issues in High Bandwidth                                 NetworkingThis memo presents the results of a working group on High BandwidthNetworking.  This RFC is for your information and you are encouraged tocomment on the issues presented.1076    Trewitt    Nov 88      HEMS Monitoring and Control LanguageThis RFC specifies a query language for monitoring and control ofnetwork entities.  This RFC supercedesRFC 1023, extending the querylanguage and providing more discussion of the underlying issues.Reynolds                                                        [Page 5]

RFC 1099                  Summary of 1000-1099             December 1991This language is a component of the High-Level Entity Monitoring System(HEMS) described inRFC 1021 andRFC 1022.  Readers may wish to consultthese RFCs when reading this memo.RFC 1024 contains detailedassignments of numbers and structures used in this system.  Portions ofRFC 1024 that define query language structures are superceded bydefinitions in this memo.  This memo assumes a knowledge of the ISO dataencoding standard, ASN.1.1075    Waitzman   Nov 88      Distance Vector Multicast Routing                                 ProtocolThis RFC describes a distance-vector-style routing protocol for routingmulticast datagrams through an internet.  It is derived from the RoutingInformation Protocol (RIP), and implements multicasting as described inRFC-1054.  This is an experimental protocol, and its implementation isnot recommended at this time.1074    Rekhter    Oct 88      The NSFNET Backbone SPF based Interior                                 Gateway ProtocolThis RFC is an implementation description of the standard ANSI IS-IS andISO ES-IS routing protocols within the NSFNET backbone network.1073    Waitzman   Oct 88      Telnet Window Size OptionThis RFC describes a proposed Telnet option to allow a client to conveywindow size to a Telnet server.1072    Jacobson   Oct 88      TCP Extensions for Long-Delay PathsThis RFC proposes a set of extensions to the TCP protocol to provideefficient operation over a path with a high bandwidth*delay product.These extensions are not proposed as an Internet standard at this time.Instead, they are intended as a basis for further experimentation andresearch on transport protocol performance.1071    Braden     Aug 88      Computing the Internet ChecksumThis RFC summarizes techniques and algorithms for efficiently computingthe Internet checksum.  It is not a standard, but a set of usefulimplementation techniques.Reynolds                                                        [Page 6]

RFC 1099                  Summary of 1000-1099             December 19911070    Hagens     Feb 89      Use of the Internet as a Subnetwork                                 for Experimentation with the OSI                                 Network LayerThis RFC proposes a scenario for experimentation with the InternationalOrganization for Standardization (ISO) Open Systems Interconnection(OSI) network layer protocols over the Internet and requests discussionand suggestions for improvements to this scenario.  This RFC alsoproposes the creation of an experimental OSI internet.  To participatein the experimental OSI internet, a system must abide by the agreementsset forth in this RFC.1069    Callon     Feb 89      Guidelines for the use of Internet-IP                                 addresses in the ISO Connectionless-                                 Mode Network ProtocolThis RFC suggests an addressing scheme for use with the ISOConnectionless Network Protocol (CLNP) in the Internet.  This is asolution to one of the problems inherent in the use of "ISO-grams" inthe Internet.  This memo is a revision ofRFC 986.  This RFC suggests aproposed protocol for the Internet community, and requests discussionand suggestions for improvements.1068    DeSchon    Aug 88      Background File Transfer Program                                 (BFTP)This RFC describes an Internet background file transfer service that isbuilt upon the third-party transfer model of FTP.  No new protocols areinvolved.  The purpose of this memo is to stimulate discussions on newInternet service modes.1067    Case       Aug 88      A Simple Network Management ProtocolThis RFC defines a simple protocol by which management information for anetwork element may be inspected or altered by logically remote users.In particular, together with its companion memos which describe thestructure of management information along with the initial managementinformation base, these documents provide a simple, workablearchitecture and system for managing TCP/IP-based internets and inparticular, the Internet.This memo specifies a draft standard for the Internet community. TCP/IPimplementations in the Internet which are network manageable areexpected to adopt and implement this specification.Reynolds                                                        [Page 7]

RFC 1099                  Summary of 1000-1099             December 19911066    McCloghrie  Aug 88      Management Information Base for Network                                  Management of TCP/IP-based internetsThis RFC provides the initial version of the Management Information Base(MIB) for use with network management protocols in TCP/IP-basedinternets in the short-term.  In particular, together with its companionmemos which describe the structure of management information along withthe initial network management protocol, these documents provide asimple, workable architecture and system for managing TCP/IP-basedinternets, and in particular, the Internet.This memo specifies a draft standard for the Internet community.  TCP/IPimplementations in the Internet which are network manageable areexpected to adopt and implement this specification.1065    Rose        Aug 88      Structure and Identification of                                  Management Information for                                  TCP/IP-based internetsThis RFC provides the common definitions for the structure andidentification of management information for TCP/IP-based internets.  Inparticular, together with its companion memos, which describe theinitial management information base along with the initial networkmanagement protocol, these documents provide a simple, workingarchitecture and system for managing TCP/IP-based internets and inparticular, the Internet.This memo specifies a draft standard for the Internet community.  TCP/IPimplementation in the Internet which are network manageable are expectedto adopt and implement this specification.1064    Crispin     Jul 88      Interactive Mail Access Protocol -                                  Version 2This memo suggests a method for workstations to dynamically access mailfrom a mailbox server ("respository").  This RFC specifies a standardfor the SUMEX-AIM community and a proposed experimental protocol for theInternet community.  Discussion and suggestions for improvement arerequested.1063    Mogul       Jul 88      IP MTU Discovery OptionsA pair of IP options that can be used to learn the minimum MTU of a paththrough an internet is described, along with its possible uses.  This isa proposal for an Experimental protocol.Reynolds                                                        [Page 8]

RFC 1099                  Summary of 1000-1099             December 19911062    Romano      Aug 88      Internet NumbersThis memo is an official status report on the network numbers andgateway autonomous system numbers used in the Internet community.1061    Never issued.1060    Reynolds    Mar 90      Assigned NumbersThis memo is a status report on the parameters (i.e., numbers andkeywords) used in protocols in the Internet community.  Distribution ofthis memo is unlimited.1059    Mills       Jul 88      Network Time Protocol (Version 1)                                  Specification and ImplementationThis memo describes the Network Time Protocol (NTP), specifies itsformal structure and summarizes information useful for itsimplementation.  NTP provides the mechanisms to synchronize time andcoordinate time distribution in a large, diverse internet operating atrates from mundane to lightwave.  It uses a returnable-time design inwhich a distributed subnet of time servers operating in a self-organizing, hierarchical master-slave configuration synchronizes logicalclocks within the subnet and to national time standards via wire orradio.  The servers can also redistribute reference time via localrouting algorithms and time daemons.The NTP architectures, algorithms and protocols which have evolved overseveral years of implementation and refinement are described in thisdocument.  The prototype system, which has been in regular operation inthe Internet for the last two years, is described in an Appendix alongwith performance data which shows that timekeeping accuracy throughoutmost portions of the Internet can be ordinarily maintained to within afew tens of milliseconds, even the cases of failure or disruption ofclocks, time servers or nets. This is a Draft Standard for an Electiveprotocol.1058    Hedrick     Jun 88      Routing Information ProtocolThis RFC describes an existing protocol for exchanging routinginformation among gateways and other hosts.  It is intended to be usedas a basis for developing gateway software for use in the Internetcommunity.Reynolds                                                        [Page 9]

RFC 1099                  Summary of 1000-1099             December 19911057    Sun         Jun 88       RPC: Remote Procedure Call Protocol                                   Specification Version 2This RFC describes a standard that Sun Microsystems and others areusing, and is one we wish to propose for the Internet's consideration.This memo is not an Internet standard at this time.1056    Lambert     Jun 88   PCMAIL: A Distributed Mail System                               for Personal ComputersThis memo is a discussion of the Pcmail workstation based distributedmail system.  It is identical to the discussion inRFC-993, save that anew, much simpler mail transport protocol is described.  The newtransport protocol is the result of continued research into ease ofprotocol implementation and use issues.1055    Romkey       Jun 88    A Nonstandard for Transmission of                                 IP Datagrams over Serial Lines: SLIPThe TCP/IP protocol family runs over a variety of network media: IEEE802.3 (ethernet) and 802.5 (token ring) LAN's, X.25 lines, satellitelinks, and serial lines.  There are standard encapsulations for IPpackets defined for many of these networks, but there is no standard forserial lines.  SLIP, Serial Line IP, is a currently a de facto standard,commonly used for point-to-point serial connections running TCP/IP.  Itis not an Internet standard.1054    Deering      May 88      Host Extensions for IP MulticastingThis memo specifies the extensions required of a host implementation ofthe Internet Protocol (IP) to support multicasting.  IP multicasting isthe transmission of an IP datagram to a "host group", a set hostsidentified by a single IP destination address.  A multicast datagram isdelivered to all members of its destination host group with the same"best-efforts" reliability as regular unicast IP datagrams.  It isproposed as a standard for IP multicasting in the Internet.  Thisspecification is a major revision ofRFC-988.1053    Levy         Apr 88       Telnet X.3 PAD OptionThis RFC proposes a new option to Telnet for the Internet community, andrequests discussion and suggestions for improvements.Reynolds                                                       [Page 10]

RFC 1099                  Summary of 1000-1099             December 19911052    Cerf         Apr 88      IAB Recommendations for the                                   Development of Internet Network                                   Management StandardsThis RFC is intended to convey to the Internet community and otherinterested parties the recommendations of the Internet Activities Board(IAB) for the development of network management protocols for use in theTCP/IP environment.  This memo does NOT, in and of itself, define orpropose an Official Internet Protocol.  It does reflect, however, thepolicy of the IAB with respect to further network management developmentin the short and long term.1051    Prindeville   Mar 88     A Standard for the Transmission of IP                                   Datagrams and ARP Packets over ARCNET                                   NetworksThis memo specifies a standard method of encapsulating Internet Protocol(IP) and Address Resolution Protocol (ARP) datagrams on an ARCNET.  ThisRFC is a standard protocol for the Internet community.1050    Sun           Apr 88      RPC: Remote Procedure Call                                    Protocol SpecificationThis memo specifies a message protocol used in implementing Sun's RemoteProcedure Call (RPC) package.  This RFC describes a standard that SunMicrosystems and others are using and is one they wish to propose forthe Internet's consideration.  It is not an Internet standard at thistime.1049    Sirbu         Mar 88      A Content-Type Header Field for                                    Internet MessagesThis memo suggests proposed additions to the Internet Mail Protocol,RFC-822, for the Internet community, and requests discussion andsuggestions for improvements.1048    Prindeville   Feb 88      BOOTP Vendor Information ExtensionsThis memo proposes an addition to the Bootstrap Protocol (BOOTP).Comments and suggestions for improvements are sought.Reynolds                                                       [Page 11]

RFC 1099                  Summary of 1000-1099             December 19911047    Partridge     Feb 88      Duplicate Messages and SMTPAn examination of a synchronization problem in the Simple Mail TransferProtocol (SMTP) is presented.  This synchronization problem can cause amessage to be delivered multiple times.  A method for avoiding thisproblem is suggested.  Nodding familiarity with the SMTP specification,RFC-821, is required.1046    Prue          Feb 88      A Queuing Algorithm to Provide                                    Type-of-Service for IP LinksThis memo is intended to explore how Type-of-Service might beimplemented in the Internet.  The proposal describes a method of queuingwhich can provide the different classes of service.  The technique alsoprohibits one class of service from consuming excessive resources orexcluding other classes of service.  This is an "idea paper" anddiscussion is strongly encouraged.1045    Cheriton      Feb 88      VMTP: Versatile Message Transaction                                    Protocol Protocol SpecificationThis memo specifies the Versatile Message Transaction Protocol (VMTP)[Version 0.7 of 19-Feb-88], a transport protocol specifically designedto support the transaction model of communication, as exemplified byremote procedure call (RPC).  The full function of VMTP, includingsupport for security, real-time, asynchronous message exchanges,streaming, multicast and idempotency, provides a rich selection to theVMTP user level.  Subsettability allows the VMTP module for particularclients and servers to be specialized and simplified to the servicesactually required.  Examples of such simple clients and servers includePROM network bootload programs, network boot servers, data sensors andsimple controllers, to mention but a few examples.  This RFC describes aprotocol proposed as a standard for the Internet community.1044    Hardwick      Feb 88      Internet Protocol on Network Systems                                    HYPERchannel Protocol SpecificationThis memo intends to provide a complete discussion of the protocols andtechniques used to embed DoD standard Internet Protocol datagrams (andits associated higher level protocols) on Network Systems Corporation'sHYPERchannel equipment.  This document is directed toward networkplanners and implementors who are already familiar with the TCP/IPprotocol suite and the techniques used to carry TCP/IP traffic on commonnetworks such as the DDN or the Ethernet.  No great familiarity with NSCproducts is assumed; an appendix is devoted to a review of NSCReynolds                                                       [Page 12]

RFC 1099                  Summary of 1000-1099             December 1991technologies and protocols.1043    Yasuda        Feb 88      TELNET Data Entry Terminal Option                                    DODIIS ImplementationThis RFC suggests a proposed protocol on the TELNET Data Entry Terminal(DET) Option - DODIIS Implementation for the Internet community.  It isintended that this specification be capatible with the specification ofDET Option inRFC-732.  Discussion and suggests for improvements areencouraged.1042    Postel        Feb 88      A Standard for the Transmission of                                    IP Datagrams over IEEE 802 NetworksThis RFC specifies a standard method of encapsulating the InternetProtocol (IP) datagrams and Address Resolution Protocol (ARP) requestsand replies on IEEE 802 Networks to allow compatible and interoperableimplementations.  This RFC specifies a protocol standard for theInternet community.1041    Rekhter       Jan 88      Telnet 3270 Regime OptionThis RFC specifies a proposed standard for the Internet community.Hosts on the Internet that want to support 3270 data stream within theTelnet protocol, are expected to adopt and implement this standard.1040    Linn          Jan 88      Privacy Enhancement for Internet                                    Electronic Mail:  Part I Message                                    Encipherment and Authentication                                    ProceduresThis RFC is the Outgrowth of a series of IAB Privacy Task Force meetingsand of internal working papers distributed for those meetings.  Thismemo defines message encipherment and authentication procedures, as theinitial phase of an effort to provide privacy enhancement services forelectronic mail transfer in the Internet.  Detailed key managementmechanisms to support these procedures will be defined in a subsequentRFC.  As a goal of this initial phase, it is intended that theprocedures defined here be compatible with a wide range of keymanagement approaches, including both conventional (symmetric) andpublic-key (asymmetric) approaches for encryption of data encryptingkeys.  Use of conventional cryptography for message text encryptionand/or integrity check computation is anticipated.Reynolds                                                       [Page 13]

RFC 1099                  Summary of 1000-1099             December 19911039    Latham        Jan 88      A DoD Statement on Open Systems                                    Interconnection ProtocolsThis RFC reproduces a memorandum issued on 2-JUL-87 from the AssistantSecretary of Defense for Command, Control, Communications, andIntelligence (ASDC31) to the Director of the Defense CommunicationsAgency (DCA).  This memo is distributed for information only.1038    St. Johns     Jan 88       Draft Revised IP Security OptionThis memo is a pre-publication draft of the revised Internet ProtocolSecurity Option.  This RFC reflects the version as approved by theProtocol Standards Steering group, and is provided for informationalpurposes only.  The final version of this document will be availablefrom Navy publications and should not differ from this document in anymajor fashion.  This document will be published as a change to the MIL-STD 1777, "Internet Protocol".1037    Greenberg     Dec 87        NFILE - A File Access ProtocolThis document includes a specification of the NFILE file access protocoland its underlying levels of protocol, the Token List Transport Layerand Byte Stream with Mark.  The goal of this specification is to promotediscussion of the ideas described here, and to encourage designers offuture file protocols to take advantage of these ideas.  A secondarygoal is to make the specification available to sites that might benefitfrom implementing NFILE.1036    Horton        Dec 87        Standard for Interchange of                                      USENET MessagesThis RFC defines the standard format for the interchange of network Newsmessages among USENET hosts.  It updates and replacesRFC-850,reflecting version B2.11 of the News program.  This memo is distributedas an RFC to make this information easily accessible to the Internetcommunity.  It does not specify an Internet standard.1035    Mockapetris   Nov 87      Domain Names - Implementation                                    SpecificationThis RFC is the revised specification of the protocol and format used inthe implementation of the Domain Name System.  It obsoletesRFC-883.This memo documents the details of the domain name client - servercommunication.Reynolds                                                       [Page 14]

RFC 1099                  Summary of 1000-1099             December 19911034    Mockapetris   Nov 87      Domain Names - Concepts and                                    FacilitiesThis RFC is the revised basic definition of The Domain Name System.  ItobsoletesRFC-882.  This memo describes the domain style names and theirused for host address look up and electronic mail forwarding.  Itdiscusses the clients and servers in the domain name system and theprotocol used between them.1033    Lottor        Nov 87     Domain Administrators Operations                                   GuideThis RFC provides guidelines for domain administrators in operating adomain server and maintaining their portion of the hierarchicaldatabase.  Familiarity with the domain system is assumed (see RFCs 1031,1032, 1034, and 1035).1032    Stahl         Nov 87     Domain Administrators GuideDomains are administrative entities that provide decentralizedmanagement of host naming and addressing.  The domain-naming system isdistributed and hierarchical.This memo describes procedures for registering a domain with the NetworkInformation Center (NIC) of Defense Data Network (DDN), and offersguidelines on the establishment and administration of a domain inaccordance with the requirements specified inRFC-920. It is recommendedthat the guidelines described in this document be used by domainadministrators in the establishment and control of second-level domains.The role of the domain administrator (DA) is that of coordinator,manager, and technician.  If his domain is established at the secondlevel or lower in the tree, the domain administrator must register byinteracting with the management of the domain directly above this.1031    Lazear        Nov 87     Milnet Name Domain TransitionThis RFC consolidates information necessary for the implementation ofdomain style names throughout the DDN/MILNET Internet community.  Theintroduction of domain style names will impact all hosts in theDDN/MILNET Internet.  This RFC is designed as an aid to implementors andadministrators by providing: 1) an overview of the transition processfrom host tables to domains, 2) a timetable for the transition, and 3)references to documentation and software relating to the domain system.Reynolds                                                       [Page 15]

RFC 1099                  Summary of 1000-1099             December 19911030    Lambert       Nov 87     On Testing the NETBLT Protocol over                                   Divers NetworksThis memo describes the results gathered from testing NETBLT over threenetworks of different bandwidths and round-trip delays.  The results arenot complete, but the information gathered so far has not beenpromising.  The NETBLT protocol is specified inRFC-998; this documentassumes an understanding of the specification as described inRFC-998.1029    Parr          May 88     A More Tolerant Approach to Address                                   Resolution  for Multi-Lan system of                                   EthernetsThis memo discusses an extension to a Bridge Protocol to detect anddisclose changes in heighbouring host address parameters in a Multi-Lansystem of Ethernets.  The problem is one which is appearing more andmore regularly as the interconnected systems grow larger on Campuses andin Commercial Institutions.  This RFC suggests a protocol enhancementfor the Internet community, and requests discussion and suggestions forimprovements.1028    Davin         Nov 87     A Simple Gateway Monitoring ProtocolThis memo defines a simple application-layer protocol by whichmanagement information for a gateway may be inspected or altered byremote users.  This proposal is intended only as an interim response toimmediate gateway monitoring needs.1027    Carl-Mitchell Oct 87     Using ARP to Implement Transparent                                   Subnet GatewaysThis RFC describes the use of the Address Resolution Protocol (ARP) bysubnet gateways to permit hosts on the connected subnets to communicatewithout being aware of the existence of subnets, using the technique of"Proxy ARP".1026    Kille         Sep 87     Addendum toRFC-987 (Mapping between                                   X.400 andRFC-882)This memo suggest a proposed protocol for the Internet community, andrequest discussion and suggestions for improvements.Reynolds                                                       [Page 16]

RFC 1099                  Summary of 1000-1099             December 19911025    Postel        Sep 87     TCP and IP Bake OffThis memo describes some of the procedures, scoring and tests used inthe TCP and IP bake offs held in the early development of theseprotocols.  These procedures and tests may still be of use in testingnewly implemented TCP and IP modules.1024    Partridge     Oct 87     HEMS Variable DefinitionsThis memo assigns instruction codes, defines object formats and objectsemantics for use with the High-Level Monitoring and Control Language,defined inRFC-1023.  A general system has been described in previousmemos (RFC-1021,RFC-1022).  This system is called the High-Level EntityManagement System (HEMS).  This memo is provisional and the definitionsare subject to change.  Readers should confirm with the authors thatthey have the most recent version.  This RFC assumes a working knowledgeof the ISO data encoding standard, ASN.1, and a general understanding ofthe IP protocol suite.1023    Partridge     Oct 87     HEMS Monitoring and Control LanguageThis RFC specifies the High-Level Entity Management System (HEMS)Monitoring and Control Language.  This language defines the requests andreplies used in HEMS.  This memo assumes knowledge of the HEMS systemdescribed inRFC-1021, and of the ISO data encoding standard, ASN.1.1022    Partridge     Oct 87     The High-Level Entity Management                                   Protocol (HEMP)This memo presents an application protocol for managing network entitiessuch as hosts, gateways, and front end machines.  This protocol is acomponent of the High-level Entity Management System HEMS), described isRFC-1021.  This memo also assumes a knowledge of the ISO data encodingstandard, ASN.1.1021    Partridge     Oct 87     The High-Level Entity Management                                   System (HEMS)This memo provides a general overview of the High-level Entitymanagement system (HEMS).  This system is experimental, and is currentlybeing tested in portions of the Internet.Reynolds                                                       [Page 17]

RFC 1099                  Summary of 1000-1099             December 19911020    Romano        Nov 87     Internet NumbersThis RFC is a list of the Assigned IP Network Numbers and EGP AutonomousSystem Numbers.  This RFC obsoletesRFC-997.1019    Arnon         Sep 87     Report of the Workshop on                                   Environments for Computational                                   MathematicsThis memo is a report on the discussion of the representation ofequations in a workshop at the ACM SIGGRAPH Conference held in Anaheim,California on 30 July 1987.1018    McKenzie      Aug 87     Some Comments on SQuIDThis memo is a discussion of some of the ideas expressed inRFC-1016 onSource Quench.  This memo introduces the distinction of the cause ofcongestion in a gateway between the effects of "Funneling" andMismatch".  It is offered in the same spirit asRFC-1016; to stimulatediscussion.  The opinions offered are personal, not corporate, opinions.1017    Leiner        Aug 87     Network Requirements for Scientific                                   ResearchThis RFC identifies the requirements on communication networks forsupporting scientific research.  It proposes some specific areas fornear term work, as well as some long term goals.  This is an "idea"paper and discussion is strongly encouraged.1016    Prue          July 87    Something a Host Could Do with Source                                   Quench:  The Source Quench Introduced                                   Delay (SQuID)The memo is intended to explore the issue of what a host could do with asource quench.  The proposal is for each source host IP module tointroduce some delay between datagrams sent to the same destinationhost.  This is a "crazy idea paper" and discussion is essential.1015    Leiner        July 87    Implementation Plan for Interagency                                   Research InternetThis RFC proposes an Interagency Research Internet as the naturaloutgrowth of the current Internet.  This is an "idea paper" andReynolds                                                       [Page 18]

RFC 1099                  Summary of 1000-1099             December 1991discussion is strongly encouraged.1014    Sun           Jun 87     XDR: External Data Representation                                   StandardXDR is a standard for the description and encoding of data.  It isuseful for transferring data between different computer architectures.XDR fits into ISO presentation layer, and is roughly analogous inpurpose to X.409, ISO Abstract Syntax Notation.  The major differencebetween these two is that XDR uses implicit typing, while X.409 usesexplicit typing.  This RFC is distributed for information only, it doesnot establish a Internet standard.1013    Scheifler     Jun 87     X Window System Protocol,                                   Version 11-BetaThis RFC is distributed to the Internet community for information only.It does not establish an Internet standard.  The X window system hasbeen widely reviewed and tested.  The Internet community is encouragedto experiment with it.1012    Reynolds      Jun 87     Bibliography of Requests for                                   Comments 1-999This RFC is a reference guide for the Internet community which providesa bibliographic summary of the Request for Comments numbers 1 through999 issued between the years 1969-1987.1011    Reynolds      May 87     Official Internet ProtocolsThis memo is an official status report on the protocols used in theInternet community.  It identifies the documents specifying the officialprotocols used in the Internet.  Comments indicate any revisions orchanges planned.1010    Reynolds      May 87     Assigned NumbersThis memo is an official status report on the numbers used in protocolsin the Internet community.  It documents the currently assigned valuesfrom several series of numbers including link, socket, port, andprotocol, used in network protocol implementations.Reynolds                                                       [Page 19]

RFC 1099                  Summary of 1000-1099             December 19911009     Braden       Jun 87     Requirements for Internet GatewaysThis RFC summarizes the requirements for gateways to be used betweennetworks supporting the Internet protocols.  This document is a formalstatement of the requirements to be met by gateways used in the Internetsystem.  As such, it is an official specification for the Internetcommunity.1008     McCoy        Jun 87     Implementation Guide for the ISO                                   Transport ProtocolThis RFC is being distributed to members of the Internet community inorder to solicit comments on the Implementors Guide.  While thisdocument may not be directly relevant to the research problems of theInternet, it may be of some interest to a number of researchers andimplementors.1007     McCoy        Jun 87     Military Supplement to the ISO                                   Transport ProtocolThis document supplements the Transport Service and Protocol of theInternational Standards Organization (ISO), IS 8072 and IS 8073,respectively, and their formal descriptions by providing conventions,option selections and parameter values.  This RFC is being distributedto members of the Internet community in order to solicit comments on theDraft Military Supplement.  While this document may not be directlyrelevant to the research problems of the Internet, it may be of someinterest to a number of researchers and implementors.1006     Rose         May 87     ISO Transport Services on top of                                   the TCP Version: 3This memo specifies a standard for the Internet community.  Hosts on theInternet that choose to implement ISO transport services on top of theTCP are expected to adopt and implement this standard.  TCP port 102 isreserved for hosts which implement this standard.  This memo specifiesversion 3 of the protocol and supersedesRFC-983.  Changes between theprotocol is described inRFC-983 and this memo are minor, butunfortunately incompatible.1005     Khanna       May 87     The ARPANET AHIP-E Host Access                                   Protocol (Enhanced AHIP)This RFC is a proposed specification for the encoding of Class A IPReynolds                                                       [Page 20]

RFC 1099                  Summary of 1000-1099             December 1991addresses for use on ARPANET-style networks such as the Milnet andArpanet, and for enhancements to the ARPANET AHIP Host Access Protocol(AHIP; formerly known as 1822).  These enhancements increase the size ofthe PSN field, allow ARPANET hosts to use logical names to address eachother, allow for the communication of type-of-service information fromthe host to the PSN and enable the PSN to provide congestion feedback tothe host on a connection basis.1004     Mills        Apr 87     A Distributed-Protocol                                   Authentication SchemeThe purpose of this RFC is to focus discussion on authenticationproblems in the Internet and possible methods of solution.  The proposedsolutions this document are not intended as standards for the Internetat this time.  Rather, it is hoped that a general consensus will emergeas to the appropriate solution to authentication problems, leadingeventually to the adoption of standards.  This document suggestsmediated access-control and authentication procedures suitable for thosecases when an association is to be set up between users belonging todifferent trust environments.1003     Katz         Mar 87     Issues in Defining an Equations                                   Representation StandardThis memo is intended to identify and explore issues in defining astandard for the exchange of mathematical equations.  No attempt is madeat a complete definition and more questions are asked than are answered.Questions about the user interface are only addressed to the extent thatthey affect interchange issues.1002    NETBIOS       Mar 87     Protocol Standard for A NetBIOS                                   Service on a TCP/UDP Transport:                                   Detailed SpecificationsThis RFC defines a proposed standard protocol to support NetBIOSservices in a TCP/IP environment.  Both local network and internetoperation are supported.  Various node types are defined to accommodatelocal and internet topologies and to allow operation with or without theuse of IP broadcast.  This RFC gives the detailed specifications of thenetBIOS-over-TCP packets, protocols, and defined constants andvariables.  A more general overview is found in a companion RFC,"Protocol Standard For NetBIOS Service on TCP/UDP Transport: Conceptsand Methods".Reynolds                                                       [Page 21]

RFC 1099                  Summary of 1000-1099             December 19911001    NETBIOS       Mar 87     Protocol Standard for A NetBIOS                                   Service on a TCP/UDP Transport:                                   Concepts and MethodsThis RFC defines a proposed standard protocol to support NetBIOSservices in a TCP/IP environment.  Both local network and internetoperation are supported.  Various node types are defined to accommodatelocal and internet topologies and to allow operation with or without theuse of IP broadcast.  This RFC describes the NetBIOS-over-TCP protocolsin a general manner, emphasizing the underlying ideas and techniques.Detailed specifications are found in a companion RFC, "Protocol StandardFor a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications".1000    Reynolds      Aug 87     The Request for Comments Reference                                   GuideThis RFC Reference Guide is intended to provide a historical account bycategorizing and summarizing of the Request for Comments numbers 1through 999 issued between the years 1969-1987.  These documents havebeen crossed referenced to indicate which RFCs are current, obsolete, orrevised.Security Considerations   Security issues are not discussed in this memo.Author's Address   Joyce K. Reynolds   University of Southern California   Information Sciences Institute   4676 Admiralty Way   Marina del Rey, CA 90292   Phone:  (310) 822-1511   EMail:  JKREY@ISI.EDUReynolds                                                       [Page 22]