rfc2599.txt

RFC 的详细文档！

This memo describes five types of SNMP applications which make use of
an SNMP engine. This memo also defines MIB modules for specifying
targets of management operations, for notification filtering, and for
proxy fowarding.  [STANDARDS-TRACK]










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


2572    Case            May 1999        Message Processing and
                                        Dispatching for the Simple
                                        Network Management Protocol
                                        (SNMP)

This document describes the Message Processing and Dispatching for
SNMP messages within the SNMP architecture.  It defines the procedures
for dispatching potentially multiple versions of SNMP messages to the
proper SNMP Message Processing Models, and for dispatching PDUs to
SNMP applications.  This document also describes one Message
Processing Model - the SNMPv3 Message Processing Model.
[STANDARDS-TRACK]


2571    Harrington      May 1999        An Architecture for Describing
                                        SNMP Management Frameworks

This document describes an architecture for describing SNMP Management
Frameworks.  [STANDARDS-TRACK]


2570    Case            Apr 1999        Introduction to Version 3
                                        of the Internet-standard
                                        Network Management Framework

The purpose of this document is to provide an overview of the third
version of the Internet-standard Management Framework, termed the SNMP
version 3 Framework (SNMPv3). This memo provides information for the
Internet community.


2569    Herriot         Apr 1999        Mapping between LPD and IPP
                                        Protocols

This document is one of a set of documents, which together describe all
aspects of a new Internet Printing Protocol (IPP). One of the purposes
of this document is to compare the functionality of the two protocols.
Another purpose is to facilitate implementation of gateways between LPD
and IPP.  This memo defines an Experimental Protocol for the Internet
community.











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


2568    Zilles          Apr 1999        Rationale for the Structure of
                                        the Model and Protocol for the
                                        Internet Printing Protocol

This document describes IPP from a high level view, defines a roadmap
for the various documents that form the suite of IPP specifications, and
gives background and rationale for the IETF working group's major
decisions. This memo defines an Experimental Protocol for the Internet
community.


2567    Wright          Apr 1999        Design Goals for an Internet
                                        Printing Protocol

This document takes a broad look at distributed printing functionality,
and it enumerates real-life scenarios that help to clarify the features
that need to be included in a printing protocol for the Internet.  It
identifies requirements for three types of users: end users, operators,
and administrators.  This memo defines an Experimental Protocol for the
Internet community.


2566     deBry          Apr 1999        Internet Printing
                                        Protocol/1.0: Model and
                                        Semantics

This document describes a simplified model consisting of abstract
objects, their attributes, and their operations that is independent of
encoding and transport.  This document also addresses security,
internationalization, and directory issues. This memo defines an
Experimental Protocol for the Internet community.


2565    Herriot          Apr 1999       Internet Printing
                                        Protocol/1.0: Encoding and
                                        Transport

This document defines the rules for encoding IPP operations and IPP
attributes into a new Internet mime media type called "application/ipp".
This document also defines the rules for transporting over HTTP a
message body whose Content-Type is "application/ipp". This document
defines an Experimental protocol for the Internet community.









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


2564    Kalbfleisch     May 1999        Application Management MIB

This memo defines a standards track portion of the Management
Information Base (MIB) for use with network management protocols in the
Internet Community.  In particular, it defines objects used for the
management of applications.  [STANDARDS-TRACK]


2563    Troll           May 1999        DHCP Option to Disable
                                        Stateless Auto-Configuration in
                                        IPv4 Clients

This document describes a mechanism by which DHCP servers are able to
tell clients that they do not have an IP address to offer, and that the
client should not generate an IP address it's own.  [STANDARDS-TRACK]


2562    White           Apr 1999        Definitions of Protocol and
                                        Managed Objects for TN3270E
                                        Response Time Collection Using
                                        SMIv2 (TN3270E-RT-MIB)

This memo defines the protocol and the Management Information Base (MIB)
for performing response time data collection on TN3270 and TN3270E
sessions by a TN3270E server.  [STANDARDS-TRACK]

2561     White          Apr 1999        Base Definitions of Managed
                                        Objects for TN3270E Using SMIv2

This memo defines a Management Information Base (MIB) for configuring
and managing TN3270E servers.  The MIB defined by this memo provides
generic support for both host and gateway TN3270E server
implementations.  [STANDARDS-TRACK]


2560    Myers           Jun 1999        X.509 Internet Public Key
                                        Infrastructure Online
                                        Certificate Status
                                        Protocol - OCSP

This document specifies a protocol useful in determining the current
status of a digital certificate without requiring CRLs.  [STANDARDS-
TRACK]








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


2559    Boeyen           Apr 1999       Internet X.509 Public Key
                                        Infrastructure Operational
                                        Protocols - LDAPv2

Specifically, this document addresses requirements to provide access to
Public Key Infrastructure (PKI) repositories for the purposes of
retrieving PKI information and managing that same information.
[STANDARDS-TRACK]


2558    Tesink          Mar 1999        Definitions of Managed Objects
                                        for the SONET/SDH Interface Type

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in TCP/IP-based internets.  In
particular, it defines objects for managing Synchronous Optical
Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces.  This
document is a companion to the documents that define Managed Objects for
the DS1/E1/DS2/E2 and DS3/E3 Interface Types. [STANDARDS-TRACK]


2557     Palme           Mar 1999       MIME Encapsulation of
                                        Aggregate Documents, such
                                        as HTML (MHTML)

This document a) defines the use of a MIME multipart/related structure
to aggregate a text/html root resource and the subsidiary resources it
references, and b) specifies a MIME content-header (Content-Location)
that allow URIs in a multipart/related text/html root body part to
reference subsidiary resources in other body parts of the same
multipart/related structure.  [STANDARDS-TRACK]


2556    Bradner          Mar 1999       OSI connectionless transport
                                        services on top of UDP
                                        Applicability Statement for
                                        Historic Status

RFC 1240, "OSI connectionless transport services on top of UDP", was
published as a Proposed Standard in June 1991 but at this time there do
not seem to be any implementations which follow RFC 1240.  In addition
there is a growing concern over using UDP-based transport protocols in
environments where congestion is a possibility This memo provides
information for the Internet community.







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


2555     RFC Editor     Apr 1999        30 Years of RFCs

The rest of this document contains a brief recollection from the present
RFC Editor Joyce K. Reynolds, followed by recollections from three
pioneers: Steve Crocker who wrote RFC 1, Vint Cerf whose long-range
vision continues to guide us, and Jake Feinler who played a key role in
the middle years of the RFC series. This memo provides information for
the Internet community.


2554    Myers           Mar 1999        SMTP Service Extension

This document defines an SMTP service extension [ESMTP] whereby an SMTP
client may indicate an authentication mechanism to the server, perform
an authentication protocol exchange, and optionally negotiate a security
layer for subsequent protocol interactions.  [STANDARDS-TRACK]


2553    Gilligan        Mar 1999        Basic Socket Interface
                                        Extensions for IPv6

TCP/IP applications written using the sockets API have in the past
enjoyed a high degree of portability and we would like the same
portability with IPv6 applications.  But changes are required to the
sockets API to support IPv6 and this memo describes these changes.
These include a new socket address structure to carry IPv6 addresses,
new address conversion functions, and some new socket options.  This
memo provides information for the Internet community.


2552    Blinov          Apr 1999        Architecture for Information
                                        Brokerage in the ACTS Project
                                        GAIA

This memo introduces a domain and supplier independent generic
architecture for information brokerage, designed as part of the ACTS
project GAIA (Generic Architecture for Information Availability). This
memo provides information for the Internet community.













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


2551    Bradner         1 Apr 1999      The Roman Standards Process --
                                        Revision III

This memo documents the process used by the Roman community for the
standardization of protocols and procedures.  It defines the stages in
the standardization process, the requirements for moving a document
between stages and the types of documents used during this process.  It
also addresses the intellectual property rights and copyright issues
associated with the standards process.


2550    Glassman         1 Apr 1999     Y10K and Beyond

This specification provides a solution to the "Y10K" problem which has
also been called the "YAK" problem (hex) and the "YXK" problem (Roman
numerals). This memo provides information for the Internet community.


2549     Waitzman        1 Apr 1999     IP over Avian Carriers with
                                        Quality of Service

This memo amends RFC 1149, "A Standard for the Transmission of IP
Datagrams on Avian Carriers", with Quality of Service information.  This
is an experimental, not recommended standard. This memo defines an