rfc1899.txt

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

1868    Malkin       Nov 95   ARP Extension - UNARP

This document specifies a trivial modification to the ARP mechanism, not
the packet format, which allows a node to announce that it is leaving
the network and that all other nodes should modify their ARP tables
accordingly.  This memo defines an Experimental Protocol for the
Internet community.









Elliott                      Informational                      [Page 7]

RFC 1899                  Summary of 1800-1899              January 1997


1867    Nebel        Nov 95   Form-based File Upload in HTML

Since file-upload is a feature that will benefit many applications, this
proposes an extension to HTML to allow information providers to express
file upload requests uniformly, and a MIME compatible representation for
file upload responses.  This memo defines an Experimental Protocol for
the Internet community.


1866    Berners-Lee  Nov 95   Hypertext Markup Language - 2.0

This document defines a HTML 2.0 (to distinguish it from the previous
informal specifications).  [STANDARDS-TRACK]


1865    Houser       Jan 96   EDI Meets the Internet: Frequently Asked
                              Questions about Electronic Data
                              Interchange (EDI) on the Internet

This memo is targeted towards the EDI community that is unfamiliar with
the Internet, including EDI software developers, users, and service
providers.  The memo introduces the Internet and assumes a basic
knowledge of EDI.  This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.


1864    Myers        Oct 95   The Content-MD5 Header Field

This memo specifies an optional header field, Content-MD5, for use with
MIME-conformant messages.  [STANDARDS-TRACK]


1863    Haskin       Oct 95   A BGP/IDRP Route Server alternative to a
                              full mesh routing

This document describes the use and detailed design of Route Servers for
dissemination of routing information among BGP/IDRP speaking routers.
This memo defines an Experimental Protocol for the Internet community.













Elliott                      Informational                      [Page 8]

RFC 1899                  Summary of 1800-1899              January 1997


1862    McCahill     Nov 95   Report of the IAB Workshop on Internet
                              Information Infrastructure,
                              October 12-14, 1994

This document is a report on an Internet architecture workshop,
initiated by the IAB and held at MCI on October 12-14, 1994.  This
workshop generally focused on aspects of the information infrastructure
on the Internet.  This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.


1861    Gwinn        Oct 95   Simple Network Paging Protocol -
                              Version 3 - Two-Way Enhanced

This RFC suggests a simple way for delivering wireless messages, both
one and two-way, to appropriate receiving devices.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


1860    Pummill      Oct 95   Variable Length Subnet Table For IPv4

This document itemizes the potential values for IPv4 subnets.  This memo
provides information for the Internet community.  This memo does not
specify an Internet standard of any kind.


1859    Pouffary     Oct 95   ISO Transport Class 2 Non-use of
                              Explicit Flow Control over
                              TCP RFC1006 extension

This document is an extension to STD35, RFC1006, a standard for the
Internet community. The document does not duplicate the protocol
definitions contained in RFC1006 and in International Standard ISO 8073.
It supplements that information with the description of how to implement
ISO Transport Class 2 Non-use of Explicit Flow Control on top of TCP.
This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.













Elliott                      Informational                      [Page 9]

RFC 1899                  Summary of 1800-1899              January 1997


1858    Ziemba       Oct 95   Security Considerations for
                              IP Fragment Filtering

IP fragmentation can be used to disguise TCP packets from IP filters
used in routers and hosts. This document describes two methods of attack
as well as remedies to prevent them.  This memo provides information for
the Internet community.  This memo does not specify an Internet standard
of any kind.


1857    Lambert      Oct 95   A Model for Common Operational
                              Statistics

This memo describes a model for operational statistics in the Internet.
This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.


1856    Clark        Shpt 95   The Opstat Client-Server Model for
                              Statistics Retrieval

This document defines a model and protocol for a set of tools which
could be used by NSPs and Network Operation Centers (NOCs) to share data
among themselves and with customers.  This memo provides information for
the Internet community.  This memo does not specify an Internet standard
of any kind.


1855    Hambridge    Oct 95   Netiquette Guidelines

This document provides a minimum set of guidelines for Network Etiquette
(Netiquette) which organizations may take and adapt for their own use.
This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.


1854    Freed        Oct 95   SMTP Service Extension for
                              Command Pipelining

This memo defines an extension to the SMTP service whereby a server can
indicate the extent of its ability to accept multiple commands in a
single TCP send operation.  [STANDARDS-TRACK]









Elliott                      Informational                     [Page 10]

RFC 1899                  Summary of 1800-1899              January 1997


1853    Simpson      Oct 95   IP in IP Tunneling

This document discusses implementation techniques for using IP
Protocol/Payload number 4 Encapsulation for tunneling with IP Security
and other protocols.  This memo provides information for the Internet
community.  It does not specify an Internet standard.


1852    Metzger      Spt 95   IP Authentication using Keyed SHA

This document describes the use of keyed SHA with the IP Authentication
Header.  This document defines an Experimental Protocol for the Internet
community.


1851    Karn         Spt 95   The ESP Triple DES Transform

This document describes the Triple DES-CBC security transform for the IP
Encapsulating Security Payload (ESP).  This document defines an
Experimental Protocol for the Internet community.


1850    Baker        Nov 95   OSPF Version 2 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 the Open Shortest Path First
Routing Protocol.  [STANDARDS-TRACK]


1849    Never Issued.


1848    Crocker      Oct 95   MIME Object Security Services

This document defines MIME Object Security Services (MOSS), a protocol
that uses the multipart/signed and multipart/encrypted framework [7] to
apply digital signature and encryption services to MIME objects.
[STANDARDS-TRACK]


1847    Galvin       Oct 95   Security Multiparts for MIME:
                              Multipart/Signed and Multipart/Encrypted

This document defines a framework within which security services may be
applied to MIME body parts.  [STANDARDS-TRACK]




Elliott                      Informational                     [Page 11]

RFC 1899                  Summary of 1800-1899              January 1997


1846    Durand       Spt 95   SMTP 521 Reply Code

This memo defines a new Simple Mail Transfer Protocol (SMTP) [1] reply
code, 521, which one may use to indicate that an Internet host does not
accept incoming mail.  This memo defines an Experimental Protocol for
the Internet community.


1845    Crocker      Spt 95   SMTP Service Extension
                              for Checkpoint/Restart

This memo defines an extension to the SMTP service whereby an
interrupted SMTP transaction can be restarted at a later time without
having to repeat all of the commands and message content sent prior to
the interruption.  This memo defines an Experimental Protocol for the
Internet community.


1844    Huizer       Aug 95   Multimedia E-mail (MIME) User
                              Agent checklist

This document presents a checklist to facilitate evaluation of MIME
capable User Agents.  This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.


1843    Lee          Aug 95   HZ - A Data Format for Exchanging Files
                              of Arbitrarily Mixed Chinese and ASCII
                              characters

The content of this memo is identical to an article of the same title
written by the author on September 4, 1989.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


1842    Wei          Aug 95   ASCII Printable Characters-Based Chinese
                              Character Encoding for Internet Messages

This document describes the encoding used in electronic mail [RFC822]
and network news [RFC1036] messages over the Internet.  This memo
provides information for the Internet community.  This memo does not
specify an Internet standard of any kind.








Elliott                      Informational                     [Page 12]

RFC 1899                  Summary of 1800-1899              January 1997


1841    Chapman      Spt 95   PPP Network Control Protocol for
                              LAN Extension

Telecommunications infrastructure is improving to offer higher bandwidth
connections at lower cost. Access to the network is changing from modems
to more intelligent devices. This informational RFC discusses a PPP
Network Control Protocol for one such intelligent device. The protocol
is the LAN extension interface protocol.  This memo provides information
for the Internet community.  This memo does not specify an Internet
standard of any kind.


1840    Never Issued.


1839    Never Issued.


1838    Kille        Aug 95   Use of the X.500 Directory to support
                              mapping between X.400 and RFC 822
                              Addresses

This document defines how to use directory to support the mapping
between X.400 O/R Addresses and mailboxes defined in RFC 1327 [2].  This
memo defines an Experimental Protocol for the Internet community.


1837    Kille        Aug 95   Representing Tables and Subtrees in the
                              X.500 Directory

This document defines techniques for representing two types of
information mapping in the OSI Directory.  This memo defines an
Experimental Protocol for the Internet community.


1836    Kille        Aug 95   Representing the O/R Address hierarchy
                              in the X.500 Directory Information Tree

This document defines a representation of the O/R Address hierarchy in
the Directory Information Tree [6, 1].  This memo defines an
Experimental Protocol for the Internet community.










Elliott                      Informational                     [Page 13]

RFC 1899                  Summary of 1800-1899              January 1997


1835    Deutsch      Aug 95   Architecture of the WHOIS++ service

This document describes WHOIS++, an extension to the trivial WHOIS
service described in RFC 954 to permit WHOIS-like servers to make
available more structured information to the Internet.  [STANDARDS-
TRACK]


1834    Gargano      Aug 95   Whois and Network Information
                              Lookup Service Whois++

This memo describes new features for WHOIS.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.