rfc2699.txt

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

Network Working Group                                          S. Ginoza
Request for Comments: 2699                                           ISI
Category: Informational                                         May 2000


                      Request for Comments Summary

                         RFC Numbers 2600-2699

Status of This Memo

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


2699    Ginoza          Apr 2000        Request for Comments Summary

This memo.


2698    Heinanen        Sep 1999        A Two Rate Three Color Marker

This document defines a Two Rate Three Color Marker (trTCM), which can
be used as a component in a Diffserv traffic conditioner.  This memo
provides information for the Internet community.






Ginoza                       Informational                      [Page 1]

RFC 2699                  Summary of 2600-2699                  May 2000


2697    Heinanen        Sep 1999        A Single Rate Three Color Marker

This document defines a Single Rate Three Color Marker (srTCM), which
can be used as component in a Diffserv traffic conditioner.  This memo
provides information for the Internet community.


2696    Weider          Sep 1999        LDAP Control Extension for
                                        Simple Paged Results
                                        Manipulation

This document describes an LDAPv3 control extension for simple paging of
search results.  This memo provides information for the Internet
community.


2695    Chiu            Sep 1999        Authentication Mechanisms for
                                        ONC RPC

This document describes two authentication mechanisms created by Sun
Microsystems that are commonly used in conjunction with the ONC Remote
Procedure Call (ONC RPC Version 2) protocol.  This memo provides
information for the Internet community.


2694    Srisuresh       Sep 1999        DNS extensions to Network
                                        Address Translators (DNS_ALG)

This document identifies the need for DNS extensions to NATs and
outlines how a DNS Application Level Gateway (DNS_ALG) can meet the
need.  This memo provides information for the Internet community.


2693    Ellison         Sep 1999        SPKI Certificate Theory

This document gives the theory behind SPKI certificates and ACLs without
going into technical detail about those structures or their uses.  This
memo defines an Experimental Protocol for the Internet community.


2692    Ellison         Sep 1999        SPKI Requirements

The SPKI Working Group first established a list of things one might want
to do with certificates (attached at the end of this document), and then
summarized that list of desires into requirements.  This document
presents that summary of requirements.  This memo defines an
Experimental Protocol for the Internet community.




Ginoza                       Informational                      [Page 2]

RFC 2699                  Summary of 2600-2699                  May 2000


2691    Bradner         Sep 1999        A Memorandum of Understanding
                                        for an ICANN Protocol Support
                                        Organization

This is the text of the Memorandum of Understanding (MoU) that was
signed by ICANN, the IETF, the ITU-T, W3C and ETSI on July 14, 1999 in
Oslo. This MoU creates the Protocol Support Organization (PSO) within
the Internet Corporation for Assigned Names and Numbers (ICANN).  This
memo provides information for the Internet community.


2690    Bradner         Sep 1999        A Proposal for an MOU-Based
                                        ICANN Protocol Support
                                        Organization

This is a copy of the proposal for an MOU-based Protocol Supporting
Organization that was submitted to ICANN on April 23, 1999.  This memo
provides information for the Internet community.


2689    Bormann         Sep 1999        Providing Integrated Services
                                        over Low-bitrate Links

This document describes an architecture for providing integrated
services over low-bitrate links, such as modem lines, ISDN B-channels,
and sub-T1 links.  This memo provides information for the Internet
community.


2688    Jackowski       Sep 1999        Integrated Services Mappings
                                        for Low Speed Networks

This document defines the service mappings of the IETF Integrated
Services for low-bitrate links, specifically the controlled load and
guaranteed services.  [STANDARDS-TRACK]


2687    Bormann         Sep 1999        PPP in a Real-time Oriented
                                        HDLC-like Framing

This document proposes the suspend/resume-oriented solution for the
real-time encapsulation format part of the architecture.  [STANDARDS-
TRACK]








Ginoza                       Informational                      [Page 3]

RFC 2699                  Summary of 2600-2699                  May 2000


2686    Bormann         Sep 1999        The Multi-Class Extension to
                                        Multi-Link PPP

This document proposes the fragment-oriented solution for the real-time
encapsulation format part of the architecture.  [STANDARDS-TRACK]


2685    Fox             Sep 1999        Virtual Private Networks
                                        Identifier

This document proposes a format for a globally unique VPN identifier.
[STANDARDS-TRACK]


2684    Grossman        Sep 1999        Multiprotocol Encapsulation
                                        over ATM Adaptation Layer 5

This memo replaces RFC 1483.  It describes two encapsulations methods
for carrying network interconnect traffic over AAL type 5 over  ATM.
[STANDARDS-TRACK]


2683    Leiba           Sep 1999        IMAP4 Implementation
                                        Recommendations

The IMAP4 specification describes a rich protocol for use in building
clients and servers for storage, retrieval, and manipulation of
electronic mail.  Because the protocol is so rich and has so many
implementation choices, there are often trade-offs that must be made and
issues that must be considered when designing such clients and servers.
This document attempts to outline these issues and to make
recommendations in order to make the end products as interoperable as
possible.  This memo provides information for the Internet community.


2682    Widjaja         Sep 1999        Performance Issues in VC-Merge
                                        Capable ATM LSRs

This document investigates the impact of VC merging on the additional
buffer required for the reassembly buffers and other buffers.  This memo
provides information for the Internet community.










Ginoza                       Informational                      [Page 4]

RFC 2699                  Summary of 2600-2699                  May 2000


2681    Almes           Sep 1999        A Round-trip Delay Metric for IPP

This memo defines a metric for round-trip delay of packets across
Internet paths.  [STANDARDS-TRACK]


2680    Almes           Sep 1999        A One-way Packet Loss Metric
                                        for IPPM

This memo defines a metric for one-way packet loss across Internet
paths.  [STANDARDS-TRACK]


2679    Almes           Sep 1999        A One-way Delay Metric for IPPM

This memo defines a metric for one-way delay of packets across Internet
paths.  [STANDARDS-TRACK]


2678    Mahdavi         Sep 1999        IPPM Metrics for Measuring
                                        Connectivity

This memo defines a series of metrics for connectivity between a pair of
Internet hosts.  [STANDARDS-TRACK]


2677    Greene          Sep 1999        Definitions of Managed Objects
                                        for the NBMA Next Hop
                                        Resolution Protocol (NHRP)

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.
[STANDARDS-TRACK]


2676    Apostolopoulos  Aug 1999        QoS Routing Mechanisms
                                        and OSPF Extensions

This memo describes extensions to the OSPF protocol to support QoS
routes.  The focus of this document is on the algorithms used to compute
QoS routes and on the necessary modifications to OSPF to support this
function, e.g., the information needed, its format, how it is
distributed, and how it is used by the QoS path selection process.  This
memo defines an Experimental Protocol for the Internet community.







Ginoza                       Informational                      [Page 5]

RFC 2699                  Summary of 2600-2699                  May 2000


2675    Borman          Aug 1999        IPv6 Jumbograms

This document describes the IPv6 Jumbo Payload option, which provides
the means of specifying such large payload lengths.  It also describes
the changes needed to TCP and UDP to make use of jumbograms.
[STANDARDS-TRACK]


2674    Bell            Sep 1999        Definitions of Managed Objects
                                        for Bridges with Traffic
                                        Classes, Multicast Filtering
                                        and Virtual LAN Extensions

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in TCP/IP based internets.
[STANDARDS-TRACK]


2673    Crawford        Aug 1999        Binary Labels in the
                                        Domain Name System

This document defines a "Bit-String Label" which may appear within
domain names.  This new label type compactly represents a sequence of
"One-Bit Labels" and enables resource records to be stored at any bit-
boundary in a binary-named section of the domain name tree.
[STANDARDS-TRACK]


2672    Crawford        Aug 1999        Non-Terminal DNS Name
                                        Redirection

This document defines a new DNS Resource Record called "DNAME", which
provides the capability to map an entire subtree of the DNS name space
to another domain.  [STANDARDS-TRACK]


2671    Vixie           Aug 1999        Extension Mechanisms
                                        for DNS (EDNS0)

The Domain Name System's wire protocol includes a number of fixed fields
whose range has been or soon will be exhausted and does not allow
clients to advertise their capabilities to servers.  This document
describes backward compatible mechanisms for allowing the protocol to
grow.  [STANDARDS-TRACK]







Ginoza                       Informational                      [Page 6]

RFC 2699                  Summary of 2600-2699                  May 2000


2670    St. Johns       Aug 1999        Radio Frequency (RF)
                                        Interface Management
                                        Information Base for
                                        MCNS/DOCSIS compliant
                                        RF interfaces

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it defines a basic set of managed objects for SNMP-based
management of MCNS/DOCSIS compliant Radio Frequency (RF) interfaces.
[STANDARDS-TRACK]


2669    St. Johns       Aug 1999        DOCSIS Cable Device MIB
                                        Cable Device Management
                                        Information Base for
                                        DOCSIS compliant Cable
                                        Modems and Cable Modem
                                        Termination Systems

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it defines a basic set of managed objects for SNMP-based
management of DOCSIS 1.0 compliant Cable Modems and Cable Modem
Termination Systems.  [STANDARDS-TRACK]


2668    Smith           Sep 1999        Definitions of Managed Objects
                                        for IEEE 802.3 Medium
                                        Attachment Units (MAUs)

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.
[STANDARDS-TRACK]


2667    Thaler          Aug 1999        IP Tunnel MIB

This memo defines a Management Information Base (MIB) for use with
network management protocols in the Internet community.  In particular,
it describes managed objects used for managing tunnels of any type over
IPv4 networks.  [STANDARDS-TRACK]









Ginoza                       Informational                      [Page 7]

RFC 2699                  Summary of 2600-2699                  May 2000


2666    Flick           Sep 1999        Definitions of Object
                                        Identifiers for Identifying
                                        Ethernet Chip Sets

This memo defines OBJECT IDENTIFIER values for use with network
management protocols in the Internet community.  This memo provides
information for the Internet community.


2665    Flick           Sep 1999        Definitions of Managed Objects
                                        for the Ethernet-like
                                        Interface Types

This memo defines a portion of the Management Information Base (MIB) for