📄 rfc2799.txt
字号:
Network Working Group S. GinozaRequest for Comments: 2799 ISICategory: Informational September 2000 Request for Comments Summary RFC Numbers 2700-2799Status of This Memo This RFC is a slightly annotated list of the 100 RFCs from RFC 2700 through RFCs 2799. 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 (YEAR). 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--- ------ ---- -----2799 Ginoza Request for Comments SummaryThis memo.2798 Smith Apr 2000 Definition of the inetOrgPerson LDAP Object ClassWe define a new object class called inetOrgPerson for use in LDAP andX.500 directory services that extends the X.521 standardorganizationalPerson class to meet these needs. This memo providesinformation for the Internet community.Ginoza Informational [Page 1]RFC 2799 Summary of 2700-2799 September 20002797 Myers Apr 2000 Certificate Management Messages over CMSThis document defines a Certificate Management protocol using CMS (CMC).[STANDARDS TRACK]2796 Bates Apr 2000 BGP Route Reflection - An Alternative to Full Mesh IBGPThis document describes the use and design of a method known as "RouteReflection" to alleviate the the need for "full mesh" IBGP. [STANDARDSTRACK]2795 Christey Mar 2000 The Infinite Monkey Protocol Suite (IMPS)This memo describes a protocol suite which supports an infinite numberof monkeys that sit at an infinite number of typewriters in order todetermine when they have either produced the entire works of WilliamShakespeare or a good television show. This memo provides informationfor the Internet community.2794 Calhoun Mar 2000 Mobile IP Network Access Identifier Extension for IPv4Our proposal defines a way for the mobile node to identify itself, byincluding the NAI along with the Mobile IP Registration Request. Thismemo also updates RFC 2290 which specifies the Mobile-IPv4 Configurationoption for IPCP, by allowing the Mobile Node's Home Address field ofthis option to be zero. [STANDARDS TRACK]2793 Hellstrom May 2000 RTP Payload for Text ConversationThis memo describes how to carry text conversation session contents inRTP packets. Text conversation session contents are specified in ITU-TRecommendation T.140. [STANDARDS TRACK]Ginoza Informational [Page 2]RFC 2799 Summary of 2700-2799 September 20002792 Blaze Mar 2000 DSA and RSA Key and Signature Encoding for the KeyNote Trust Management SystemThis memo describes RSA and DSA key and signature encoding, and binarykey encoding for version 2 of the KeyNote trust-management system. Thismemo provides information for the Internet community.2791 Yu Jul 2000 Scalable Routing Design PrinciplesThis document identifies major factors affecting routing scalability aswell as basic principles of designing scalable routing for largenetworks. This memo provides information for the Internet community.2790 Waldbusser Mar 2000 Host Resources MIBThis memo obsoletes RFC 1514, the "Host Resources MIB". This memoextends that specification by clarifying changes based on implementationand deployment experience and documenting the Host Resources MIB inSMIv2 format while remaining semantically identical to the existingSMIv1-based MIB. [STANDARDS TRACK]2789 Freed Mar 2000 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 defined in RFC 2788 [16] to allow monitoring of Message TransferAgents (MTAs). It may also be used to monitor MTA components withingateways. [STANDARDS TRACK]2788 Freed Mar 2000 Network Services Monitoring MIBThis document defines a MIB which contains the elements common to themonitoring of any network service application. [STANDARDS TRACK]Ginoza Informational [Page 3]RFC 2799 Summary of 2700-2799 September 20002787 Jewell Mar 2000 Definitions of Managed Objects for the Virtual Router Redundancy ProtocolThis 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 routersthat employ the Virtual Router Redundancy Protocol (VRRP). [STANDARDSTRACK]2786 St. Johns Mar 2000 Diffie-Helman USM Key Management Information Base and Textual ConventionThis memo defines an experimental portion of the Management InformationBase (MIB) for use with network management protocols the Internetcommunity. In particular, it defines a textual convention for doingDiffie-Helman key agreement key exchanges an set of objects which extendthe usmUserTable to permit the use of DH key exchange in addition to thekey change method. This memo defines an Experimental Protocol for theInternet community.2785 Zuccherato Mar 2000 Methods for Avoiding the "Small-Subgroup" Attacks on the Diffie-Hellman Key Agreement Method for S/MIMEThis document will describe the situations relevant to implementationsof S/MIME version 3 in which protection is necessary and the methodsthat can be used to prevent these attacks. This memo providesinformation for the Internet community.2784 Farinacci Mar 2000 Generic Routing Encapsulation (GRE)This document specifies a protocol for encapsulation of an arbitrarynetwork layer protocol over another arbitrary network layer protocol.[STANDARDS TRACK]Ginoza Informational [Page 4]RFC 2799 Summary of 2700-2799 September 20002783 Mogul Mar 2000 Pulse-Per-Second API for UNIX-like Operating Systems, Version 1.0RFC 1589 did not define an API for managing the PPS facility, leavingimplementors without a portable means for using PPS sources. Thisdocument specifies such an API. This memo provides information for theInternet community.2782 Gulbrandsen Feb 2000 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. [STANDARDS TRACK]2781 Hoffman Feb 2000 UTF-16, an encoding of ISO 10646This document describes the UTF-16 encoding of Unicode/ISO-10646,addresses the issues of serializing UTF-16 as an octet stream fortransmission over the Internet, discusses MIME charset naming asdescribed in [CHARSET-REG], and contains the registration for three MIMEcharset parameter values: UTF-16BE (big-endian), UTF-16LE (little-endian), and UTF-16. This memo provides information for the Internetcommunity.2780 Bradner Mar 2000 IANA Allocation Guidelines For Values In the Internet Protocol and Related HeadersThis memo provides guidance for the IANA to use in assigning parametersfor fields in the IPv4, IPv6, ICMP, UDP and TCP protocol headers. Thisdocument specifies an Internet Best Current Practices for the InternetCommunity, and requests discussion and suggestions for improvements.2779 Day Feb 2000 Instant Messaging / Presence Protocol RequirementsThis document defines a minimal set of requirements that IMPP must meet.This memo provides information for the Internet community.Ginoza Informational [Page 5]RFC 2799 Summary of 2700-2799 September 20002778 Day Feb 2000 A Model for Presence and Instant MessagingThis document defines an abstract model for a presence and instantmessaging system. It defines the various entities involved, definesterminology, and outlines the services provided by the system. Thismemo provides information for the Internet community.2777 Eastlake Feb 2000 Publicly Verifiable Nomcom Random SelectionThis document describes a method for making random selections in such away that the unbiased nature of the choice is publicly verifiable. Thismemo provides information for the Internet community.2776 Handley Feb 2000 Multicast-Scope Zone Announcement Protocol (MZAP)This document defines a protocol, the Multicast-Scope Zone AnnouncementProtocol (MZAP), for discovering the multicast administrative scopezones that are relevant at a particular location. [STANDARDS TRACK]2775 Carpenter Feb 2000 Internet TransparencyThis document describes the current state of the Internet from thearchitectural viewpoint, concentrating on issues of end-to-endconnectivity and transparency.2774 Nielsen Feb 2000 An HTTP Extension FrameworkThis document describes a generic extension mechanism for HTTP, which isdesigned to address the tension between private agreement and publicspecification and to accommodate extension of applications using HTTPclients, servers, and proxies. This memo defines an ExperimentalProtocol for the Internet community.Ginoza Informational [Page 6]RFC 2799 Summary of 2700-2799 September 20002773 Housley Feb 2000 Encryption using KEA and SKIPJACKThis document defines a method to encrypt a file transfer using the FTPspecification STD 9, RFC 959, "File Transfer Protocol (FTP)", (October1985) and RFC 2228, "FTP Security Extensions" (October 1997). This memodefines an Experimental Protocol for the Internet community.2772 Rockell Feb 2000 6Bone Backbone Routing GuidelinesThis document provides a set of guidelines for all 6bone routingequipment operators to use as a reference for efficient and stabledeployment of 6bone routing systems. This memo provides information forthe Internet community.2771 Finlayson Feb 2000 An Abstract API for Multicast Address AllocationThis document describes the "abstract service interface" for the dynamicmulticast address allocation service, as seen by applications. Thismemo provides information for the Internet community.2770 Meyer Feb 2000 GLOP Addressing in 233/8This describes an experimental policy for use of the class D addressspace using 233/8 as the experimental statically assigned subset of theclass D address space. This memo defines an Experimental Protocol forthe Internet community.2769 Villamizar Feb 2000 Routing Policy System ReplicationThis document addresses the need to distribute data over multiplerepositories and delegate authority for data subsets to otherrepositories without compromising the authorization model established inRouting Policy System Security RFC. [STANDARDS TRACK]Ginoza Informational [Page 7]RFC 2799 Summary of 2700-2799 September 20002768 Aiken Feb 2000 Network Policy and Services: A Report of a Workshop on MiddlewareAn ad hoc middleware workshop was held at the International Center forAdvanced Internet Research in December 1998. The need for a moreorganized framework for middleware R&D was recognized, and a list ofspecific topics needing further work was identified. This memo providesinformation for the Internet community.2767 Tsuchiya Feb 2000 Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)This memo proposes a mechanism of dual stack hosts using the techniquecalled "Bump-in-the-Stack" in the IP security area. This memo providesinformation for the Internet community.2766 Tsirtsis Feb 2000 Network Address Translation - Protocol Translation (NAT-PT)This document specifies an IPv4-to-IPv6 transition mechanism, inaddition to those already specified. [STANDARDS TRACK]2765 Nordmark Feb 2000 Stateless IP/ICMP Translation Algorithm (SIIT)This document specifies a transition mechanism algorithm in addition tothe mechanisms already specified. [STANDARDS TRACK]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -