rfc2299.txt

RFC 的详细文档！

RFC 2299                  Summary of 2200-2299              January 1999


2221    Gahrns          Oct 1997        IMAP4 Login Referrals


When dealing with large amounts of users and many IMAP4 [RFC-2060]
servers, it is often necessary to move users from one IMAP4 server to
another.  Login referrals allow clients to transparently connect to an
alternate IMAP4 server, if their home IMAP4 server has changed.
[STANDARDS-TRACK]

2220    Guenther        Oct 1997        The Application/MARC Content-
                                        type

This memorandum provides a mechanism for representing objects which are
files of Machine-Readable Cataloging records (MARC).  The MARC formats
are standards for the representation and communication of bibliographic
and related information.  A MARC record contains metadata for an
information resource following MARC format specifications.  This memo
provides information for the Internet community.  It does not specify an
Internet standard of any kind.


2219    Hamilton        Oct 1997        Use of DNS Aliases for Network
                                        Services

It has become a common practice to use symbolic names (usually CNAMEs)
in the Domain Name Service (DNS - [RFC-1034, RFC-1035]) to refer to
network services such as anonymous FTP [RFC-959] servers, Gopher [RFC-
1436] servers, and most notably World-Wide Web HTTP [RFC-1945] servers.
This is desirable for a number of reasons.  It provides a way of moving
services from one machine to another transparently, and a mechanism by
which people or agents may programmatically discover that an
organization runs, say, a World-Wide Web server.  Although this approach
has been almost universally adopted, there is no standards document or
similar specification for these commonly used names.  This document
seeks to rectify this situation by gathering together the extant
'folklore' on naming conventions, and proposes a mechanism for
accommodating new protocols.  This document specifies an Internet Best
Current Practices for the Internet Community, and requests discussion
and suggestions for improvements.


2218    Genovese        Oct 1997        A Common Schema for the
                                        Internet White Pages Service

This document specifies the minimum set of core attributes of a White
Pages entry for an individual and describes how new objects with those
attributes can be defined and published.  [STANDARDS-TRACK]




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


2217    Clark           Oct 1997        Telnet Com Port Control Option

This memo proposes a protocol to allow greater use of modems attached to
a network for outbound dialing purposes.  This memo defines an
Experimental Protocol for the Internet community.


2216    Shenker         Sep 1997        Network Element Service
                                        Specification Template

This document defines a framework for specifying services provided by
network elements, and available to applications, in an internetwork
which offers multiple qualities of service. The document first provides
some necessary context -- including relevant definitions and suggested
data formats -- and then specifies a "template" which service
specification documents should follow.  This memo provides information
for the Internet community.  It does not specify an Internet standard of
any kind.


2215    Shenker         Sep 1997        General Characterization
                                        Parameters for Integrated
                                        Service Network Elements

This memo defines a set of general control and characterization
parameters for network elements supporting the IETF integrated services
QoS control framework.  [STANDARDS-TRACK]


2214    Baker           Sep 1997        Integrated Services Management
                                        Information Base Guaranteed
                                        Service Extensions using SMIv2

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 the the interface attributes
defined in the Guaranteed Service of the Integrated Services Model.
[STANDARDS-TRACK]


2213    Baker           Sep 1997        Integrated Services Management
                                        Information Base using SMIv2

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 the the interface attributes
defined in the Integrated Services Model.  [STANDARDS-TRACK]




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


2212    Shenker         Sep 1997        Specification of Guaranteed
                                        Quality of Service

This memo describes the network element behavior required to deliver a
guaranteed service (guaranteed delay and bandwidth) in the Internet.
[STANDARDS-TRACK]


2211    Wroclawski      Sep 1997        Specification of the
                                        Controlled-Load Network
                                        Element Service

This memo specifies the network element behavior required to deliver
Controlled-Load service in the Internet.  [STANDARDS-TRACK]


2210    Wroclawski      Sep 1997        The Use of RSVP with IETF
                                        Integrated Services

This note describes the use of the RSVP resource reservation protocol
with the Controlled-Load and Guaranteed QoS control services.
[STANDARDS-TRACK]


2209    Braden          Sep 1997        Resource ReSerVation Protocol
                                        (RSVP) -- Version 1 Message
                                        Processing Rules


This memo contains an algorithmic description of the rules used by an
RSVP implementation for processing messages.  It is intended to clarify
the version 1 RSVP protocol specification.  This memo provides
information for the Internet community.  It does not specify an Internet
standard of any kind.


2208    Mankin          Sep 1997        Resource ReSerVation Protocol
                                        (RSVP) Version 1 Applicability
                                        Statement Some Guidelines on
                                        Deployment

This document describes the applicability of RSVP along with the
Integrated Services protocols and other components of resource
reservation and offers guidelines for deployment of resource reservation
at this time. This memo provides information for the Internet community.
It does not specify an Internet standard of any kind.





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


2207    Berger          Sep 1997        RSVP Extensions for IPSEC Data
                                        Flows

This document presents extensions to Version 1 of RSVP.  These
extensions permit support of individual data flows using RFC 1826, IP
Authentication Header (AH) or RFC 1827, IP Encapsulating Security
Payload (ESP).  [STANDARDS-TRACK]


2206    Baker           Sep 1997        RSVP Management Information
                                        This memo defines a portion of

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 the Resource Reservation
Protocol (RSVP) within the interface attributes defined in the
Integrated Services Model.  [STANDARDS-TRACK]


2205    Braden          Sep 1997        Resource ReSerVation Protocol
                                        (RSVP)--Version 1 Functional
                                        Specification

This memo describes version 1 of RSVP, a resource reservation setup
protocol designed for an integrated services Internet.  RSVP provides
receiver-initiated setup of resource reservations for multicast or
unicast data flows, with good scaling and robustness properties.
[STANDARDS-TRACK]


2204    Nash            Sep 1997        ODETTE File Transfer Protocol

This memo describes a file transfer protocol to facilitate electronic
data interchange between trading partners.  This memo provides
information for the Internet community.  It does not specify an Internet
standard of any kind.


2203    Eisler          Sep 1997        RPCSEC_GSS Protocol Specification

This memo describes an ONC/RPC security flavor that allows RPC protocols
to access the Generic Security Services Application Programming
Interface (referred to henceforth as GSS-API).  [STANDARDS-TRACK]








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


2202    Cheng           Sep 1997        Test Cases for HMAC-MD5 and
                                        HMAC-SHA-1

This document provides two sets of test cases for HMAC-MD5 and HMAC-
SHA-1, respectively. HMAC-MD5 and HMAC-SHA-1 are two constructs of the
HMAC [HMAC] message authentication function using the MD5 [MD5] hash
function and the SHA-1 [SHA] hash function.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


2201    Ballardie       Sep 1997        Core Based Trees (CBT)
                                        Multicast Routing Architecture

CBT is a multicast routing architecture that builds a single delivery
tree per group which is shared by all of the group's senders and
receivers.  This memo defines an Experimental Protocol for the Internet
community.


2200    IAB             Jun 1997        INTERNET OFFICIAL PROTOCOL
                                        STANDARDS

A discussion of the standardization process and the RFC document series
is presented first, followed by an explanation of the terms.  Sections
6.2 - 6.10 contain the lists of protocols in each stage of
standardization.  Finally are pointers to references and contacts for
further information.  [STANDARDS-TRACK]



Security Considerations

   There are no security issues in this Informational RFC.

Author's Address

   Alegre Ramos
   University of Southern California
   Information Sciences Institute
   4676 Admiralty Way
   Marina del Rey, CA 90292

   Phone:  [phone]
   EMail: [e-mail]






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


Full Copyright Statement

   Copyright (C) The Internet Society (1999).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
























Ramos                        Informational                     [Page 24]