rfc1699.txt

中、英文RFC文档大全打包下载完全版 .

1632    Getchell     May 94   A Revised Catalog of Available X.500
                              Implementations

This document is the result of a survey that gathered new or updated
descriptions of currently available implementations of X.500, including
commercial products and openly available offerings. This document is a
revision of RFC 1292.  This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.


1631    Egevang      May 94   The IP Network Address Translator (NAT)

This memo proposes another short-term solution, address reuse, that
complements CIDR or even makes it unnecessary. The address reuse
solution is to place Network Address Translators (NAT) at the borders of
stub domains.  This memo provides information for the Internet
community.  This memo does not specify an Internet standard of any kind.


1630    Berners-Lee  Jun 94   Universal Resource Identifiers in WWW

This document defines the syntax used by the World-Wide Web initiative
to encode the names and addresses of objects on the Internet.  This memo
provides information for the Internet community.  This memo does not
specify an Internet standard of any kind.


1629    Colella      May 94   Guidelines for OSI NSAP Allocation in
                              the Internet

This paper provides guidelines for allocating NSAP addresses in the
Internet.  The guidelines provided in this paper have been the basis for
initial deployment of CLNP in the Internet, and have proven very
valuable both as an aid to scaling of CLNP routing, and for address
administration.  [STANDARDS-TRACK]


1628    Case         May 94   UPS Management Information Base

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it defines objects for managing uninterruptible power supply
(UPS) systems.  [STANDARDS-TRACK]








Elliott                      Informational                     [Page 15]

RFC 1699                  Summary of 1600-1699              January 1997


1627    Lear         Jul 94   Network 10 Considered Harmful
                              (Some Practices Shouldn't be Codified)

This document restates the arguments for maintaining a unique address
space.  Concerns for Internet architecture and operations, as well as
IETF procedure, are explored.  This memo provides information for the
Internet community.  This memo does not specify an Internet standard of
any kind.


1626    Atkinson     May 94   Default IP MTU for use over ATM AAL5

There are a number of good reasons to have a reasonably large default
MTU value for IP over ATM AAL5.  This paper presents the default IP MIU
for use over ATM AAL5.  [STANDARDS-TRACK]


1625    St. Pierre   Jun 94   WAIS over Z39.50-1988

The purpose of this memo is to initiate a discussion for a migration
path of the WAIS technology from Z39.50-1988 Information Retrieval
Service Definitions and Protocol Specification for Library Applications
[1] to Z39.50-1992 [2] and then to Z39.50-1994 [3].  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


1624    Rijsinghani  May 94   Computation of the Internet Checksum
                              via Incremental Update

This memo describes an updated technique for incremental computation of
the standard Internet checksum.  It updates the method described in RFC
1141.  This memo provides information for the Internet community.  This
memo does not specify an Internet standard of any kind.


1623    Kastenholz   May 94   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 the Internet community.  In
particular, it defines objects for managing ethernet-like objects.
[STANDARDS-TRACK]








Elliott                      Informational                     [Page 16]

RFC 1699                  Summary of 1600-1699              January 1997


1622    Francis      May 94   Pip Header Processing

The purpose of this RFC and the companion RFC "Pip Near-term
Architecture" are to record the ideas (good and bad) of Pip.  This memo
provides information for the Internet community.  This memo does not
specify an Internet standard of any kind.


1621    Francis      May 94   Pip Near-term Architecture

The purpose of this RFC and the companion RFC "Pip Header Processing"
are to record the ideas (good and bad) of Pip.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


1620    Braden       May 94   Internet Architecture Extensions for
                              Shared Media

This memo discusses alternative approaches to extending the Internet
architecture to eliminate some or all unnecessary hops.  This memo
provides information for the Internet community.  This memo does not
specify an Internet standard of any kind.


1619    Simpson      May 94   PPP over SONET/SDH

This document describes the use of PPP over Synchronous Optical Network
(SONET) and Synchronous Digital Heirarchy (SDH) circuits.  [STANDARDS-
TRACK]


1618    Simpson      May 94   PPP over ISDN

This document describes the use of PPP over Integrated Services Digital
Network (ISDN) switched circuits.  [STANDARDS-TRACK]


1617    Barker       May 94   Naming and Structuring Guidelines for
                              X.500 Directory Pilots

This document defines a number of naming and structuring guidelines
focused on White Pages usage. Alignment to these guidelines is
recommended for directory pilots.  This memo provides information for
the Internet community.  This memo does not specify an Internet standard
of any kind.





Elliott                      Informational                     [Page 17]

RFC 1699                  Summary of 1600-1699              January 1997


1616    RARE WG-MSG  May 94   A report by the RARE Task Force on
                              X.400(1988) of the RARE Working Group on
                              Mail & Messaging

The report documents the results of a task force on X.400(1988)
deployment of the RARE Mails and Messaging Work Group during the period
from November 1992 until October 1993.  This memo provides information
for the Internet community.  This memo does not specify an Internet
standard of any kind.


1615    Houttuin     May 94   Migrating from X.400(84) to X.400(88)

This document compares X.400(88) to X.400(84) and describes what
problems can be anticipated in the migration, especially considering the
migration from the existing X.400(84) infrastructure created by the
COSINE MHS project to an X.400(88) infrastructure.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


1614    Adie         May 94   Network Access to Multimedia Information

This report summarises the requirements of research and academic network
users for network access to multimedia information.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


1613    Foster       May 94   cisco Systems X.25 over TCP (XOT)

This memo documents a method of sending X.25 packets over IP internets
by encapsulating the X.25 Packet Level in TCP packets.  This memo
provides information for the Internet community.  This memo does not
specify an Internet standard of any kind.


1612    Austein      May 94   DNS Resolver MIB Extensions

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 a set of extensions which instrument DNS
resolver functions.  This memo was produced by the DNS working group.
[STANDARDS-TRACK]







Elliott                      Informational                     [Page 18]

RFC 1699                  Summary of 1600-1699              January 1997


1611    Austein      May 94   DNS Server MIB Extensions

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 a set of extensions which instrument DNS name
server functions.  This memo was produced by the DNS working group.
[STANDARDS-TRACK]


1610    I.A.B        Jul 94   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]


1609    Mansfield    Mar 94   Charting Networks in the X.500 Directory

This document presents a model in which a communication network with all
its related details and descriptions can be represented in the X.500
Directory.  This memo defines an Experimental Protocol for the Internet
community.


1608    Johannsen    Mar 94   Representing IP Information in the X.500
                              Directory

This document describes the objects necessary to include information
about IP networks and IP numbers in the X.500 Directory. It extends the
work "Charting networks in the X.500 Directory" [1] where a general
framework is presented for representing networks in the Directory by
applying it to IP networks.  This memo defines an Experimental Protocol
for the Internet community.


1607    Cerf         Apr 94   A VIEW FROM THE 21ST CENTURY

This document is a composition of letters discussing a possible future.
This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.











Elliott                      Informational                     [Page 19]

RFC 1699                  Summary of 1600-1699              January 1997


1606    Onion        Apr 94   A Historical Perspective On The Usage Of
                              IP Version 9

This paper reviews the usages of the old IP version protocol. It
considers some of its successes and its failures.  This memo provides
information for the Internet community.  This memo does not specify an
Internet standard of any kind.


1605    Shakespeare  Apr 94   SONET to Sonnet Translation

Because Synchronous Optical Network (SONET) transmits data in frames of
bytes, it is fairly easy to envision ways to compress SONET frames to
yield higher bandwidth over a given fiber optic link.  This memo
describes a particular method, SONET Over Novel English Translation
(SONNET).  This memo provides information for the Internet community.
This memo does not specify an Internet standard of any kind.


1604    Brown        Mar 94   Definitions of Managed Objects
                              for Frame Relay Service

This memo defines an extension to the Management Information Base (MIB)
for use with network management protocols in TCP/IP-based internets.  In
particular, it defines objects for managing the Frame Relay Service.
[STANDARDS-TRACK]


1603    Huizer       Mar 94   IETF Working Group
                              Guidelines and Procedures

This document describes the guidelines and procedures for formation and
operation of IETF working groups. It describes the formal relationship
between IETF participants WG and the Internet Engineering Steering Group
(IESG).  This memo provides information for the Internet community.
This memo does not specify an Internet standard of any kind.


1602    I.A.B.       Mar 94   The Internet Standards Process --
                              Revision 2

This document is a revision of RFC 1310, which defined the official
procedures for creating and documenting Internet Standards.  This memo
provides information for the Internet community.  This memo does not
specify an Internet standard of any kind.






Elliott                      Informational                     [Page 20]

RFC 1699                  Summary of 1600-1699              January 1997


1601    Huitema      Mar 94   Charter of the Internet Architecture
                              Board (IAB)

This memo documents the composition, selection, roles, and organization
of the Internet Architecture Board and its subsidiary organizations.
This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.


1600    I.A.B.       Mar 94   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]

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 21]