Request for Comments Summary
RFC 2299

Document Type RFC - Informational (January 1999; No errata)
Last updated 2013-03-02
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 2299 (Informational)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           A. Ramos
Request for Comments: 2299                                           ISI
Category: Informational                                     January 1999

                      Request for Comments Summary

                         RFC Numbers 2200-2299

Status of This Memo

   This RFC is a slightly annotated list of the 100 RFCs from RFC 2200
   through RFCs 2299.  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 (1999).  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
---     ------          ----            -----

2299    Ramos           Jan 1999        Request for Comments Summary

This memo.

2298    Fajman          Mar 1998        An Extensible Message Format

This memo defines a MIME content-type that may be used by a mail user
agent (UA) or electronic mail gateway to report the disposition of a
message after it has been sucessfully delivered to a recipient.
[STANDARDS-TRACK]

Ramos                        Informational                      [Page 1]
RFC 2299                  Summary of 2200-2299              January 1999

2297    Newman          Mar 1998        Ipsilon's General Switch
                                        Management Protocol
                                        Specification Version 2.0

This memo specifies enhancements to the General Switch Management
Protocol (GSMP) [RFC1987].  This memo provides information for the
Internet community.  It does not specify an Internet standard of any
kind.

2296    Holtman         Mar 1998        HTTP Remote Variant Selection
                                        Algorithm -- RVSA/1.0

HTTP allows web site authors to put multiple versions of the same
information under a single URL.  Transparent content negotiation is a
mechanism for automatically selecting the best version when the URL is
accessed.  A remote variant selection algorithm can be used to speed up
the transparent negotiation process. This document defines the remote
variant selection algorithm with the version number 1.0.  This memo
defines an Experimental Protocol for the Internet community.  It does
not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.

2295    Holtman         Mar 1998        Transparent Content
                                        Negotiation in HTTP

HTTP allows web site authors to put multiple versions of the same
information under a single URL.  Transparent content negotiation is an
extensible negotiation mechanism, layered on top of HTTP, for
automatically selecting the best version when the URL is accessed.  This
enables the smooth deployment of new web data formats and markup tags.
This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.

2294    Kille           Mar 1998        Representing the O/R Address
                                        hierarchy in the X.500
                                        Directory Information Tree

This document defines a representation of the O/R Address hierarchy in
the Directory Information Tree.  [STANDARDS-TRACK]

Ramos                        Informational                      [Page 2]
RFC 2299                  Summary of 2200-2299              January 1999

2293    Kille           Mar 1998        Representing Tables and
                                        Subtrees in the X.500 Directory

This document defines techniques for representing two types of
information mapping in the OSI Directory: Mapping from a key to a value
(or set of values), as might be done in a table lookup, and mapping from
a distinguished name to an associated value (or values), where the
values are not defined by the owner of the entry.  This is achieved by
use of a directory subtree.  [STANDARDS-TRCK]

2292    Stevens         Feb 1998        Advanced Sockets API for IPv6

The current document defines some the "advanced" features of the sockets
API that are required for applications to take advantage of additional
features of IPv6.  This memo provides information for the Internet
community.  It does not specify an Internet standard of any kind.

2291    Slein           Feb 1998        Requirements for a Distributed
Show full document text