Movatterモバイル変換

Network Working Group                                           A. RamosRequest for Comments: 2299                                           ISICategory: Informational                                     January 1999Request for Comments Summary                         RFC Numbers 2200-2299Status of This Memo   This RFC is a slightly annotated list of the 100 RFCs fromRFC 2200   through RFCs 2299.  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.Copyright Notice   Copyright (C) The Internet Society (1999).  All Rights Reserved.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---     ------          ----            -----2299    Ramos         Jan 1999        Request for Comments SummaryThis memo.2298    Fajman        Mar 1998        An Extensible Message FormatThis memo defines a MIME content-type that may be used by a mail useragent (UA) or electronic mail gateway to report the disposition of amessage after it has been sucessfully delivered to a recipient.[STANDARDS-TRACK]Ramos                        Informational                      [Page 1]

RFC 2299                  Summary of 2200-2299              January 19992297    Newman        Mar 1998        Ipsilon's General Switch                                        Management Protocol                                        Specification Version 2.0This memo specifies enhancements to the General Switch ManagementProtocol (GSMP) [RFC1987].  This memo provides information for theInternet community.  It does not specify an Internet standard of anykind.2296    Holtman       Mar 1998        HTTP Remote Variant Selection                                        Algorithm -- RVSA/1.0HTTP allows web site authors to put multiple versions of the sameinformation under a single URL.  Transparent content negotiation is amechanism for automatically selecting the best version when the URL isaccessed.  A remote variant selection algorithm can be used to speed upthe transparent negotiation process. This document defines the remotevariant selection algorithm with the version number 1.0.  This memodefines an Experimental Protocol for the Internet community.  It doesnot specify an Internet standard of any kind.  Discussion andsuggestions for improvement are requested.2295    Holtman       Mar 1998        Transparent Content                                        Negotiation in HTTPHTTP allows web site authors to put multiple versions of the sameinformation under a single URL.  Transparent content negotiation is anextensible negotiation mechanism, layered on top of HTTP, forautomatically selecting the best version when the URL is accessed.  Thisenables the smooth deployment of new web data formats and markup tags.This memo defines an Experimental Protocol for the Internet community.It does not specify an Internet standard of any kind.  Discussion andsuggestions for improvement are requested.2294    Kille         Mar 1998        Representing the O/R Address                                        hierarchy in the X.500                                        Directory Information TreeThis document defines a representation of the O/R Address hierarchy inthe Directory Information Tree.  [STANDARDS-TRACK]Ramos                        Informational                      [Page 2]

RFC 2299                  Summary of 2200-2299              January 19992293    Kille         Mar 1998        Representing Tables and                                        Subtrees in the X.500 DirectoryThis document defines techniques for representing two types ofinformation mapping in the OSI Directory: Mapping from a key to a value(or set of values), as might be done in a table lookup, and mapping froma distinguished name to an associated value (or values), where thevalues are not defined by the owner of the entry.  This is achieved byuse of a directory subtree.  [STANDARDS-TRCK]2292    Stevens       Feb 1998        Advanced Sockets API for IPv6The current document defines some the "advanced" features of the socketsAPI that are required for applications to take advantage of additionalfeatures of IPv6.  This memo provides information for the Internetcommunity.  It does not specify an Internet standard of any kind.2291    Slein         Feb 1998        Requirements for a Distributed                                        Authoring and Versioning                                        Protocol for the World Wide WebThis document presents a list of features in the form of requirementsfor a Web Distributed Authoring and Versioning protocol which, ifimplemented, would improve the efficiency of common remote editingoperations, provide a locking mechanism to prevent overwrite conflicts,improve link management support between non-HTML data types, provide asimple attribute-value metadata facility, provide for the creation andreading of container data types, and integrate versioning into the WWW.This memo provides information for the Internet community.  It does notspecify an Internet standard of any kind.2290    Solomon       Feb 1998        Mobile-IPv4 Configuration                                        Option for PPP IPCPMobile IP [RFC 2002] defines media-independent procedures by which aMobile Node can maintain existing transport and application-layerconnections despite changing its point-of-attachment to the Internet andwithout changing its IP address.  PPP [RFC 1661] provides a standardmethod for transporting multi-protocol packets over point-to-pointlinks.  As currently specified, Mobile IP Foreign Agents which supportMobile Node connections via PPP can do so only by first assigning uniqueaddresses to those Mobile Nodes, defeating one of the primary advantagesof Foreign Agents.  This documents corrects this problem by defining theMobile-IPv4 Configuration Option to the Internet Protocol ControlProtocol (IPCP) [RFC 1332].  Using this option, two peers canRamos                        Informational                      [Page 3]

RFC 2299                  Summary of 2200-2299              January 1999communicate their support for Mobile IP during the IPCP phase of PPP.Familiarity with Mobile IP [RFC 2002], IPCP [RFC 1332], and PPP [RFC1661] is assumed.  [STANDARDS-TRACK]2289    Haller        Feb 1998        A One-Time Password SystemThis document describes a one-time password authentication system (OTP).The system provides authentication for system access (login) and otherapplications requiring authentication that is secure against passiveattacks based on replaying captured reusable passwords.  [STANDARDS-TRACK]2288    Lynch         Feb 1998        Using Existing Bibliographic                                        Identifiers as Uniform                                        Resource NamesThis document discusses how three major bibliographic identifiers (theISBN, ISSN and SICI) can be supported within the URN framework and thecurrently proposed syntax for URNs.  This memo provides information forthe Internet community.  It does not specify an Internet standard of anykind.2287    Krupczak      Feb 1998        Definitions of System-Level                                        Managed Objects for ApplicationsThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it describes a basic set of managed objects for fault,configuration and performance management of applications from a systemsperspective.  [STANDARDS-TRACK]2286    Kapp          Feb 1998        Test Cases for HMAC-RIPEMD160                                        and HMAC-RIPEMD128This document provides two sets of test cases for HMAC-RIPEMD160 andHMAC-RIPEMD128.  This memo provides information for the Internetcommunity.  It does not specify an Internet standard of any kind.Ramos                        Informational                      [Page 4]

RFC 2299                  Summary of 2200-2299              January 19992285    Mandeville    Feb 1998        Benchmarking Terminology for                                        LAN Switching DevicesThis document is intended to provide terminology for the benchmarking oflocal area network (LAN) switching devices.  It extends the terminologyalready defined for benchmarking network interconnect devices in RFCs1242 and 1944 to switching devices.This memo provides information forthe Internet community.  It does not specify an Internet standard of anykind.2284    Blunk         Mar 1998        PPP Extensible Authentication                                        Protocol (EAP)The Point-to-Point Protocol (PPP) provides a standard method fortransporting multi-protocol datagrams over point-to-point links.  PPPalso defines an extensible Link Control Protocol, which allowsnegotiation of an Authentication Protocol for authenticating its peerbefore allowing Network Layer protocols to transmit over the link.  Thisdocument defines the PPP Extensible Authentication Protocol.[STANDARDS-TRACK]2283    Bates         Feb 1998        Multiprotocol Extensions for                                        BGP-4This document defines extensions to BGP-4 to enable it to carry routinginformation for multiple Network Layer protocols (e.g., IPv6, IPX,etc...). The extensions are backward compatible - a router that supportsthe extensions can interoperate with a router that doesn't support theextensions.  [STANDARDS-TRACK]2282    Galvin        Feb 1998        IAB and IESG Selection,                                        Confirmation, and Recall                                        Process: Operation of the                                        Nominating and Recall                                        CommitteesThe process by which the members of the IAB and IESG are selected,confirmed, and recalled is specified.  This document specifies anInternet Best Current Practices for the Internet Community, and requestsdiscussion and suggestions for improvements.Ramos                        Informational                      [Page 5]

RFC 2299                  Summary of 2200-2299              January 19992281    Li            Mar 1998        Cisco Hot Standby Router                                        Protocol (HSRP)The memo specifies the Hot Standby Router Protocol (HSRP).  The goal ofthe protocol is to allow hosts to appear to use a single router and tomaintain connectivity even if the actual first hop router they are usingfails.  This memo provides information for the Internet community.  Itdoes not specify an Internet standard of any kind.2280    Alaettinoglu  Jan 1998        Routing Policy Specification                                        Language (RPSL)This memo is the reference document for the Routing Policy SpecificationLanguage (RPSL). RPSL allows a network operator to be able to specifyrouting policies at various levels in the Internet hierarchy; forexample at the Autonomous System (AS) level.  At the same time, policiescan be specified with sufficient detail in RPSL so that low level routerconfigurations can be generated from them.  RPSL is extensible; newrouting protocols and new protocol features can be introduced at anytime.  [STANDARDS-TRACK]2279    Yergeau       Jan 1998        UTF-8, a transformation format                                        of ISO 10646UTF-8, the object of this memo, has the characteristic of preserving thefull US-ASCII range, providing compatibility with file systems, parsersand other software that rely on US-ASCII values but are transparent toother values. This memo updates and replacesRFC 2044, in particularaddressing the question of versions of the relevant standards.[STANDARDS-TRACK]2278    Freed         Jan 1998        IANA Charset                                        Registration ProceduresMIME [RFC-2045,RFC-2046,RFC-2047,RFC-2184] and various other modernInternet protocols are capable of using many different charsets. This inturn means that the ability to label different charsets is essential.This registration procedure exists solely to associate a specific nameor names with a given charset and to give an indication of whether ornot a given charset can be used in MIME text objects.  This documentspecifies an Internet Best Current Practices for the Internet Community,and requests discussion and suggestions for improvements.Ramos                        Informational                      [Page 6]

RFC 2299                  Summary of 2200-2299              January 19992277    Alvestrand    Jan 1998        IETF Policy on Character Sets                                        and LanguagesThis document is the current policies being applied by the InternetEngineering Steering Group (IESG) towards the standardization efforts inthe Internet Engineering Task Force (IETF) in order to help Internetprotocols fulfill these requirements.  This document specifies anInternet Best Current Practices for the Internet Community, and requestsdiscussion and suggestions for improvements.2276    Sollins       Jan 1998        Architectural Principles of                                        Uniform Resource Name ResolutionThis document addresses the issues of the discovery of URN (UniformResource Name) resolver services that in turn will directly translateURNs into URLs (Uniform Resource Locators) and URCs (Uniform ResourceCharacteristics).  This memo provides information for the Internetcommunity.  It does not specify an Internet standard of any kind.2275    Wijnen        Jan 1998        View-based Access Control                                        Model (VACM) for the                                        Simple Network Management                                        Protocol (SNMP)This document describes the View-based Access Control Model for use inthe SNMP architecture [RFC2261].  It defines the Elements of Procedurefor controlling access to management information.  This document alsoincludes a MIB for remotely managing the configuration parameters forthe View-based Access Control Model.  [STANDARDS-TRACK]2274    Blumenthal    Jan 1998        User-based Security Model                                        (USM) for version 3 of the                                        Simple Network Management                                        Protocol (SNMPv3)This document describes the User-based Security Model (USM) for SNMPversion 3 for use in the SNMP architecture [RFC2261].  It defines theElements of Procedure for providing SNMP message level security.  Thisdocument also includes a MIB for remotely monitoring/managing theconfiguration parameters for this Security Model.  [STANDARDS-TRACK]Ramos                        Informational                      [Page 7]

RFC 2299                  Summary of 2200-2299              January 19992273    Levi          Jan 1998        SNMPv3 ApplicationsThis memo describes five types of SNMP applications which make use of anSNMP engine as described in [RFC2261].  The types of applicationdescribed are Command Generators, Command Responders, NotificationOriginators, Notification Receivers, and Proxy Forwarders.  This memoalso defines MIB modules for specifying targets of managementoperations, for notification filtering, and for proxy forwarding.[STANDARDS-TRACK]2272    Case          Jan 1998        Message Processing and                                        Dispatching for the Simple                                        Network Management Protocol                                        (SNMP)This document describes the Message Processing and Dispatching for SNMPmessages within the SNMP architecture [RFC2271].  It defines theprocedures for dispatching potentially multiple versions of SNMPmessages to the proper SNMP Message Processing Models, and fordispatching PDUs to SNMP applications.  This document also describes oneMessage Processing Model - the SNMPv3 Message Processing Model.[STANDARDS-TRACK]2271    Harrington    Jan 1998        An Architecture for Describing                                        SNMP Management FrameworksThis document describes an architecture for describing SNMP ManagementFrameworks.  The architecture is designed to be modular to allow theevolution of the SNMP protocol standards over time.  [STANDARDS-TRACK]2270    Stewart       Jan 1998        Using a Dedicated AS for Sites                                        Homed to a Single ProviderWith the increased growth of the Internet, the number of customers usingBGP4 has grown significantly.RFC1930 outlines a set of guidelines forwhen one needs and should use an AS. However, the customer and serviceprovider (ISP) are left with a problem as a result of this in that whilethere is no need for an allocated AS under the guidelines, certainconditions make the use of BGP4 a very pragmatic and perhaps only way toconnect a customer homed to a single ISP.  This paper proposes asolution to this problem in line with recommendations set forth inRFC1930.  This memo provides information for the Internet community.  Itdoes not specify an Internet standard of any kind.Ramos                        Informational                      [Page 8]

RFC 2299                  Summary of 2200-2299              January 19992269    Armitage      Jan 1998        Using the MARS Model in                                        non-ATM NBMA NetworksThis document is intended to state the obvious equivalences, and explainthe less obvious implications.  This memo provides information for theInternet community.  It does not specify an Internet standard of anykind.2268    Rivest        Mar 1998        A Description of the RC2(r)                                        Encryption AlgorithmThis memo describes a conventional (secret-key) block encryptionalgorithm, called RC2, which may be considered as a proposal for a DESreplacement.  This memo provides information for the Internet community.It does not specify an Internet standard of any kind.2267    Ferguson      Jan 1998        Network Ingress Filtering:                                        Defeating Denial of Service                                        Attacks which employ                                        IP Source Address SpoofingThis paper discusses a simple, effective, and straightforward method forusing ingress traffic filtering to prohibit DoS attacks which use forgedIP addresses to be propagated from 'behind' an Internet ServiceProvider's (ISP) aggregation point.  This memo provides information forthe Internet community.  It does not specify an Internet standard of anykind.2266    Flick         Jan 1998        Definitions of Managed Objects                                        for IEEE 802.12 Repeater DevicesThis 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 network repeaters based onIEEE 802.12.  [STANDARDS-TRACK]Ramos                        Informational                      [Page 9]

RFC 2299                  Summary of 2200-2299              January 19992265    Wijnen        Jan 1998        View-based Access Control                                        Model (VACM) for the                                        Simple Network Management                                        Protocol (SNMP)This document describes the View-based Access Control Model for use inthe SNMP architecture [RFC2261].  It defines the Elements of Procedurefor controlling access to management information.  This document alsoincludes a MIB for remotely managing the configuration parameters forthe View-based Access Control Model.  [STANDARDS-TRACK]2264    Blumenthal    Jan 1998        User-based Security Model                                        (USM) for version 3 of the                                        Simple Network Management                                        Protocol (SNMPv3)This document describes the User-based Security Model (USM) for SNMPversion 3 for use in the SNMP architecture [RFC2261].  It defines theElements of Procedure for providing SNMP message level security.  Thisdocument also includes a MIB for remotely monitoring/managing theconfiguration parameters for this Security Model.  [STANDARDS-TRACK]2263    Levi          Jan 1998        SNMPv3 ApplicationsThis memo describes five types of SNMP applications which make use of anSNMP engine as described in [RFC2261].  The types of applicationdescribed are Command Generators, Command Responders, NotificationOriginators, Notification Receivers, and Proxy Forwarders.  This memoalso defines MIB modules for specifying targets of managementoperations, for notification filtering, and for proxy forwarding.[STANDARDS-TRACK]2262    Case          Jan 1998        Message Processing and                                        Dispatching for the Simple                                        Network Management Protocol                                        (SNMP)This document describes the Message Processing and Dispatching for SNMPmessages within the SNMP architecture [RFC2261].  It defines theprocedures for dispatching potentially multiple versions of SNMPmessages to the proper SNMP Message Processing Models, and fordispatching PDUs to SNMP applications.  This document also describes oneMessage Processing Model - the SNMPv3 Message Processing Model.[STANDARDS-TRACK]Ramos                        Informational                     [Page 10]

RFC 2299                  Summary of 2200-2299              January 19992261    Harrington    Jan 1998        An Architecture for Describing                                        SNMP Management FrameworksThis document describes an architecture for describing SNMP ManagementFrameworks.  The architecture is designed to be modular to allow theevolution of the SNMP protocol standards over time.  [STANDARDS-TRACK]2260    Bates         Jan 1998        Scalable Support for                                        Multi-homed Multi-provider                                        ConnectivityThis document describes addressing and routing strategies for multi-homed enterprises attached to multiple Internet Service Providers (ISPs)that are intended to reduce the routing overhead due to theseenterprises in the global Internet routing system.  This memo providesinformation for the Internet community.  It does not specify an Internetstandard of any kind.2259    Elliott       Jan 1998        Simple Nomenclator Query                                        Protocol (SNQP)The Simple Nomenclator Query Protocol (SNQP) allows a client tocommunicate with a descriptive name service or other relational-stylequery service.  This memo provides information for the Internetcommunity.  It does not specify an Internet standard of any kind2258    Ordille       Jan 1998        Internet Nomenclator ProjectThe goal of the Internet Nomenclator Project is to integrate thehundreds of publicly available CCSO servers from around the world.  Thisdocument provides an overview of the Nomenclator system, describes howto register a CCSO server in the Internet Nomenclator Project, and howto use the Nomenclator search engine to find people on the Internet.This memo provides information for the Internet community.  It does notspecify an Internet standard of any kind.2257    Daniele       Jan 1998        Agent Extensibility (AgentX)                                        Protocol Version 1This memo defines a standardized framework for extensible SNMP agents.It defines processing entities called master agents and subagents, aprotocol (AgentX) used to communicate between them, and the elements ofprocedure by which the extensible agent processes SNMP protocolmessages.  [STANDARDS-TRACK]Ramos                        Informational                     [Page 11]

RFC 2299                  Summary of 2200-2299              January 19992256    Wahl          Dec 1997        A Summary of the X.500(96)                                          User Schema for use with LDAPv3This document provides an overview of the attribute types and objectclasses defined by the ISO and ITU-T committees in the X.500 documents,in particular those intended for use by directory clients.  [STANDARDS-TRACK]2255    Howes         Dec 1997        The LDAP URL FormatThis document describes a format for an LDAP Uniform Resource Locator.[STANDARDS-TRACK]2254    Howes         Dec 1997        The String Representation of                                        LDAP Search FiltersThis document defines a human-readable string format for representingLDAP search filters.  [STANDARDS-TRACK]2253    Wahl          Dec 1997        Lightweight Directory Access                                        Protocol (v3): UTF-8 String                                        Representation of                                        Distinguished NamesThis specification defines the string format for representing names,which is designed to give a clean representation of commonly useddistinguished names, while being able to represent any distinguishedname.  [STANDARDS-TRACK]2252    Wahl          Dec 1997        Lightweight Directory Access                                        Protocol (v3): Attribute                                        Syntax DefinitionsThis document defines a set of syntaxes for LDAPv3, and the rules bywhich attribute values of these syntaxes are represented as octetstrings for transmission in the LDAP protocol.  [STANDARDS-TRACK]Ramos                        Informational                     [Page 12]

RFC 2299                  Summary of 2200-2299              January 19992251    Wahl          Dec 1997        Lightweight Directory Access                                        Protocol (v3)The protocol described in this document is designed to provide access todirectories supporting the X.500 models, while not incurring theresource requirements of the X.500 Directory Access Protocol (DAP).[STANDARDS-TRACK]2250    Hoffman       Jan 1998        RTP Payload Format for                                        MPEG1/MPEG2 VideoThis memo describes a packetization scheme for MPEG video and audiostreams.  [STANDARDS-TRACK]2249    Freed         Jan 1998        Mail Monitoring MIBThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.Specifically, this memo extends the basic Network Services MonitoringMIB [8] to allow monitoring of Message Transfer Agents (MTAs). It mayalso be used to monitor MTA components within gateways.  [STANDARDS-TRACK]2248    Freed         Jan 1998        Network Services Monitoring MIBThis MIB may be used on its own for any application, and for most simpleapplications this will suffice.  This MIB is also designed to serve as abuilding block which can be used in conjunction with application-specific monitoring and management.  [STANDARDS-TRACK]2247    Kille         Jan 1998        Using Domains in LDAP/X.500                                        Distinguished NamesThis document defines an algorithm by which a name registered with theInternet Domain Name Service [2] can be represented as an LDAPdistinguished name.  [STANDARDS-TRACK]Ramos                        Informational                     [Page 13]

RFC 2299                  Summary of 2200-2299              January 19992246    Dierks        Jan 1999        The TLS Protocol Version 1.0This document specifies Version 1.0 of the Transport Layer Security(TLS) protocol. The TLS protocol provides communications privacy overthe Internet. The protocol allows client/server applications tocommunicate in a way that is designed to prevent eavesdropping,tampering, or message forgery.  [STANDARDS-TRACK]2245    Newman        Nov 1997        Anonymous SASL MechanismAs plaintext login commands are not permitted in new IETF protocols, anew way to provide anonymous login is needed within the context of theSASL [SASL] framework.  [STANDARDS-TRACK]2244    Newman        Nov 1997        ACAP -- Application                                        Configuration Access ProtocolThe Application Configuration Access Protocol (ACAP) is designed tosupport remote storage and access of program option, configuration andpreference information.  [STANDARDS-TRACK]2243    Metz          Nov 1997        OTP Extended ResponsesThis document provides a specification for a type of response to an OTP[RFC 1938] challenge that carries explicit indication of the response'sencoding.  This document also provides a specification for a responsethat allows an OTP generator to request that a server re-initialize asequence and change parameters such as the secret pass phrase.[STANDARDS-TRACK]2242    Droms         Nov 1997        NetWare/IP Domain Name and                                        InformationThis document defines options that carry NetWare/IP domain name andNetWare/IP sub-options to DHCP clients.  [STANDARDS-TRACK]Ramos                        Informational                     [Page 14]

RFC 2299                  Summary of 2200-2299              January 19992241    Provan        Nov 1997        DHCP Options for Novell                                        Directory ServicesThis document defines three new DHCP options for deliveringconfiguration information to clients of the Novell Directory Services.This document defines three new DHCP options for deliveringconfiguration information to clients of the Novell Directory Services.[STANDARDS-TRACK]2240    Vaughan       Nov 1997        A Legal Basis for Domain Name                                        AllocationThe purpose of this memo is to focus discussion on the particularproblems with the exhaustion of the top level domain space in theInternet and the possible conflicts that can occur when multipleorganisations are vying for the same name.  This memo providesinformation for the Internet community.  It does not specify an Internetstandard of any kind.2239    de Graaf      Nov 1997        Definitions of Managed Objects                                        for IEEE 802.3 Medium                                        Attachment Units (MAUs) using SMIv2This memo defines an portion of the Management Information Base (MIB)for use with network management protocols in the Internet community.  Inparticular, it defines objects for managing 10 and 100 Mb/second MediumAttachment Units (MAUs) based on IEEE Std 802.3Section 30, "10 & 100Mb/s Management," October 26, 1995.  [STANDARDS-TRACK]2238    Clouston      Nov 1997        Definitions of Managed Objects                                        for HPR using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it defines objects for monitoring and controlling networkdevices with HPR (High Performance Routing) capabilities.  This memoidentifies managed objects for the HPR protocol.  [STANDARDS-TRACK]2237    Tamaru        Nov 1997        Japanese Character Encoding                                        for Internet MessagesThis memo defines an encoding scheme for the Japanese Characters,describes "ISO-2022-JP-1", which is used in electronic mail [RFC-822],and network news [RFC 1036]. Also this memo provides a listing of theRamos                        Informational                     [Page 15]

RFC 2299                  Summary of 2200-2299              January 1999Japanese Character Set that can be used in this encoding scheme.  Thismemo provides information for the Internet community.  It does notspecify an Internet standard of any kind.2236    Fenner        Nov 1997        Internet Group Management                                        Protocol, Version 2This memo documents IGMPv2, used by IP hosts to report their multicastgroup memberships to routers.  It updates STD 5,RFC 1112.  [STANDARDS-TRACK]2235    Zakon         Nov 1997        Hobbes' Internet TimelineThis document presents a history of the Internet in timeline fashion,highlighting some of the key events and technologies which helped shapethe Internet as we know it today.  A growth summary of the Internet andsome associated technologies is also included.  This memo providesinformation for the Internet community.  It does not specify an Internetstandard of any kind.2234    Crocker       Nov 1997        Augmented BNF for Syntax                                        Specifications: ABNFIn the early days of the Arpanet, each specification contained its owndefinition of ABNF.  This included the email specifications,RFC733 andthenRFC822 which have come to be the common citations for definingABNF.  The current document separates out that definition, to permitselective reference.  Predictably, it also provides some modificationsand enhancements.  [STANDARDS-TRACK]2233    McCloghrie    Nov 1997        The Interfaces Group 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 NetworkInterfaces.  [STANDARDS-TRACK]Ramos                        Informational                     [Page 16]

RFC 2299                  Summary of 2200-2299              January 19992232    Clouston      Nov 1997        Definitions of Managed Objects                                        for DLUR using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it defines objects for monitoring and controlling networkdevices with DLUR (Dependent LU Requester) capabilities.  This memoidentifies managed objects for the DLUR protocol.  [STANDARDS-TRACK]2231    Freed         Nov 1997        MIME Parameter Value and                                        Encoded Word Extensions:                                        Character Sets, Languages, and                                        ContinuationsThis memo defines extensions to theRFC 2045 media type andRFC 2183disposition parameter value mechanisms.  This memo also defines anextension to the encoded words defined inRFC 2047 to allow thespecification of the language to be used for display as well as thecharacter set.  [STANDARDS-TRACK]2230    Atkinson      Nov 1997        Key Exchange Delegation Record                                        for the DNSThis note describes a mechanism whereby authorisation for one node toact as key exchanger for a second node is delegated and made availablevia the Secure DNS.  This mechanism is intended to be used only with theSecure DNS.  This memo provides information for the Internet community.It does not specify an Internet standard of any kind.2229    Faith         Oct 1997        A Dictionary Server ProtocolThe Dictionary Server Protocol (DICT) is a TCP transaction basedquery/response protocol that allows a client to access dictionarydefinitions from a set of natural language dictionary databases.  Thismemo provides information for the Internet community.  It does notspecify an Internet standard of any kind.2228    Horowitz      Oct 1997        FTP Security ExtensionsThis document defines extensions to the FTP specification STD 9, RFC959, "FILE TRANSFER PROTOCOL (FTP)" (October 1985).  [STANDARDS-TRACK]Ramos                        Informational                     [Page 17]

RFC 2299                  Summary of 2200-2299              January 19992227    Mogul         Oct 1997        Simple Hit-Metering and                                        Usage-Limiting for HTTPThis document proposes a simple extension to HTTP, using a new "Meter"header.  [STANDARDS-TRACK]2226    Smith         Oct 1997        IP Broadcast over ATM NetworksThis memo describes how the IP multicast service being developed by theIP over ATM working group may be used to support IP broadcasttransmission.  [STANDARDS-TRACK]2225    Laubach       Apr 1998        Classical IP and ARP over ATMThis memo defines an initial application of classical IP and ARP in anAsynchronous Transfer Mode (ATM) network environment configured as aLogical IP Subnetwork (LIS).  [STANDARDS-TRACK]2224    Callaghan     Oct 1997        NFS URL SchemeA new URL scheme, 'nfs' is defined.  It is used to refer to files anddirectories on NFS servers using the general URL syntax defined in RFC1738, "Uniform Resource Locators (URL)".  This memo provides informationfor the Internet community.  It does not specify an Internet standard ofany kind.2223    Postel        Oct 1997        Instructions to RFC AuthorsThis Request for Comments (RFC) provides information about thepreparation of RFCs, and certain policies relating to the publication ofRFCs.  This memo provides information for the Internet community.  Thismemo does not specify an Internet standard of any kind.2222    Myers         Oct 1997        Simple Authentication and                                        Security Layer (SASL)This document describes a method for adding authentication support toconnection-based protocols.  [STANDARDS-TRACK]Ramos                        Informational                     [Page 18]

RFC 2299                  Summary of 2200-2299              January 19992221    Gahrns        Oct 1997        IMAP4 Login ReferralsWhen dealing with large amounts of users and many IMAP4 [RFC-2060]servers, it is often necessary to move users from one IMAP4 server toanother.  Login referrals allow clients to transparently connect to analternate IMAP4 server, if their home IMAP4 server has changed.[STANDARDS-TRACK]2220    Guenther      Oct 1997        The Application/MARC Content-                                        typeThis memorandum provides a mechanism for representing objects which arefiles of Machine-Readable Cataloging records (MARC).  The MARC formatsare standards for the representation and communication of bibliographicand related information.  A MARC record contains metadata for aninformation resource following MARC format specifications.  This memoprovides information for the Internet community.  It does not specify anInternet standard of any kind.2219    Hamilton      Oct 1997        Use of DNS Aliases for Network                                        ServicesIt has become a common practice to use symbolic names (usually CNAMEs)in the Domain Name Service (DNS - [RFC-1034,RFC-1035]) to refer tonetwork services such as anonymous FTP [RFC-959] servers, Gopher [RFC-1436] servers, and most notably World-Wide Web HTTP [RFC-1945] servers.This is desirable for a number of reasons.  It provides a way of movingservices from one machine to another transparently, and a mechanism bywhich people or agents may programmatically discover that anorganization runs, say, a World-Wide Web server.  Although this approachhas been almost universally adopted, there is no standards document orsimilar specification for these commonly used names.  This documentseeks to rectify this situation by gathering together the extant'folklore' on naming conventions, and proposes a mechanism foraccommodating new protocols.  This document specifies an Internet BestCurrent Practices for the Internet Community, and requests discussionand suggestions for improvements.2218    Genovese      Oct 1997        A Common Schema for the                                        Internet White Pages ServiceThis document specifies the minimum set of core attributes of a WhitePages entry for an individual and describes how new objects with thoseattributes can be defined and published.  [STANDARDS-TRACK]Ramos                        Informational                     [Page 19]

RFC 2299                  Summary of 2200-2299              January 19992217    Clark         Oct 1997        Telnet Com Port Control OptionThis memo proposes a protocol to allow greater use of modems attached toa network for outbound dialing purposes.  This memo defines anExperimental Protocol for the Internet community.2216    Shenker       Sep 1997        Network Element Service                                        Specification TemplateThis document defines a framework for specifying services provided bynetwork elements, and available to applications, in an internetworkwhich offers multiple qualities of service. The document first providessome necessary context -- including relevant definitions and suggesteddata formats -- and then specifies a "template" which servicespecification documents should follow.  This memo provides informationfor the Internet community.  It does not specify an Internet standard ofany kind.2215    Shenker       Sep 1997        General Characterization                                        Parameters for Integrated                                        Service Network ElementsThis memo defines a set of general control and characterizationparameters for network elements supporting the IETF integrated servicesQoS control framework.  [STANDARDS-TRACK]2214    Baker         Sep 1997        Integrated Services Management                                        Information Base Guaranteed                                        Service Extensions using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets.  Inparticular, it defines objects for managing the the interface attributesdefined in the Guaranteed Service of the Integrated Services Model.[STANDARDS-TRACK]2213    Baker         Sep 1997        Integrated Services Management                                        Information Base using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets.  Inparticular, it defines objects for managing the the interface attributesdefined in the Integrated Services Model.  [STANDARDS-TRACK]Ramos                        Informational                     [Page 20]

RFC 2299                  Summary of 2200-2299              January 19992212    Shenker       Sep 1997        Specification of Guaranteed                                        Quality of ServiceThis memo describes the network element behavior required to deliver aguaranteed service (guaranteed delay and bandwidth) in the Internet.[STANDARDS-TRACK]2211    Wroclawski    Sep 1997        Specification of the                                        Controlled-Load Network                                        Element ServiceThis memo specifies the network element behavior required to deliverControlled-Load service in the Internet.  [STANDARDS-TRACK]2210    Wroclawski    Sep 1997        The Use of RSVP with IETF                                        Integrated ServicesThis note describes the use of the RSVP resource reservation protocolwith the Controlled-Load and Guaranteed QoS control services.[STANDARDS-TRACK]2209    Braden        Sep 1997        Resource ReSerVation Protocol                                        (RSVP) -- Version 1 Message                                        Processing RulesThis memo contains an algorithmic description of the rules used by anRSVP implementation for processing messages.  It is intended to clarifythe version 1 RSVP protocol specification.  This memo providesinformation for the Internet community.  It does not specify an Internetstandard of any kind.2208    Mankin        Sep 1997        Resource ReSerVation Protocol                                        (RSVP) Version 1 Applicability                                        Statement Some Guidelines on                                        DeploymentThis document describes the applicability of RSVP along with theIntegrated Services protocols and other components of resourcereservation and offers guidelines for deployment of resource reservationat this time. This memo provides information for the Internet community.It does not specify an Internet standard of any kind.Ramos                        Informational                     [Page 21]

RFC 2299                  Summary of 2200-2299              January 19992207    Berger        Sep 1997        RSVP Extensions for IPSEC Data                                        FlowsThis document presents extensions to Version 1 of RSVP.  Theseextensions permit support of individual data flows usingRFC 1826, IPAuthentication Header (AH) orRFC 1827, IP Encapsulating SecurityPayload (ESP).  [STANDARDS-TRACK]2206    Baker         Sep 1997        RSVP Management Information                                        This memo defines a portion ofThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets.  Inparticular, it defines objects for managing the Resource ReservationProtocol (RSVP) within the interface attributes defined in theIntegrated Services Model.  [STANDARDS-TRACK]2205    Braden        Sep 1997        Resource ReSerVation Protocol                                        (RSVP)--Version 1 Functional                                        SpecificationThis memo describes version 1 of RSVP, a resource reservation setupprotocol designed for an integrated services Internet.  RSVP providesreceiver-initiated setup of resource reservations for multicast orunicast data flows, with good scaling and robustness properties.[STANDARDS-TRACK]2204    Nash          Sep 1997        ODETTE File Transfer ProtocolThis memo describes a file transfer protocol to facilitate electronicdata interchange between trading partners.  This memo providesinformation for the Internet community.  It does not specify an Internetstandard of any kind.2203    Eisler        Sep 1997        RPCSEC_GSS Protocol SpecificationThis memo describes an ONC/RPC security flavor that allows RPC protocolsto access the Generic Security Services Application ProgrammingInterface (referred to henceforth as GSS-API).  [STANDARDS-TRACK]Ramos                        Informational                     [Page 22]

RFC 2299                  Summary of 2200-2299              January 19992202    Cheng         Sep 1997        Test Cases for HMAC-MD5 and                                        HMAC-SHA-1This document provides two sets of test cases for HMAC-MD5 and HMAC-SHA-1, respectively. HMAC-MD5 and HMAC-SHA-1 are two constructs of theHMAC [HMAC] message authentication function using the MD5 [MD5] hashfunction and the SHA-1 [SHA] hash function.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.2201    Ballardie     Sep 1997        Core Based Trees (CBT)                                        Multicast Routing ArchitectureCBT is a multicast routing architecture that builds a single deliverytree per group which is shared by all of the group's senders andreceivers.  This memo defines an Experimental Protocol for the Internetcommunity.2200    IAB           Jun 1997        INTERNET OFFICIAL PROTOCOL                                        STANDARDSA discussion of the standardization process and the RFC document seriesis presented first, followed by an explanation of the terms.  Sections6.2 - 6.10 contain the lists of protocols in each stage ofstandardization.  Finally are pointers to references and contacts forfurther information.  [STANDARDS-TRACK]Security Considerations   There are no security issues in this Informational RFC.Author's Address   Alegre Ramos   University of Southern California   Information Sciences Institute   4676 Admiralty Way   Marina del Rey, CA 90292   Phone:  (310) 822-1511   EMail: ramos@isi.eduRamos                        Informational                     [Page 23]

RFC 2299                  Summary of 2200-2299              January 1999Full Copyright Statement   Copyright (C) The Internet Society (1999).  All Rights Reserved.   This document and translations of it may be copied and furnished to   others, and derivative works that comment on or otherwise explain it   or assist in its implementation may be prepared, copied, published   and distributed, in whole or in part, without restriction of any   kind, provided that the above copyright notice and this paragraph are   included on all such copies and derivative works.  However, this   document itself may not be modified in any way, such as by removing   the copyright notice or references to the Internet Society or other   Internet organizations, except as needed for the purpose of   developing Internet standards in which case the procedures for   copyrights defined in the Internet Standards process must be   followed, or as required to translate it into languages other than   English.   The limited permissions granted above are perpetual and will not be   revoked by the Internet Society or its successors or assigns.   This document and the information contained herein is provided on an   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.Ramos                        Informational                     [Page 24]