rfc2599.txt

RFC 的详细文档！

Network Working Group                                        A. DeLaCruz
Request for Comments: 2599                                           ISI
Category: Informational                                       March 2000


                      Request for Comments Summary

                         RFC Numbers 2500-2599

Status 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 Summary

This memo.


2598    Jacobson        Jun 1999        An Expedited Forwarding PHB

The definition of PHBs (per-hop forwarding behaviors) is a critical part
of the work of the Diffserv Working Group.  This document describes a
PHB called Expedited Forwarding.  [STANDARDS-TRACK]






DeLaCruz                     Informational                      [Page 1]

RFC 2599                  Summary of 2500-2599                March 2000


2597    Heinanen        Jun 1999        Assured Forwarding PHB Group

This 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 LDAP

This document describes how language codes are carried in LDAP and are
to be interpreted by LDAP servers.  [STANDARDS-TRACK]


2595    Newman          Jun 1999        Using TLS with IMAP, POP3
                                        and ACAP

Recognizing that such sites will desire simple password authentication
in combination with TLS encryption, this specification defines the PLAIN
SASL mechanism for use with protocols which lack a simple password
authentication command such as ACAP and SMTP.  [STANDARDS-TRACK]


2594    Hazewinkel      May 1999        Definitions of Managed
                                        Objects for WWW Services

This 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 objects for managing World Wide Web
(WWW) services.  [STANDARDS-TRACK]


2593    Schoenwaelder    May 1999       Script MIB Extensibility
                                        Protocol Version 1.0

The Script MIB extensibility protocol (SMX) defined in this memo
separates language specific runtime systems from language independent
Script MIB implementations. This memo defines an Experimental Protocol
for the Internet community.













DeLaCruz                     Informational                      [Page 2]

RFC 2599                  Summary of 2500-2599                March 2000


2592    Levi            May 1999        Definitions of Managed Objects
                                        for the Delegation of
                                        Management Scripts

This 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 the
delegation of management scripts to distributed managers.
[STANDARDS-TRACK]


2591     Levi            May 1999       Definitions of Managed Objects
                                        for Scheduling Management
                                        Operations

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.
[STANDARDS-TRACK]


2590    Conta            May 1999       Transmission of IPv6 Packets
                                        over Frame Relay Networks
                                        Specification

This memo describes mechanisms for the transmission of IPv6 packets over
Frame Relay networks.  [STANDARDS-TRACK]


2589    Yaacovi         May 1999        Lightweight Directory Access
                                        Protocol (v3): Extensions for
                                        Dynamic Directory Services

This document defines the requirements for dynamic directory services
and specifies the format of request and response extended operations for
supporting client-server interoperation in a dynamic directories
environment.  [STANDARDS-TRACK]


2588    Finlayson       May 1999        IP Multicast and Firewalls

In this document, we discuss the issues surrounding the traversal of IP
multicast traffic across a firewall, and describe possible ways in which
a firewall can implement and control this traversal.  We also explain
why some firewall mechanisms - such as SOCKS - that were designed
specifically 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 2000


2587     Boeyen         Jun 1999        Internet X.509 Public Key
                                        Infrastructure LDAPv2 Schema

The schema defined in this document is a minimal schema to support PKIX
in an LDAPv2 environment, as defined in RFC 2559.  Only PKIX-specific
components are specified here.  [STANDARDS-TRACK]


2586    Salsman         May 1999       The Audio/L16 MIME content type

This document defines the audio/L16 MIME type, a reasonable quality
audio format for use in Internet applications.  This memo provides
information for the Internet community.


2585     Housley        May 1999        Internet X.509 Public Key
                                        Infrastructure Operational
                                        The protocol conventions
                                        Protocols: FTP and HTTP

The protocol conventions described in this document satisfy some of the
operational requirements of the Internet Public Key Infrastructure
(PKI).  This document specifies the conventions for using the File
Transfer Protocol (FTP) and the Hypertext Transfer Protocol (HTTP) to
obtain certificates and certificate revocation lists (CRLs) from PKI
repositories.  [STANDARDS-TRACK]


2584     Clouston        May 1999       Definitions of Managed Objects
                                        for APPN/HPR in IP Networks

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. In
particular, it defines objects for monitoring and controlling HPR (High
Performance Routing) network devices which have the capability to
communicate in IP (Internet Protocol) networks.  [STANDARDS-TRACK]


2583    Carlson         May 1999        Guidelines for Next Hop Client
                                        (NHC) Developers

This document provides guidelines for developers of the Next Hop
Resolution Protocol Clients (NHC).  The intent is to define the
interaction between the NHC code and the TCP/IP protocol stack of the
local host operating system. This memo provides information for the
Internet community.





DeLaCruz                     Informational                      [Page 4]

RFC 2599                  Summary of 2500-2599                March 2000


2582    Floyd           Apr 1999        The NewReno Modification to
                                        TCP's Fast Recovery Algorithm

This document describes a specific algorithm for responding to partial
acknowledgments, referred to as NewReno.  This memo defines an
Experimental Protocol for the Internet community.


2581    Allman           Apr 1999       TCP Congestion Control

This document defines TCP's four intertwined congestion control
algorithms: slow start, congestion avoidance, fast retransmit, and fast
recovery.  In addition, the document specifies how TCP should begin
transmission after a relatively long idle period, as well as discussing
various acknowledgment generation methods.  [STANDARDS-TRACK]


2580    McCloghrie       Apr 1999       Conformance Statements for SMIv2

Collections of related objects are defined in MIB modules.  It may be
useful to define the acceptable lower-bounds of implementation, along
with the actual level of implementation achieved.  It is the purpose
of this document to define the notation used for these purposes.
[STANDARDS-TRACK]


2579    McCloghrie      Apr 1999        Textual Conventions for SMIv2

It is the purpose of this document to define the initial set of textual
conventions 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 Management
Information Version 2 (SMIv2), to define that adapted subset, and to
assign a set of associated administrative values.  [STANDARDS-TRACK]


2577    Allman          May 1999        FTP Security Considerations

This document provides suggestions for system administrators and those
implementing FTP servers that will decrease the security problems
associated with FTP.  This memo provides information for the Internet
community.





DeLaCruz                     Informational                      [Page 5]

RFC 2599                  Summary of 2500-2599                March 2000


2576    Frye            March 2000      Coexistence between Version 1,
                                        Version 2, and Version 3 of
                                        the Internet-standard Network
                                        Management Framework

The purpose of this document is to describe coexistence between
version 3 of the Internet-standard Network Management Framework,
(SNMPv3), version 2 of the Internet-standard Network Management
Framework (SNMPv2), and the original Internet-standard Network
Management 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 in
the SNMP architecture (RFC2571).  It defines the Elements of Procedure
for controlling access to management information.  This document also
includes a MIB for remotely managing the configuration parameters for
the 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 SNMP
version 3 for use in the SNMP architecture.  It defines the Elements
of Procedure for providing SNMP message level security.  This document
also includes a MIB for remotely monitoring/managing the configuration
parameters for this Security Model.  [STANDARDS-TRACK]


2573     Levi            Apr 1999       SNMP Applications