rfc2899.txt

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

unique root.  It is a technical constraint inherent in the design of the
DNS.  One root must be supported by a set of coordinated root servers
administered by a unique naming authority.  It is not technically
feasible for there to be more than one root in the public DNS.  This
memo provides information for the Internet community.












Ginoza                       Informational                     [Page 15]

RFC 2899                  Summary of 2800-2899                  May 2001


2825    IAB             May 2000        A Tangled Web: Issues of I18N,
                                        Domain Names, and the Other
                                        Internet protocols

This document is a statement by the Internet Architecture Board.  It is
not a protocol specification, but an attempt to clarify the range of
architectural issues that the internationalization of domain names
faces.  This memo provides information for the Internet community.


2824    Lennox          May 2000        Call Processing Language
                                        Framework and Requirements

This document describes an architectural framework we call a processing
language, as a simple and standardized way for implementing and
deploying Internet telephony.  A large number of the services we wish to
make possible for Internet telephony require fairly elaborate
combinations of signalling operations, often in network devices, to
complete.  It also outlines requirements for such a language.  This memo
provides information for the Internet community.


2823    Carlson         May 2000        PPP over Simple Data Link
                                        (SDL) using SONET/SDH with
                                        ATM-like framing

This document extends methods found in the Point-to-Point Protocol (PPP)
and RFCs 1662 and 2615 to include a new encapsulation for PPP called
Simple Data Link (SDL).  SDL provides a standard method for transporting
multi-protocol datagrams over point-to-point links, and RFCs 1662 and
2615 provide a means to carry PPP over Synchronous Optical Network
(SONET) and Synchronous Digital Hierarchy (SDH) circuits.  SDL provides
a very low overhead alternative to HDLC-like encapsulation, and can also
be used on SONET/SDH links.  This memo defines an Experimental Protocol
for the Internet community.


2822    Resnick         Apr 2001        Internet Message Format

This document specifies a syntax for text messages that are sent between
computer users, within the framework of "electronic mail" messages.
[STANDARDS TRACK]









Ginoza                       Informational                     [Page 16]

RFC 2899                  Summary of 2800-2899                  May 2001


2821    Klensin         Apr 2001        Simple Mail Transfer Protocol

This document is a self-contained specification of the basic protocol
for the Internet electronic mail transport.  [STANDARDS TRACK]


2820    Stokes          May 2000        Access Control Requirements
                                        for LDAP

This document describes the fundamental requirements of an access
control list (ACL) model for the Lightweight Directory Application
Protocol (LDAP) directory service.  This memo provides information for
the Internet community.


2819    Waldbusser      May 2000        Remote Network Monitoring
                                        Management Information Base

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 remote network monitoring
devices.  [STANDARDS TRACK]


2818    Rescorla        May 2000        HTTP Over TLS


This memo describes how to use Transport Layer Security (TLS) to secure
Hypertext Transfer Protocol (HTTP) connections over the Internet.  This
memo provides information for the Internet community.


2817    Khare           May 2000        Upgrading to TLS Within
                                        HTTP/1.1

This memo explains how to use the Upgrade mechanism in HTTP/1.1 to
initiate Transport Layer Security (TLS) over an existing TCP connection.
[STANDARDS TRACK]


2816    Ghanwani        May 2000        A Framework for Integrated
                                        Services Over Shared and
                                        Switched IEEE 802 LAN
                                        Technologies

This memo describes a framework for supporting IETF Integrated Services
on shared and switched LAN infrastructure.  This memo provides
information for the Internet community.



Ginoza                       Informational                     [Page 17]

RFC 2899                  Summary of 2800-2899                  May 2001


2815    Seaman          May 2000        Integrated Service Mappings on
                                        IEEE 802 Networks

This document describes mappings of IETF Integrated Services over LANs
built from IEEE 802 network segments which may be interconnected by IEEE
802.1D MAC Bridges (switches).  [STANDARDS TRACK]


2814    Yavatkar        May 2000        SBM (Subnet Bandwidth
                                        Manager): A Protocol for
                                        RSVP-based Admission Control
                                        over IEEE 802-style networks

This document describes a signaling method and protocol for RSVP-based
admission control over IEEE 802-style LANs.  [STANDARDS TRACK]


2813    Kalt            Apr 2000        Internet Relay Chat: Server
                                        Protocol

This document defines the protocol used by servers to talk to each
other.  This memo provides information for the Internet community.


2812    Kalt            Apr 2000        Internet Relay Chat: Client
                                        Protocol

This document defines the Client Protocol, and assumes that the reader
is familiar with the IRC Architecture.  This memo provides information
for the Internet community.


2811    Kalt            Apr 2000        Internet Relay Chat: Channel
                                        Management

This document specifies how channels, their characteristics and
properties are managed by IRC servers.  This memo provides information
for the Internet community.


2810    Kalt            Apr 2000        Internet Relay Chat:
                                        Architecture

This document is an update describing the architecture of the current
IRC protocol and the role of its different components.  Other documents
describe in detail the protocol used between the various components
defined here.  This memo provides information for the Internet
community.



Ginoza                       Informational                     [Page 18]

RFC 2899                  Summary of 2800-2899                  May 2001


2809    Aboba           Apr 2000        Implementation of L2TP
                                        Compulsory Tunneling via
                                        RADIUS

This document discusses implementation issues arising in the
provisioning of compulsory tunneling in dial-up networks using the L2TP
(Layer Two Tunneling Protocol) protocol.  This memo provides information
for the Internet community.


2808    Nystrom         Apr 2000        The SecurID(r) SASL Mechanism

This document defines a SASL (Simple Authentication and Security Layer)
authentication mechanism using SecurID (a hardware token card product
(or software emulation thereof) produced by RSA Security Inc., which is
used for end-user authentication), thereby providing a means for such
tokens to be used in SASL environments.  This mechanism is only is only
for authentication, and has no effect on the protocol encoding and is
not designed to provide integrity or confidentiality services.  This
memo provides information for the Internet community.


2807    Reagle          Jul 2000        XML Signature Requirements

This document lists the design principles, scope, and requirements for
the XML Digital Signature specification.  It includes requirements as
they relate to the signature syntax, data model, format, cryptographic
processing, and external requirements and coordination.  This memo
provides information for the Internet community.


2806    Vaha-Sipila     Apr 2000        URLs for Telephone Calls


This document specifies URL (Uniform Resource Locator) schemes "tel",
"fax" and "modem" for specifying the location of a terminal in the phone
network and the connection types (modes of operation) that can be used
to connect to that entity.  [STANDARDS TRACK]













Ginoza                       Informational                     [Page 19]

RFC 2899                  Summary of 2800-2899                  May 2001


2805    Greene          Apr 2000        Media Gateway Control Protocol
                                        Architecture and Requirements

This document describes protocol requirements for the Media Gateway
Control Protocol between a Media Gateway Controller and a Media Gateway.
This memo provides information for the Internet community.


2804    IAB             May 2000        IETF Policy on Wiretapping

This document describes the position that the Internet Engineering Task
Force (IETF) has taken regarding the inclusion into IETF standards-track
documents of functionality designed to facilitate wiretapping.  This
memo explains what the IETF thinks the question means, why its answer is
"no", and what that answer means.  This memo provides information for
the Internet community.


2803    Maruyama        Apr 2000        Digest Values for DOM (DOMHASH)

This memo defines a clear and unambiguous definition of digest (hash)
values of the XML objects regardless of the surface string variation of
XML.  This memo provides information for the Internet community.


2802    Davidson        Apr 2000        Digital Signatures for the
                                        v1.0 Internet Open Trading
                                        Protocol (IOTP)

This document describes the syntax and procedures for the computation
and verification of digital signatures for use within Version 1.0 of the
Internet Open Trading Protocol (IOTP).  This memo provides information
for the Internet community.


2801    Burdett         Apr 2000        Internet Open Trading Protocol
                                        - IOTP Version 1.0

This document discusses the Internet Open Trading Protocol (IOTP) and
its provision of an interoperable framework for Internet commerce.  This
memo provides information for the Internet community.










Ginoza                       Informational                     [Page 20]

RFC 2899                  Summary of 2800-2899                  May 2001


2800    Reynolds        May 2001        Internet Official Protocol
                                        Standards

This memo contains a snapshot of the state of standardization of
protocols used in the Internet as of April 17, 2001.  It lists only
official protocol standards RFCs; it is not a complete index to the RFC
series.  [STANDARDS TRACK]

Security Considerations

   This memo does not affect the technical security of the Internet, but
   may cite important security specifications.

Author's Address

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

   Phone:  [phone]

   EMail: [e-mail]



























Ginoza                       Informational                     [Page 21]

RFC 2899                  Summary of 2800-2899                  May 2001


Full Copyright Statement

   Copyright (C) The Internet Society (2001).  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.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Ginoza                       Informational                     [Page 22]