Movatterモバイル変換

Network Working Group                                         J. ElliottRequest for Comments: 2099                                           ISICategory: Informational                                       March 1997Request for Comments Summary                         RFC Numbers 2000-2099Status of This Memo   This RFC is a slightly annotated list of the 100 RFCs fromRFC 2000   through RFCs 2099.  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---     ------       ----      -----    Elliott    Mar 97   Request for Comments SummaryThis memo.    Katsube    Feb 97   Toshiba's Router Architecture Extensions                              for ATM : OverviewThis memo describes a new internetworking architecture which makesbetter use of the property of ATM.  This memo provides information forthe Internet community.  This memo does not specify an Internet standardof any kind.Elliott                      Informational                      [Page 1]

RFC 2099                  Summary of 2000-2099                March 1997    Pall       Jan 97   The PPP NetBIOS Frames Control Protocol                              (NBFCP)This document defines the Network Control Protocol for establishing andconfiguring the NBF protocol over PPP.  The NBFCP protocol is onlyapplicable for an end system to connect to a peer system or the LAN thatpeer system is connected to.  [STANDARDS-TRACK]    Baker      Jan 97   IP Forwarding Table MIBThis memo defines an update toRFC 1354.  The significant differencebetween this MIB andRFC 1354 is the recognition (explicitly discussedbut by consensus left to future work) that CIDR routes may have the samenetwork number but different network masks.  [STANDARDS-TRACK]    Klensin    Jan 97   IMAP/POP AUTHorize Extension for Simple                              Challenge/ResponseThis specification provides a simple challenge-response authenticationprotocol that is suitable for use with IMAP4.  [STANDARDS-TRACK]    Harney     Mar 97   Group Key Management Protocol (GKMP)                              ArchitectureThis specification proposes a protocol to create grouped symmetric keysand distribute them amongst communicating peers.  This memo defines anExperimental Protocol for the Internet community.    Harney     Mar 97   Group Key Management Protocol (GKMP)                              SpecificationThis specification proposes a protocol to create grouped symmetric keysand distribute them amongst communicating peers.  This memo defines anExperimental Protocol for the Internet community.    Sherry     Jan 97   Protocol Analysis for Triggered RIPAs required by Routing Protocol Criteria [1], this report documents thekey features of Triggered Extensions to RIP to Support Demand Circuits[2] and the current implementation experience.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.Elliott                      Informational                      [Page 2]

RFC 2099                  Summary of 2000-2099                March 1997    Meyer      Jan 97   Triggered Extensions to RIP to Support                              Demand CircuitsThis document defines a modification which can be applied to Bellman-Ford (distance vector) algorithm information broadcasting protocols.[STANDARDS-TRACK]    Emberson   Feb 97   TFTP Multicast OptionThis document describes a new TFTP option. This new option will allowthe multiple clients to receive the same file concurrently through theuse of Multicast packets.  This memo defines an Experimental Protocolfor the Internet community.    Wijnen     Jan 97   V2ToV1 Mapping SNMPv2 onto SNMPv1 within                              a bi-lingual SNMP agentThe goal of this memo is to document a common way of mapping an SNMPv2response into an SNMPv1 response within a bi-lingual SNMP agent (onethat supports both SNMPv1 and SNMPv2).  This memo provides informationfor the Internet community.  This memo does not specify an Internetstandard of any kind.    Myers      Jan 97   IMAP4 non-synchronizing literalsThe Internet Message Access Protocol [IMAP4] contains the "literal"syntactic construct for communicating strings.  When sending a literalfrom client to server, IMAP4 requires the client to wait for the serverto send a command continuation request between sending the octet countand the string data.  This document specifies an alternate form ofliteral which does not require this network round trip.  [STANDARDS-TRACK]    Myers      Jan 97   IMAP4 QUOTA extensionThe QUOTA extension of the Internet Message Access Protocol [IMAP4]permits administrative limits on resource usage (quotas) to bemanipulated through the IMAP protocol.  [STANDARDS-TRACK]Elliott                      Informational                      [Page 3]

RFC 2099                  Summary of 2000-2099                March 1997    Myers      Jan 97   IMAP4 ACL extensionThe ACL extension of the Internet Message Access Protocol [IMAP4]permits access control lists to be manipulated through the IMAPprotocol.  [STANDARDS-TRACK]    Oehler     Feb 97   HMAC-MD5 IP Authentication with Replay                              PreventionThis document describes a keyed-MD5 transform to be used in conjunctionwith the IP Authentication Header [RFC-1826]. The particular transformis based on [HMAC-MD5].  An option is also specified to guard againstreplay attacks.  [STANDARDS-TRACK]    Bossert    Jan 97   Considerations for Web Transaction                              SecurityThis document specifies the requirements for the provision of securityservices to the HyperText Transport Protocol.  These services includeconfidentiality, integrity, user authentication, and authentication ofservers/services, including proxied or gatewayed services.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.    Boutell    Jan 97   PNG (Portable Network Graphics)                              Specification Version 1.0This document describes PNG (Portable Network Graphics), an extensiblefile format for the lossless, portable, well-compressed storage ofraster images.  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.    Baker      Jan 97   RIP-2 MD5 AuthenticationGrowth in the Internet has made us aware of the need for improvedauthentication of routing information.  RIP-2 provides forunauthenticated service (as in classical RIP), or passwordauthentication.  [STANDARDS-TRACK]Elliott                      Informational                      [Page 4]

RFC 2099                  Summary of 2000-2099                March 1997    Malkin     Jan 97   RIPng Protocol Applicability StatementAs required by Routing Protocol Criteria (RFC 1264), this report definesthe applicability of the RIPng protocol within the Internet.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.    Malkin     Jan 97   RIPng for IPv6This document specifies a routing protocol for an IPv6 internet.  It isbased on protocols and algorithms currently in wide use in the IPv4Internet [STANDARDS-TRACK]    Smith      Jan 97   Definition of an X.500 Attribute Type                              and an Object Class to Hold Uniform                              Resource Identifiers (URIs)This document builds on the experimentation to date and defines a newattribute type and an auxiliary object class to allow URIs, includingURLs, to be stored in directory entries in a standard way.  [STANDARDS-TRACK]    Linn       Jan 97   Generic Security Service Application                              Program Interface, Version 2The Generic Security Service Application Program Interface (GSS-API), asdefined inRFC-1508, provides security services to callers in a genericfashion, supportable with a range of underlying mechanisms andtechnologies and hence allowing source-level portability of applicationsto different environments.  [STANDARDS-TRACK]    Nelson     Jan 97   The Model Primary Content Type for                              Multipurpose Internet Mail ExtensionsThe purpose of this memo is to propose an update to InternetRFC 2045 toinclude a new primary content-type to be known as "model".  [STANDARDS-TRACK]Elliott                      Informational                      [Page 5]

RFC 2099                  Summary of 2000-2099                March 1997    Palme      Feb 97   Common Internet Message HeadersThis memo contains a table of commonly occurring headers in headings ofe-mail messages.  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.    Partridge  Jan 97   IP Echo Host ServiceThis memo describes how to implement an IP echo host.  IP echo hostssend back IP datagrams after exchanging the source and destination IPaddresses.  This memo defines an Experimental Protocol for the Internetcommunity.    Bierman    Jan 97   Remote Network Monitoring MIB Protocol                              IdentifiersThis memo defines an experimental portion of the Management InformationBase (MIB) for use with network management protocols in the Internetcommunity.  In particular, it describes the algorithms required toidentify different protocol encapsulations managed with the RemoteNetwork Monitoring MIB Version 2 [RMON2].  [STANDARDS-TRACK]    Rekhter    Jan 97   An IPv6 Provider-Based Unicast Address                              FormatThis document defines an IPv6 provider-based unicast address format foruse in the Internet.  [STANDARDS-TRACK]    Berkowitz  Jan 97   Router Renumbering GuideRouters interact with numerous network infrastructure servers, includingDNS and SNMP.  These interactions, not just the pure addressing androuting structure, must be considered as part of router renumbering.This memo provides information for the Internet community.  This memodoes not specify an Internet standard of any kind.Elliott                      Informational                      [Page 6]

RFC 2099                  Summary of 2000-2099                March 1997    Ferguson   Jan 97   Network Renumbering Overview:                              Why would I want it and what is it anyway?This document attempts to clearly define the concept of networkrenumbering and discuss some of the more pertinent reasons why anorganization would have a need to do so.  This memo provides informationfor the Internet community.  This memo does not specify an Internetstandard of any kind.    Yergeau    Jan 97   Internationalization of the Hypertext                              Markup LanguageThis document is meant to address the issue of the internationalization(i18n, i followed by 18 letters followed by n) of HTML by extending thespecification of HTML and giving additional recommendations for properinternationalization support.  [STANDARDS-TRACK]    Franks     Jan 97   An Extension to HTTP : Digest Access                              AuthenticationThe protocol referred to as "HTTP/1.0" includes the specification for aBasic Access Authentication scheme.  This scheme is not considered to bea secure method of user authentication, as the user name and passwordare passed over the network as clear text.  A specification for adifferent authentication scheme is needed to address this severelimitation.  This document provides specification for such a scheme,referred to as "Digest Access Authentication".  [STANDARDS-TRACK]    Fielding   Jan 97   Hypertext Transfer Protocol -- HTTP/1.1The Hypertext Transfer Protocol (HTTP) is an application-level protocolfor distributed, collaborative, hypermedia information systems.[STANDARDS-TRACK]    Renwick    Jan 97   IP over HIPPIANSI Standard X3.218-1993 (HIPPI-LE[3]) defines the encapsulation ofIEEE 802.2 LLC PDUs and, by implication, IP on HIPPI.  This memo is arevision ofRFC 1374, "IP and ARP on HIPPI", and is intended to replaceit in the Standards Track.  [STANDARDS-TRACK]Elliott                      Informational                      [Page 7]

RFC 2099                  Summary of 2000-2099                March 1997    Gellens    Jan 97   TELNET CHARSET OptionThis document specifies a mechanism for passing character set andtranslation information between a TELNET client and server.  This memodefines an Experimental Protocol for the Internet community.    Eastlake   Jan 97   Domain Name System Security ExtensionsThe Domain Name System (DNS) has become a critical operational part ofthe Internet infrastructure yet it has no strong security mechanisms toassure data integrity or authentication.  Extensions to the DNS aredescribed that provide these services to security aware resolvers orapplications through the use of cryptographic digital signatures.[STANDARDS-TRACK]    Brownlee   Jan 97   Traffic Flow Measurement:  Meter MIBThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets.  Inparticular, this memo defines managed objects used for obtaining trafficflow information from network traffic meters.  This memo defines anExperimental Protocol for the Internet community.    Brownlee   Jan 97   Traffic Flow Measurement:  ArchitectureThis document describes an architecture for the measurement andreporting of network traffic flows, discusses how this relates to anoverall network traffic flow architecture, and describes how it can beused within the Internet.  This memo defines an Experimental Protocolfor the Internet community.    Crispin    Dec 96   Internet Message Access Protocol -                              Obsolete SyntaxThis document describes obsolete syntax which may be encountered byIMAP4 implementations which deal with older versions of the InternetMail Access Protocol.  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.Elliott                      Informational                      [Page 8]

RFC 2099                  Summary of 2000-2099                March 1997    Crispin    Dec 96   IMAP4 COMPATIBILITY WITH IMAP2BISThis document is intended to be read along withRFC 1176 and the mostrecent IMAP4 specification (RFC 2060) to assist implementors in creatingan IMAP4 implementation to interoperate with implementations thatconform to earlier specifications.  This memo provides information forthe Internet community.  This memo does not specify an Internet standardof any kind.    Crispin    Dec 96   INTERNET MESSAGE ACCESS PROTOCOL -                              VERSION 4rev1The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1) allows aclient to access and manipulate electronic mail messages on a server.[STANDARDS-TRACK]    Rigney     Jan 97   RADIUS AccountingThis document describes a protocol for carrying accounting informationbetween a Network Access Server and a shared Accounting Server.  Thismemo provides information for the Internet community.  This memo doesnot specify an Internet standard of any kind.    Rigney     Jan 97   Remote Authentication Dial In User                              Service (RADIUS)This document describes a protocol for carrying authentication,authorization, and configuration information between a Network AccessServer which desires to authenticate its links and a sharedAuthentication Server.  [STANDARDS-TRACK]    Bradner    Nov 96   Source Directed Access Control on the                              InternetThis memo was developed from a deposition that I submitted as part of achallenge to the Communications Decency Act of 1996, part of theTelecommunications Reform Act of 1996.  This memo provides informationfor the Internet community.  This memo does not specify an Internetstandard of any kind.Elliott                      Informational                      [Page 9]

RFC 2099                  Summary of 2000-2099                March 1997    Denenberg  Nov 96   Uniform Resource Locators for Z39.50Z39.50 is an information retrieval protocol that does not fit neatlyinto a retrieval model designed primarily around the stateless fetch ofdata.  Instead, it models a general user inquiry as a session-oriented,multi-step task, any step of which may be suspended temporarily whilethe server requests additional parameters from the client beforecontinuing.  [STANDARDS-TRACK]    Callaghan  Oct 96   WebNFS Server SpecificationThis document describes the specifications for a server of WebNFSclients.  This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.    Callaghan  Oct 96   WebNFS Client SpecificationThis document describes a lightweight binding mechanism that allows NFSclients to obtain service from WebNFS-enabled servers with a minimum ofprotocol overhead.  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.    Der-DanieliantzOct 96   The AM (Armenia) DomainThe AM Domain is an official Internet top-level domain of Armenia.  Thismemo provides information for the Internet community.  This memo doesnot specify an Internet standard of any kind.    GulbrandsenOct 96   A DNS RR for specifying the location of                              services (DNS SRV)This document describes a DNS RR which specifies the location of theserver(s) for a specific protocol and domain (like a more general formof MX).  This memo defines an Experimental Protocol for the Internetcommunity.Elliott                      Informational                     [Page 10]

RFC 2099                  Summary of 2000-2099                March 1997    Allen      Oct 96   Definitions of Managed Objects for APPC                              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 managing the configuration,monitoring and controlling of network devices with APPC (AdvancedProgram-to-Program Communications) capabilities.  This memo identifiesmanaged objects for the SNA LU6.2 protocols.  [STANDARDS-TRACK]    Hubbard    Nov 96   INTERNET REGISTRY IP ALLOCATION                              GUIDELINESThis document describes the registry system for the distribution ofglobally unique Internet address space and registry operations.Particularly this document describes the rules and guidelines governingthe distribution of this address space.  This document specifies anInternet Best Current Practices for the Internet Community, and requestsdiscussion and suggestions for improvements.    Freed      Nov 96   Multipurpose Internet Mail Extensions                              (MIME) Part Five: Conformance Criteria                              and ExamplesThis set of documents, collectively called the Multipurpose InternetMail Extensions, or MIME, redefines the format of messages.  This fifthand final document describes MIME conformance criteria as well asproviding some illustrative examples of MIME message formats,acknowledgements, and the bibliography.  [STANDARDS-TRACK]    Freed      Nov 96   Multipurpose Internet Mail Extensions                              (MIME) Part Four: Registration                              ProceduresThis set of documents, collectively called the Multipurpose InternetMail Extensions, or MIME, redefines the format of messages.  This fourthdocument,RFC 2048, specifies various IANA registration procedures forsome MIME facilities.  This document specifies an Internet Best CurrentPractices for the Internet Community, and requests discussion andsuggestions for improvements.Elliott                      Informational                     [Page 11]

RFC 2099                  Summary of 2000-2099                March 1997    Moore      Nov 96   MIME (Multipurpose Internet Mail                              Extensions) Part Three: Message Header                              Extensions for Non-ASCII TextThis particular document is the third document in the series.  Itdescribes extensions toRFC 822 to allow non-US-ASCII text data inInternet mail header fields.  [STANDARDS-TRACK]    Freed      Nov 96   Multipurpose Internet Mail Extensions                              (MIME) Part Two: Media TypesThis second document defines the general structure of the MIME mediatyping system and defines an initial set of media types.  [STANDARDS-TRACK]    Freed      Nov 96   Multipurpose Internet Mail Extensions                              (MIME) Part One: Format of Internet                              Message BodiesThis initial document specifies the various headers used to describe thestructure of MIME messages.  [STANDARDS-TRACK]    Yergeau    Oct 96   UTF-8, a transformation format of                              Unicode and ISO 10646The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993 jointlydefine a 16 bit character set which encompasses most of the world'swriting systems.  UTF-8, the object of this memo, has the characteristicof preserving the full US-ASCII range.  This memo provides informationfor the Internet community.  This memo does not specify an Internetstandard of any kind.    Fuqua      Oct 96   The PPP SNA Control Protocol (SNACP)This document defines the Network Control Protocols for establishing andconfiguring Systems Network Architecture (SNA) over PPP and SNA over LLC802.2 over PPP.[STANDARDS-TRACK]Elliott                      Informational                     [Page 12]

RFC 2099                  Summary of 2000-2099                March 1997    Manning    Jan 97   Registering New BGP Attribute TypesThis document describes the process for creating new BGP attribute typecodes.  Basic attribute type codes are described inRFC 1771, pages 12through 15.  These, and new attribute type codes that are used in theInternet are registered with the IANA.  This memo provides informationfor the Internet community.  This memo does not specify an Internetstandard of any kind.    Noble      Oct 96   Mobile Network TracingThis RFC argues that mobile network tracing provides both tools toimprove our understanding of wireless channels, as well as to buildrealistic, repeatable testbeds for mobile software and systems.  Thismemo provides information for the Internet community.  This memo doesnot specify an Internet standard of any kind.    Baldwin    Oct 96   The RC5, RC5-CBC, RC5-CBC-Pad, and                              RC5-CTS AlgorithmsThis document defines four ciphers with enough detail to ensureinteroperability between different implementations.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.    KalbfleischNov 96   Applicablity of Standards Track MIBs to                              Management of World Wide Web ServersThis document was produced at the request of the Network Management AreaDirector following the HTTP-MIB BOF at the 35th IETF meeting to reporton the applicability of the existing standards track MIBs to managementof WWW servers.  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.    Hoffman    Oct 96   RTP Payload Format for MPEG1/MPEG2 VideoThis memo describes a packetization scheme for MPEG video and audiostreams.  The scheme proposed can be used to transport such a video oraudio flow over the transport protocols supported by RTP.  [STANDARDS-TRACK]Elliott                      Informational                     [Page 13]

RFC 2099                  Summary of 2000-2099                March 1997    McCloghrie Oct 96   Entity 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 multiplelogical and physical entities managed by a single SNMP agent.[STANDARDS-TRACK]    Huston     Oct 96   Observations on the use of Components of                              the Class A Address Space within the                              InternetThis document is a commentary on the recommendation that IANA commenceallocation of the presently unallocated components of the Class Aaddress space to registries, for deployment within the Internet asclass-less address blocks.  This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.    Berc       Oct 96   RTP Payload Format for JPEG-compressed                              VideoThis memo describes the RTP payload format for JPEG video streams.  Thepacket format is optimized for real-time video streams where codecparameters change rarely from frame to frame.  [STANDARDS-TRACK]    Freed      Oct 96   SMTP Service Extension for                              Returning Enhanced Error CodesThis memo defines an extension to the SMTP service [RFC-821,RFC-1869]whereby an SMTP server augments its responses with the enhanced mailsystem status codes defined inRFC 1893.  [STANDARDS-TRACK]    Myers      Oct 96   Local Mail Transfer ProtocolSMTP [SMTP] [HOST-REQ] and its service extensions [ESMTP] provide amechanism for transferring mail reliably and efficiently.  The design ofthe SMTP protocol effectively requires the server to manage a maildelivery queue.  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.Elliott                      Informational                     [Page 14]

RFC 2099                  Summary of 2000-2099                March 1997    Turletti   Oct 96   RTP Payload Format for H.261 Video                              StreamsThis memo describes a scheme to packetize an H.261 video stream fortransport using the Real-time Transport Protocol, RTP, with any of theunderlying protocols that carry RTP.  [STANDARDS-TRACK]    Huizer     Oct 96   IETF-ISOC relationshipThis memo summarises the issues on IETF - ISOC relationships as the havebeen discussed by the Poised Working Group. The purpose of the documentis to gauge consensus on these issues. And to allow further discussionswhere necessary.  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.    Mills      Oct 96   Simple Network Time Protocol (SNTP)                              Version 4 for IPv4, IPv6 and OSIThis memorandum describes the Simple Network Time Protocol (SNTP)Version 4, which is an adaptation of the Network Time Protocol (NTP)used to synchronize computer clocks in the Internet.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.    Speer      Oct 96   RTP Payload Format of Sun's CellB Video                              EncodingThis memo describes a packetization scheme for the CellB video encoding.The scheme proposed allows applications to transport CellB video flowsover protocols used by RTP.  This document is meant for implementors ofvideo applications that want to use RTP and CellB.  [STANDARDS-TRACK]    Hovey     Oct 96   The Organizations Involved in the IETF                             Standards ProcessThis document describes the individuals and organizations involved inthe IETF.  This includes descriptions of the IESG, the IETF WorkingGroups and the relationship between the IETF and the Internet Society.This document specifies an Internet Best Current Practices for theInternet Community, and requests discussion and suggestions forimprovements.Elliott                      Informational                     [Page 15]

RFC 2099                  Summary of 2000-2099                March 1997    Galvin    Oct 96   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 has been exercised four times since its formalcreation.  The evolution of the process has relied principally on oraltradition as a means by which the lessons learned could be passed on tosuccessive committees.  This document is a self-consistent, organizedcompilation of the process as it is known today.  This documentspecifies an Internet Best Current Practices for the Internet Community,and requests discussion and suggestions for improvements.    Bradner    Oct 96   The Internet Standards Process --                              Revision 3This memo documents the process used by the Internet community for thestandardization of protocols and procedures.  It defines the stages inthe standardization process, the requirements for moving a documentbetween stages and the types of documents used during this process.This document specifies an Internet Best Current Practices for theInternet Community, and requests discussion and suggestions forimprovements.    Adams      Oct 96   The Simple Public-Key GSS-API Mechanism                              (SPKM)This 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 using theSimple Public-Key Mechanism.  [STANDARDS-TRACK]    Chen       Oct 96   Definitions of Managed Objects for Data                              Link Switching using SMIv2This specification defines an extension to the Management InformationBase (MIB) for use with SNMP-based network management.  In particular,it defines objects for configuring, monitoring, and controlling DataLink Switches (DLSw).  [STANDARDS-TRACK]Elliott                      Informational                     [Page 16]

RFC 2099                  Summary of 2000-2099                March 1997    Haskin     Oct 96   IP Version 6 over PPPThis document defines the method for transmission of IP Version 6 [2]packets over PPP links as well as the Network Control Protocol (NCP) forestablishing and configuring the IPv6 over PPP.  [STANDARDS-TRACK]    Armitage   Nov 96   Support for Multicast over UNI 3.0/3.1                              based ATM Networks.This memo describes a mechanism to support the multicast needs of Layer protocols in general, and describes its application to IP multicastingin particular.  [STANDARDS-TRACK]    Waldbusser Jan 97   Remote Network Monitoring Management                              Information Base Version 2 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 remote network monitoringdevices.  [STANDARDS-TRACK]    Flick      Oct 96   Definitions of Managed Objects for IEEE                              802.12 InterfacesThis 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 interfaces based onIEEE 802.12.  [STANDARDS-TRACK]    Crawford   Oct 96   A Method for the Transmission of IPv6                              Packets over FDDI NetworksThis memo specifies the MTU and frame format for transmission of IPv6[IPV6] packets on FDDI networks, including a method for MTUdetermination in the presence of 802.1d bridges to other media.[STANDARDS-TRACK]    Mathis     Oct 96   TCP Selective Acknowledgment OptionsThis memo proposes an implementation of SACK and discusses itsperformance and related issues.  [STANDARDS-TRACK]Elliott                      Informational                     [Page 17]

RFC 2099                  Summary of 2000-2099                March 1997    Freed      Oct 96   Definition of the URL                              MIME External-Body Access-TypeThis memo defines a new access-type for message/external-body MIME partsfor Uniform Resource Locators (URLs).  [STANDARDS-TRACK]    Daigle     Oct 96   Uniform Resource Agents (URAs)This paper presents an experimental architecture for an agent systemthat provides sophisticated Internet information access and management.This memo defines an Experimental Protocol for the Internet community.    Elkins     Oct 96   MIME Security with Pretty Good Privacy                              (PGP)This document describes how Pretty Good Privacy (PGP) can be used toprovide privacy and authentication using the Multipurpose Internet MailExtensions (MIME) security content types described inRFC1847.[STANDARDS-TRACK]    Weinrib    Oct 96   IRTF Research Group Guidelines and                              ProceduresThis document describes the guidelines and procedures for formation andoperation of IRTF Research Groups.  It describes the relationshipbetween IRTF participants, Research Groups, the Internet ResearchSteering Group (IRSG) and the Internet Architecture Board (IAB).  Thisdocument specifies an Internet Best Current Practices for the InternetCommunity, and requests discussion and suggestions for improvements.    McCloghrie Nov 96   SNMPv2 Management Information Base for                              the User Datagram Protocol using SMIv2This document is the MIB module which defines managed objects formanaging implementations of the User Datagram Protocol (UDP).[STANDARDS-TRACK]Elliott                      Informational                     [Page 18]

RFC 2099                  Summary of 2000-2099                March 1997    McCloghrie Nov 96   SNMPv2 Management Information Base for                              the Transmission Control Protocol using                              SMIv2This document is the MIB module which defines managed objects formanaging implementations of the Transmission Control Protocol (TCP).[STANDARDS-TRACK]    McCloghrie Nov 96   SNMPv2 Management Information Base                              for the Internet Protocol using SMIv2This document is the MIB module which defines managed objects formanaging implementations of the Internet Protocol (IP) and itsassociated Internet Control Message Protocol (ICMP).  [STANDARDS-TRACK]    Manning    Oct 96   Operational Criteria for Root Name                              ServersThis document specifies the operational requirements of root nameservers, including host hardware capacities, name server softwarerevisions, network connectivity, and physical environment.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.    Imielinski Nov 96   GPS-Based Addressing and RoutingThis document describes a possible experiment with geographic addresses.It uses several specific IP addresses and domain names in the discussionas concrete examples to aid in understanding the concepts.  This memodefines an Experimental Protocol for the Internet community.    Rekhter    Oct 96   Implications of Various Address                              Allocation Policies for Internet RoutingThe purpose of this document is to articulate certain relevantfundamental technical issues that must be considered in formulatingunicast address allocation and management policies for the PublicInternet, and to provide recommendations with respect to these policies.This document specifies an Internet Best Current Practices for theInternet Community, and requests discussion and suggestions forimprovements.Elliott                      Informational                     [Page 19]

RFC 2099                  Summary of 2000-2099                March 1997    Foster     Oct 96   Catalogue of Network Training MaterialsThe purpose of this document is to provide a catalogue of qualityNetwork Training Materials for use by Internet trainers in trainingtheir users.  This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.    Cong       Oct 96   The Definitions of Managed Objects for                              IP Mobility Support using SMIv2This memo defines the Management Information Base (MIB) for use withnetwork management protocols in TCP/IP-based internets.  In particular,it describes managed objects used for managing the Mobile Node, ForeignAgent and Home Agent of the Mobile IP Protocol.  [STANDARDS-TRACK]    Solomon    Oct 96   Applicability Statement for IP Mobility                              SupportAs required by [RFC 1264], this report discusses the applicability ofMobile IP to provide host mobility in the Internet.  In particular, thisdocument describes the key features of Mobile IP and shows how therequirements for advancement to Proposed Standard RFC have beensatisfied.  [STANDARDS-TRACK]    Perkins    Oct 96   Minimal Encapsulation within IPThis document specifies a method by which an IP datagram may beencapsulated (carried as payload) within an IP datagram, with lessoverhead than "conventional" IP encapsulation that adds a second IPheader to each encapsulated datagram.  [STANDARDS-TRACK]    Perkins    Oct 96   IP Encapsulation within IPThis document specifies a method by which an IP datagram may beencapsulated (carried as payload) within an IP datagram.  [STANDARDS-TRACK]Elliott                      Informational                     [Page 20]

RFC 2099                  Summary of 2000-2099                March 1997    Perkins    Oct 96   IP Mobility SupportThis document specifies protocol enhancements that allow transparentrouting of IP datagrams to mobile nodes in the Internet.  [STANDARDS-TRACK]    Stevens    Jan 97   TCP Slow Start, Congestion Avoidance,                              Fast Retransmit, and Fast Recovery                              AlgorithmsModern implementations of TCP contain four intertwined algorithms thathave never been fully documented as Internet standards: slow start,congestion avoidance, fast retransmit, and fast recovery.  [STANDARDS-TRACK]    I.A.B.     Feb 97   INTERNET OFFICIAL PROTOCOL STANDARDSThis memo describes the state of standardization of protocols used inthe Internet as determined by the Internet Architecture Board (IAB).This memo is an Internet Standard.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 21]