Movatterモバイル変換
[0]ホーム
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]
INFORMATIONAL
Network Working Group S. GinozaRequest for Comments: 2899 ISICategory: Informational May 2001Request for Comments Summary RFC Numbers 2800-2899Status of This Memo This RFC is a slightly annotated list of the 100 RFCs fromRFC 2800 through RFCs 2899. 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 (2001). 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--- ------ ---- -----2899 Ginoza May 2001 Request for Comments SummaryThis memo.2898 Kaliski Sep 2000 PKCS #5: Password-Based Cryptography Specification Version 2.0This document provides recommendations for the implementation ofpassword-based cryptography, covering key derivation functions,encryption schemes, message-authentication schemes, and ASN.1 syntaxidentifying the techniques. This memo provides information for theInternet community.Ginoza Informational [Page 1]
RFC 2899 Summary of 2800-2899 May 20012897 Cromwell Aug 2000 Proposal for an MGCP Advanced Audio PackageThis document is a proposal to add a new event/signal package to theMGCP (Media Gateway Control Protocol) protocol to control an ARF (AudioResource Function) which may reside on a Media Gateway or specializedAudio Server. This memo provides information for the Internetcommunity.2896 Bierman Aug 2000 Remote Network Monitoring MIB Protocol Identifier MacrosThis memo contains various protocol identifier examples, which can beused to produce valid protocolDirTable INDEX encodings, as defined bythe Remote Network Monitoring MIB and the RMON Protocol IdentifierReference. This memo provides information for the Internet community.2895 Bierman Aug 2000 Remote Network Monitoring MIB Protocol Identifier ReferenceThis memo defines a notation describing protocol layers in a protocolencapsulation, specifically for use in encoding INDEX values for theprotocolDirTable, found in the RMON-2 MIB. [STANDARDS TRACK]2894 Crawford Aug 2000 Router Renumbering for IPv6This document defines a mechanism called Router Renumbering ("RR") whichallows address prefixes on routers to be configured and reconfiguredalmost as easily as the combination of Neighbor Discovery and AddressAutoconfiguration works for hosts. [STANDARDS TRACK]2893 Gilligan Aug 2000 Transition Mechanisms for IPv6 Hosts and RoutersThis document specifies IPv4 compatibility mechanisms that can beimplemented by IPv6 hosts and routers. [STANDARDS TRACK]Ginoza Informational [Page 2]
RFC 2899 Summary of 2800-2899 May 20012892 Tsiang Aug 2000 The Cisco SRP MAC Layer ProtocolThis document specifies the MAC layer protocol, "Spatial Reuse Protocol"(SRP) for use with ring based media. This is a second version of theprotocol (V2). This memo provides information for the Internetcommunity.2891 Howes Aug 2000 LDAP Control Extension for Server Side Sorting of Search ResultsThis document describes two LDAPv3 control extensions for server sidesorting of search results. These controls allows a client to specifythe attribute types and matching rules a server should use whenreturning the results to an LDAP search request. [STANDARDS TRACK]2890 Dommety Sep 2000 Key and Sequence Number Extensions to GREThis document describes extensions by which two fields, Key and SequenceNumber, can be optionally carried in the GRE Header. [STANDARDS TRACK]2889 Mandeville Aug 2000 Benchmarking Methodology for LAN Switching DevicesThis document is intended to provide methodology for the benchmarking oflocal area network (LAN) switching devices. This memo providesinformation for the Internet community.2888 Srisuresh Aug 2000 Secure Remote Access with L2TPThe objective of this document is to extend security characteristics ofIPsec to remote access users, as they dial-in through the Internet.This memo provides information for the Internet community.2887 Handley Aug 2000 The Reliable Multicast Design Space for Bulk Data TransferThis document provides an overview of the design space and the ways inwhich application constraints affect possible solutions. This memoprovides information for the Internet community.Ginoza Informational [Page 3]
RFC 2899 Summary of 2800-2899 May 20012886 Taylor Sep 2000 Megaco ErrataThis document records the errors found in the Megaco/H.248 protocoldocument, along with the changes proposed in the text of that documentto resolve them. [STANDARDS TRACK]2885 Cuervo Sep 2000 Megaco Protocol version 0.8This document is common text with Recommendation H.248 as redeterminedin Geneva, February 2000. It must be read in conjunction with theMegaco Errata,RFC 2886. [STANDARDS TRACK]2884 Hadi Salim Jul 2000 Performance Evaluation of Explicit Congestion Notification (ECN) in IP NetworksThis memo presents a performance study of the Explicit CongestionNotification (ECN) mechanism in the TCP/IP protocol using ourimplementation on the Linux Operating System. This memo providesinformation for the Internet community.2883 Floyd Jul 2000 An Extension to the Selective Acknowledgement (SACK) Option for TCPThis note defines an extension of the Selective Acknowledgement (SACK)Option for TCP. [STANDARDS TRACK]2882 Mitton Jul 2000 Network Access Servers Requirements: Extended RADIUS PracticesThis document describes current practices implemented in NAS productsthat go beyond the scope of the RADIUS (Remote Authentication Dial InUser Service) RFCs 2138, 2139. This memo provides information for theInternet community.Ginoza Informational [Page 4]
RFC 2899 Summary of 2800-2899 May 20012881 Mitton Jul 2000 Network Access Server Requirements Next Generation (NASREQNG) NAS ModelThis document describes the terminology and gives a model of typicalNetwork Access Server (NAS). This memo provides information for theInternet community.2880 McIntyre Aug 2000 Internet Fax T.30 Feature MappingThis document describes how to map Group 3 fax capability identificationbits, described in ITU T.30, into the Internet fax feature schemadescribed in "Content feature schema for Internet fax". This memoprovides information for the Internet community.2879 Klyne Aug 2000 Content Feature Schema for Internet Fax (V2)This document defines a content media feature schema for Internet fax.[STANDARDS TRACK]2878 Higashiyama Jul 2000 PPP Bridging Control Protocol (BCP)This document defines the Network Control Protocol for establishing andconfiguring Remote Bridging for PPP links. [STANDARDS TRACK]2877 Murphy, Jr. Jul 2000 5250 Telnet EnhancementsThis memo describes the interface to the IBM 5250 Telnet server thatallows client Telnet to request a Telnet terminal or printer sessionusing a specific device name. This memo provides information for theInternet community.2876 Pawling Jul 2000 Use of the KEA and SKIPJACK Algorithms in CMSThis document describes the conventions for using the Key ExchangeAlgorithm (KEA) and SKIPJACK encryption algorithm in conjunction withthe Cryptographic Message Syntax [CMS] enveloped-data and encrypted-data content types. This memo provides information for the Internetcommunity.Ginoza Informational [Page 5]
RFC 2899 Summary of 2800-2899 May 20012875 PrafullchandraJul 2000 Diffie-Hellman Proof-of-Possession AlgorithmsThis document describes two methods for producing an integrity checkvalue from a Diffie-Hellman key pair. [STANDARDS TRACK]2874 Crawford Jul 2000 DNS Extensions to Support IPv6 Address Aggregation and RenumberingThis document defines changes to the Domain Name System to supportrenumberable and aggregatable IPv6 addressing. [STANDARDS TRACK]2873 Xiao Jun 2000 TCP Processing of the IPv4 Precedence FieldThis memo describes a conflict between TCP and DiffServ on the use ofthe three leftmost bits in the TOS octet of an IPv4 header. [STANDARDSTRACK]2872 Bernet Jun 2000 Application and Sub Application Identity Policy Element for Use with RSVPRSVP signaling messages typically include policy data objects, which inturn contain policy elements. Policy elements may describe user and/orapplication information, which may be used by RSVP aware networkelements to apply appropriate policy decisions to a traffic flow. Thismemo details the usage of policy elements that provide applicationinformation. [STANDARDS TRACK]2871 Rosenberg Jun 2000 A Framework for Telephony Routing over IPThis document serves as a framework for Telephony Routing over IP(TRIP), which supports the discovery and exchange of IP telephonygateway routing tables between providers. This memo providesinformation for the Internet community.Ginoza Informational [Page 6]
RFC 2899 Summary of 2800-2899 May 20012870 Bush Jun 2000 Root Name Server Operational RequirementsThe primary focus of this document is to provide guidelines foroperation of the root name servers. This document specifies an InternetBest Current Practices for the Internet Community, and requestsdiscussion and suggestions for improvements.2869 Rigney Jun 2000 RADIUS ExtensionsThis document describes additional attributes for carryingauthentication, authorization and accounting information between aNetwork Access Server (NAS) and a shared Accounting Server using theRemote Authentication Dial In User Service (RADIUS) protocol describedinRFC 2865 andRFC 2866. This memo provides information for theInternet community.2868 Zorn Jun 2000 RADIUS Attributes for Tunnel Protocol SupportThis document defines a set of RADIUS (Remote Authentication Dial InUser Service) attributes designed to support the provision of compulsorytunneling in dial-up networks. This memo provides information for theInternet community.2867 Zorn Jun 2000 RADIUS Accounting Modifications for Tunnel Protocol SupportThis document defines new RADIUS (Remote Authentication Dial In UserService) accounting Attributes and new values for the existing Acct-Status-Type Attribute designed to support the provision of compulsorytunneling in dial-up networks. This memo provides information for theInternet community.2866 Rigney Jun 2000 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.Ginoza Informational [Page 7]
RFC 2899 Summary of 2800-2899 May 20012865 Rigney Jun 2000 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]2864 McCloghrie Jun 2000 The Inverted Stack Table Extension to the Interfaces Group MIBThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it describes managed objects which provide an invertedmapping of the interface stack table used for managing networkinterfaces. [STANDARDS TRACK]2863 McCloghrie Jun 2000 The Interfaces Group MIBThis memo discusses the 'interfaces' group of MIB-II, especially theexperience gained from the definition of numerous media-specific MIBmodules for use in conjunction with the 'interfaces' group for managingvarious sub-layers beneath the internetwork-layer. It specifiesclarifications to, and extensions of, the architectural issues withinthe MIB-II model of the 'interfaces' group. [STANDARDS TRACK]2862 Civanlar Jun 2000 RTP Payload Format for Real-Time PointersThis document describes an RTP payload format for transporting thecoordinates of a dynamic pointer that may be used during a presentation.[STANDARDS TRACK]2861 Handley Jun 2000 TCP Congestion Window ValidationThis document describes a simple modification to TCP's congestioncontrol algorithms to decay the congestion window cwnd after thetransition from a sufficiently-long application-limited period, whileusing the slow-start threshold ssthresh to save information about theprevious value of the congestion window. This memo defines anExperimental Protocol for the Internet community.Ginoza Informational [Page 8]
RFC 2899 Summary of 2800-2899 May 20012860 Carpenter Jun 2000 Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers AuthorityThis document places on record the text of the Memorandum ofUnderstanding concerning the technical work of the IANA that was signedon March 1, 2000 between the IETF and ICANN, and ratified by the ICANNBoard on March 10, 2000. This memo provides information for theInternet community.2859 Fang Jun 2000 A Time Sliding Window Three This memo defines a TimeThis memo defines a Time Sliding Window Three Colour Marker (TSWTCM),which can be used as a component in a Diff-Serv traffic conditioner.This memo defines an Experimental Protocol for the Internet community.2858 Bates Jun 2000 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...). [STANDARDS TRACK]2857 Keromytis Jun 2000 The Use of HMAC-RIPEMD-160-96 within ESP and AHThis memo describes the use of the HMAC algorithm in conjunction withthe RIPEMD-160 algorithm as an authentication mechanism within therevised IPSEC Encapsulating Security Payload (ESP) and the revised IPSECAuthentication Header (AH). [STANDARDS TRACK]2856 Bierman Jun 2000 Textual Conventions for Additional High Capacity Data TypesThis memo specifies new textual conventions for additional high capacitydata types, intended for SNMP implementations which already support theCounter64 data type. [STANDARDS TRACK]Ginoza Informational [Page 9]
RFC 2899 Summary of 2800-2899 May 20012855 Fujisawa Jun 2000 DHCP for IEEE 1394This memo describes specific usage of some fields of DHCP (Dynamic HostConfiguration Protocol) messages. IEEE Std 1394-1995 is a standard fora High Performance Serial Bus. Since 1394 uses a different link-layeraddressing method than conventional IEEE802/Ethernet, the usage of somefields must be clarified to achieve interoperability. [STANDARDS TRACK]2854 Connolly Jun 2000 The 'text/html' Media TypeThis document summarizes the history of HTML development, and definesthe "text/html" MIME type by pointing to the relevant W3Crecommendations. This memo provides information for the Internetcommunity.2853 Kabat Jun 2000 Generic Security Service API Version 2 : Java BindingsThis document specifies the Java bindings for GSS-API (Generic SecurityService Application Program Interface) which is described at a languageindependent conceptual level inRFC 2743. [STANDARDS TRACK]2852 Newman Jun 2000 Deliver By SMTP Service ExtensionThis memo defines a mechanism whereby a SMTP client can request, whentransmitting a message to a SMTP server, that the server deliver themessage within a prescribed period of time. [STANDARDS TRACK]2851 Daniele Jun 2000 Textual Conventions for Internet Network AddressesThis MIB module defines textual conventions to represent commonly usedInternet network layer addressing information. [STANDARDS TRACK]2850 IAB May 2000 Charter of the Internet Architecture Board (IAB)This memo documents the composition, selection, roles, and organizationof the Internet Architecture Board. It replacesRFC 1601. Thisdocument specifies an Internet Best Current Practices for the InternetCommunity, and requests discussion and suggestions for improvements.Ginoza Informational [Page 10]
RFC 2899 Summary of 2800-2899 May 20012849 Good Jun 2000 The LDAP Data Interchange Format (LDIF) - Technical SpecificationThis document describes a file format suitable for describing directoryinformation or modifications made to directory information. [STANDARDSTRACK]2848 Petrack Jun 2000 The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call ServicesThis document contains the specification of the PINT Service Protocol1.0, which defines a protocol for invoking certain telephone servicesfrom an IP network. [STANDARDS TRACK]2847 Eisler Jun 2000 LIPKEY - A Low Infrastructure Public Key Mechanism Using SPKMThis memorandum describes a method whereby one can use GSS-API (GenericSecurity Service Application Program Interface) to supply a securechannel between a client and server, authenticating the client with apassword, and a server with a public key certificate. [STANDARDS TRACK]2846 Allocchio Jun 2000 GSTN Address Element Extensions in E-mail ServicesThis memo defines a full syntax for a specific application in whichthere is a need to represent GSTN (Global Switched Telephone Network)addressing and Internet addressing. [STANDARDS TRACK]2845 Vixie May 2000 Secret Key Transaction Authentication for DNS (TSIG)This protocol allows for transaction level authentication using sharedsecrets and one way hashing. It can be used to authenticate dynamicupdates as coming from an approved client, or to authenticate responsesas coming from an approved recursive name server. [STANDARDS TRACK]Ginoza Informational [Page 11]
RFC 2899 Summary of 2800-2899 May 20012844 Przygienda May 2000 OSPF over ATM and Proxy-PARThis memo specifies, for OSPF implementors and users, mechanismsdescribing how the protocol operates in ATM networks over PVC (PermanentVirtual Connections) and SVC (Switched Virtual Circuit) meshes with thepresence of Proxy-PAR (PNNI Augmented Routing). This memo defines anExperimental Protocol for the Internet community.2843 Droz May 2000 Proxy-PARThe intention of this document is to provide general information aboutProxy-PAR (PNNI Augmented Routing). [STANDARDS TRACK]2842 Chandra May 2000 Capabilities Advertisement with BGP-4This document defines new Optional Parameter, called Capabilities, thatis expected to facilitate introduction of new capabilities in BGP byproviding graceful capability advertisement without requiring that BGPpeering be terminated. [STANDARDS TRACK]2841 Metzger Nov 2000 IP Authentication using Keyed SHA1 with Interleaved Padding (IP-MAC)This document describes the use of keyed SHA1 (Secure Hash Algorithm)with the IP Authentication Header. This memo defines a HistoricDocument for the Internet community.2840 Altman May 2000 TELNET KERMIT OPTIONThis document describes an extension to the Telnet protocol to allow thenegotiation, coordination, and use of the Kermit file transfer andmanagement protocol over an existing Telnet protocol connection. Thismemo provides information for the Internet community.2839 da Cruz May 2000 Internet Kermit ServiceThis document describes a new file transfer service for the Internetbased on Telnet Protocol for option negotiation and Kermit Protocol forfile transfer and management. This memo provides information for theInternet community.Ginoza Informational [Page 12]
RFC 2899 Summary of 2800-2899 May 20012838 Zigmond May 2000 Uniform Resource Identifiers for Television BroadcastsThis document describes a widely-implemented URI scheme, as World-WideWeb browsers are starting to appear on a variety of consumer electronicdevices, such as television sets and television set-top boxes, which arecapable of receiving television programming from either terrestrialbroadcast, satellite broadcast, or cable. In this context there is aneed to reference television broadcasts using the URI format describedinRFC 2396. This memo provides information for the Internet community.2837 Teow May 2000 Definitions of Managed Objects for the Fabric Element in Fibre Channel StandardThis memo defines an extension to the Management Information Base (MIB)for use with network management protocols in TCP/IP-based internets. Inparticular, it defines the objects for managing the operations of theFabric Element portion of the Fibre Channel Standards. [STANDARDSTRACK]2836 Brim May 2000 Per Hop Behavior Identification CodesThis document defines a binary encoding to uniquely identify PHBs (PerHop Behaviors) and/or sets of PHBs in protocol messages. [STANDARDSTRACK]2835 Pittet May 2000 IP and ARP over HIPPI-6400 (GSN)This document further specifies a method for resolving IP addresses toHIPPI-6400 (High-Performance Parallel Interface) hardware addresses(HARP) and for emulating IP broadcast in a logical IP subnet (LIS) as adirect extension of HARP. Furthermore, it is the goal of this memo todefine a IP and HARP that will allow interoperability for HIPPI-800 andHIPPI-6400 equipment both broadcast and non-broadcast capable networks.[STANDARDS TRACK]Ginoza Informational [Page 13]
RFC 2899 Summary of 2800-2899 May 20012834 Pittet May 2000 ARP and IP Broadcast over HIPPI-800This document specifies a method for resolving IP addresses to ANSIHigh-Performance Parallel Interface (HIPPI) hardware addresses and foremulating IP broadcast in a logical IP subnet (LIS) as a directextension of HARP (hardware addresses). This memo defines a HARP thatwill interoperate between HIPPI-800 and HIPPI-6400 (also known asGigabyte System Network, GSN). This document (when combined with RFC2067 "IP over HIPPI") obsoletesRFC 1374.[STANDARDS TRACK]2833 Schulzrinne May 2000 RTP Payload for DTMF Digits, Telephony Tones and Telephony SignalsThis memo describes how to carry dual-tone multifrequency (DTMF)signaling, other tone signals and telephony events in RTP packets.[STANDARDS TRACK]2832 Hollenbeck May 2000 NSI Registry Registrar Protocol (RRP) Version 1.1.0This document describes a protocol for the registration and managementof second level domain names and associated name servers in both genericTop Level Domains (gTLDs) and country code Top Level Domains (ccTLDs).This memo provides information for the Internet community.2831 Leach May 2000 Using Digest Authentication as a SASL MechanismThis specification defines how HTTP Digest Authentication can be used asa SASL mechanism for any protocol that has a SASL (Simple Authenticationand Security Layer) profile. [STANDARDS TRACK]2830 Hodges May 2000 Lightweight Directory Access Protocol (v3): Extension for Transport Layer SecurityThis document defines the "Start Transport Layer Security (TLS)Operation" for LDAP. [STANDARDS TRACK]Ginoza Informational [Page 14]
RFC 2899 Summary of 2800-2899 May 20012829 Wahl May 2000 Authentication Methods for LDAPThis document specifies particular combinations of security mechanismswhich are required and recommended in LDAP implementations. [STANDARDSTRACK]2828 Shirey May 2000 Internet Security GlossaryThis Glossary provides abbreviations, explanations, and recommendationsfor use of information system security terminology. This memo providesinformation for the Internet community.2827 Ferguson May 2000 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 (Denial of Service)attacks which use forged IP addresses to be propagated from 'behind' anInternet Service Provider's (ISP) aggregation point. This documentspecifies an Internet Best Current Practices for the Internet Community,and requests discussion and suggestions for improvements.2826 IAB May 2000 IAB Technical Comment on the Unique DNS RootThis document discusses the existence of a globally unique public namespace in the Internet called the DNS (Domain Name System). This namespace is a hierarchical name space derived from a single, globallyunique root. It is a technical constraint inherent in the design of theDNS. One root must be supported by a set of coordinated root serversadministered by a unique naming authority. It is not technicallyfeasible for there to be more than one root in the public DNS. Thismemo provides information for the Internet community.Ginoza Informational [Page 15]
RFC 2899 Summary of 2800-2899 May 20012825 IAB May 2000 A Tangled Web: Issues of I18N, Domain Names, and the Other Internet protocolsThis document is a statement by the Internet Architecture Board. It isnot a protocol specification, but an attempt to clarify the range ofarchitectural issues that the internationalization of domain namesfaces. This memo provides information for the Internet community.2824 Lennox May 2000 Call Processing Language Framework and RequirementsThis document describes an architectural framework we call a processinglanguage, as a simple and standardized way for implementing anddeploying Internet telephony. A large number of the services we wish tomake possible for Internet telephony require fairly elaboratecombinations of signalling operations, often in network devices, tocomplete. It also outlines requirements for such a language. This memoprovides information for the Internet community.2823 Carlson May 2000 PPP over Simple Data Link (SDL) using SONET/SDH with ATM-like framingThis document extends methods found in the Point-to-Point Protocol (PPP)and RFCs 1662 and 2615 to include a new encapsulation for PPP calledSimple Data Link (SDL). SDL provides a standard method for transportingmulti-protocol datagrams over point-to-point links, and RFCs 1662 and2615 provide a means to carry PPP over Synchronous Optical Network(SONET) and Synchronous Digital Hierarchy (SDH) circuits. SDL providesa very low overhead alternative to HDLC-like encapsulation, and can alsobe used on SONET/SDH links. This memo defines an Experimental Protocolfor the Internet community.2822 Resnick Apr 2001 Internet Message FormatThis document specifies a syntax for text messages that are sent betweencomputer users, within the framework of "electronic mail" messages.[STANDARDS TRACK]Ginoza Informational [Page 16]
RFC 2899 Summary of 2800-2899 May 20012821 Klensin Apr 2001 Simple Mail Transfer ProtocolThis document is a self-contained specification of the basic protocolfor the Internet electronic mail transport. [STANDARDS TRACK]2820 Stokes May 2000 Access Control Requirements for LDAPThis document describes the fundamental requirements of an accesscontrol list (ACL) model for the Lightweight Directory ApplicationProtocol (LDAP) directory service. This memo provides information forthe Internet community.2819 Waldbusser May 2000 Remote Network Monitoring Management Information BaseThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets. Inparticular, it defines objects for managing remote network monitoringdevices. [STANDARDS TRACK]2818 Rescorla May 2000 HTTP Over TLSThis memo describes how to use Transport Layer Security (TLS) to secureHypertext Transfer Protocol (HTTP) connections over the Internet. Thismemo provides information for the Internet community.2817 Khare May 2000 Upgrading to TLS Within HTTP/1.1This memo explains how to use the Upgrade mechanism in HTTP/1.1 toinitiate Transport Layer Security (TLS) over an existing TCP connection.[STANDARDS TRACK]2816 Ghanwani May 2000 A Framework for Integrated Services Over Shared and Switched IEEE 802 LAN TechnologiesThis memo describes a framework for supporting IETF Integrated Serviceson shared and switched LAN infrastructure. This memo providesinformation for the Internet community.Ginoza Informational [Page 17]
RFC 2899 Summary of 2800-2899 May 20012815 Seaman May 2000 Integrated Service Mappings on IEEE 802 NetworksThis document describes mappings of IETF Integrated Services over LANsbuilt from IEEE 802 network segments which may be interconnected by IEEE802.1D MAC Bridges (switches). [STANDARDS TRACK]2814 Yavatkar May 2000 SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networksThis document describes a signaling method and protocol for RSVP-basedadmission control over IEEE 802-style LANs. [STANDARDS TRACK]2813 Kalt Apr 2000 Internet Relay Chat: Server ProtocolThis document defines the protocol used by servers to talk to eachother. This memo provides information for the Internet community.2812 Kalt Apr 2000 Internet Relay Chat: Client ProtocolThis document defines the Client Protocol, and assumes that the readeris familiar with the IRC Architecture. This memo provides informationfor the Internet community.2811 Kalt Apr 2000 Internet Relay Chat: Channel ManagementThis document specifies how channels, their characteristics andproperties are managed by IRC servers. This memo provides informationfor the Internet community.2810 Kalt Apr 2000 Internet Relay Chat: ArchitectureThis document is an update describing the architecture of the currentIRC protocol and the role of its different components. Other documentsdescribe in detail the protocol used between the various componentsdefined here. This memo provides information for the Internetcommunity.Ginoza Informational [Page 18]
RFC 2899 Summary of 2800-2899 May 20012809 Aboba Apr 2000 Implementation of L2TP Compulsory Tunneling via RADIUSThis document discusses implementation issues arising in theprovisioning of compulsory tunneling in dial-up networks using the L2TP(Layer Two Tunneling Protocol) protocol. This memo provides informationfor the Internet community.2808 Nystrom Apr 2000 The SecurID(r) SASL MechanismThis document defines a SASL (Simple Authentication and Security Layer)authentication mechanism using SecurID (a hardware token card product(or software emulation thereof) produced by RSA Security Inc., which isused for end-user authentication), thereby providing a means for suchtokens to be used in SASL environments. This mechanism is only is onlyfor authentication, and has no effect on the protocol encoding and isnot designed to provide integrity or confidentiality services. Thismemo provides information for the Internet community.2807 Reagle Jul 2000 XML Signature RequirementsThis document lists the design principles, scope, and requirements forthe XML Digital Signature specification. It includes requirements asthey relate to the signature syntax, data model, format, cryptographicprocessing, and external requirements and coordination. This memoprovides information for the Internet community.2806 Vaha-Sipila Apr 2000 URLs for Telephone CallsThis document specifies URL (Uniform Resource Locator) schemes "tel","fax" and "modem" for specifying the location of a terminal in the phonenetwork and the connection types (modes of operation) that can be usedto connect to that entity. [STANDARDS TRACK]Ginoza Informational [Page 19]
RFC 2899 Summary of 2800-2899 May 20012805 Greene Apr 2000 Media Gateway Control Protocol Architecture and RequirementsThis document describes protocol requirements for the Media GatewayControl Protocol between a Media Gateway Controller and a Media Gateway.This memo provides information for the Internet community.2804 IAB May 2000 IETF Policy on WiretappingThis document describes the position that the Internet Engineering TaskForce (IETF) has taken regarding the inclusion into IETF standards-trackdocuments of functionality designed to facilitate wiretapping. Thismemo explains what the IETF thinks the question means, why its answer is"no", and what that answer means. This memo provides information forthe Internet community.2803 Maruyama Apr 2000 Digest Values for DOM (DOMHASH)This memo defines a clear and unambiguous definition of digest (hash)values of the XML objects regardless of the surface string variation ofXML. This memo provides information for the Internet community.2802 Davidson Apr 2000 Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP)This document describes the syntax and procedures for the computationand verification of digital signatures for use within Version 1.0 of theInternet Open Trading Protocol (IOTP). This memo provides informationfor the Internet community.2801 Burdett Apr 2000 Internet Open Trading Protocol - IOTP Version 1.0This document discusses the Internet Open Trading Protocol (IOTP) andits provision of an interoperable framework for Internet commerce. Thismemo provides information for the Internet community.Ginoza Informational [Page 20]
RFC 2899 Summary of 2800-2899 May 20012800 Reynolds May 2001 Internet Official Protocol StandardsThis memo contains a snapshot of the state of standardization ofprotocols used in the Internet as of April 17, 2001. It lists onlyofficial protocol standards RFCs; it is not a complete index to the RFCseries. [STANDARDS TRACK]Security Considerations This memo does not affect the technical security of the Internet, but may cite important security specifications.Author's Address Sandy Ginoza University of Southern California Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 Phone: (310) 822-1511 EMail: ginoza@isi.eduGinoza Informational [Page 21]
RFC 2899 Summary of 2800-2899 May 2001Full Copyright Statement Copyright (C) The Internet Society (2001). 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.Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society.Ginoza Informational [Page 22]
[8]ページ先頭