rfc1799.txt

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


RFC 1799                  Summary of 1700-1799              January 1997


1768   Marlow  Mar 95   Host Group Extensions for CLNP Multicasting

This memo provides a specification for multicast extensions to the CLNP
protocol similar to those provided to IP by RFC1112. This memo defines
an Experimental Protocol for the Internet community.  This memo does not
specify an Internet standard of any kind.


1767   Crocker  Mar 95   MIME Encapsulation of EDI Objects

Since there are many different EDI specifications, the current document
defines three distinct categories as three different MIME content-types.
[STANDARDS-TRACK]


1766   Alvestrand Mar 95  Tags for the Identification of Languages

This document describes a language tag for use in cases where it is
desired to indicate the language used in an information object.
[STANDARDS-TRACK]


1765   Moy       Mar 95   OSPF Database Overflow

This memo details a way of gracefully handling unanticipated database
overflows. This memo defines an Experimental Protocol for the Internet
community.  This memo does not specify an Internet standard of any kind.


1764   Senum     Mar 95   The PPP XNS IDP Control Protocol (XNSCP)

This document defines the Network Control Protocol for establishing and
configuring the Xerox Network Systems (XNS) Internet Datagram Protocol
(IDP) over PPP. [STANDARDS-TRACK]


1763   Senum     Mar 95   The PPP Banyan Vines Control Protocol (BVCP)

This document defines the Network Control Protocol for establishing and
configuring the Banyan VINES protocol over PPP. [STANDARDS-TRACK]











Kennedy                      Informational                      [Page 8]

RFC 1799                  Summary of 1700-1799              January 1997


1762   Senum     Mar 95   The PPP DECnet Phase IV Control Protocol
                          (DNCP)

This document defines the NCP for establishing and configuring Digital's
DNA Phase IV Routing protocol (DECnet Phase IV) over PPP.  This document
applies only to DNA Phase IV Routing messages (both data and control),
and not to other DNA Phase IV protocols (MOP, LAT, etc). [STANDARDS-
TRACK]


1761   Callaghan  Feb 95  Snoop Version 2 Packet Capture File Format

This paper describes the file format used by "snoop", a packet
monitoring and capture program developed by Sun.  This paper is provided
so that people can write compatible programs to generate and interpret
snoop packet capture files. This memo provides information for the
Internet community.  This memo does not specify an Internet standard of
any kind.


1760   Haller     Feb 95  The S/KEY One-Time Password System

This document describes the S/KEY* One-Time Password system as released
for public use by Bellcore. This memo provides information for the
Internet community.  This memo does not specify an Internet standard of
any kind.


1759   Smith      Mar 95  Printer MIB

A printer is the physical device that takes media from an input source,
produces marks on that media according to some page description or page
control language and puts the result in some output destination,
possibly with finishing applied. The information needed in the
management of the physical printer and the management of a printing job
overlap highly and many of the tasks in each management area require the
same or similar information. [STANDARDS-TRACK]


1758   N.A.D.F.   Feb 95    NADF Standing Documents: A Brief Overview

The purpose of this document is to provide a brief overview of the
NADF's Standing Document series. This memo provides information for the
Internet community.  This memo does not specify an Internet standard of
any kind.






Kennedy                      Informational                      [Page 9]

RFC 1799                  Summary of 1700-1799              January 1997


1757   Waldbusser Feb 95   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]


1756    Rinne     Jan 95   REMOTE WRITE PROTOCOL - VERSION 1.0

This document describes a simple Remote Write Protocol (RWP). This memo
defines an Experimental Protocol for the Internet community.  This memo
does not specify an Internet standard of any kind.


1755    Perez     Feb 95   ATM Signaling Support for IP over ATM

This memo describes the ATM call control signaling exchanges needed to
support Classical IP over ATM implementations as described in RFC 1577.
[STANDARDS-TRACK]


1754    Laubach   Jan 95   IP over ATM Working Group's
                           Recommendations for the ATM Forum's
                           Multiprotocol BOF
                           Version 1

This document represents an initial list of requirements submitted to
the ATM Forum's Multiprotocol BOF for the operation of IP over ATM
networks as determined by the IETF IP over ATM Working Group and other
working groups. This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.


1753     Chiappa   Dec 94   IPng Technical Requirements
                            Of the Nimrod Routing and Addressing
                            Architecture

This document presents the requirements that the Nimrod routing and
addressing architecture has upon the internetwork layer protocol. To be
most useful to Nimrod, any protocol selected as the IPng should satisfy
these requirements. This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.







Kennedy                      Informational                     [Page 10]

RFC 1799                  Summary of 1700-1799              January 1997


1752     Bradner   Jan 95   The Recommendation for the IP Next
                            Generation Protocol

This document presents the recommendation of the IPng Area Directors on
what should be used to replace the current version of the Internet
Protocol. [STANDARDS-TRACK]


1751     McDonald   Dec 94   A Convention for Human-Readable 128-bit
                             Keys

This memo proposes a convention for use with Internet applications &
protocols using 128-bit cryptographic keys. This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


1750     Eastlake    Dec 94  Randomness Recommendations for Security

Choosing random quantities to foil a resourceful and motivated adversary
is surprisingly difficult.  This paper points out many pitfalls in using
traditional pseudo-random number generation techniques for choosing such
quantities.  It recommends the use of truly random hardware techniques
and shows that the existing hardware on many systems can be used for
this purpose. This memo provides information for the Internet community.
This memo does not specify an Internet standard of any kind.


1749   McCloghrie    Dec 94   IEEE 802.5 Station Source Routing MIB
                              using SMIv2

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it describes managed objects used by IEEE 802.5 end-stations
for managing source routes on a Token Ring network where IEEE source-
routing is in use. [STANDARDS-TRACK]


1748   McCloghrie    Dec 94   IEEE 802.5 MIB using SMIv2

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it describes managed objects used for managing subnetworks
which use the IEEE 802.5 Token Ring technology described in 802.5 Token
Ring Access Method and Physical Layer Specifications, IEEE Standard
802.5-1989. [STANDARDS-TRACK]





Kennedy                      Informational                     [Page 11]

RFC 1799                  Summary of 1700-1799              January 1997


1747   Hilgeman     Jan 95   Definitions of Managed Objects for SNA
                             Data Link Control (SDLC) using SMIv2

This specification defines an extension to the Management Information
Base (MIB) for use with SNMP-based network management.  In particular,
it defines objects for managing the configuration, monitoring and
control of data link controls in an SNA environment. [STANDARDS-TRACK]


1746   Manning      Dec 94   Ways to Define User Expectations

This paper covers basic fundamentals that must be understood when one
defines, interprets, or implements methods to control user expectations
on or over the Internet. This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.


1745    Varadhan     Dec 94   BGP4/IDRP for IP---OSPF Interaction

This memo defines the various criteria to be used when designing an
Autonomous System Border Router (ASBR) that will run either BGP4 or IDRP
for IP with other ASBRs external to the AS and OSPF as its IGP.
[STANDARDS-TRACK]


1744     Huston      Dec 94   Observations on the Management of
                              the Internet Address Space

This memo examines some of the issues associated with the current
management practices of the Internet IPv4 address space, and examines
the potential outcomes of these practices as the unallocated address
pool shrinks in size. This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.


1743     McCloghrie  Dec 94    IEEE 802.5 MIB using SMIv2

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it describes managed objects used for managing subnetworks
which use the IEEE 802.5 Token Ring technology described in 802.5 Token
Ring Access Method and Physical Layer Specifications, IEEE Standard
802.5-1989. [STANDARDS-TRACK]








Kennedy                      Informational                     [Page 12]

RFC 1799                  Summary of 1700-1799              January 1997


1742     Waldbusser  Jan 95    AppleTalk Management Information Base II

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 AppleTalk networks.
[STANDARDS-TRACK]


1741     Falstrom     Dec 94  MIME Content Type for BinHex Encoded Files

This memo describes the format to use when sending BinHex4.0 files via
MIME [BORE93]. This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.


1740     Falstron     Dec 94   MIME Encapsulation of Macintosh Files -
                               MacMIME

This memo describes the format to use when sending Apple Macintosh files
via MIME [BORE93]. [STANDARDS-TRACK]


1739     Kessler       Dec 94   A Primer On Internet and TCP/IP Tools

This memo is an introductory guide to some of the TCP/IP and Internet
tools and utilities that allow users to access the wide variety of
information on the network, from determining if a particular host is up
to viewing a multimedia thesis on foreign policy. It also describes
discussion lists accessible from the Internet, ways to obtain Internet
documents, and resources that help users weave their way through the
Internet. This memo provides information for the Internet community.
This memo does not specify an Internet standard of any kind.


1738     Berners-Lee   Dec 94   Uniform Resource Locators (URL)

This document specifies a Uniform Resource Locator (URL), the syntax and
semantics of formalized information for location and access of resources
via the Internet. [STANDARDS-TRACK]


1737     Sollins       Dec 94   Functional Requirements for Uniform
                                Resource Names

This document specifies a minimum set of requirements for a kind of
Internet resource identifier known as Uniform Resource Names (URNs).
This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.



Kennedy                      Informational                     [Page 13]

RFC 1799                  Summary of 1700-1799              January 1997


1736     Kunze        Feb 95    Functional Recommendations for
                                Internet Resource Locators

This document specifies a minimum set of requirements for Internet
resource locators, which convey location and access information for
resources. This memo provides information for the Internet community.
This memo does not specify an Internet standard of any kind.


1735     Heinanen     Dec 94    NBMA Address Resolution Protocol (NARP)

This document describes the NBMA Address Resolution Protocol (NARP).
NARP can be used by a source terminal (host or router) connected to a
Non-Broadcast, Multi-Access link layer (NBMA) network to find out the
NBMA addresses of the a destination terminal provided that the
destination terminal is connected to the same NBMA network. This memo
defines an Experimental Protocol for the Internet community.  This memo
does not specify an Internet standard of any kind.


1734     Myers        Dec 94   POP3 AUTHentication command

This document describes the optional AUTH command, for indicating an
authentication mechanism to the server, performing an authentication
protocol exchange, and optionally negotiating a protection mechanism for
subsequent protocol interactions. [STANDARDS-TRACK]


1733     Crispin      Dec 94   Distributed Electronic Mail
                               Models in IMAP4


There are three fundamental models of client/server email: offline,
online, and disconnected use.  IMAP4 can be used in any one of these
three models.  This memo provides information for the Internet
community. This memo does not specify an Internet standard of any kind.


1732     Crispin      Dec 94   IMAP4 COMPATIBILITY WITH IMAP2
                               AND IMAP2BIS

This is a summary of hints and recommendations to enable an IMAP4
implementation to interoperate with implementations that conform to
earlier specifications. This memo provides information for the Internet
community. This memo does not specify an Internet standard of any kind.






Kennedy                      Informational                     [Page 14]

RFC 1799                  Summary of 1700-1799              January 1997