Movatterモバイル変換

Network Working Group                                         J. ElliottRequest for Comments: 1999                                           ISICategory: Informational                                     January 1997Request for Comments Summary                         RFC Numbers 1900-1999Status of This Memo   This RFC is a slightly annotated list of the 100 RFCs fromRFC 1900   through RFCs 1999.  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---     ------       ----      -----1999    Elliott    Jan 97   Requests For Comments SummaryThis memo.1998    Chen       Aug 96   An Application of the BGP Community                              Attribute in Multi-home RoutingThis document presents an application of the BGP community attribute [2]in simplifying the implementation and configuration of routing policiesin the multi-provider Internet.  This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.Elliott                      Informational                      [Page 1]

RFC 1999                  Summary of 1900-1999              January 19971997    Chandra    Aug 96   BGP Communities AttributeThis document describes an extension to BGP which may be used to passadditional information to both neighboring and remote BGP peers.[STANDARDS-TRACK]1996    Vixie      Aug 96   A Mechanism for Prompt Notification of                              Zone Changes (DNS NOTIFY)This memo describes the NOTIFY opcode for DNS, by which a master serveradvises a set of slave servers that the master's data has been changedand that a query should be initiated to discover the new data.[STANDARDS-TRACK]1995    Ohta       Aug 96   Incremental Zone Transfer in DNSThis document proposes extensions to the DNS protocols to provide anincremental zone transfer (IXFR) mechanism.  [STANDARDS-TRACK]1994    Simpson    Aug 96   PPP Challenge Handshake Authentication                              Protocol (CHAP)This document defines a method for Authentication using PPP, which usesa random Challenge, with a cryptographically hashed Response whichdepends upon the Challenge and a secret key.  [STANDARDS-TRACK]1993    Barbir     Aug 96   PPP Gandalf FZA Compression ProtocolThis document describes the use of the Gandalf FZA data compressionalgorithm [3] for compressing PPP encapsulated packets.  This memoprovides information for the Internet community.  It does not specify anInternet standard.1992    Castineyra Aug 96   The Nimrod Routing ArchitectureNimrod is a scalable routing architecture designed to accommodate acontinually expanding and diversifying internetwork.  First suggested byNoel Chiappa, the Nimrod architecture has undergone revision andrefinement through the efforts of the Nimrod working group of the IETF.In this document, we present a detailed description of thisarchitecture.  This memo provides information for the Internetcommunity.  It does not specify an Internet standard.Elliott                      Informational                      [Page 2]

RFC 1999                  Summary of 1900-1999              January 19971991    Atkins     Aug 96   PGP Message Exchange FormatsThis document describes the format of "PGP files", i.e., messages thathave been encrypted and/or signed with PGP.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1990    Sklower    Aug 96   The PPP Multilink Protocol (MP)This document proposes a method for splitting, recombining andsequencing datagrams across multiple logical data links.  [STANDARDS-TRACK]1989    Simpson    Aug 96   PPP Link Quality MonitoringThis document defines a protocol for generating Link-Quality-Reports.[STANDARDS-TRACK]1988    McAnally   Aug 96   Conditional Grant of Rights to Specific                              Hewlett-Packard Patents In Conjunction                              With the Internet Engineering Task                              Force's Internet-Standard Network                              Management FrameworkThis grant is made to help facilitate inclusion of certain patentedsearch address technology covering network device mapping in IETFstandards-track Management Information Base (MIB) modules.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1987    Newman     Aug 96   Ipsilon's General Switch Management                              Protocol Specification Version 1.1The General Switch Management Protocol (GSMP), is a general purposeprotocol to control an ATM switch. GSMP allows a controller to establishand release connections across the switch; add and delete leaves on apoint-to-multipoint connection; manage switch ports; requestconfiguration information; and request statistics.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.Elliott                      Informational                      [Page 3]

RFC 1999                  Summary of 1900-1999              January 19971986    Polites    Aug 96   Experiments with a Simple File Transfer                              Protocol for Radio Links using Enhanced                              Trivial File Transfer Protocol (ETFTP)This document is a description of the Enhanced Trivial File TransferProtocol (ETFTP). This protocol is an experimental implementation of theNETwork BLock Transfer Protocol (NETBLT),RFC 998 [1], as a filetransfer application program.  This memo defines an ExperimentalProtocol for the Internet community.1985    De Winter  Aug 96   SMTP Service Extension                              for Remote Message Queue StartingThis memo defines an extension to the SMTP service whereby an SMTPclient and server may interact to give the server an opportunity tostart the processing of its queues for messages to go to a given host.[STANDARDS-TRACK]1984    I.A.B.     Aug 96   IAB and IESG Statement on Cryptographic                              Technology and the InternetThe Internet Architecture Board (IAB) and the Internet EngineeringSteering Group (IESG), the bodies which oversee architecture andstandards for the Internet, are concerned by the need for increasedprotection of international commercial transactions on the Internet, andby the need to offer all Internet users an adequate degree of privacy.This memo provides information for the Internet community.  This memodoes not specify an Internet standard of any kind.1983    Malkin     Aug 96   Internet Users' GlossaryThere are many networking glossaries in existence.  This glossaryconcentrates on terms which are specific to the Internet.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1982    Elz        Aug 96   Serial Number ArithmeticThe DNS has long relied upon serial number arithmetic, a concept whichhas never really been defined, certainly not in an IETF document, thoughwhich has been widely understood.  This memo supplies the missingdefinition.  It is intended to updateRFC1034 andRFC1035.  [STANDARDS-TRACK]Elliott                      Informational                      [Page 4]

RFC 1999                  Summary of 1900-1999              January 19971981    McCann     Aug 96   Path MTU Discovery for IP version 6This document describes Path MTU Discovery for IP version 6.  It islargely derived fromRFC 1191, which describes Path MTU Discovery for IPversion 4.  [STANDARDS-TRACK]1980    Seidman    Aug 96   A Proposed Extension to HTML :                              Client-Side Image MapsThis document specifies an extension to the HTML language, referred toas "Client-Side Image Maps," which resolves some limitations.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1979    Woods      Aug 96   PPP Deflate ProtocolThis document describes the use of the PPP Deflate compression protocolfor compressing PPP encapsulated packets.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1978    Rand       Aug 96   PPP Predictor Compression ProtocolThis document describes the use of the Predictor data compressionalgorithm for compressing PPP encapsulated packets.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1977    Schryver   Aug 96   PPP BSD Compression ProtocolThis document describes the use of the Unix Compress compressionprotocol for compressing PPP encapsulated packets.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.Elliott                      Informational                      [Page 5]

RFC 1999                  Summary of 1900-1999              January 19971976    Schneider  Aug 96   PPP for Data Compression in Data                              Circuit-Terminating Equipment (DCE)This document defines a specific set of parameters for these protocolsand an LCP extension to define a standard way of using PPP for datacompression of serial data in Data Circuit-Terminating Equipment (DCE).This memo provides information for the Internet community.  This memodoes not specify an Internet standard of any kind.1975    Schremp    Aug 96   PPP Magnalink Variable Resource                              CompressionThe Magnalink Variable Resource Compression Algorithm (MVRCA) allows awide range of interoperable compression implementations whoseperformance characteristics are a function of available CPU and memoryresources.  This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1974    Friend     Aug 96   PPP Stac LZS Compression ProtocolThis document describes the use of the Stac LZS data compressionalgorithm, with single or multiple compression histories, forcompressing PPP encapsulated packets.  This memo provides informationfor the Internet community.  This memo does not specify an Internetstandard of any kind.1973    Simpson    Jun 96   PPP in Frame RelayThis document describes the use of Frame Relay for framing PPPencapsulated packets.  [STANDARDS-TRACK]1972    Crawford   Aug 96   A Method for the Transmission of IPv6                              Packets over Ethernet NetworksThis memo specifies the frame format for transmission of IPv6 [IPV6]packets and the method of forming IPv6 link-local addresses on Ethernetnetworks.  [STANDARDS-TRACK]1971    Thomson    Aug 96   IPv6 Stateless Address AutoconfigurationThis document specifies the steps a host takes in deciding how toautoconfigure its interfaces in IP version 6.  [STANDARDS-TRACK]Elliott                      Informational                      [Page 6]

RFC 1999                  Summary of 1900-1999              January 19971970    Narten     Aug 96   Neighbor Discovery for IP Version 6                              (IPv6)This document specifies the Neighbor Discovery protocol for IP Version6.  [STANDARDS-TRACK]1969    Sklower    Jun 96   The PPP DES Encryption Protocol (DESE)This document provides specific details for the use of the DES standard[5, 6] for encrypting PPP encapsulated packets.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1968    Meyer      Jun 96   The PPP Encryption Control Protocol                              (ECP)This document defines a method for negotiating data encryption over PPPlinks.  [STANDARDS-TRACK]1967    Schneider  Aug 96   PPP LZS-DCP Compression Protocol                              (LZS-DCP)This document describes the use of the Stac LZS data compressionalgorithm for compressing PPP encapsulated packets, using a DCP header[6].  This memo provides information for the Internet community.  Thismemo does not specify an Internet standard of any kind.1966    Bates      Jun 96   BGP Route Reflection                              An alternative to full mesh IBGPThis document describes the use and design of a method known as "RouteReflection" to alleviate the the need for "full mesh" IBGP.  This memodefines an Experimental Protocol for the Internet community.1965    Traina     Jun 96   Autonomous System Confederations for BGPThis document describes an extension to BGP which may be used to createa confederation of autonomous systems which is represented as one singleautonomous system to BGP peers external to the confederation.  This memodefines an Experimental Protocol for the Internet community.Elliott                      Informational                      [Page 7]

RFC 1999                  Summary of 1900-1999              January 19971964    Linn       Jun 96   The Kerberos Version 5 GSS-API MechanismThis specification defines protocols, procedures, and conventions to beemployed by peers implementing the Generic Security Service ApplicationProgram Interface (as specified in RFCs 1508 and 1509) when usingKerberos Version 5 technology (as specified inRFC 1510).  [STANDARDS-TRACK]1963    Schneider  Aug 96   PPP Serial Data Transport Protocol                              (SDTP)This document describes a new Network level protocol (from the PPP pointof view), PPP Serial Data Transport Protocol, that providesencapsulation and an associated control protocol for transporting serialdata streams over a PPP link.  This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1962    Rand       Jun 96   The PPP Compression Control Protocol                              (CCP)This document defines a method for negotiating data compression over PPPlinks.  [STANDARDS-TRACK]1961    McMahon    Jun 96   GSS-API Authentication Method for SOCKS                              Version 5This document provides the specification for the SOCKS V5 GSS-APIauthentication protocol, and defines a GSS-API-based encapsulation forprovision of integrity, authentication and optional confidentiality.[STANDARDS-TRACK]1960    Howes      Jun 96   A String Representation of LDAP                              Search FiltersThe Lightweight Directory Access Protocol (LDAP) [1] defines a networkrepresentation of a search filter transmitted to an LDAP server.  Someapplications may find it useful to have a common way of representingthese search filters in a human-readable form.  This document defines ahuman-readable string format for representing LDAP search filters.[STANDARDS-TRACK]Elliott                      Informational                      [Page 8]

RFC 1999                  Summary of 1900-1999              January 19971959    Howes      Jun 96   An LDAP URL FormatThis document describes a format for an LDAP Uniform Resource Locatorwhich will allow Internet clients to have direct access to the LDAPprotocol.  [STANDARDS-TRACK]1958    Carpenter  Jun 96   Architectural Principles of the InternetThe Internet and its architecture have grown in evolutionary fashionfrom modest beginnings, rather than from a Grand Plan. While thisprocess of evolution is one of the main reasons for the technology'ssuccess, it nevertheless seems useful to record a snapshot of thecurrent principles of the Internet architecture. This is intended forgeneral guidance and general interest, and is in no way intended to be aformal or invariant reference model.  This memo provides information forthe Internet community.  This memo does not specify an Internet standardof any kind.1957    Nelson     Jun 96   Some Observations on Implementations                              of the Post Office Protocol (POP3)This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.1956    EngebretsonJun 96   Registration in the MIL DomainThis RFC describes the policy for the registration of second leveldomains under the ".MIL" domain.  This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1955    Hinden     Jun 96   New Scheme for Internet Routing and                              Addressing (ENCAPS) for IPNGThis paper proposes a new scheme which I believe is a good medium termsolution to the routing and address problems of the internet.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.Elliott                      Informational                      [Page 9]

RFC 1999                  Summary of 1900-1999              January 19971954    Newman     May 96   Transmission of Flow Labelled IPv4 on                              ATM Data Links Ipsilon Version 1.0This document specifies the manner for transmitting IPv4 datagrams overan ATM data link, both in a default manner and in the presence of flowlabelling via Ipsilon Flow Management Protocol [IFMP].  This documentprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1953    Newman     May 96   Ipsilon Flow Management Protocol                              Specification for IPv4 Version 1.0The Ipsilon Flow Management Protocol (IFMP), is a protocol for allowinga node to instruct an adjacent node to attach a layer 2 label to aspecified IP flow.  This document provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1952    Deutsch    May 96   GZIP file format specification                              version 4.3This specification defines a lossless compressed data format that iscompatible with the widely used GZIP utility.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1951    Deutsch    May 96   DEFLATE Compressed Data Format                              Specification version 1.3This specification defines a lossless compressed data format thatcompresses data using a combination of the LZ77 algorithm and Huffmancoding, with efficiency comparable to the best currently availablegeneral-purpose compression methods.  This memo provides information forthe Internet community.  This memo does not specify an Internet standardof any kind.1950    Deutsch    May 96   ZLIB Compressed Data Format                              Specification version 3.3This specification defines a lossless compressed data format.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.Elliott                      Informational                     [Page 10]

RFC 1999                  Summary of 1900-1999              January 19971949    Ballarde   May 96   Scalable Multicast Key DistributionThis memo provides a scalable solution to the multicast key distributionproblem.  This memo defines an Experimental Protocol for the Internetcommunity.1948    Bellovin   May 96   Defending Against Sequence Number                              AttacksIP spoofing attacks based on sequence number spoofing have become aserious threat on the Internet (CERT Advisory CA-95:01).  Whileubiquitous crypgraphic authentication is the right answer, we propose asimple modification to TCP implementations that should be a verysubstantial block to the current wave of attacks.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1947    Spinellis  May 96   Greek Character Encoding for Electronic                              Mail MessagesThis document describes a standard encoding for electronic mail [RFC822]containing Greek text and provides implementation guide-lines.  Thismemo provides information for the Internet community.  This memo doesnot specify an Internet standard of any kind.1946    Jackowski  May 96   Native ATM Support for ST2+This memo describes a working implementation which enables applicationsto directly invoke ATM services in the following environments: ATM tointernet, internet to ATM, and internet to internet across ATM.  Thismemo provides information for the Internet community.  This memo doesnot specify an Internet standard of any kind.1945    Berners-LeeMay 96   Hypertext Transfer Protocol -- HTTP/1.0The Hypertext Transfer Protocol (HTTP) is an application-level protocolwith the lightness and speed necessary for distributed, collaborative,hypermedia information systems.  This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.Elliott                      Informational                     [Page 11]

RFC 1999                  Summary of 1900-1999              January 19971944    Bradner    May 96   Benchmarking Methodology for Network                              Interconnect DevicesThis document discusses and defines a number of tests that may be usedto describe the performance characteristics of a network interconnectingdevice.  This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1943    Jennings   May 96   Building an X.500 Directory Service                              in the USThis document provides definition and recommends considerations thatmust be undertaken to operate a X.500 Directory Service in the UnitedStates.  This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1942    Raggett    May 96   HTML TablesThis specification extends HTML to support a wide variety of tables.This memo defines an Experimental Protocol for the Internet community.1941    Sellers    May 96   Frequently Asked Questions for SchoolsThe goal of this FYI document, produced by the Internet SchoolNetworking (ISN) group in the User Services Area of the InternetEngineering Task Force (IETF), is to act as an introduction to theInternet for faculty, administration, and other school personnel inprimary and secondary schools.  This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1940    Estrin     May 96   Source Demand Routing: Packet Format and                              Forwarding Specification (Version 1).The purpose of SDRP is to support source-initiated selection of routesto complement the route selection provided by existing routing protocolsfor both inter-domain and intra-domain routes.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.Elliott                      Informational                     [Page 12]

RFC 1999                  Summary of 1900-1999              January 19971939    Myers      May 96   Post Office Protocol - Version 3The Post Office Protocol - Version 3 (POP3) is intended to permit aworkstation to dynamically access a maildrop on a server host in auseful fashion.  [STANDARDS-TRACK]1938    Haller     May 96   A One-Time Password SystemThis document describes a one-time password authentication system (OTP).[STANDARDS-TRACK]1937    Rekhter    May 96   "Local/Remote" Forwarding Decision in                              Switched Data Link SubnetworksThis document describes extensions to the IP architecture that relaxesthese constraints, thus enabling the full utilization of the servicesprovided by SVC-based Data Link subnetworks.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1936    Touch     Apr 96    Implementing the Internet Checksum in                              HardwareThis memo presents a techniques for efficiently implementing theInternet Checksum in hardware. It includes PLD code for programming asingle, low cost part to perform checksumming at 1.26 Gbps.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1935    Quarterman Apr 96   What is the Internet, Anyway?This memo provides information for the Internet community.  This memodoes not specify an Internet standard of any kind.1934    Smith      Apr 96   Ascend's Multilink Protocol Plus (MP+)This document proposes an extension to the PPP Multilink Protocol (MP)[1]. Multilink Protocol Plus (MP+) is a new control protocol formanaging multiple data links that are bundled by MP.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.Elliott                      Informational                     [Page 13]

RFC 1999                  Summary of 1900-1999              January 19971933    Gilligan   Apr 96   Transition Mechanisms for IPv6 Hosts                              and RoutersThis document specifies IPv4 compatibility mechanisms that can beimplemented by IPv6 hosts and routers.  [STANDARDS-TRACK]1932    Cole       Apr 96   IP over ATM: A Framework DocumentIt is hoped that this document, in classifying ATM approaches and issueswill help to focus the IP over ATM working group's direction.This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1931    Brownell   Apr 96   Dynamic RARP Extensions for                              Automatic Network Address AcquisitionThis memo describes extensions to the Reverse Address ResolutionProtocol (RARP [2]) and called Dynamic RARP (DRARP, pronounced D-RARP).This memo provides information for the Internet community.  This memodoes not define an Internet standard of any kind.1930    Hawkinson  Mar 96   Guidelines for creation, selection, and                              registration of an Autonomous System (AS)This memo discusses when it is appropriate to register and utilize anAutonomous System (AS), and lists criteria for such.  This documentspecifies an Internet Best Current Practices for the Internet Community,and requests discussion and suggestions for improvements.1929    Leech      Mar 96   Username/Password Authentication for                              SOCKS V5The protocol specification for SOCKS Version 5 specifies a generalizedframework for the use of arbitrary authentication protocols in theinitial socks connection setup. This document describes one of thoseprotocols, as it fits into the SOCKS Version 5 authentication"subnegotiation".  [STANDARDS-TRACK]Elliott                      Informational                     [Page 14]

RFC 1999                  Summary of 1900-1999              January 19971928    Leech      Mar 96   SOCKS Protocol Version 5This memo describes a protocol that is an evolution of the previousversion of the protocol, version 4 [1]. This new protocol stems fromactive discussions and prototype implementations.  [STANDARDS-TRACK]1927    Rogers     Apr 96   Suggested Additional MIME Types for                              Associating DocumentsSeven new types of MIME types are suggested in this document.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1926    Eriksson   Apr 96   An Experimental Encapsulation of IP                              Datagrams on Top of ATMThis RFC describes a method of encapsulating IP datagrams on top ofAcoustical Transmission Media (ATM).  This is a non-recommendedstandard.  This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1925    Callon     Apr 96   The Twelve Networking TruthsThis memo documents the fundamental truths of networking for theInternet community. This memo does not specify a standard, except in thesense that all standards must implicitly follow the fundamental truths.This memo provides information for the Internet community.  This memodoes not specify an Internet standard of any kind.1924    Elz        Apr 96   A Compact Representation of IPv6 AddressesThis document specifies a more compact representation of IPv6 addresses,which permits encoding in a mere 20 bytes.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.Elliott                      Informational                     [Page 15]

RFC 1999                  Summary of 1900-1999              January 19971923    Halpern    Mar 96   RIPv1 Applicability Statement for                              Historic StatusRIP Version 1 [RFC-1058] has been declared an historic document.  ThisApplicability statement provides the supporting motivation for thatdeclaration.  The primary reason, as described below, is the Classfulnature of RIPv1.  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1922    Zhu        Mar 96   Chinese Character Encoding for Internet                              MessagesThis memo describes methods of transporting Chinese characters inInternet services which transport text, such as electronic mail[RFC-822], network news [RFC-1036], telnet [RFC-854] and the World WideWeb [RFC-1866].  This memo provides information for the Internetcommunity.  It does not specify an Internet standard.1921    Dujonc     Mar 96   TNVIP ProtocolThe goal of this document specifies a Telnet profile to support VIPterminal emulation allowing the access to the BULL hosts applicationsthrough a TCP/IP network.  This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1920    I.A.B.     Mar 96   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]1919    Chatel     Mar 96   Classical versus Transparent IP ProxiesThis document explains "classical" and "transparent" proxy techniquesand attempts to provide rules to help determine when each proxy systemmay be used without causing problems.  This memo provides informationfor the Internet community.  This memo does not specify an Internetstandard of any kind.Elliott                      Informational                     [Page 16]

RFC 1999                  Summary of 1900-1999              January 19971918    Rekhter    Feb 96   Address Allocation for Private InternetsThis document describes address allocation for private internets.  Thisdocument specifies an Internet Best Current Practices for the InternetCommunity, and requests discussion and suggestions for improvements.1917    Nesser     Feb 96   An Appeal to the Internet Community to                              Return Unused IP Networks (Prefixes)                              to the IANAThis document is an appeal to the Internet community to return unusedaddress space, i.e. any block of consecutive IP prefixes, to theInternet Assigned Numbers Authority (IANA) or any of the delegatedregistries, for reapportionment.  This document specifies an InternetBest Current Practices for the Internet Community, and requestsdiscussion and suggestions for improvements.1916    Berkowitz  Feb 96   Enterprise Renumbering: Experience and                              Information SolicitationBecause of the urgent need for, and substantial difficulty in,renumbering IP networks, the PIER working group is compiling a series ofdocuments to assist sites in their renumbering efforts.  The intent ofthese documents is to provide both educational and practical informationto the Internet community.  This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1915    Kastenholz Feb 96   Variance for The PPP Connection Control                              Protocol and The PPP Encryption Control                              ProtocolThe PPP Working group has developed two protocols, one to controlcompression on PPP links; the Compression Control Protocol (CCP),documented indraft-ietf-pppext-compression-04.txt. The second is theEncryption Control Protocol (ECP), used to control encryption on seriallinks, documented indraft-ietf-pppext-encryption-03.txt.  This documentspecifies an Internet Best Current Practices for the Internet Community,and requests discussion and suggestions for improvements.Elliott                      Informational                     [Page 17]

RFC 1999                  Summary of 1900-1999              January 19971914    Faltstrom  Feb 96   How to Interact with a Whois++ MeshIn the Whois++ architecture [Deutsch94],[Weider94], mesh traversal isdone by the client, since each server 'refers' the client to the nextappropriate server(s).  [STANDARDS-TRACK]1913    Weider     Feb 96   Architecture of the Whois++ Index ServiceThe authors describe an architecture for indexing in distributeddatabases, and apply this to the WHOIS++ protocol.  [STANDARDS-TRACK]1912    Barr       Feb 96   Common DNS Operational and Configuration                              ErrorsThis memo describes errors often found in both the operation of DomainName System (DNS) servers, and in the data that these DNS serverscontain.  This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1911    Vaudreuil  Feb 96   Voice Profiule of Internet MailThe following document is a profile of the Internet standard MIME andESMTP protocols for use as a digital voice networking protocol.  Thismemo defines an Experimental Protocol for the Internet community.1910    Waters     Feb 96   User-based Security Model for SNMPv2In this administrative framework, a security model defines themechanisms used to achieve an administratively-defined level of securityfor protocol interactions.  Although many such security models might bedefined, it is the purpose of this document, User-based Security Modelfor SNMPv2, to define the first, and, as of this writing, only, securitymodel for this administrative framework.  This memo defines anExperimental Protocol for the Internet community.1909    McClogherieFeb 96   An Administrative Infrastructure for                              SNMPv2It is the purpose of this document, An Administrative Infrastructure forSNMPv2, to define an administrative framework which realizes effectivemanagement in a variety of configurations and environments.  This memodefines an Experimental Protocol for the Internet community.Elliott                      Informational                     [Page 18]

RFC 1999                  Summary of 1900-1999              January 19971908    Case       Jan 96   Coexistence between Version 1 and                              Version 2 of the Internet-standard                              Network Management FrameworkThe purpose of this document is to describe coexistence between version2 of the Internet-standard Network Management Framework [1-6], termedthe SNMP version 2 framework (SNMPv2), and the original Internet-standard Network Management Framework (SNMPv1>.  [STANDARDS-TRACK]1907    Case       Jan 96   Management Information Base for Version                              2 of the Simple Network Management                              Protocol (SNMPv2)It is the purpose of this document to define managed objects whichdescribe the behavior of a SNMPv2 entity.  [STANDARDS-TRACK]1906    Case       Jan 96   Transport Mappings for Version 2 of the                              Simple Network Management Protocol (SNMPv2)It is the purpose of this document to define how the SNMPv2 maps onto aninitial set of transport domains.  [STANDARDS-TRACK]1905    Case       Jan 96   Protocol Operations for Version 2 of the                              Simple Network Management Protocol (SNMPv2)It is the purpose of this document, Protocol Operations for SNMPv2, todefine the operations of the protocol with respect to the sending andreceiving of the PDUs.  [STANDARDS-TRACK]1904    Case       Jan 96   Conformance Statements for Version 2 of                              the Simple Network Management Protocol                              (SNMPv2)It may be useful to define the acceptable lower-bounds ofimplementation, along with the actual level of implementation achieved.It is the purpose of this document to define the notation used for thesepurposes.  [STANDARDS-TRACK]Elliott                      Informational                     [Page 19]

RFC 1999                  Summary of 1900-1999              January 19971903    Case       Jan 96   Textual Conventions for Version 2 of the                              Simple Network Management Protocol (SNMPv2)It is the purpose of this document to define the initial set of textualconventions available to all MIB modules.  [STANDARDS-TRACK]1902    Case       Jan 96   Structure of Management Information for                              Version 2 of the Simple Network                              Management Protocol (SNMPv2)It is the purpose of this document, the Structure of ManagementInformation (SMI), to define that adapted subset, and to assign a set ofassociated administrative values.  [STANDARDS-TRACK]1901    Case       Jan 96   Introduction to Community-based SNMPv2The purpose of this document is to define the Community-basedAdministrative Framework for the SNMP version 2 framework (SNMPv2).This document specifies an Experimental protocol for the Internetcommunity.1900    Carpenter  Feb 96   Renumbering Needs WorkHosts in an IP network are identified by IP addresses, and the IPaddress prefixes of subnets are advertised by routing protocols.  Achange in such IP addressing information associated with a host orsubnet is known as "renumbering".  This memo provides information forthe Internet community.  This memo does not specify an Internet standardof any kind.Security Considerations   Security issues are not discussed in this memo.Author's Address   Josh Elliott   University of Southern California   Information Sciences Institute   4676 Admiralty Way   Marina del Rey, CA 90292   Phone:  (310) 822-1511   EMail: elliott@isi.eduElliott                      Informational                     [Page 20]