rfc2499.txt

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

Protocol (RTP).  [STANDARDS-TRACK]


2430    Li              Oct 1998        A Provider Architecture for
                                        Differentiated Services and
                                        Traffic Engineering (PASTE)

This document describes the Provider Architecture for Differentiated
Services and Traffic Engineering (PASTE) for Internet Service Providers
(ISPs).  This memo provides information for the Internet community.







Ramos                        Informational                     [Page 15]

RFC 2499                  Summary of 2400-2499                 July 1999


2429    Bormann         Oct 1998        RTP Payload Format for the
                                        1998 Version of ITU-T
                                        Rec. H.263 Video (H.263+)

This document specifies an RTP payload header format applicable to the
transmission of video streams generated based on the 1998 version of
ITU-T Recommendation H.263.  [STANDARDS-TRACK]


2428    Allman          Sep 1998        FTP Extensions for IPv6 and NATs

This paper specifies extensions to FTP that will allow the protocol to
work over IPv4 and IPv6.  [STANDARDS-TRACK]


2427    Brown           Sep 1998        Multiprotocol Interconnect
                                        over Frame Relay

This memo describes an encapsulation method for carrying network
interconnect traffic over a Frame Relay backbone.  It covers aspects of
both Bridging and Routing.  [STANDARDS-TRACK]


2426    Dawson          Sep 1998        vCard MIME Directory Profile

This memo defines the profile of the MIME Content-Type for directory
information for a white-pages person object, based on a vCard electronic
business card.  [STANDARDS-TRACK]


2425    Howes           Sep 1998        A MIME Content-Type for
                                        Directory Information

This document defines a MIME Content-Type for holding directory
information.  [STANDARDS-TRACK]


2424    Vaudreuil       Sep 1998        Content Duration MIME Header
                                        Definition

This document describes the MIME header Content-Duration that is
intended for use with any timed media content (typically audio/* or
video/*).  [STANDARDS-TRACK]








Ramos                        Informational                     [Page 16]

RFC 2499                  Summary of 2400-2499                 July 1999


2423    Vaudreuil       Sep 1998        VPIM Voice Message MIME
                                        Sub-type Registration

This document describes the registration of the MIME sub-type
multipart/voice-message for use with the Voice Profile for Internet Mail
(VPIM).  [STANDARDS-TRACK]

2422    Vaudreuil       Sep 1998        Toll Quality Voice - 32 kbit/s
                                        ADPCM MIME Sub-type Registration

This document describes the registration of the MIME sub-type
audio/32KADPCM for toll quality audio.  [STANDARDS-TRACK]


2421    Vaudreuil       Sep 1998        Voice Profile for Internet
                                        Mail - version 2

This document profiles Internet mail for voice messaging.  [STANDARDS-
TRACK]


2420    Kummert         Sep 1998        The PPP Triple-DES Encryption
                                        Protocol (3DESE)

This document provides specific details for the use of the Triple-DES
standard (3DES) for encrypting PPP encapsulated packets.  [STANDARDS-
TRACK]


2419    Sklower         Sep 1998        The PPP DES Encryption
                                        Protocol, Version 2 (DESE-bis)

This document provides specific details for the use of the DES standard
for encrypting PPP encapsulated packets.  [STANDARDS-TRACK]


2418    Bradner         Sep 1998        IETF Working Group
                                        Guidelines and Procedures

This document describes the guidelines and procedures for formation and
operation of IETF working groups.  This document specifies an Internet
Best Current Practices for the Internet Community, and requests
discussion and suggestions for improvements.








Ramos                        Informational                     [Page 17]

RFC 2499                  Summary of 2400-2499                 July 1999


2417    Chung           Sep 1998        Definitions of Managed Objects
                                        for Multicast over UNI 3.0/3.1
                                        based ATM Networks

This memo specifies a MIB module in a manner that is both compliant to
the SNMPv2 SMI, and semantically identical to the peer SNMPv1
definitions.  [STANDARDS-TRACK]


2416    Shepard         Sep 1998        When TCP Starts Up With Four
                                        Packets Into Only Three Buffers

This memo is to document a simple experiment.  The experiment showed
that in the case of a TCP receiver behind a 9600 bps modem link at the
edge of a fast Internet where there are only 3 buffers before the modem
(and the fourth packet of a four-packet start will surely be dropped),
no significant degradation in performance is experienced by a TCP
sending with a four-packet start when compared with a normal slow start
(which starts with just one packet).  This memo provides information for
the Internet community.


2415    Poduri          Sep 1998        Simulation Studies of
                                        Increased Initial TCP Window Size

This document covers some simulation studies of the effects of
increasing the initial window size of TCP.  This memo provides
information for the Internet community.


2414    Allman          Sep 1998        Increasing TCP's Initial Window

This document specifies an increase in the permitted initial window for
TCP from one segment to roughly 4K bytes.  This memo defines an
Experimental Protocol for the Internet community.


2413    Weibel          Sep 1998        Dublin Core Metadata for
                                        Resource Discovery

This is the first of a set of Informational RFCs describing the Dublin
Core.  Its purpose is to introduce the Dublin Core and to describe the
consensus reached on the semantics of each of the 15 elements.  This
memo provides information for the Internet community.







Ramos                        Informational                     [Page 18]

RFC 2499                  Summary of 2400-2499                 July 1999


2412    Orman           Nov 1998        The OAKLEY Key Determination
                                        Protocol

This document describes a protocol, named OAKLEY, by which two
authenticated parties can agree on secure and secret keying material.
The basic mechanism is the Diffie-Hellman key exchange algorithm.  This
memo provides information for the Internet community.


2411    Thayer          Nov 1998        IP Security Document Roadmap

This document is intended to provide guidelines for the development of
collateral specifications describing the use of new encryption and
authentication algorithms with the ESP protocol, described in and new
authentication algorithms used with the AH protocol.  This memo provides
information for the Internet community.


2410    Glenn           Nov 1998        The NULL Encryption Algorithm
                                        and Its Use With IPsec

This memo defines the NULL encryption algorithm and its use with the
IPsec Encapsulating Security Payload (ESP).  [STANDARDS-TRACK]


2409    Harkins         Nov 1998        The Internet Key Exchange (IKE)

This memo describes a hybrid protocol. The purpose is to negotiate, and
provide authenticated keying material for, security associations in a
protected manner.  [STANDARDS-TRACK]


2408    Maughan         Nov 1998        Internet Security Association
                                        and Key Management Protocol
                                        (ISAKMP)

This memo describes a protocol utilizing security concepts necessary for
establishing Security Associations (SA) and cryptographic keys in an
Internet environment.  [STANDARDS-TRACK]


2407    Piper           Nov 1998        The Internet IP Security
                                        Domain of Interpretation for
                                        ISAKMP

This document defines the Internet IP Security DOI (IPSEC DOI), which
instantiates ISAKMP for use with IP when IP uses ISAKMP to negotiate
security associations.  [STANDARDS-TRACK]



Ramos                        Informational                     [Page 19]

RFC 2499                  Summary of 2400-2499                 July 1999


2406    Kent            Nov 1998        IP Encapsulating Security
                                        Payload (ESP)

The Encapsulating Security Payload (ESP) header is designed to provide a
mix of security services in IPv4 and IPv6.  [STANDARDS-TRACK]


2405    Madson          Nov 1998        The ESP DES-CBC Cipher
                                        Algorithm With Explicit IV

This document describes the use of the DES Cipher algorithm in Cipher
Block Chaining Mode, with an explicit IV, as a confidentiality mechanism
within the context of the IPSec Encapsulating Security Payload (ESP).
[STANDARDS-TRACK]


2404    Madson          Nov 1998        The Use of HMAC-SHA-1-96
                                        within ESP and AH

This memo describes the use of the HMAC algorithm in conjunction with
the SHA-1 algorithm as an authentication mechanism within the revised
IPSEC Encapsulating Security Payload and the revised IPSEC
Authentication Header.  [STANDARDS-TRACK]


2403    Madson          Nov 1998        The Use of HMAC-MD5-96 within
                                        ESP and AH

This memo describes the use of the HMAC algorithm in conjunction with
the MD5 algorithm as an authentication mechanism within the revised
IPSEC Encapsulating Security Payload and the revised IPSEC
Authentication Header.  [STANDARDS-TRACK]


2402    Kent            Nov 1998        IP Authentication Header

The IP Authentication Header (AH) is used to provide connectionless
integrity and data origin authentication for IP datagrams (hereafter
referred to as just "authentication"), and to provide protection against
replays.  [STANDARDS-TRACK]











Ramos                        Informational                     [Page 20]

RFC 2499                  Summary of 2400-2499                 July 1999


2401    Kent            Nov 1998        Security Architecture for the
                                        Internet Protocol

This memo specifies the base architecture for IPsec compliant systems.
[STANDARDS-TRACK]


2400    IAB             Sep 1998        INTERNET OFFICIAL PROTOCOL
                                        STANDARDS

This memo describes the state of standardization of protocols used in
the Internet as determined by the Internet Architecture Board (IAB).
This memo is an Internet Standard.  [STANDARDS-TRACK]


Security Considerations

   This memo does not affect the technical security of the Internet, but
   it does cite some security specifications.

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 21]

RFC 2499                  Summary of 2400-2499                 July 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.

Acknowledgement

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



















Ramos                        Informational                     [Page 22]