rfc1999.txt

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

                              Automatic Network Address Acquisition

This memo describes extensions to the Reverse Address Resolution
Protocol (RARP [2]) and called Dynamic RARP (DRARP, pronounced D-RARP).
This memo provides information for the Internet community.  This memo
does not define an Internet standard of any kind.


1930    Hawkinson    Mar 96   Guidelines for creation, selection, and
                              registration of an Autonomous System (AS)

This memo discusses when it is appropriate to register and utilize an
Autonomous System (AS), and lists criteria for such.  This document
specifies an Internet Best Current Practices for the Internet Community,
and requests discussion and suggestions for improvements.


1929    Leech        Mar 96   Username/Password Authentication for
                              SOCKS V5

The protocol specification for SOCKS Version 5 specifies a generalized
framework for the use of arbitrary authentication protocols in the
initial socks connection setup. This document describes one of those
protocols, as it fits into the SOCKS Version 5 authentication
"subnegotiation".  [STANDARDS-TRACK]










Elliott                      Informational                     [Page 14]

RFC 1999                  Summary of 1900-1999              January 1997


1928    Leech        Mar 96   SOCKS Protocol Version 5

This memo describes a protocol that is an evolution of the previous
version of the protocol, version 4 [1]. This new protocol stems from
active discussions and prototype implementations.  [STANDARDS-TRACK]


1927    Rogers       Apr 96   Suggested Additional MIME Types for
                              Associating Documents

Seven new types of MIME types are suggested in this document.  This memo
provides information for the Internet community.  This memo does not
specify an Internet standard of any kind.


1926    Eriksson     Apr 96   An Experimental Encapsulation of IP
                              Datagrams on Top of ATM

This RFC describes a method of encapsulating IP datagrams on top of
Acoustical Transmission Media (ATM).  This is a non-recommended
standard.  This memo provides information for the Internet community.
This memo does not specify an Internet standard of any kind.


1925    Callon       Apr 96   The Twelve Networking Truths

This memo documents the fundamental truths of networking for the
Internet community. This memo does not specify a standard, except in the
sense that all standards must implicitly follow the fundamental truths.
This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.


1924    Elz          Apr 96   A Compact Representation of IPv6 Addresses

This document specifies a more compact representation of IPv6 addresses,
which permits encoding in a mere 20 bytes.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.












Elliott                      Informational                     [Page 15]

RFC 1999                  Summary of 1900-1999              January 1997


1923    Halpern      Mar 96   RIPv1 Applicability Statement for
                              Historic Status

RIP Version 1 [RFC-1058] has been declared an historic document.  This
Applicability statement provides the supporting motivation for that
declaration.  The primary reason, as described below, is the Classful
nature of RIPv1.  This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.


1922    Zhu          Mar 96   Chinese Character Encoding for Internet
                              Messages

This memo describes methods of transporting Chinese characters in
Internet services which transport text, such as electronic mail
[RFC-822], network news [RFC-1036], telnet [RFC-854] and the World Wide
Web [RFC-1866].  This memo provides information for the Internet
community.  It does not specify an Internet standard.


1921    Dujonc       Mar 96   TNVIP Protocol

The goal of this document specifies a Telnet profile to support VIP
terminal emulation allowing the access to the BULL hosts applications
through a TCP/IP network.  This memo provides information for the
Internet community.  This memo does not specify an Internet standard of
any kind.


1920    I.A.B.       Mar 96   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).
[STANDARDS-TRACK]


1919    Chatel       Mar 96   Classical versus Transparent IP Proxies

This document explains "classical" and "transparent" proxy techniques
and attempts to provide rules to help determine when each proxy system
may be used without causing problems.  This memo provides information
for the Internet community.  This memo does not specify an Internet
standard of any kind.








Elliott                      Informational                     [Page 16]

RFC 1999                  Summary of 1900-1999              January 1997


1918    Rekhter      Feb 96   Address Allocation for Private Internets

This document describes address allocation for private internets.  This
document specifies an Internet Best Current Practices for the Internet
Community, and requests discussion and suggestions for improvements.


1917    Nesser       Feb 96   An Appeal to the Internet Community to
                              Return Unused IP Networks (Prefixes)
                              to the IANA

This document is an appeal to the Internet community to return unused
address space, i.e. any block of consecutive IP prefixes, to the
Internet Assigned Numbers Authority (IANA) or any of the delegated
registries, for reapportionment.  This document specifies an Internet
Best Current Practices for the Internet Community, and requests
discussion and suggestions for improvements.


1916    Berkowitz    Feb 96   Enterprise Renumbering: Experience and
                              Information Solicitation

Because of the urgent need for, and substantial difficulty in,
renumbering IP networks, the PIER working group is compiling a series of
documents to assist sites in their renumbering efforts.  The intent of
these documents is to provide both educational and practical information
to the Internet community.  This memo provides information for the
Internet community.  This memo does not specify an Internet standard of
any kind.


1915    Kastenholz   Feb 96   Variance for The PPP Connection Control
                              Protocol and The PPP Encryption Control
                              Protocol

The PPP Working group has developed two protocols, one to control
compression on PPP links; the Compression Control Protocol (CCP),
documented in draft-ietf-pppext-compression-04.txt. The second is the
Encryption Control Protocol (ECP), used to control encryption on serial
links, documented in draft-ietf-pppext-encryption-03.txt.  This document
specifies an Internet Best Current Practices for the Internet Community,
and requests discussion and suggestions for improvements.









Elliott                      Informational                     [Page 17]

RFC 1999                  Summary of 1900-1999              January 1997


1914    Faltstrom    Feb 96   How to Interact with a Whois++ Mesh

In the Whois++ architecture [Deutsch94],[Weider94], mesh traversal is
done by the client, since each server 'refers' the client to the next
appropriate server(s).  [STANDARDS-TRACK]


1913    Weider       Feb 96   Architecture of the Whois++ Index Service

The authors describe an architecture for indexing in distributed
databases, and apply this to the WHOIS++ protocol.  [STANDARDS-TRACK]


1912    Barr         Feb 96   Common DNS Operational and Configuration
                              Errors

This memo describes errors often found in both the operation of Domain
Name System (DNS) servers, and in the data that these DNS servers
contain.  This memo provides information for the Internet community.
This memo does not specify an Internet standard of any kind.


1911    Vaudreuil    Feb 96   Voice Profiule of Internet Mail

The following document is a profile of the Internet standard MIME and
ESMTP protocols for use as a digital voice networking protocol.  This
memo defines an Experimental Protocol for the Internet community.


1910    Waters       Feb 96   User-based Security Model for SNMPv2

In this administrative framework, a security model defines the
mechanisms used to achieve an administratively-defined level of security
for protocol interactions.  Although many such security models might be
defined, it is the purpose of this document, User-based Security Model
for SNMPv2, to define the first, and, as of this writing, only, security
model for this administrative framework.  This memo defines an
Experimental Protocol for the Internet community.


1909    McClogherie  Feb 96   An Administrative Infrastructure for
                              SNMPv2

It is the purpose of this document, An Administrative Infrastructure for
SNMPv2, to define an administrative framework which realizes effective
management in a variety of configurations and environments.  This memo
defines an Experimental Protocol for the Internet community.




Elliott                      Informational                     [Page 18]

RFC 1999                  Summary of 1900-1999              January 1997


1908    Case         Jan 96   Coexistence between Version 1 and
                              Version 2 of the Internet-standard
                              Network Management Framework

The purpose of this document is to describe coexistence between version
2 of the Internet-standard Network Management Framework [1-6], termed
the SNMP version 2 framework (SNMPv2), and the original Internet-
standard Network Management Framework (SNMPv1>.  [STANDARDS-TRACK]


1907    Case         Jan 96   Management Information Base for Version
                              2 of the Simple Network Management
                              Protocol (SNMPv2)

It is the purpose of this document to define managed objects which
describe the behavior of a SNMPv2 entity.  [STANDARDS-TRACK]


1906    Case         Jan 96   Transport Mappings for Version 2 of the
                              Simple Network Management Protocol (SNMPv2)

It is the purpose of this document to define how the SNMPv2 maps onto an
initial set of transport domains.  [STANDARDS-TRACK]


1905    Case         Jan 96   Protocol Operations for Version 2 of the
                              Simple Network Management Protocol (SNMPv2)

It is the purpose of this document, Protocol Operations for SNMPv2, to
define the operations of the protocol with respect to the sending and
receiving of the PDUs.  [STANDARDS-TRACK]


1904    Case         Jan 96   Conformance Statements for Version 2 of
                              the Simple Network Management Protocol
                              (SNMPv2)

It may be useful to define the acceptable lower-bounds of
implementation, along with the actual level of implementation achieved.
It is the purpose of this document to define the notation used for these
purposes.  [STANDARDS-TRACK]










Elliott                      Informational                     [Page 19]

RFC 1999                  Summary of 1900-1999              January 1997


1903    Case         Jan 96   Textual Conventions for Version 2 of the
                              Simple Network Management Protocol (SNMPv2)

It is the purpose of this document to define the initial set of textual
conventions available to all MIB modules.  [STANDARDS-TRACK]


1902    Case         Jan 96   Structure of Management Information for
                              Version 2 of the Simple Network
                              Management Protocol (SNMPv2)

It is the purpose of this document, the Structure of Management
Information (SMI), to define that adapted subset, and to assign a set of
associated administrative values.  [STANDARDS-TRACK]


1901    Case         Jan 96   Introduction to Community-based SNMPv2

The purpose of this document is to define the Community-based
Administrative Framework for the SNMP version 2 framework (SNMPv2).
This document specifies an Experimental protocol for the Internet
community.


1900    Carpenter    Feb 96   Renumbering Needs Work

Hosts in an IP network are identified by IP addresses, and the IP
address prefixes of subnets are advertised by routing protocols.  A
change in such IP addressing information associated with a host or
subnet is known as "renumbering".  This memo provides information for
the Internet community.  This memo does not specify an Internet standard
of any kind.

Security Considerations

   Security issues are not discussed in this memo.

Author's Address

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

   Phone:  [phone]

   EMail: [e-mail]



Elliott                      Informational                     [Page 20]