📄 rfc2599.txt
字号:
Network Working Group A. DeLaCruzRequest for Comments: 2599 ISICategory: Informational March 2000 Request for Comments Summary RFC Numbers 2500-2599Status of This Memo This RFC is a slightly annotated list of the 100 RFCs from RFC 2500 through RFCs 2599. 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 (2000). 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--- ------ ---- -----2599 Delacruz Mar 2000 Request for Comments SummaryThis memo.2598 Jacobson Jun 1999 An Expedited Forwarding PHBThe definition of PHBs (per-hop forwarding behaviors) is a critical partof the work of the Diffserv Working Group. This document describes aPHB called Expedited Forwarding. [STANDARDS-TRACK]DeLaCruz Informational [Page 1]RFC 2599 Summary of 2500-2599 March 20002597 Heinanen Jun 1999 Assured Forwarding PHB GroupThis document defines a general use Differentiated Services (DS)Per-Hop-Behavior (PHB) Group called Assured Forwarding (AF).[STANDARDS-TRACK]2596 Wahl May 1999 Use of Language Codes in LDAPThis document describes how language codes are carried in LDAP and areto be interpreted by LDAP servers. [STANDARDS-TRACK]2595 Newman Jun 1999 Using TLS with IMAP, POP3 and ACAPRecognizing that such sites will desire simple password authenticationin combination with TLS encryption, this specification defines the PLAINSASL mechanism for use with protocols which lack a simple passwordauthentication command such as ACAP and SMTP. [STANDARDS-TRACK]2594 Hazewinkel May 1999 Definitions of Managed Objects for WWW ServicesThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet Community. Inparticular it describes a set of objects for managing World Wide Web(WWW) services. [STANDARDS-TRACK]2593 Schoenwaelder May 1999 Script MIB Extensibility Protocol Version 1.0The Script MIB extensibility protocol (SMX) defined in this memoseparates language specific runtime systems from language independentScript MIB implementations. This memo defines an Experimental Protocolfor the Internet community.DeLaCruz Informational [Page 2]RFC 2599 Summary of 2500-2599 March 20002592 Levi May 1999 Definitions of Managed Objects for the Delegation of Management ScriptsThis memo defines a portion of the Management Information Base (MIB)for use with network management protocols in the Internet community.In particular, it describes a set of managed objects that allow thedelegation of management scripts to distributed managers.[STANDARDS-TRACK]2591 Levi May 1999 Definitions of Managed Objects for Scheduling Management OperationsThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.[STANDARDS-TRACK]2590 Conta May 1999 Transmission of IPv6 Packets over Frame Relay Networks SpecificationThis memo describes mechanisms for the transmission of IPv6 packets overFrame Relay networks. [STANDARDS-TRACK]2589 Yaacovi May 1999 Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory ServicesThis document defines the requirements for dynamic directory servicesand specifies the format of request and response extended operations forsupporting client-server interoperation in a dynamic directoriesenvironment. [STANDARDS-TRACK]2588 Finlayson May 1999 IP Multicast and FirewallsIn this document, we discuss the issues surrounding the traversal of IPmulticast traffic across a firewall, and describe possible ways in whicha firewall can implement and control this traversal. We also explainwhy some firewall mechanisms - such as SOCKS - that were designedspecifically for unicast traffic, are less appropriate for multicast.This memo provides information for the Internet community.DeLaCruz Informational [Page 3]RFC 2599 Summary of 2500-2599 March 20002587 Boeyen Jun 1999 Internet X.509 Public Key Infrastructure LDAPv2 SchemaThe schema defined in this document is a minimal schema to support PKIXin an LDAPv2 environment, as defined in RFC 2559. Only PKIX-specificcomponents are specified here. [STANDARDS-TRACK]2586 Salsman May 1999 The Audio/L16 MIME content typeThis document defines the audio/L16 MIME type, a reasonable qualityaudio format for use in Internet applications. This memo providesinformation for the Internet community.2585 Housley May 1999 Internet X.509 Public Key Infrastructure Operational The protocol conventions Protocols: FTP and HTTPThe protocol conventions described in this document satisfy some of theoperational requirements of the Internet Public Key Infrastructure(PKI). This document specifies the conventions for using the FileTransfer Protocol (FTP) and the Hypertext Transfer Protocol (HTTP) toobtain certificates and certificate revocation lists (CRLs) from PKIrepositories. [STANDARDS-TRACK]2584 Clouston May 1999 Definitions of Managed Objects for APPN/HPR in IP NetworksThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it defines objects for monitoring and controlling HPR (HighPerformance Routing) network devices which have the capability tocommunicate in IP (Internet Protocol) networks. [STANDARDS-TRACK]2583 Carlson May 1999 Guidelines for Next Hop Client (NHC) DevelopersThis document provides guidelines for developers of the Next HopResolution Protocol Clients (NHC). The intent is to define theinteraction between the NHC code and the TCP/IP protocol stack of thelocal host operating system. This memo provides information for theInternet community.DeLaCruz Informational [Page 4]RFC 2599 Summary of 2500-2599 March 20002582 Floyd Apr 1999 The NewReno Modification to TCP's Fast Recovery AlgorithmThis document describes a specific algorithm for responding to partialacknowledgments, referred to as NewReno. This memo defines anExperimental Protocol for the Internet community.2581 Allman Apr 1999 TCP Congestion ControlThis document defines TCP's four intertwined congestion controlalgorithms: slow start, congestion avoidance, fast retransmit, and fastrecovery. In addition, the document specifies how TCP should begintransmission after a relatively long idle period, as well as discussingvarious acknowledgment generation methods. [STANDARDS-TRACK]2580 McCloghrie Apr 1999 Conformance Statements for SMIv2Collections of related objects are defined in MIB modules. It may beuseful to define the acceptable lower-bounds of implementation, alongwith the actual level of implementation achieved. It is the purposeof this document to define the notation used for these purposes.[STANDARDS-TRACK]2579 McCloghrie Apr 1999 Textual Conventions for SMIv2It is the purpose of this document to define the initial set of textualconventions available to all MIB modules. [STANDARDS-TRACK]2578 McCloghrie Apr 1999 Structure of Management Information Version 2 (SMIv2)It is the purpose of this document, the Structure of ManagementInformation Version 2 (SMIv2), to define that adapted subset, and toassign a set of associated administrative values. [STANDARDS-TRACK]2577 Allman May 1999 FTP Security ConsiderationsThis document provides suggestions for system administrators and thoseimplementing FTP servers that will decrease the security problemsassociated with FTP. This memo provides information for the Internetcommunity.DeLaCruz Informational [Page 5]RFC 2599 Summary of 2500-2599 March 20002576 Frye March 2000 Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management FrameworkThe purpose of this document is to describe coexistence betweenversion 3 of the Internet-standard Network Management Framework,(SNMPv3), version 2 of the Internet-standard Network ManagementFramework (SNMPv2), and the original Internet-standard NetworkManagement Framework (SNMPv1). [STANDARDS TRACK]2575 Wijnen Apr 1999 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)This document describes the View-based Access Control Model for use inthe SNMP architecture (RFC2571). It defines the Elements of Procedurefor controlling access to management information. This document alsoincludes a MIB for remotely managing the configuration parameters forthe View-based Access Control Model. [STANDARDS-TRACK]2574 Blumenthal Apr 1999 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)This document describes the User-based Security Model (USM) for SNMPversion 3 for use in the SNMP architecture. It defines the Elementsof Procedure for providing SNMP message level security. This documentalso includes a MIB for remotely monitoring/managing the configurationparameters for this Security Model. [STANDARDS-TRACK]2573 Levi Apr 1999 SNMP ApplicationsThis memo describes five types of SNMP applications which make use ofan SNMP engine. This memo also defines MIB modules for specifyingtargets of management operations, for notification filtering, and forproxy fowarding. [STANDARDS-TRACK]DeLaCruz Informational [Page 6]RFC 2599 Summary of 2500-2599 March 20002572 Case May 1999 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)This document describes the Message Processing and Dispatching forSNMP messages within the SNMP architecture. It defines the proceduresfor dispatching potentially multiple versions of SNMP messages to theproper SNMP Message Processing Models, and for dispatching PDUs toSNMP applications. This document also describes one MessageProcessing Model - the SNMPv3 Message Processing Model.[STANDARDS-TRACK]2571 Harrington May 1999 An Architecture for Describing SNMP Management FrameworksThis document describes an architecture for describing SNMP ManagementFrameworks. [STANDARDS-TRACK]2570 Case Apr 1999 Introduction to Version 3 of the Internet-standard Network Management FrameworkThe purpose of this document is to provide an overview of the thirdversion of the Internet-standard Management Framework, termed the SNMPversion 3 Framework (SNMPv3). This memo provides information for theInternet community.2569 Herriot Apr 1999 Mapping between LPD and IPP ProtocolsThis document is one of a set of documents, which together describe allaspects of a new Internet Printing Protocol (IPP). One of the purposesof this document is to compare the functionality of the two protocols.Another purpose is to facilitate implementation of gateways between LPDand IPP. This memo defines an Experimental Protocol for the Internetcommunity.DeLaCruz Informational [Page 7]RFC 2599 Summary of 2500-2599 March 20002568 Zilles Apr 1999 Rationale for the Structure of the Model and Protocol for the Internet Printing ProtocolThis document describes IPP from a high level view, defines a roadmapfor the various documents that form the suite of IPP specifications, andgives background and rationale for the IETF working group's majordecisions. This memo defines an Experimental Protocol for the Internetcommunity.2567 Wright Apr 1999 Design Goals for an Internet Printing ProtocolThis document takes a broad look at distributed printing functionality,and it enumerates real-life scenarios that help to clarify the featuresthat need to be included in a printing protocol for the Internet. Itidentifies requirements for three types of users: end users, operators,and administrators. This memo defines an Experimental Protocol for theInternet community.2566 deBry Apr 1999 Internet Printing Protocol/1.0: Model and SemanticsThis document describes a simplified model consisting of abstractobjects, their attributes, and their operations that is independent ofencoding and transport. This document also addresses security,internationalization, and directory issues. This memo defines anExperimental Protocol for the Internet community.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -