rfc1399.txt

RFC 的详细文档！

of the International Engineering Planning Group (IEPG), and the Reseaux
IP Europeens (RIPE).  There was general consensus by those groups to
support the recommendations proposed in this document for management of
the IP address space.  This memo provides information for the Internet
community.  It does not specify an Internet standard.


1365    Siyan         Spt 92   An IP Address Extension Proposal

This RFC suggests an extension to the IP protocol to solve the shortage
of IP address problem, and requests discussion and suggestions for
improvements.  This memo provides information for the Internet
community.  It does not specify an Internet standard.


1364    Varadhan      Spt 92   BGP OSPF Interaction

This memo defines the various criteria to be used when designing
Autonomous System Border Routers (ASBR) that will run BGP with other
ASBRs external to the AS and OSPF as its IGP.  [STANDARDS-TRACK]


1363    Partridge     Spt 92   A Proposed Flow Specification

The flow specification defined in this memo is intended for information
and possible experimentation (i.e., experimental use by consenting
routers and applications only).  This RFC is a product of the Internet
Research Task Force (IRTF).  This memo provides information for the
Internet community.  It does not specify an Internet standard.








Elliott                      Informational                      [Page 8]

RFC 1399                  Summary of 1300-1399              January 1997


1362    Allen         Spt 92   Novell IPX Over Various WAN Media
                               (IPXWAN)

This document describes how Novell IPX operates over various WAN media.
Specifically, it describes the common "IPX WAN" protocol Novell uses to
exchange necessary router to router information prior to exchanging
standard IPX routing information and traffic over WAN datalinks.  This
memo provides information for the Internet community.  It does not
specify an Internet standard.


1361    Mills         Aug 92   Simple Network Time Protocol (SNTP)

This memorandum describes the Simple Network Time Protocol (SNTP), which
is an adaptation of the Network Time Protocol (NTP) used to synchronize
computer clocks in the Internet.  This memorandum does not obsolete or
update any RFC.  This memo provides information for the Internet
community.  It does not specify an Internet standard.


1360    I.A.B.        Spt 92   IAB OFFICIAL PROTOCOL STANDARDS

Discussion of the standardization process and the RFC document series is
presented first, followed by an explanation of the terms.  Sections 6.2
- 6.9 contain the lists of protocols in each stage of standardization.
Finally come pointers to references and contacts for further
information.  [STANDARDS-TRACK]


1359    ACM SIGUCCS   Aug 92   Connecting to the Internet
                               What Connecting Institutions Should
                               Anticipate

This FYI RFC outlines the major issues an institution should consider in
the decision and implementation of a campus connection to the Internet.
This memo provides information for the Internet community.  It does not
specify an Internet standard.


1358    Chapin        Aug 92   Charter of the Internet Architecture
                               Board (IAB)

The Internet Architecture Board (IAB) shall be constituted and shall
operate as a technical advisory group of the Internet Society.  This
memo provides information for the Internet community.  It does not
specify an Internet standard.





Elliott                      Informational                      [Page 9]

RFC 1399                  Summary of 1300-1399              January 1997


1357    Cohen         Jul 92   A Format for E-mailing Bibliographic
                               Records

This memo defines a format for E-mailing bibliographic records of
technical reports.  It is intended to accelerate the dissemination of
information about new Computer Science Technical Reports (CS-TR).  This
memo provides information for the Internet community.  It does not
specify an Internet standard.


1356    Malis         Aug 92   Multiprotocol Interconnect
                               on X.25 and ISDN in the Packet Mode

This document specifies the encapsulation of IP and other network layer
protocols over X.25 networks, in accordance and alignment with ISO/IEC
and CCITT standards.  It is a replacement for RFC 877, "A Standard for
the Transmission of IP Datagrams Over Public Data Networks" [1].
[STANDARDS-TRACK]


1355    Curran        Aug 92   Privacy and Accuracy Issues in Network
                               Information Center Databases

This document provides a set of guidelines for the administration and
operation of public Network Information Center (NIC) databases.  This
memo provides information for the Internet community.  It does not
specify an Internet standard.


1354    Baker         Jul 92   IP Forwarding Table MIB

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 routes in the IP Internet.
[STANDARDS-TRACK]


1353    McCloghrie    Jul 92   Definitions of Managed Objects
                               for Administration of SNMP Parties

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 describes a representation of the SNMP parties defined in
[8] as objects defined according to the Internet Standard SMI [1].
[STANDARDS-TRACK]






Elliott                      Informational                     [Page 10]

RFC 1399                  Summary of 1300-1399              January 1997


1352    Galvin        Jul 92   SNMP Security Protocols

The Simple Network Management Protocol (SNMP) specification [1] allows
for the protection of network management operations by a variety of
security protocols.  The SNMP administrative model described in [2]
provides a framework for securing SNMP network management. In the
context of that framework, this memo defines protocols to support the
following three security services: data integrity, data origin
authentication and data confidentiality.  [STANDARDS-TRACK]


1351    Davin         Jul 92   SNMP Administrative Model

This memo presents an elaboration of the SNMP administrative model set
forth in [1]. This model provides a unified conceptual basis for
administering SNMP protocol entities to support: authenticaiton and
integrity, privacy, access control, and cooperation of protocol
entities.  [STANDARDS-TRACK]


1350    Sollins       Jul 92   THE TFTP PROTOCOL (REVISION 2)

TFTP is a very simple protocol used to transfer files.  It is from this
that its name comes, Trivial File Transfer Protocol or TFTP.  Each
nonterminal packet is acknowledged separately.  This document describes
the protocol and its types of packets.  The document also explains the
reasons behind some of the design decisions.  [STANDARDS-TRACK]


1349   Almquist       Jul 92   Type of Service in the Internet
                               Protocol Suite

This memo changes and clarifies some aspects of the semantics of the
Type of Service octet in the Internet Protocol (IP) header.
[STANDARDS-TRACK]


1348    Manning       Jul 92   DNS NSAP RRs

This RFC defines the format of two new Resource Records (RRs) for the
Domain Name System (DNS), and reserves corresponding DNS type mnemonic
and numerical codes.  This memo defines an Experimental Protocol for the
Internet community.








Elliott                      Informational                     [Page 11]

RFC 1399                  Summary of 1300-1399              January 1997


1347    Callon        Jun 92   TCP and UDP with bigger Addresses
                               (TUBA), A Simple Proposal for Internet
                               Addressing and Routing

This paper describes a simple proposal which provides a long-term
solution to Internet addressing, routing, and scaling.  This memo
provides information for the Internet community. It does not specify an
Internet standard.


1346    Jones         Jun 92   Resource Allocation, Control, and
                               Accounting for the Use of Network
                               Resources

The purpose of this RFC is to focus discussion on particular challenges
in large service networks in general, and the International IP Internet
in particular.  No solution discussed in this document is intended as a
standard.  Rather, it is hoped that a general consensus will emerge as
to the appropriate solutions, leading eventually to the adoption of
standards.  This memo provides information for the Internet community.
It does not specify an Internet standard.


1345    Simonsen      Jun 92   Character Mnemonics & Character Sets

This memo lists a selection of characters and their presence in some
coded character sets.  This memo provides information for the Internet
community.  It does not specify an Internet standard.


1344   Borenstein     Jun 92   Implicaitons of MIME for Internet Mail
                               Gateways

While MIME was carefully designed so that it does not require any
changes to Internet electronic message transport facilities, there are
several ways in which message transport systems may want to take
advantage of MIME.  These opportunities are the subject of this memo.
This memo provides information for the Internet community.  It does not
specify an Internet standard.


1343    Borenstein     Jun 92   A User Agent Configuration Mechanism
                                For Multimedia Mial Format Information

This memo suggests a file format to be used to inform multiple mail
reading user agent programs about the locally-installed facilities for
handling mail in various formats.  This memo provides information for
the Internet community.  It does not specify an Internet standard.



Elliott                      Informational                     [Page 12]

RFC 1399                  Summary of 1300-1399              January 1997


1342    Moore          Jun 92   Representation of Non-ASCII Text in
                                Internet Message Headers

This memo describes an extension to the message format defined in [1]
(known to the IETF Mail Extensions Working Group as "RFC 1341"), to
allow the representation of character sets other than ASCII in RFC 822
message headers.  [STANDARDS-TRACK]


1341    Borenstein     Jun 92   MIME: Mechanisms for Specifying and
                                Describing the Format of Internet
                                Message Bodies

This document redefines the format of message bodies to allow multi-part
textual and non-textual message bodies to be represented and exchanged
without loss of information.  [STANDARDS-TRACK]


1340    Reynolds       Jul 92   ASSIGNED NUMBERS

This Network Working Group Request for Comments documents the currently
assigned values from several series of numbers used in network protocol
implementations. This memo is a status report on the parameters (i.e.,
numbers and keywords) used in protocols in the Internet community.


1339    Dorner         Jun 92   Remote Mail Checking Protocol

This RFC defines a protocol to provide a mail checking service to be
used between a client and server pair. Typically, a small program on a
client workstation would use the protocol to query a server in order to
find out whether new mail has arrived for a specified user.  This memo
defines an Experimental Protocol for the Internet community.


1338    Fuller         Jun 92   Supernetting: an Address Assignment
                                and Aggregation Strategy

This memo discusses strategies for address assignment of the existing IP
address space with a view to conserve the address space and stem the
explosive growth of routing tables in default-route-free routers run by
transit routing domain providers.  This memo provides information for
the Internet community. It does not specify an Internet standard.








Elliott                      Informational                     [Page 13]

RFC 1399                  Summary of 1300-1399              January 1997


1337    Braden         May 92   TIME-WAIT Assassination Hazards in TCP

This note describes some theoretically-possible failure modes for TCP
connections and discusses possible remedies.  In particular, one very
simple fix is identified.  This memo provides information for the
Internet community.  It does not specify an Internet standard.


1336    Malkin         May 92   Who's Who in the Internet
                                Biographies of IAB, IESG and
                                IRSG Members

This FYI RFC contains biographical information about members of the
Internet Activities Board (IAB), the Internet Engineering Steering Group
(IESG) of the Internet Engineering Task Force (IETF), and the the
Internet Research Steering Group (IRSG) of the Internet Research Task
Force (IRTF).  This memo provides information for the Internet
community.  It does not specify any standard.


1335    Wang           May 92   A Two-Tier Address Structure for the
                                Internet:  A Solution to the Problem
                                of Address Space Exhaustion

This RFC presents a solution to problem of address space exhaustion in
the Internet.  It proposes a two-tier address structure for the
Internet.  This is an "idea" paper and discussion is strongly
encouraged.  This memo provides information for the Internet community.
It does not specify an Internet standard.


1334    Lloyd          Oct 92   PPP Authentication Protocols

This document defines two protocols for Authentication: the Password
Authentication Protocol and the Challenge-Handshake Authentication
Protocol.  [STANDARDS-TRACK]


1333    Simpson        May 92   PPP Link Quality Monitoring

The Point-to-Point Protocol (PPP) [1] provides a standard method of
encapsulating Network Layer protocol information over point-to-point
links.  PPP also defines an extensible Link Control Protocol, which
allows negotiation of a Quality Protocol for continuous monitoring of
the viability of the link.  [STANDARDS-TRACK]






Elliott                      Informational                     [Page 14]

RFC 1399                  Summary of 1300-1399              January 1997


1332    McGregor       May 92   The PPP Internet Protocol Control
                                Protocol (IPCP)

The Point-to-Point Protocol (PPP) [1] provides a standard method of
encapsulating Network Layer protocol information over point-to-point
links.  PPP also defines an extensible Link Control Protocol, and
proposes a family of Network Control Protocols (NCPs) for establishing
and configuring different network-layer protocols.  [STANDARDS-TRACK]


1331    Simpson        May 92   The Point-to-Point Protocol (PPP>
                                for the Transmission of Multi-protocol
                                Datagrams over Point-to-Point Links

This document defines the PPP encapsulation scheme, together with the
PPP Link Control Protocol (LCP), an extensible option negotiation
protocol which is able to negotiate a rich assortment of configuration
parameters and provides additional management functions.  [STANDARDS-
TRACK]


1330    E.S.C.C.       May 92   Recommendations for the Phase I
                                Deployment of OSI Directory Services
                                (X.500) and OSI Message Handling
                                Services <X.400) within the ESnet
                                Community

This RFC is a near verbatim copy of the whitepaper produced by the ESnet
Site Coordinating Committee's X.500/X.400 Task Force.  This memo
provides information for the Internet community.  It does not specify an
Internet standard.


1329    Kuehn          May 92   Thoughts on Address Resolution for