📄 rfc2899.txt
字号:
Network Working Group S. GinozaRequest for Comments: 2899 ISICategory: Informational May 2001 Request for Comments Summary RFC Numbers 2800-2899Status of This Memo This RFC is a slightly annotated list of the 100 RFCs from RFC 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 Prafullchandra Jul 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 describedin RFC 2865 and RFC 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) for
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -