Movatterモバイル変換

Network Working Group                                         M. KennedyRequest for Comments: 1799                                           ISICategory: Informational                                     January 1997Request for Comments Summary                         RFC Numbers 1700-1799Status of This Memo   This RFC is a slightly annotated list of the 100 RFCs fromRFC 1700   through RFCs 1799.  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---     ------       ----      -----1799    Kennedy   Jan 97     Requests For Comments SummaryThis memo.1798    Young     Jun 95      Connection-less Lightweight X.500                                Directory Access ProtocolThe protocol described in this document is designed to provide access tothe Directory while not incurring the resource requirements of theDirectory Access Protocol (DAP). [STANDARDS-TRACK]Kennedy                      Informational                      [Page 1]

RFC 1799                  Summary of 1700-1799              January 19971797    IANA      Apr 95      Class A Subnet ExperimentThere appears to be some interest in experimenting with subnetting theclass A addresses. It is suggested that conducting an experiment now toidentify and fix any software that does not properly handle subnettedclass A addresses would be useful and important. This document definesan Experimental Protocol for the Internet community.  This does notspecify an Internet standard of any kind.1796    Huitema   Apr 95      Not All RFCs are StandardsThis document discusses the relationship of the Request for Comments(RFCs) notes to Internet Standards. This memo provides information forthe Internet community.  This memo does not specify an Internet standardof any kind.1795     Wells    Apr 95      Data Link Switching: Switch-to-Switch                                Protocol                                AIW DLSw RIG: DLSw Closed Pages, DLSw                                Standard Version 1.0This RFC describes use of Data Link Switching over TCP/IP. This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1794     Brisco   Apr 95     DNS Support for Load BalancingThis RFC is meant to first chronicle a foray into the IETF DNS WorkingGroup, discuss other possible alternatives to provide/simulate loadbalancing support for DNS, and to provide an ultimate, flexible solutionfor providing DNS support for balancing loads of many types. This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1793     Moy       Apr 95    Extending OSPF to Support Demand CircuitsThis memo defines enhancements to the OSPF protocol that allow efficientoperation over "demand circuits". [STANDARDS-TRACK]Kennedy                      Informational                      [Page 2]

RFC 1799                  Summary of 1700-1799              January 19971792     Sung      Apr 95    TCP/IPX Connection Mib SpecificationNew MIB objects, tcpIpxConnTable, udpIpxTable, tcpUnspecConnTable andudpUnspecTable are presented in this paper, to be used in place oftcpConnTable and udpListenerTable when TCP and UDP are running over IPX.This document defines an Experimental Protocol for the Internetcommunity.  This does not specify an Internet standard of any kind.1791     Sung      Apr 95    TCP And UDP Over IPX Networks With                               Fixed Path MTUTCP/IPX allows TCP/IP applications to run over IPX networks by lettingTCP and UDP run over IPX.  And this memo specifies the packet format andoperational procedures for running TCP and UDP over IPX. This documentdefines an Experimental Protocol for the Internet community.  This doesnot specify an Internet standard of any kind.1790    Cerf       Apr 95    An Agreement between the Internet                               Society and Sun Microsystems, Inc.                               in the Matter of ONC RPC and XDR                               ProtocolsThis RFC is an official public record of an agreement between SUNMicrosystems and the Internet Society.  This memo provides informationfor the Internet community.  It does not specify an Internet standard ofany kind.1789    Yang      Apr 95     INETPhone: Telephone Services and                               Servers on InternetThis RFC presents a true telephone service, called INETPhone, whichsupports voice communication through the Internet. This memo providesinformation for the Internet community.  It does not specify an Internetstandard of any kind.1788    Simpson   Apr 95     ICMP Domain Name MessagesThis document specifies ICMP messages for learning the Fully QualifiedDomain Name associated with an IP address. This document defines anExperimental Protocol for the Internet community.  This does not specifyan Internet standard of any kind.Kennedy                      Informational                      [Page 3]

RFC 1799                  Summary of 1700-1799              January 19971787    Rekhter  Apr 95     Routing in a Multi-provider InternetThis document presents some of the issues related to network layerrouting in a multi-provider Internet, and specifically to the unicastrouting. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1786    Bates    Mar 95     Representation of IP Routing PoliciesThis document is an update to the original `ripe-81' proposal forrepresenting and storing routing polices within the RIPE database. Itincorporates several extensions proposed by Merit Inc. and gives detailsof a generalized IP routing policy representation to be used by allInternet routing registries.  It acts as both tutorial and providesdetails of database objects and attributes that use and make up arouting registry. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.1785    Malkin   Mar 95     TFTP Option Negotiation AnalysisThis document was written to allay concerns that the presence of optionsin a TFTP Request packet might cause pathological behavior on serverswhich do not support TFTP option negotiation. This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1784    Malkin   Mar 95    TFTP Timeout Interval and Transfer                             Size OptionsThis document describes two TFTP options. The first allows the clientand server to negotiate the Timeout Interval.  The second allows theside receiving the file to determine the ultimate size of the transferbefore it begins. [STANDARDS-TRACK]1783    Malkin   Mar 95    TFTP Blocksize OptionThis document describes a TFTP option which allows the client and serverto negotiate a blocksize more applicable to the network medium.[STANDARDS-TRACK]Kennedy                      Informational                      [Page 4]

RFC 1799                  Summary of 1700-1799              January 19971782    Malkin   Mar 95    TFTP Option ExtensionThe Trivial File Transfer Protocol is a simple, lock-step, file transferprotocol which allows a client to get or put a file onto a remote host.This document describes a simple extension to TFTP to allow optionnegotiation prior to the file transfer.1781    Kille   Mar 95    Using the OSI Directory to Achieve                            User Friendly NamingThis proposal sets out some conventions for representing names in afriendly manner, and shows how this can be used to achieve reallyfriendly naming. [STANDARDS-TRACK]1780   IAB     Mar 95    Internet Official Protocol StandardsThis memo describes the state of standardization of protocols used inthe Internet as determined by the Internet Architecture Board (IAB).[STANDARDS-TRACK]1779   Kille   Mar 95     A String Representation of Distinguished                            NamesThe OSI Directory uses distinguished names as the primary keys toentries in the directory.  Distinguished Names are encoded in ASN.1.When a distinguished name is communicated between to users not using adirectory protocol (e.g., in a mail message), there is a need to have auser-oriented string representation of distinguished name. Thisspecification defines a string format for representing names, which isdesigned to give a clean representation of commonly used names, whilstbeing able to represent any distinguished name. [STANDARDS-TRACK]1778   Howes  Mar 95     The String Representation of Standard                           Attribute SyntaxesThe Lightweight Directory Access Protocol (LDAP) requires that thecontents of AttributeValue fields in protocol elements be octet strings.This document defines the requirements that must be satisfied byencoding rules used to render X.500 Directory attribute syntaxes into aform suitable for use in the LDAP, then goes on to define the encodingrules for the standard set of attribute syntaxes.  [STANDARDS-TRACK]Kennedy                      Informational                      [Page 5]

RFC 1799                  Summary of 1700-1799              January 19971777   Yeong   Mar 95     Lightweight Directory Access ProtocolThe protocol described in this document is designed to provide access tothe X.500 Directory while not incurring the resource requirements of theDirectory Access Protocol (DAP).This protocol is specifically targetedat simple management applications and browser applications that providesimple read/write interactive access to the X.500 Directory, and isintended to be a complement to the DAP itself.  [STANDARDS-TRACK]1776   Crocker Apr 95     The Address is the MessageDeclaring that the address is the message, the IPng WG has selected apacket format which includes 1696 bytes of address space. This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1775   Crocker Mar 95    To Be "On" the InternetThe Internet permits different levels of access for consumers andproviders of service.  The nature of those differences is quiteimportant in the capabilities They afford.  Hence, it is appropriate toprovide terminology that distinguishes among the range, so that theInternet community can gain some clarity when distinguishing whether auser (or an organization) is "on" the Internet.  This document suggestsfour terms, for distinguishing the major classes of access. This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1774   Traina Mar 95    BGP-4 Protocol AnalysisThe purpose of this report is to document how the requirements foradvancing a routing protocol to Draft Standard have been satisfied bythe Border Gateway Protocol version 4 (BGP-4). This report summarizesthe key features of BGP, and analyzes the protocol with respect toscaling and performance. This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.Kennedy                      Informational                      [Page 6]

RFC 1799                  Summary of 1700-1799              January 19971773    TrainaMar 95   Experience with the BGP-4 protocolThe purpose of this memo is to document how the requirements foradvancing a routing protocol to Draft Standard have been satisfied byBorder Gateway Protocol version 4 (BGP-4).  This report documentsexperience with BGP. This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1772   RekhterMar 95   Application of the Border Gateway                         Protocol in the InternetThis document, together with its companion document, "A Border GatewayProtocol 4 (BGP-4)", define an inter-autonomous system routing protocolfor the Internet. This document describes the usage of the BGP in theInternet.  [STANDARDS-TRACK]1771   RekhterMar 95   A Border Gateway Protocol 4 (BGP-4)This document, together with its companion document, "Application of theBorder Gateway Protocol in the Internet", define an inter-autonomoussystem routing protocol for the Internet. [STANDARDS-TRACK]1770   Graff Mar 95   IPv4 Option for Sender Directed                        Multi-Destination DeliveryThis memo defines an IPv4 option to provide a sender directed multi-destination delivery mechanism called Selective Directed Broadcast Mode(SDBM). This memo provides information for the Internet community.  Thismemo does not specify an Internet standard of any kind.1769   Mills Mar 95   Simple Network Time Protocol (SNTP)This memorandum describes the Simple Network Time Protocol (SNTP), whichis an adaptation of the Network Time Protocol (NTP) used to synchronizecomputer clocks in the Internet. This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.Kennedy                      Informational                      [Page 7]

RFC 1799                  Summary of 1700-1799              January 19971768   MarlowMar 95   Host Group Extensions for CLNP MulticastingThis memo provides a specification for multicast extensions to the CLNPprotocol similar to those provided to IP byRFC1112. This memo definesan Experimental Protocol for the Internet community.  This memo does notspecify an Internet standard of any kind.1767   CrockerMar 95   MIME Encapsulation of EDI ObjectsSince there are many different EDI specifications, the current documentdefines three distinct categories as three different MIME content-types.[STANDARDS-TRACK]1766   Alvestrand Mar 95Tags for the Identification of LanguagesThis document describes a language tag for use in cases where it isdesired to indicate the language used in an information object.[STANDARDS-TRACK]1765   Moy     Mar 95   OSPF Database OverflowThis memo details a way of gracefully handling unanticipated databaseoverflows. This memo defines an Experimental Protocol for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1764   Senum   Mar 95   The PPP XNS IDP Control Protocol (XNSCP)This document defines the Network Control Protocol for establishing andconfiguring the Xerox Network Systems (XNS) Internet Datagram Protocol(IDP) over PPP. [STANDARDS-TRACK]1763   Senum   Mar 95   The PPP Banyan Vines Control Protocol (BVCP)This document defines the Network Control Protocol for establishing andconfiguring the Banyan VINES protocol over PPP. [STANDARDS-TRACK]Kennedy                      Informational                      [Page 8]

RFC 1799                  Summary of 1700-1799              January 19971762   Senum   Mar 95   The PPP DECnet Phase IV Control Protocol                          (DNCP)This document defines the NCP for establishing and configuring Digital'sDNA Phase IV Routing protocol (DECnet Phase IV) over PPP.  This documentapplies only to DNA Phase IV Routing messages (both data and control),and not to other DNA Phase IV protocols (MOP, LAT, etc). [STANDARDS-TRACK]1761   CallaghanFeb 95  Snoop Version 2 Packet Capture File FormatThis paper describes the file format used by "snoop", a packetmonitoring and capture program developed by Sun.  This paper is providedso that people can write compatible programs to generate and interpretsnoop packet capture files. This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1760   Haller   Feb 95  The S/KEY One-Time Password SystemThis document describes the S/KEY* One-Time Password system as releasedfor public use by Bellcore. This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1759   Smith    Mar 95  Printer MIBA printer is the physical device that takes media from an input source,produces marks on that media according to some page description or pagecontrol language and puts the result in some output destination,possibly with finishing applied. The information needed in themanagement of the physical printer and the management of a printing joboverlap highly and many of the tasks in each management area require thesame or similar information. [STANDARDS-TRACK]1758   N.A.D.F. Feb 95    NADF Standing Documents: A Brief OverviewThe purpose of this document is to provide a brief overview of theNADF's Standing Document series. This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.Kennedy                      Informational                      [Page 9]

RFC 1799                  Summary of 1700-1799              January 19971757   Waldbusser Feb 95 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]1756    Rinne   Jan 95   REMOTE WRITE PROTOCOL - VERSION 1.0This document describes a simple Remote Write Protocol (RWP). This memodefines an Experimental Protocol for the Internet community.  This memodoes not specify an Internet standard of any kind.1755    Perez   Feb 95   ATM Signaling Support for IP over ATMThis memo describes the ATM call control signaling exchanges needed tosupport Classical IP over ATM implementations as described inRFC 1577.[STANDARDS-TRACK]1754    Laubach Jan 95   IP over ATM Working Group's                           Recommendations for the ATM Forum's                           Multiprotocol BOF                           Version 1This document represents an initial list of requirements submitted tothe ATM Forum's Multiprotocol BOF for the operation of IP over ATMnetworks as determined by the IETF IP over ATM Working Group and otherworking groups. This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1753     Chiappa Dec 94   IPng Technical Requirements                            Of the Nimrod Routing and Addressing                            ArchitectureThis document presents the requirements that the Nimrod routing andaddressing architecture has upon the internetwork layer protocol. To bemost useful to Nimrod, any protocol selected as the IPng should satisfythese requirements. This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.Kennedy                      Informational                     [Page 10]

RFC 1799                  Summary of 1700-1799              January 19971752     Bradner Jan 95   The Recommendation for the IP Next                            Generation ProtocolThis document presents the recommendation of the IPng Area Directors onwhat should be used to replace the current version of the InternetProtocol. [STANDARDS-TRACK]1751     McDonald Dec 94   A Convention for Human-Readable 128-bit                             KeysThis memo proposes a convention for use with Internet applications &protocols using 128-bit cryptographic keys. This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1750     Eastlake  Dec 94  Randomness Recommendations for SecurityChoosing random quantities to foil a resourceful and motivated adversaryis surprisingly difficult.  This paper points out many pitfalls in usingtraditional pseudo-random number generation techniques for choosing suchquantities.  It recommends the use of truly random hardware techniquesand shows that the existing hardware on many systems can be used forthis purpose. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1749   McCloghrie  Dec 94   IEEE 802.5 Station Source Routing MIB                              using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it describes managed objects used by IEEE 802.5 end-stationsfor managing source routes on a Token Ring network where IEEE source-routing is in use. [STANDARDS-TRACK]1748   McCloghrie  Dec 94   IEEE 802.5 MIB using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it describes managed objects used for managing subnetworkswhich use the IEEE 802.5 Token Ring technology described in 802.5 TokenRing Access Method and Physical Layer Specifications, IEEE Standard802.5-1989. [STANDARDS-TRACK]Kennedy                      Informational                     [Page 11]

RFC 1799                  Summary of 1700-1799              January 19971747   Hilgeman   Jan 95   Definitions of Managed Objects for SNA                             Data Link Control (SDLC) using SMIv2This specification defines an extension to the Management InformationBase (MIB) for use with SNMP-based network management.  In particular,it defines objects for managing the configuration, monitoring andcontrol of data link controls in an SNA environment. [STANDARDS-TRACK]1746   Manning    Dec 94   Ways to Define User ExpectationsThis paper covers basic fundamentals that must be understood when onedefines, interprets, or implements methods to control user expectationson or over the Internet. This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1745    Varadhan   Dec 94   BGP4/IDRP for IP---OSPF InteractionThis memo defines the various criteria to be used when designing anAutonomous System Border Router (ASBR) that will run either BGP4 or IDRPfor IP with other ASBRs external to the AS and OSPF as its IGP.[STANDARDS-TRACK]1744     Huston    Dec 94   Observations on the Management of                              the Internet Address SpaceThis memo examines some of the issues associated with the currentmanagement practices of the Internet IPv4 address space, and examinesthe potential outcomes of these practices as the unallocated addresspool shrinks in size. This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1743     McCloghrieDec 94    IEEE 802.5 MIB using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it describes managed objects used for managing subnetworkswhich use the IEEE 802.5 Token Ring technology described in 802.5 TokenRing Access Method and Physical Layer Specifications, IEEE Standard802.5-1989. [STANDARDS-TRACK]Kennedy                      Informational                     [Page 12]

RFC 1799                  Summary of 1700-1799              January 19971742     WaldbusserJan 95    AppleTalk Management Information Base IIThis 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 AppleTalk networks.[STANDARDS-TRACK]1741     Falstrom   Dec 94  MIME Content Type for BinHex Encoded FilesThis memo describes the format to use when sending BinHex4.0 files viaMIME [BORE93]. This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1740     Falstron   Dec 94   MIME Encapsulation of Macintosh Files -                               MacMIMEThis memo describes the format to use when sending Apple Macintosh filesvia MIME [BORE93]. [STANDARDS-TRACK]1739     Kessler     Dec 94   A Primer On Internet and TCP/IP ToolsThis memo is an introductory guide to some of the TCP/IP and Internettools and utilities that allow users to access the wide variety ofinformation on the network, from determining if a particular host is upto viewing a multimedia thesis on foreign policy. It also describesdiscussion lists accessible from the Internet, ways to obtain Internetdocuments, and resources that help users weave their way through theInternet. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1738     Berners-Lee Dec 94   Uniform Resource Locators (URL)This document specifies a Uniform Resource Locator (URL), the syntax andsemantics of formalized information for location and access of resourcesvia the Internet. [STANDARDS-TRACK]1737     Sollins     Dec 94   Functional Requirements for Uniform                                Resource NamesThis document specifies a minimum set of requirements for a kind ofInternet resource identifier known as Uniform Resource Names (URNs).This memo provides information for the Internet community.  This memodoes not specify an Internet standard of any kind.Kennedy                      Informational                     [Page 13]

RFC 1799                  Summary of 1700-1799              January 19971736     Kunze      Feb 95    Functional Recommendations for                                Internet Resource LocatorsThis document specifies a minimum set of requirements for Internetresource locators, which convey location and access information forresources. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1735     Heinanen   Dec 94    NBMA Address Resolution Protocol (NARP)This document describes the NBMA Address Resolution Protocol (NARP).NARP can be used by a source terminal (host or router) connected to aNon-Broadcast, Multi-Access link layer (NBMA) network to find out theNBMA addresses of the a destination terminal provided that thedestination terminal is connected to the same NBMA network. This memodefines an Experimental Protocol for the Internet community.  This memodoes not specify an Internet standard of any kind.1734     Myers      Dec 94   POP3 AUTHentication commandThis document describes the optional AUTH command, for indicating anauthentication mechanism to the server, performing an authenticationprotocol exchange, and optionally negotiating a protection mechanism forsubsequent protocol interactions. [STANDARDS-TRACK]1733     Crispin    Dec 94   Distributed Electronic Mail                               Models in IMAP4There are three fundamental models of client/server email: offline,online, and disconnected use.  IMAP4 can be used in any one of thesethree models.  This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.1732     Crispin    Dec 94   IMAP4 COMPATIBILITY WITH IMAP2                               AND IMAP2BISThis is a summary of hints and recommendations to enable an IMAP4implementation to interoperate with implementations that conform toearlier specifications. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.Kennedy                      Informational                     [Page 14]

RFC 1799                  Summary of 1700-1799              January 19971731    Myers       Dec 94   IMAP4 Authentication MechanismsThe Internet Message Access Protocol, Version 4 [IMAP4] contains theAUTHENTICATE command, for identifying and authenticating a user to anIMAP4 server and for optionally negotiating a protection mechanism forsubsequent protocol interactions.  This document describes severalauthentication mechanisms for use by the IMAP4 AUTHENTICATE command.[STANDARDS-TRACK]1730    Crispin     Dec 94   Internet Message Access Protocol                               - Version 4The Internet Message Access Protocol, Version 4 (IMAP4) allows a clientto access and manipulate electronic mail messages on a server. IMAP4permits manipulation of remote message folders, called "mailboxes", in away that is functionally equivalent to local mailboxes.  IMAP4 alsoprovides the capability for an offline client to resynchronize with theserver. [STANDARDS-TRACK]1729    Lynch      Dec 94    Using the Z39.50 Information                               Retrieval Protocol in the Internet                               EnvironmentThis memo describes an approach to the implementation of the ANSI/NISOZ39.50-1992 Standard for Information Retrieval in the TCP/IP environmentwhich is currently in wide use by the Z39.50 implementor community. Thismemo provides information for the Internet community.  This memo doesnot specify an Internet standard of any kind.1728    Weider    Dec 94    Resource TranspondersThis paper describes an automatic mechanism, the resource transponder,for maintaining resource location information.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1727    Weider    Dec 94    A Vision of an Integrated Internet                              Information ServiceThis paper lays out a vision of how Internet information services mightbe integrated over the next few years, and discusses in some detail whatsteps will be needed to achieve this integration. This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.Kennedy                      Informational                     [Page 15]

RFC 1799                  Summary of 1700-1799              January 19971726    Partridge Dec 94   Technical Criteria for Choosing                             IP The Next Generation (IPng)This RFC specifies criteria related to mobility for consideration indesign and selection of the Next Generation of IP. This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1725    Myers     Nov 94   Post Office Protocol - Version 3This memo is a revision toRFC 1460, a Draft Standard. [STANDARDS-TRACK]1724    Malkin    Nov 94   RIP Version 2 MIB ExtensionThis 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 RIP Version 2.  [STANDARDS-TRACK]1723    Malkin   Nov 94    RIP Version 2                             Carrying Additional InformationThis document specifies an extension of the Routing Information Protocol(RIP), o expand the amount of useful information carried in RIP messagesand to add a measure of security.  This memo obsoletesRFC 1388, whichspecifies an update to the "Routing Information Protocol" STD 34, RFC1058. [STANDARDS-TRACK]1722    Malkin   Nov 94    RIP Version 2 Protocol Applicability                             StatementAs required by Routing Protocol Criteria (RFC 1264), this report definesthe applicability of the RIP-2 protocol within the Internet.  Thisreport is a prerequisite to advancing RIP-2 on the standards track.[STANDARDS-TRACK]Kennedy                      Informational                     [Page 16]

RFC 1799                  Summary of 1700-1799              January 19971721    Malkin  Nov 94    RIP Version 2 Protocol AnalysisAs required by Routing Protocol Criteria (RFC 1264), this reportdocuments the key features of the RIP-2 protocol and the currentimplementation experience.  This report is a prerequisite to advancingRIP-2 on the standards track. This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1720    IAB     Nov 94    Internet Official Protocol StandardsThis memo describes the state of standardization of protocols used inthe Internet as determined by the Internet Architecture Board (IAB).[STANDARDS-TRACK]1719    Gross   Dec 94    A Direction for IPng                              Specification and ImplementationThis RFC specifies criteria related to mobility for consideration indesign and selection of the Next Generation of IP. This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1718    IETF SecretariatNov 94   The Tao of IETF                                   A Guide for New Attendees of the                                   Internet Engineering Task ForceThe purpose of this For Your Information (FYI) RFC is to explain to thenewcomers how the IETF works. This memo provides information for theInternet community.  It does not specify an Internet standard. [FYI 17]1717    Sklower      Nov 94     The PPP Multilink Protocol (MP)This document proposes a method for splitting, recombining andsequencing datagrams across multiple logical data links. [STANDARDS-TRACK]Kennedy                      Informational                     [Page 17]

RFC 1799                  Summary of 1700-1799              January 19971716    Almquist     Nov 94     Towards Requirements for IP RoutersThe goal of this work is to replaceRFC-1009, Requirements for InternetGateways ([INTRO:1]) with a new document. It defines and discussesrequirements for devices which perform the network layer forwardingfunction of the Internet protocol suite. This memo provides informationfor the Internet community.  This memo does not specify an Internetstandard of any kind.1715    Huitema      Nov 94     The H Ratio for Address Assignment                                  EfficiencyThis document was submitted to the IETF IPng area in response to RFC1550. This memo provides information for the Internet community.Thismemo does not specify an Internet standard of any kind.1714    Williamson   Nov 94     Referral Whois Protocol (RWhois)This memo describes version 1.0 of the client/server interaction ofRWhois.  RWhois provides a distributed system for the display ofhierarchical information. This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1713    Romao        Nov 94      Tools for DNS debuggingAlthough widely used (and most of the times unnoticed), DNS (Domain NameSystem) is too much overlooked, in the sense that people, especiallyadministrators, tend to ignore possible anomalies as long asapplications that need name-to-address mapping continue to work.  Thisdocument presents some tools available for domain administrators todetect and correct those anomalies. This memo provides information forthe Internet community.  This memo does not specify an Internet standardof any kind.1712    Farrell      Nov 94     DNS Encoding of Geographical LocationThis document defines the format of a new Resource Record (RR) for theDomain Naming System (DNS), and reserves a corresponding DNS typemnemonic and numerical code. This memo defines an Experimental Protocolfor the Internet community.  This memo does not specify an Internetstandard of any kind.Kennedy                      Informational                     [Page 18]

RFC 1799                  Summary of 1700-1799              January 19971711     Houttuin    Oct 94     Classifications in E-mail RoutingThis paper presents a classification for e-mail routing issues. Thismemo provides information for the Internet community.  This memo doesnot specify an Internet standard of any kind.1710     Hinden     Oct 94      Simple Internet Protocol Plus                                  White PaperThis document was submitted to the IETF IPng area in response to RFC1550. This memo provides information for the Internet community.Thismemo does not specify an Internet standard of any kind.1709     Gargano    Nov 94      K-12 Internetworking GuidelinesThe K-12 community traditionally has not had this level of staffingavailable for telecommunications planning.  This document is intended tobridge that gap and provides a recommended technical direction, anintroduction to the role the Internet now plays in K-12 education andtechnical guidelines for building a campus data communicationsinfrastructure that provides internetworking services and connections tothe Internet. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1708     Gowin     Oct 94      NTP PICS PROFORMA                                 For the Network Time Protocol                                 Version 3This RFC describes a PICS Proforma translated into an Internetacceptable form. This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1707     McGovern  Oct 94     CATNIP: Common Architecture for                                the InternetThis document was submitted to the IETF IPng area in response to RFC1550. This paper describes a common architecture for the network layerprotocol. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.Kennedy                      Informational                     [Page 19]

RFC 1799                  Summary of 1700-1799              January 19971706    Manning   Oct 94     DNS NSAP Resource RecordsThis document defines the format of one new Resource Record (RR) for theDNS for domain name-to-NSAP mapping. The RR may be used with any NSAPaddress format.  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1705    Carlson   Oct 94      Six Virtual Inches to the Left:                                The Problem with IPngThis document was submitted to the IETF IPng area in response to RFC1550. This RFC suggests that a new version of TCP (TCPng), and UDP, bedeveloped and deployed. This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1704    Haller    Oct 94      On Internet AuthenticationThis document describes a spectrum of authentication technologies andprovides suggestions to protocol developers on what kinds ofauthentication might be suitable for some kinds of protocols andapplications used in the Internet. This document provides informationfor the Internet community.  This memo does not specify an Internetstandard of any kind.1703    Rose     Oct 94      Principles of Operation for the TPC.INT                               Subdomain:                               Radio Paging -- Technical ProceduresThis memo describes a technique for radio paging using the Internet mailinfrastructure.  In particular, this memo focuses on the case in whichradio pagers are identified via the international telephone network.This memo provides information for the Internet community.  This memodoes not specify an Internet standard of any kind.1702    Hanks     Oct 94    Generic Routing Encapsulation over                              IPv4 networksThis memo addresses the case of using IP as the delivery protocol or thepayload protocol and the special case of IP as both the delivery andpayload.  This memo also describes using IP addresses and autonomoussystem numbers as part of a GRE source route. This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.Kennedy                      Informational                     [Page 20]

RFC 1799                  Summary of 1700-1799              January 19971701    Hanks     Oct 94   Generic Routing Encapsulation (GRE)This document specifies a protocol for performing encapsulation of anarbitrary network layer protocol over another arbitrary network layerprotocol. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1700    Reynolds   Oct 94      Assigned NumbersThis RFC is a snapshot of the ongoing process of the assignment ofprotocol parameters for the Internet protocol suite.  To make thecurrent information readily available the assignments are kept up-to-date in a set of online text files. This memo is a status report on theparameters (i.e., numbers and keywords) used in protocols in theInternet community.Security 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 21]