Movatterモバイル変換
[0]ホーム
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]
INFORMATIONAL
Network Working Group S. GinozaRequest for Comments: 2999 ISICategory: Informational August 2001Request for Comments Summary RFC Numbers 2900-2999Status of This Memo This RFC is a slightly annotated list of the 100 RFCs fromRFC 2900 through RFCs 2999. 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--- ------ ---- -----2999 Ginoza Aug 2001 Request for Comments SummaryThis memo.2998 Bernet Nov 2000 A Framework for Integrated Services Operation over Diffserv NetworksThis document describes a framework by which Integrated Services may besupported over Diffserv networks. This memo provides information forthe Internet community.Ginoza Informational [Page 1]
RFC 2999 Summary of 2900-2999 August 20012997 Bernet Nov 2000 Specification of the Null Service TypeThe Null Service allows applications to identify themselves to networkQuality of Service (QoS) policy agents, using RSVP signaling. However,it does not require them to specify resource requirements. QoS policyagents in the network respond by applying QoS policies appropriate forthe application (as determined by the network administrator). This modeof RSVP usage is particularly applicable to networks that combinedifferentiated service (diffserv) QoS mechanisms with RSVP signaling.In this environment, QoS policy agents may direct the signaledapplication's traffic to a particular diffserv class of service.[STANDARDS TRACK]2996 Bernet Nov 2000 Format of the RSVP DCLASS ObjectThis document specifies the format of the DCLASS object and brieflydiscusses its use. [STANDARDS TRACK]2995 Lu Nov 2000 Pre-SPIRITS Implementations of PSTN-initiated ServicesThis document describes four existing implementations of SPIRITS-likeservices from Korea Telecom, Lucent Technologies, NEC, and Telia incooperation with Nortel Networks. SPIRITS-like services are thoseoriginating in the Public Switched Telephone Network (PSTN) andnecessitating the interactions of the Internet and PSTN. This memoprovides information for the Internet community.2994 Ohta Nov 2000 A Description of the MISTY1 Encryption AlgorithmThis document describes a secret-key cryptosystem MISTY1, which is blockcipher with a 128-bit key, a 64-bit block and a variable number ofrounds. It documents the algorithm description including key schedulingpart and data randomizing part. This memo provides information for theInternet community.Ginoza Informational [Page 2]
RFC 2999 Summary of 2900-2999 August 20012993 Hain Nov 2000 Architectural Implications of NATThis document discusses some of the architectural implications andguidelines for implementations of Network Address Translation (NAT).This memo provides information for the Internet community.2992 Hopps Nov 2000 Analysis of an Equal-Cost Multi-Path AlgorithmEqual-cost multi-path (ECMP) is a routing technique for routing packetsalong multiple paths of equal cost. The forwarding engine identifiespaths by next-hop. When forwarding a packet the router must decidewhich next-hop (path) to use. This document gives an analysis of onemethod for making that decision. The analysis includes the performanceof the algorithm and the disruption caused by changes to the set ofnext-hops. This memo provides information for the Internet community.2991 Thaler Nov 2000 Multipath Issues in Unicast and Multicast Next-Hop SelectionThe effect of multipath routing on a forwarder is that the forwarderpotentially has several next-hops for any given destination and must usesome method to choose which next-hop should be used for a given datapacket. This memo summarizes current practices, problems, andsolutions. This memo provides information for the Internet community.2990 Huston Nov 2000 Next Steps for the IP QoS ArchitectureThis document highlights the outstanding architectural issues relatingto the deployment and use of QoS mechanisms within internet networks,noting those areas where further standards work may assist with thedeployment of QoS internets. This document is the outcome of acollaborative exercise on the part of the Internet Architecture Board.This memo provides information for the Internet community.2989 Aboba Nov 2000 Criteria for Evaluating AAA Protocols for Network AccessThis document represents a summary of Authentication, Authorization,Accounting (AAA) protocol requirements for network access. This memoprovides information for the Internet community.Ginoza Informational [Page 3]
RFC 2999 Summary of 2900-2999 August 20012988 Paxson Nov 2000 Computing TCP's Retransmission TimerThis document defines the standard algorithm that Transmission ControlProtocol (TCP) senders are required to use to compute and manage theirretransmission timer. [STANDARDS TRACK]2987 Hoffman Nov 2000 Registration of Charset and Languages Media Features TagsThis document contains the registration for two media feature tags:"charset" and "language". [STANDARDS TRACK]2986 Nystrom Nov 2000 PKCS #10: Certification Request Syntax Specification Version 1.7This memo represents a republication of PKCS #10 v1.7 from RSALaboratories' Public-Key Cryptography Standards (PKCS) series, andchange control is retained within the PKCS process. The body of thisdocument, except for the security considerations section, is takendirectly from the PKCS #9 v2.0 or the PKCS #10 v1.7 document. This memoprovides information for the Internet community.2985 Nystrom Nov 2000 PKCS #9: Selected Object Classes and Attribute Types Version 2.0This memo represents a republication of PKCS #9 v2.0 from RSALaboratories' Public-Key Cryptography Standards (PKCS) series, andchange control is retained within the PKCS process. The body of thisdocument, except for the security considerations section, is takendirectly from that specification. This memo provides information forthe Internet community.2984 Adams Oct 2000 Use of the CAST-128 Encryption Algorithm in CMSThis document specifies how to incorporate CAST-128 into the S/MIMECryptographic Message Syntax (CMS) as an additional algorithm forsymmetric encryption. [STANDARDS TRACK]Ginoza Informational [Page 4]
RFC 2999 Summary of 2900-2999 August 20012983 Black Oct 2000 Differentiated Services and TunnelsThis document considers the interaction of Differentiated Services(diffserv) with IP tunnels of various forms. This memo providesinformation for the Internet community.2982 Kavasseri Oct 2000 Distributed Management Expression 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 used for managing expressionsof MIB objects. [STANDARDS TRACK]2981 Kavasseri Oct 2000 Event 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 that can be used to manage andmonitor MIB objects and take action through events. [STANDARDS TRACK]2980 Barber Oct 2000 Common NNTP ExtensionsIn this document, a number of popular extensions to the Network NewsTransfer Protocol (NNTP) protocol defined inRFC 977 are documented anddiscussed. While this document is not intended to serve as a standardof any kind, it will hopefully serve as a reference document for futureimplementers of the NNTP protocol. This memo provides information forthe Internet community.2979 Freed Oct 2000 Behavior of and Requirements for Internet FirewallsThis memo defines behavioral characteristics of and interoperabilityrequirements for Internet firewalls. This memo provides information forthe Internet community.Ginoza Informational [Page 5]
RFC 2999 Summary of 2900-2999 August 20012978 Freed Oct 2000 IANA Charset Registration ProceduresMultipurpose Internet Mail Extensions (MIME) and various other Internetprotocols are capable of using many different charsets. This in turnmeans that the ability to label different charsets is essential. Thisdocument specifies an Internet Best Current Practices for the InternetCommunity, and requests discussion and suggestions for improvements.2977 Glass Oct 2000 Mobile IP Authentication, Authorization, and Accounting RequirementsThis document contains the requirements which would have to be supportedby a AAA service to aid in providing Mobile IP services. This memoprovides information for the Internet community.2976 Donovan Oct 2000 The SIP INFO MethodThis document proposes an extension to the Session Initiation Protocol(SIP). This extension adds the INFO method to the SIP protocol. Theintent of the INFO method is to allow for the carrying of sessionrelated control information that is generated during a session.[STANDARDS TRACK]2975 Aboba Oct 2000 Introduction to Accounting ManagementThis document describes and discusses the issues involved in the designof the modern accounting systems. The field of Accounting Management isconcerned with the collection the collection of resource consumptiondata for the purposes of capacity and trend analysis, cost allocation,auditing, and billing. This memo provides information for the Internetcommunity.2974 Handley Oct 2000 Session Announcement ProtocolThis document describes version 2 of the multicast session directoryannouncement protocol, Session Announcement Protocol (SAP), and therelated issues affecting security and scalability that should be takeninto account by implementors. This memo defines an ExperimentalProtocol for the Internet community.Ginoza Informational [Page 6]
RFC 2999 Summary of 2900-2999 August 20012973 Balay Oct 2000 IS-IS Mesh GroupsThis document describes a mechanism to reduce redundant packettransmissions for the Intermediate System to Intermediate System (IS-IS)Routing protocol, as described in ISO 10589. This memo providesinformation for the Internet community.2972 Popp Oct 2000 Context and Goals for Common Name ResolutionThis document establishes the context and goals for a Common NameResolution Protocol. This memo provides information for the Internetcommunity.2971 Showalter Oct 2000 IMAP4 ID extensionThis document describes an ID extension which will enable InternetMessage Access Protocol - Version 4rev1 (IMAP4rev1) to advertise whatprogram a client or server uses to provide service. The ID extensionallows the server and client to exchange identification information ontheir implementation in order to make bug reports and usage statisticsmore complete. [STANDARDS TRACK]2970 Daigle Oct 2000 Architecture for Integrated Directory Services - Result from TISDAGDrawing from experiences with the TISDAG (Technical Infrastructure forSwedish Directory Access Gateways) project, this document outlines anapproach to providing the necessary infrastructure for integrating suchwidely-scattered servers into a single service, rather than attemptingto mandate a single protocol and schema set for all participatingservers to use. This memo provides information for the Internetcommunity.Ginoza Informational [Page 7]
RFC 2999 Summary of 2900-2999 August 20012969 Eklof Oct 2000 Wide Area Directory Deployment - Experiences from TISDAGThis document catalogues some of the experiences gained in developingthe necessary infrastructure for a national (i.e., multi-organizational)directory service and pilot deployment of the service in an environmentwith off-the-shelf directory service products. This memo providesinformation for the Internet community.2968 Daigle Oct 2000 Mesh of Multiple DAG servers - Results from TISDAGThis document defines the basic principle for establishing a mesh, thatinteroperating services should exchange index objects, according to thearchitecture of the mesh (e.g., hierarchical, or graph-like, preferablywithout loops!). The Common Indexing Protocol (CIP) is designed tofacilitate the creation not only of query referral indexes, but also ofmeshes of (loosely) affiliated referral indexes. The purpose of such amesh of servers is to implement some kind of distributed sharing ofindexing and/or searching tasks across different servers. So far, theTISDAG (Technical Infrastructure for Swedish Directory Access Gateways)project has focused on creating a single referral index; the obviousnext step is to integrate that into a larger set of interoperatingservices. This memo provides information for the Internet community.2967 Daigle Oct 2000 TISDAG - Technical Infrastructure for Swedish Directory Access GatewaysThe overarching goal of this project is to develop the necessarytechnical infrastructure to provide a single-access-point service forsearching for whitepages information on Swedish Internet users. Thismemo provides information for the Internet community.2966 Li Oct 2000 Domain-wide Prefix Distribution with Two-Level IS-ISThis document describes extensions to the Intermediate System toIntermediate System (IS-IS) protocol to support optimal routing within atwo-level domain. This memo provides information for the Internetcommunity.Ginoza Informational [Page 8]
RFC 2999 Summary of 2900-2999 August 20012965 Kristol Oct 2000 HTTP State Management MechanismThis document specifies a way to create a stateful session withHypertext Transfer Protocol (HTTP) requests and responses. [STANDARDSTRACK]2964 Moore Oct 2000 Use of HTTP State ManagementThis memo identifies specific uses of Hypertext Transfer Protocol (HTTP)State Management protocol which are either (a) not recommended by theIETF, or (b) believed to be harmful, and discouraged. This memo alsodetails additional privacy considerations which are not covered by theHTTP State Management protocol specification. This document specifiesan Internet Best Current Practices for the Internet Community, andrequests discussion and suggestions for improvements.2963 Bonaventure Oct 2000 A Rate Adaptive Shaper for Differentiated ServicesThis memo describes several Rate Adaptive Shapers (RAS) that can be usedin combination with the single rate Three Color Markers (srTCM) and thetwo rate Three Color Marker (trTCM) described inRFC2697 andRFC2698,respectively. This memo provides information for the Internetcommunity.2962 Raz Oct 2000 An SNMP Application Level Gateway for Payload Address TranslationThis document describes the ALG (Application Level Gateway) for the SNMP(Simple Network Management Protocol) by which IP (Internet Protocol)addresses in the payload of SNMP packets are statically mapped from onegroup to another. This memo provides information for the Internetcommunity.Ginoza Informational [Page 9]
RFC 2999 Summary of 2900-2999 August 20012961 Berger Apr 2001 RSVP Refresh Overhead Reduction ExtensionsThis document describes a number of mechanisms that can be used toreduce processing overhead requirements of refresh messages, eliminatethe state synchronization latency incurred when an RSVP (ResourceReserVation Protocol) message is lost and, when desired, refreshingstate without the transmission of whole refresh messages. [STANDARDSTRACK]2960 Stewart Oct 2000 Stream Control Transmission ProtocolThis document describes the Stream Control Transmission Protocol (SCTP).[STANDARDS TRACK]2959 Baugher Oct 2000 Real-Time Transport Protocol Management Information BaseThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.[STANDARDS TRACK]2958 Daigle Oct 2000 The application/whoispp- response Content-typeThe intention of this document, in conjunction withRFC 2957, is toenable MIME-enabled mail software, and other systems using Internetmedia types, to carry out Whois++ transactions. This memo providesinformation for the Internet community.2957 Daigle Oct 2000 The application/whoispp-query Content-TypeThe intention of this document, in conjunction withRFC 2958, is toenable MIME-enabled mail software, and other systems using Internetmedia types, to carry out Whois++ transactions. This memo providesinformation for the Internet community.Ginoza Informational [Page 10]
RFC 2999 Summary of 2900-2999 August 20012956 Kaat Oct 2000 Overview of 1999 IAB Network Layer WorkshopThis document is an overview of a workshop held by the InternetArchitecture Board (IAB) on the Internet Network Layer architecturehosted by SURFnet in Utrecht, the Netherlands on 7-9 July 1999. Thegoal of the workshop was to understand the state of the network layerand its impact on continued growth and usage of the Internet. This memoprovides information for the Internet community.2955 Rehbehn Oct 2000 Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking FunctionThis memo defines a Management Information Base (MIB) to configure,monitor, and control a service interworking function (IWF) for PermanentVirtual Connections (PVC) between Frame Relay and Asynchronous TransferMode (ATM) technologies. [STANDARDS TRACK]2954 Rehbehn Oct 2000 Definitions of Managed Objects for Frame Relay ServiceThis memo defines an extension to the Management Information Base (MIB)for use with network management protocols in Transmission ControlProtocol/Internet Protocol-based (TCP/IP) internets. In particular, itdefines objects for managing the frame relay service. [STANDARDS TRACK]2953 Ts'o Sep 2000 Telnet Encryption: DES 64 bit Output FeedbackThis document specifies how to use the data encryption standard (DES)encryption algorithm in output feedback mode with the telnet encryptionoption. This memo provides information for the Internet community.2952 Ts'o Sep 2000 Telnet Encryption: DES 64 bit Cipher FeedbackThis document specifies how to use the DES encryption algorithm incipher feedback mode with the telnet encryption option. This memoprovides information for the Internet community.Ginoza Informational [Page 11]
RFC 2999 Summary of 2900-2999 August 20012951 Housley Sep 2000 TELNET Authentication Using KEA and SKIPJACKThis document defines a method to authenticate TELNET using the KeyExchange Algorithm (KEA), and encryption of the TELNET stream usingSKIPJACK. This memo provides information for the Internet community.2950 Altman Sep 2000 Telnet Encryption: CAST-128 64 bit Cipher FeedbackThis document specifies how to use the CAST-128 encryption algorithm incipher feedback mode with the telnet encryption option. Two key sizesare defined: 40 bit and 128 bit. [STANDARDS TRACK]2949 Altman Sep 2000 Telnet Encryption: CAST-128 64 bit Output FeedbackThis document specifies how to use the CAST-128 encryption algorithm inoutput feedback mode with the telnet encryption option. Two key sizesare defined: 40 bit and 128 bit. [STANDARDS TRACK]2948 Altman Sep 2000 Telnet Encryption: DES3 64 bit Output FeedbackThis document specifies how to use the Triple-DES (data encryptionstandard) encryption algorithm in output feedback mode with the telnetencryption option. [STANDARDS TRACK]2947 Altman Sep 2000 Telnet Encryption: DES3 64 bit Cipher FeedbackThis document specifies how to use the Triple-DES (data encryptionstandard) encryption algorithm in cipher feedback mode with the telnetencryption option. [STANDARDS TRACK]2946 Ts'o Sep 2000 Telnet Data Encryption OptionThis document describes a the telnet encryption option as a genericmethod of providing data confidentiality services for the telnet datastream. [STANDARDS TRACK]Ginoza Informational [Page 12]
RFC 2999 Summary of 2900-2999 August 20012945 Wu Sep 2000 The SRP Authentication and Key Exchange SystemThis document describes a cryptographically strong networkauthentication mechanism known as the Secure Remote Password (SRP)protocol. [STANDARDS TRACK]2944 Wu Sep 2000 Telnet Authentication: SRPThis document specifies an authentication scheme for the Telnet protocolunder the framework described inRFC 2941, using the Secure RemotePassword Protocol (SRP) authentication mechanism. [STANDARDS TRACK]2943 Housley Sep 2000 TELNET Authentication Using DSAThis document defines a telnet authentication mechanism using theDigital Signature Algorithm (DSA). It relies on the TelnetAuthentication Option. [STANDARDS TRACK]2942 Ts'o Sep 2000 Telnet Authentication: Kerberos Version 5This document describes how Kerberos Version 5 is used with the telnetprotocol. It describes an telnet authentication suboption to be usedwith the telnet authentication option. [STANDARDS TRACK]2941 Ts'o Sep 2000 Telnet Authentication OptionThis document describes the authentication option to the telnet protocolas a generic method for negotiating an authentication type and modeincluding whether encryption should be used and if credentials should beforwarded. [STANDARDS TRACK]2940 Smith Oct 2000 Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol ClientsThis 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 a client of the Common OpenPolicy Service (COPS) protocol. [STANDARDS TRACK]Ginoza Informational [Page 13]
RFC 2999 Summary of 2900-2999 August 20012939 Droms Sep 2000 Procedures and IANA Guidelines for Definition of New DHCP Options and Message TypesThis document describes the procedure for defining new DHCP options andmessage types. This document specifies an Internet Best CurrentPractices for the Internet Community, and requests discussion andsuggestions for improvements.2938 Klyne Sep 2000 Identifying Composite Media FeaturesThis document describes an abbreviated format for a composite mediafeature set, based upon a hash of the feature expression describing thatcomposite. [STANDARDS TRACK]2937 Smith Sep 2000 The Name Service Search Option for DHCPThis document defines a new Dynamic Host Configuration Protocol (DHCP)option which is passed from the DHCP Server to the DHCP Client tospecify the order in which name services should be consulted whenresolving hostnames and other information. [STANDARDS TRACK]2936 Eastlake Sep 2000 HTTP MIME Type Handler DetectionEntities composing web pages to provide services over the HypertextTransfer Protocol (HTTP) frequently have the problem of not knowing whatMultipurpose Internet Mail Extensions (MIME) types have handlersinstalled at a user's browser. This document summarizes reasonabletechniques to solve this problem for most of the browsers actuallydeployed on the Internet as of early 2000. This memo providesinformation for the Internet community.2935 Eastlake Sep 2000 Internet Open Trading Protocol (IOTP) HTTP SupplementThe goal of mapping to the transport layer is to ensure that theunderlying XML documents are carried successfully between the variousparties. This document describes that mapping for the Hyper TextTransport Protocol (HTTP), Versions 1.0 and 1.1. [STANDARDS TRACK]Ginoza Informational [Page 14]
RFC 2999 Summary of 2900-2999 August 20012934 McCloghrie Oct 2000 Protocol Independent Multicast MIB for IPv4This 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 the ProtocolIndependent Multicast (PIM) protocol for IPv4. This memo defines anExperimental Protocol for the Internet community.2933 McCloghrie Oct 2000 Internet Group Management Protocol MIBThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it describes objects used for managing the Internet GroupManagement Protocol (IGMP). [STANDARDS TRACK]2932 McCloghrie Oct 2000 IPv4 Multicast Routing 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 used for managing IP MulticastRouting for IPv4, independent of the specific multicast routing protocolin use. [STANDARDS TRACK]2931 Eastlake Sep 2000 DNS Request and Transaction Signatures ( SIG(0)s )This document describes the minor but non-interoperable changes inRequest and Transaction signature resource records ( SIG(0)s ) thatimplementation experience has deemed necessary. [STANDARDS TRACK]2930 Eastlake Sep 2000 Secret Key Establishment for DNS (TKEY RR)This document describes a Transaction Key (TKEY) RR that can be used ina number of different modes to establish shared secret keys between aDNS resolver and server. [STANDARDS TRACK]Ginoza Informational [Page 15]
RFC 2999 Summary of 2900-2999 August 20012929 Eastlake Sep 2000 Domain Name System (DNS) IANA ConsiderationsThis document discusses the Internet Assigned Number Authority (IANA)parameter assignment considerations given for the allocation of DomainName System (DNS) classes, Resource Record (RR) types, operation codes,error codes, etc. This document specifies an Internet Best CurrentPractices for the Internet Community, and requests discussion andsuggestions for improvements.2928 Hinden Sep 2000 Initial IPv6 Sub-TLA ID AssignmentsThis document defines initial assignments of IPv6 Sub-Top-LevelAggregation Identifiers (Sub-TLA ID) to the Address Registries. Thismemo provides information for the Internet community.2927 Wahl Sep 2000 MIME Directory Profile for LDAP SchemaThis document defines a multipurpose internet mail extensions (MIME)directory profile for holding a lightweight directory access protocol(LDAP) schema. This memo provides information for the Internetcommunity.2926 Kempf Sep 2000 Conversion of LDAP Schemas to and from SLP TemplatesThis document describes a procedure for mapping between Service LocationProtocol (SLP) service advertisements and lightweight directory accessprotocol (LDAP) descriptions of services. This memo providesinformation for the Internet community.2925 White Sep 2000 Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup OperationsThis memo defines Management Information Bases (MIBs) for performingremote ping, traceroute and lookup operations at a remote host.[STANDARDS TRACK]Ginoza Informational [Page 16]
RFC 2999 Summary of 2900-2999 August 20012924 Brownlee Sep 2000 Accounting Attributes and Record FormatsThis document summarises Internet Engineering Task Force (IETF) andInternational Telecommunication Union (ITU-T) documents related toAccounting. This memo provides information for the Internet community.2923 Lahey Sep 2000 TCP Problems with Path MTU DiscoveryThis memo catalogs several known Transmission Control Protocol (TCP)implementation problems dealing with Path Maximum Transmission UnitDiscovery (PMTUD), including the long-standing black hole problem,stretch acknowlegements (ACKs) due to confusion between Maximum SegmentSize (MSS) and segment size, and MSS advertisement based on PMTU. Thismemo provides information for the Internet community.2922 Bierman Sep 2000 Physical Topology 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 used for managing physicaltopology identification and discovery. This memo provides informationfor the Internet community.2921 Fink Sep 2000 6BONE pTLA and pNLA Formats (pTLA)This memo defines how the 6bone uses the 3FFE::/16 IPv6 address prefix,allocated inRFC 2471, "IPv6 Testing Address Allocation", to createpseudo Top-Level Aggregation Identifiers (pTLA's) and pseudo Next-LevelAggregation Identifiers (pNLA's). This memo provides information forthe Internet community.2920 Freed Sep 2000 SMTP Service Extension for Command PipeliningThis memo defines an extension to the Simple Mail Transfer Protocol(SMTP) service whereby a server can indicate the extent of its abilityto accept multiple commands in a single Transmission Control Protocol(TCP) send operation. [STANDARDS TRACK]Ginoza Informational [Page 17]
RFC 2999 Summary of 2900-2999 August 20012919 Chandhok Mar 2001 List-Id: A Structured Field and Namespace for the Identification of Mailing ListsSoftware that handles electronic mailing list messages (servers and useragents) needs a way to reliably identify messages that belong to aparticular mailing list. With the advent of list management headers, ithas become even more important to provide a unique identifier for amailing list regardless of the particular host that serves as the listprocessor at any given time. [STANDARDS TRACK]2918 Chen Sep 2000 Route Refresh Capability for BGP-4This document defines a new Border Gateway Protocol (BGP) capabilitytermed 'Route Refresh Capability', which would allow the dynamicexchange of route refresh request between BGP speakers and subsequentre-advertisement of the respective Adj-RIB-Out. [STANDARDS TRACK]2917 Muthukrishnan Sep 2000 A Core MPLS IP VPN ArchitectureThis memo presents an approach for building core Virtual Private Network(VPN) services in a service provider's MPLS backbone. This memoprovides information for the Internet community.2916 Faltstrom Sep 2000 E.164 number and DNSThis document discusses the use of the Domain Name System (DNS) forstorage of E.164 numbers. [Standards Track]2915 Mealling Sep 2000 The Naming Authority Pointer (NAPTR) DNS Resource RecordThis document describes a Domain Name System (DNS) resource record whichspecifies a regular expression based rewrite rule that, when applied toan existing string, will produce a new domain label or Uniform ResourceIdentifier (URI). [STANDARDS TRACK]Ginoza Informational [Page 18]
RFC 2999 Summary of 2900-2999 August 20012914 Floyd Sep 2000 Congestion Control PrinciplesThe goal of this document is to explain the need for congestion controlin the Internet, and to discuss what constitutes correct congestioncontrol. This document specifies an Internet Best Current Practices forthe Internet Community, and requests discussion and suggestions forimprovements.2913 Klyne Sep 2000 MIME Content Types in Media Feature ExpressionsThis memo defines a media feature tag whose value is a MultipurposeInternet Mail Extensions (MIME) content type. [STANDARDS TRACK]2912 Klyne Sep 2000 Indicating Media Features for MIME ContentThis memo defines a Multipurpose Internet Mail Extensions (MIME) 'Content-features:' header that can be used to annotate a MIME messagepart using this expression format, and indicates some ways it might beused. [STANDARDS TRACK]2911 Hastings Sep 2000 Internet Printing Protocol/1.1: Model and SemanticsThis document is one of a set of documents, which together describe allaspects of a new Internet Printing Protocol (IPP). [STANDARDS TRACK]2910 Herriot Sep 2000 Internet Printing Protocol/1.1: Encoding and TransportThis document is one of a set of documents, which together describe allaspects of a new Internet Printing Protocol (IPP). [STANDARDS TRACK]Ginoza Informational [Page 19]
RFC 2999 Summary of 2900-2999 August 20012909 Radoslavov Sep 2000 The Multicast Address-Set Claim (MASC) ProtocolThis document describes the Multicast Address-Set Claim (MASC) protocolwhich can be used for inter-domain multicast address set allocation.This memo defines an Experimental Protocol for the Internet community.2908 Thaler Sep 2000 The Internet Multicast Address Allocation ArchitectureThis document proposes a multicast address allocation architecture(MALLOC) for the Internet. This memo provides information for theInternet community.2907 Kermode Sep 2000 MADCAP Multicast Scope Nesting State OptionThis document defines a new option to the Multicast Address DynamicClient Allocation Protocol (MADCAP) to support nested scoping.[STANDARDS TRACK]2906 Farrell Aug 2000 AAA Authorization RequirementsThis document specifies the requirements that AuthenticationAuthorization Accounting (AAA) protocols must meet in order to supportauthorization services in the Internet. This memo provides informationfor the Internet community.2905 Vollbrecht Aug 2000 AAA Authorization Application ExamplesThis memo describes several examples of applications requiringauthorization. This memo provides information for the Internetcommunity.2904 Vollbrecht Aug 2000 AAA Authorization FrameworkThis memo serves as the base requirements for Authorization of InternetResources and Services (AIRS). It presents an architectural frameworkfor understanding the authorization of Internet resources and servicesand derives requirements for authorization protocols. This memoprovides information for the Internet community.Ginoza Informational [Page 20]
RFC 2999 Summary of 2900-2999 August 20012903 de Laat Aug 2000 Generic AAA ArchitectureThis memo proposes an Authentication, Authorization, Accounting (AAA)architecture that would incorporate a generic AAA server along with anapplication interface to a set of Application Specific Modules thatcould perform application specific AAA functions. This memo defines anExperimental Protocol for the Internet community.2902 Deering Aug 2000 Overview of the 1998 IAB Routing WorkshopThis document is an overview of a Routing workshop held by the InternetArchitecture Board (IAB) during March 25-27, 1998. This memo providesinformation for the Internet community.2901 Wenzel Aug 2000 Guide to Administrative Procedures of the Internet InfrastructureThis document describes the administrative procedures for networksseeking to connect to the global Internet. This memo providesinformation for the Internet community.2900 Reynolds Aug 2001 Internet Official Protocol StandardsThis memo contains a snapshot of the state of standardization ofprotocols used in the Internet as of July 17, 2001. It lists officialprotocol standards and Best Current Practice RFCs; it is not a completeindex to the RFC series. This memo is an Internet Standard.Security Considerations This memo does not affect the technical security of the Internet, but may cite important security specifications.Ginoza Informational [Page 21]
RFC 2999 Summary of 2900-2999 August 2001Author'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 22]
RFC 2999 Summary of 2900-2999 August 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 23]
[8]ページ先頭