rfc1399.txt

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

Network Working Group                                         J. Elliott
Request for Comments: 1399                                           ISI
Category: Informational                                     January 1997


                      Request for Comments Summary

                         RFC Numbers 1300-1399

Status of This Memo

   This RFC is a slightly annotated list of the 100 RFCs from RFC 1300
   through RFCs 1399.  This is a status report on these RFCs.  This memo
   provides information for the Internet community.  It does not specify
   an Internet standard of any kind.  Distribution of this memo is
   unlimited.

Note

   Many RFCs, but not all, are Proposed Standards, Draft Standards, or
   Standards.  Since the status of these RFCs may change during the
   standards processing, we note here only that they are on the
   standards track.  Please see the latest edition of "Internet Official
   Protocol Standards" for the current state and status of these RFCs.
   In the following, RFCs on the standards track are marked [STANDARDS-
   TRACK].

RFC     Author       Date      Title
---     ------       ----      -----

1399    Elliott      Jan 97   Requests For Comments Summary

This memo.


1398    Kastenholz   Jan 93   Definitions of Managed Objects for the
                              Ethernet-like Interface Types

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 ehternet-like objects.
[STANDARDS-TRACK]









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


1397    Haskin       Jan 93   Default Route Advertisement In BGP2 and
                              BGP3 Versions of the Border Gateway
                              Protocol

This document speficies the recommendation of the BGP Working Group on
default route advertisement support in BGP2 [1] and BGP3 [2] versions of
the Border Gateway Protocol.  [STANDARDS-TRACK]


1396    Crocker      Jan 93   The Process for Organization of Internet
                              Standards

This report provides a summary of the POISED Working Group (WG),
starting from the events leading to the formation of the WG to the end
of 1992.  This memo provides information for the Internet community.  It
does not specify an Internet standard.


1395    Reynolds     Jan 93   BOOTP Vendor Information Extensions

This RFC is a slight revision and extension of RFC-1048 by Philip
Prindeville, who should be credited with the original work in this memo.
This memo will be updated as additional tags are defined.  This edition
introduces Tag 14 for Merit Dump File, Tag 15 for Domain Name, Tag 16
for Swap Server and Tag 17 for Root Path.  This memo is a status report
on the vendor information extensions used int the Bootstrap Protocol
(BOOTP).


1394    Robinson     Jan 93   Relationship of Telex Answerback Codes
                              to Internet Domains

This RFC gives the list, as best known, of all common Internet domains
and the conversion between specific country telex answerback codes and
Internet country domain identifiers.  It also lists the telex code and
international dialing code, wherever it is available.  It will also list
major Internet "Public" E-Mail addresses.  This memo provides
information for the Internet community.  It does not specify an Internet
standard.


1393    Malkin       Jan 93   Traceroute Using an IP Option

This document specifies a new IP option and ICMP message type which
duplicates the functionality of the existing traceroute method while
generating fewer packets and completing in a shorter time.  This memo
defines an Experimental Protocol for the Internet community.




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


1392    Malkin       Jan 93   Internet Users' Glossary

There are many networking glossaries in existence.  This glossary
concentrates on terms which are specific to the Internet.  This memo
provides information for the Internet community.  It does not specify an
Internet standard.


1391    Malkin       Jan 93   The Tao of IETF
                              A Guide for New Attendees of the
                              Internet Engineering Task Force

The purpose of this For Your Information (FYI) RFC is to explain to the
newcomers how the IETF works.  This will give them a warm, fuzzy feeling
and enable them to make the meeting more productive for everyone.  This
memo provides information for the Internet community.  It does not
specify an Internet standard.


1390    Katz         Jan 93   Transmission of IP and ARP over FDDI
                              Networks

This memo defines a method of encapsulating the Internet Protocol (IP)
datagrams and Address Resolution Protocol (ARP) requests and replies on
Fiber Distributed Data Interface (FDDI) Networks.  [STANDARDS-TRACK]


1389    Malkin       Jan 93   RIP Version 2 MIB Extension

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in TCP/IP-based internets.
[STANDARDS-TRACK]


1388    Malkin       Jan 93   RIP Version 2
                              Carrying Additional Information

This document specifies an extension of the Routing Information Protocol
(RIP), as defined in [1], to expand the amount of useful information
carried in RIP packets and to add a measure of security.  [STANDARDS-
TRACK]










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


1387    Malkin       Jan 93   RIP Version 2 Protocol Analysis

As required by Routing Protocol Criteria (RFC 1264), this report
documents the key features of the RIP-2 protocol and the current
implementation experience.  This memo provides information for the
Internet community.  It does not specify an Internet standard.


1386    Cooper       Dec 92   The US Domain

This is a description of the US Top Level Domains on the Internet.  This
memo provides information for the Internet community. It does not
specify an Internet standard.


1385    Wang         Nov 92   EIP: The Extended Internet Protocol
                              A Framework for Maintaining Backward
                              Compatibility

EIP can substantially reduce the amount of modifications needed to the
current Internet systems and greatly ease the difficulties of
transition. This is an "idea" paper and discussion is strongly
encouraged on [e-mail].  This memo provides
information for the Internet community. It does not specify an Internet
standard.


1384    Barker       Jan 93   Naming Guidelines for Directory Pilots

This document defines a number of naming guidelines.  Alignment to these
guidelines is recommended for directory pilots.  This memo provides
information for the Internet community. It does not specify an Internet
standard.


1383    Huitema      Dec 92   An Experiment in DNS Based IP Routing

Potential solutions to the routing explosion.  This memo defines an
Experimental Protocol for the Internet community.


1382    Throop       Nov 92   SNMP MIB Extension for the X.25 Packet
                              Layer

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in TCP/IP-based internets.
[STANDARDS-TRACK]




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


1381    Throop       Nov 92   SNMP MIB Extension for X.25 LAPB

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 Link Layer of X.25,
LAPB.  [STANDARDS-TRACK]


1380    Gross        Nov 92    IESG Deliberations on Routing and
                               Addressing

This memo summarizes issues surrounding the routing and addressing
scaling problems in the IP architecture, and it provides a brief
background of the ROAD group and related activities in the Internet
Engineering Task Force (IETF).  This memo provides information for the
Internet community.  It does not specify an Internet standard.


1379    Braden       Nov 92    Extending TCP for Transactions --
                               Concepts

This memo discusses extension of TCP to provide transaction-oriented
service, without altering its virtual-circuit operation.  This memo
provides information for the Internet community.  It does not specify an
Internet standard.


1378    Parker       Nov 92    The PPP AppleTalk Control Protocol
                               (ATCP)

This document defines the NCP for establishing and configuring the
AppleTalk Protocol [3] over PPP.  [STANDARDS-TRACK]


1377     Katz        Nov 92    The PPP OSI Network Layer Control
                               Protocol (OSINLCP)

This document defines the NCP for establishing and configuring OSI
Network Layer Protocols.  [STANDARDS-TRACK]












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


1376    Senum         Nov 92   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]


1375    Robinson      Oct 92   Suggestion for New Classes of IP
                               Addresses

This RFC suggests a change in the method of specifying the IP address to
add new classes of networks to be called F, G, H, and K, to reduce the
amount of wasted address space, and to increase the available IP address
number space, especially for smaller organizations or classes of
connectors that do not need or do not want a full Class C IP address.
This memo provides information for the Internet community.  It does not
specify an Internet standard.


1374    Renwick       Oct 92   IP and ARP on HIPPI

The ANSI X3T9.3 committee has drafted a proposal for the encapsulation
of IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI.  Another X3T9.3
draft describes the operation of HIPPI physical switches.  X3T9.3 chose
to leave HIPPI networking issues largely outside the scope of their
standards; this document discusses methods of using of ANSI standard
HIPPI hardware and protocols in the context of the Internet, including
the use of HIPPI switches as LANs and interoperation with other
networks.  This memo is intended to become an Internet Standard.
[STANDARDS-TRACK]


1373    Tignor        Oct 92   PORTABLE DUAs

This document comes in two parts. The first part is for regular people
who wish to set up their own DUAs (Directory User Interfaces) to access
the Directory.  The second part is for ISODE-maintainers wishing to
provide portable DUAs to users. This part gives instructions in a
similar but longer, step-by-step format.  This memo provides information
for the Internet community.  It does not specify an Internet standard.








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


1372    Hedrick       Oct 92   Telnet Remote Flow Control Option

This document specifies an extended version of the Telnet Remote Flow
Control Option, RFC 1080, with the addition of the RESTART-ANY and
RESTART-XON suboptions.  [STANDARDS-TRACK]


1371    Gross         Oct 92   Choosing a "Common IGP" for the IP
                               Internet
                               (The IESG's Recommendation to the IAB)

This memo presents motivation, rationale and other surrounding
background information leading to the IESG's recommendation to the IAB
for a single "common IGP" for the IP portions of the Internet.  This
memo provides information for the Internet community.  It does not
specify an Internet standard.


1370    I.A.B.        Oct 92   Applicability Statement for OSPF

This Applicability Statement places a requirement on vendors claiming
conformance to this standard, in order to assure that users will have
the option of deploying OSPF when they need a multivendor, interoperable
IGP in their environment.  [STANDARDS-TRACK]


1369    Kastenholz    Oct 92   Implementation Notes and Experience for
                               The Internet Ethernet MIB

This document reflects the currently known status of 11 different
implementations of the MIB by 7 different vendors on 7 different
Ethernet interface chips.  This memo provides information for the
Internet community.  It does not specify an Internet standard.


1368    McMaster      Oct 92   Definitions of Managed Objects for IEEE
                               802.3 Repeater Devices

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 IEEE 802.3 10 Mb/second
baseband repeaters, sometimes referred to as "hubs".  [STANDARDS-TRACK]









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


1367    Topolcic      Oct 92   Schedule for IP Address Space
                               Management Guidelines

This memo suggests a schedule for the implementation of the IP network
number allocation plan described in RFC 1366.  This memo provides
information for the Internet community.  It does not specify an Internet
standard.


1366    Gerich        Oct 92   Guidelines for Management of IP Address
                               Space

This document has been reviewed by the Federal Engineering Task Force
(FEPG) on behalf of the Federal Networking Council (FNC), the co-chairs