rfc2599.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

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
Experimental Protocol for the Internet community.


2548    Zorn            Mar 1999        Microsoft Vendor-specific
                                        RADIUS Attributes

This document describes the set of Microsoft vendor-specific RADIUS
attributes.  This memo provides information for the Internet community.


2547    Rosen            Mar 1999       BGP/MPLS VPNs

This document describes a method by which a Service Provider with an IP
backbone may provide VPNs (Virtual Private Networks) for its customers.
This memo provides information for the Internet community.












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


2546    Durand          Mar 1999        6Bone Routing Practice

This memo identifies guidelines on how 6Bone sites might operate, so
that the 6Bone can remain a quality experimentation environment and to
avoid pathological situations that have been encountered in the past.
It defines the 'best current practice' acceptable in the 6Bone for the
configuration of both Interior Gateway Protocols and Exterior Gateway
Protocols. This memo provides information for the Internet community.


2545    Marques         Mar 1999        Use of BGP-4 Multiprotocol
                                        Extensions for IPv6
                                        Inter-Domain Routing

BGP-4 Multiprotocol Extensions (BGP-MP) defines the format of two BGP
attributes (MP_REACH_NLRI and MP_UNREACH_NLRI) that can be used to
announce and withdraw the announcement of reachability information.
This document defines how compliant systems should make use of those
attributes for the purpose of conveying IPv6 routing information.
[STANDARDS-TRACK]


2544    Bradner         Mar 1999        Benchmarking Methodology
                                        for Network Interconnect Devices

This document is a republication of RFC 1944 correcting the values for
the IP addresses which were assigned to be used as the default addresses
for networking test equipment. This memo provides information for the
Internet community.


2543    Handley         Mar 1999        SIP: Session Initiation Protocol

The Session Initiation Protocol (SIP) is an application-layer control
(signaling) protocol for creating, modifying and terminating sessions
with one or more participants.  [STANDARDS-TRACK]


2542    Masinter        Mar 1999        Terminology and Goals for
                                        Internet Fax

This document defines a number of terms useful for the discussion of
Internet Fax. In addition, it describes the goals of the Internet Fax
working group and establishes a baseline of desired functionality
against which protocols for Internet Fax can be judged. This memo
provides information for the Internet community.





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


2541    Eastlake         Mar 1999       DNS Security Operational
                                        Consideration

This document discusses these operational aspects for keys and
signatures used in connection with the KEY and SIG DNS resource records.
This memo provides information for the Internet community.


2540    Eastlake         Mar 1999       Detached Domain Name System
                                        (DNS) Information

A standard format is defined for representing detached DNS information.
This is anticipated to be of use for storing information retrieved from
the Domain Name System (DNS), including security information, in
archival contexts or contexts not connected to the Internet. This memo
defines an Experimental Protocol for the Internet community.


2539    Eastlake         Mar 1999       Storage of Diffie-Hellman
                                        Keys in the Domain Name
                                        System (DNS)

A standard method for storing Diffie-Hellman keys in the Domain Name
System is described which utilizes DNS KEY resource records.
[STANDARDS-TRACK]


2538     Eastlake       Mar 1999        Storing Certificates in the
                                        Domain Name System (DNS)

Cryptographic public key are frequently published and their authenticity
demonstrated by certificates.  A CERT resource record (RR) is defined so
that such certificates and related certificate revocation lists can be
stored in the Domain Name System (DNS).  [STANDARDS-TRACK]


2537    Eastlake        Mar 1999        RSA/MD5 KEYs and SIGs in
                                        the Domain Name System (DNS)

A standard method for storing RSA keys and and RSA/MD5 based signatures
in the Domain Name System is described which utilizes DNS KEY and SIG
resource records.  [STANDARDS-TRACK]









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


2536     Eastlake        Mar 1999       DSA KEYs and SIGs in the
                                        Domain Name System (DNS)

A standard method for storing US Government Digital Signature Algorithm
keys and signatures in the Domain Name System is described which
utilizes DNS KEY and SIG resource records.  [STANDARDS-TRACK]


2535    Eastlake        Mar 1999        Domain Name System Security
                                        Extensions

This document incorporates feedback on RFC 2065 from early implementers
and potential users.  [STANDARDS-TRACK]


2534    Masinter        Mar 1999        Media Features for Display,
                                        Print, and Fax

This specification defines some common media features for describing
image resolution, size, color, and image representation methods that are
common to web browsing, printing, and facsimile applications.
[STANDARDS-TRACK]


2533     Klyne          Mar 1999        A Syntax for Describing Media
                                        Feature Sets

This document introduces and describes a syntax that can be used to
define feature sets which are formed from combinations and relations
involving individual media features.  [STANDARDS-TRACK]


2532    Masinter         Mar 1999       Extended Facsimile Using
                                        Internet Mail

This document describes extensions to "Simple Mode of Facsimile Using
Internet Mail", and describes additional features, including
transmission of enhanced document characteristics (higher resolution,
color) and confirmation of delivery and processing.  [STANDARDS-TRACK]


2531    Klyne           Mar 1999        Content Feature Schema for
                                        Internet Fax

This document defines a content feature schema that is a profile of the
media feature registration mechanisms for use in performing capability
identification between extended Internet fax systems.  [STANDARDS-TRACK]




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


2530    Wing            Mar 1999        Indicating Supported Media
                                        Features Using Extensions to
                                        DSN and MDN

This memo describes a format for generating Message Disposition
Notifications and Delivery Status Notifications which contain such
information.  [STANDARDS-TRACK]


2529    Carpenter       Mar 1999        Transmission of IPv6 over IPv4
                                        Domains without Explicit Tunnels

This memo specifies the frame format for transmission of IPv6 (IPV6)
packets and the method of forming IPv6 link-local addresses over IPv4
domains.  It also specifies the content of the Source/Target Link-layer
Address option used in the Router Solicitation, Router Advertisement,