Movatterモバイル変換

Network Working Group                                         J. ElliottRequest for Comments: 1699                                           ISICategory: Informational                                     January 1997Request for Comments Summary                         RFC Numbers 1600-1699Status of This Memo   This RFC is a slightly annotated list of the 100 RFCs fromRFC 1600   through RFCs 1699.  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---     ------       ----      -----1699    Elliott    Jan 97   Requests For Comments SummaryThis memo.1698    Furniss    Oct 94   Octet Sequences for Upper-Layer OSI                              to Support Basic Communications                              ApplicationsThis document states particular octet sequences that comprise the OSIupper-layer protocols (Session, Presentation and ACSE) when used tosupport applications with "basic communications requirements".  Thismemo provides information for the Internet community.  This memo doesnot specify an Internet standard of any kind.Elliott                      Informational                      [Page 1]

RFC 1699                  Summary of 1600-1699              January 19971697    Brower     Aug 94   Relational Database Management System                              (RDBMS) Management Information Base                              (MIB) using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it describes managed objects used for managing relationaldatabase (RDBMS) implementations.  [STANDARDS-TRACK]1696    Barnes     Aug 94   Modem Management Information Base (MIB)                              using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it describes managed objects used for managing dial-upmodems and similar dial-up devices.  [STANDARDS-TRACK]1695    Ahmed      Aug 94   Definitions of Managed Objects                              for ATM Management Version 8.0                              using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it describes objects used for managing ATM-based interfaces,devices, networks and services.  [STANDARDS-TRACK]1694    Brown      Aug 94   Definitions of Managed Objects                              for SMDS Interfaces using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets.  Inparticular, it defines objects for managing objects for SMDS accessinterfaces.  [STANDARDS-TRACK]1693    Connolly   Nov 94   An Extension to TCP : Partial Order                              ServiceThis RFC introduces a new transport mechanism for TCP based upon partialordering.  The aim is to present the concepts of partial ordering andpromote discussions on its usefulness in network communications.  Thismemo defines an Experimental Protocol for the Internet community.Elliott                      Informational                      [Page 2]

RFC 1699                  Summary of 1600-1699              January 19971692    Cameron    Aug 94   Transport Multiplexing Protocol (TMux)This RFC documents the extended TACACS protocol use by the Cisco Systemsterminal servers.  This same protocol is used by the University ofMinnesota's distributed authentication system.  This memo providesinformation for the Internet community.  It does not specify an Internetstandard.1691    Turner     Aug 94   The Document Architecture for the                              Cornell Digital LibraryThis memo defines an architecture for the storage and retrieval of thedigital representations for books, journals, photographic images, etc.,which are collected in a large organized digital library.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1690    Huston     Aug 94   Introducing the Internet Engineering                              and Planning Group (IEPG)This memo introduces the IEPG to the Internet Community.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1689    Foster     Aug 94   A Status Report on Networked Information                              Retrieval: Tools and GroupsThe purpose of this report is to increase the awareness of NetworkedInformation Retrieval by bringing together in one place informationabout the various networked information retrieval tools, theirdevelopers, interested organisations, and other activities that relateto the production, dissemination, and support of NIR tools.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1688    Simpson    Aug 94   IPng Mobility ConsiderationsThis RFC specifies criteria related to mobility for consideration indesign and selection of the Next Generation of IP.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.Elliott                      Informational                      [Page 3]

RFC 1699                  Summary of 1600-1699              January 19971687    Fleischman Aug 94   A Large Corporate User's View of IPngThe goal of this paper is to examine the implications of IPng from thepoint of view of Fortune 100 corporations which have heavily invested inTCP/IP technology in order to achieve their (non-computer related)business goals.This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1686    Vecchi     Aug 94   IPng Requirements: A Cable Television                              Industry ViewpointThis paper provides comments on topics related to the IPng requirementsand selection criteria from a cable television industry viewpoint.  Thismemo provides information for the Internet community.  This memo doesnot specify an Internet standard of any kind.1685    Alvestrand Aug 94   Writing X.400 O/R NamesThere is a need for human beings who use X.400 systems to be able towrite down O/R names in a uniform way.  This memo is a discussion ofthis topic.  This memo provides information for the Internet Community.It does not specify an Internet Standard of any kind.1684    Jurg       Aug 94   Introduction to White Pages Services                              based on X.500The document provides an introduction to the international ITU-T(formerly CCITT) X.500 and ISO 9594 standard, which is particularlysuited for providing an integrated local and global electronic WhitePages Service.  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1683    Clark      Aug 94   Multiprotocol Interoperability In IPngIn this document, we identify several features that affect a protocol'sability to operate in a multiprotocol environment and propose theincorporation of these features into IPng.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.Elliott                      Informational                      [Page 4]

RFC 1699                  Summary of 1600-1699              January 19971682    Bound      Aug 94   IPng BSD Host Implementation AnalysisThis IPng white paper, IPng BSD Host Implementation Analysis, wassubmitted to the IPng Directorate to provide a BSD host point ofreference to assist with the engineering considerations during the IETFprocess to select an IPng proposal.  This memo provides information forthe Internet community.  This memo does not specify an Internet standardof any kind.1681    Bellovin   Aug 94   On Many Addresses per HostThis document was submitted to the IETF IPng area in response to RFC1550.This memo provides information for the Internet community.  Thismemo does not specify an Internet standard of any kind.1680    Bradziunas Aug 94   IPng Support for ATM ServicesThis white paper describes engineering considerations for IPng assolicited byRFC 1550 [1]. This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1679    Green      Aug 94   HPN Working Group Input to the IPng                              Requirements SolicitationThe purpose of this document is to provide what the HPN working groupperceives as requirements for an IPng protocol set.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1678    Britton    Aug 94   IPng Requirements of Large Corporate                              NetworksThis draft summarizes some of the requirements of large corporatenetworks for the next generation of the Internet protcol suite.  Thismemo provides information for the Internet community.  This memo doesnot specify an Internet standard of any kind.Elliott                      Informational                      [Page 5]

RFC 1699                  Summary of 1600-1699              January 19971677    Adamson    Aug 94   Tactical Radio Frequency Communication                              Requirments for IPngThis paper describes requirements for Internet Protocol next generation(IPng) candidates with respect to their application to military tacticalradio frequency (RF) communication networks.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1676    Ghiselli   Aug 94   INFN Requirements for an IPng With this paper we would like to emphasize the key points that we wouldto consider if charged with IPng plan.  This memo provides informationfor the Internet community.  This memo does not specify an Internetstandard of any kind.1675    Bellovin   Aug 94   Security Concerns for IPngA number of the candidates for IPng have some features that are somewhatworrisome from a security perspective.  While it is not necessary thatIPng be an improvement over IPv4, it is mandatory that it not makethings worse.  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1674    Taylor     Aug 94   A Cellular Industry View of IPngThis is a draft of the requirements for IPng as envisioned byrepresentatives of the Cellular Digital Packet Data (CDPD) consortium ofservice providers.  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1673    Skelton    Aug 94   Electric Power Research Institute                              Comments on IPngThis document was submitted to the IETF IPng area in response to RFC1550.  This memo provides information for the Internet community.Thismemo does not specify an Internet standard of any kind.Elliott                      Informational                      [Page 6]

RFC 1699                  Summary of 1600-1699              January 19971672    Brownless  Aug 94   Accounting Requirements for IPngThis white paper discusses accounting requirements for IPng. Itrecommends that all IPng packets carry accounting tags, which would varyin size.  This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1671    Carpenter  Aug 94   IPng White Paper on Transition and Other                              ConsiderationsThis white paper outlines some general requirements for IPng in selectedareas.  This memo provides information for the Internet community.  Thismemo does not specify an Internet standard of any kind.1670    Heagerty   Aug 94   Input to IPng Engineering ConsiderationsThis white paper expresses some personal opinions on IPng engineeringconsiderations, based on experience with DECnet Phase V transition.  Itsuggests breaking down the IPng decisions and transition tasks intosmaller parts so they can be tackled early by the relevant experts.This memo provides information for the Internet community.  This memodoes not specify an Internet standard of any kind.1669    Curran     Aug 94   Market Viability as a IPng Criteria"Viability in the Marketplace" is an important requirement for any IPngcandidate and this paper is an attempt to summarize some importantfactors in determing market viability of IPng proposals.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1668    Estrin     Aug 94   Unified Routing Requirements for IPngThe document provides requirements on the IPng from the perspective ofthe Unified Routing Architecture, as described inRFC 1322.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.Elliott                      Informational                      [Page 7]

RFC 1699                  Summary of 1600-1699              January 19971667    Symington  Aug 94   Modeling and Simulation Requirements for                              IPngThis white paper summarizes the Distributed Interactive Simulationenvironment that is under development, with regard to its real-timenature, scope and magnitude of networking requirements.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1666    KielczewskiAug 94   Definitions of Managed Objects                              for SNA NAUs using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it defines objects for managing the configuration,monitoring and control of Physical Units (PUs) and Logical Units (LUs)in an SNA environment.  [STANDARDS-TRACK]1665    KielczewskiJul 94   Definitions of Managed Objects                              for SNA NAUs using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it defines objects for managing the configuration,monitoring and control of Physical Units (PUs) and Logical Units (LUs)in an SNA environment.  [STANDARDS-TRACK]1664    Allocchio  Aug 94   Using the Internet DNS to DistributeRFC1327 Mail Address Mapping TablesThis memo defines how to store in the Internet Domain Name System themapping information needed by e-mail gateways and other tools to mapRFC822 domain names into X.400 O/R names and vice versa.  This memodefines an Experimental Protocol for the Internet community.1663    Rand       Jul 94   PPP Reliable TransmissionThis document defines a method for negotiating and using Numbered-Mode,as defined by ISO 7776 [2], to provide a reliable serial link.[STANDARDS-TRACK]Elliott                      Informational                      [Page 8]

RFC 1699                  Summary of 1600-1699              January 19971662    Simpson    Jul 94   PPP in HDLC-Like FramingThis document describes the use of HDLC-like framing for PPPencapsulated packets.  [STANDARDS-TRACK]1661    Simpson    Jul 94   The Ponit-to-Point Protocol (PPP)This document defines the PPP organization and methodology, and the PPPencapsulation, together with an extensible option negotiation mechanismwhich is able to negotiate a rich assortment of configuration parametersand provides additional management functions.  [STANDARDS-TRACK]1660    Stewart    Jul 94   Definitions of Managed Objects for                              Parallel-printer-like Hardware Devices                              using SMIv2This memo defines an extension to the Management Information Base (MIB)for use with network management protocols in the Internet community.  Inparticular, it defines objects for the management of Parallel-printer-like devices.  [STANDARDS-TRACK]1659    Stewart    Jul 94   Definitions of Managed Objects for                              RS-232-like Hardware Devices using SMIv2This memo defines an extension to the Management Information Base (MIB)for use with network management protocols in the Internet community.  Inparticular, it defines objects for the management of RS-232-likedevices. [STANDARDS-TRACK]1658    Stewart    Jul 94   Definitions of Managed Objects for                              Character Stream Devices using SMIv2This memo defines an extension to the Management Information Base (MIB)for use with network management protocols in the Internet community.  Inparticular, it defines objects for the management of character streamdevices.  [STANDARDS-TRACK]Elliott                      Informational                      [Page 9]

RFC 1699                  Summary of 1600-1699              January 19971657    Willis     Jul 94   Definitions of Managed Objects for the                              Fourth Version of the Border Gateway                              Protocol (BGP-4) using SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it describes managed objects used for managing the BorderGateway Protocol Version 4 or lower [1, 2].  [STANDARDS-TRACK]1656    Traina     Jul 94   BGP-4 Protocol Document Roadmap and                              Implementation ExperienceBorder Gateway Protocol v4 (BGP-4) [1] is an inter-Autonomous Systemrouting protocol.  It is built on experience gained with BGP as definedinRFC-1267 [2] and BGP usage in the connected Internet as described inRFC-1268 [3].  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1655    Rekhter    Jul 94   Application of the Border Gateway                              Protocol in the InternetThis document, together with its companion document, "A Border GatewayProtocol 4 (BGP-4)", define an inter-autonomous system routing protocolfor the Internet.  [STANDARDS-TRACK]1654    Rekhter    Jul 94   A Border Gateway Protocol 4 (BGP-4)This document defines an inter-autonomous system routing protocol forthe Internet.  [STANDARDS-TRACK]1653    Klensin    Jul 94   SMTP Service Extension for Message Size                              DeclarationThis memo defines an extension to the SMTP service whereby an SMTPclient and server may interact to give the server an opportunity todecline to accept a message (perhaps temporarily) based on the client'sestimate of the message size.  [STANDARDS-TRACK]Elliott                      Informational                     [Page 10]

RFC 1699                  Summary of 1600-1699              January 19971652    Klensin    Jul 94   SMTP Service Extension for                              8bit-MIMEtransportThis memo defines an extension to the SMTP service whereby an SMTPcontent body consisting of text containing octets outside of the US-ASCII octet range (hex 00-7F) may be relayed using SMTP.  [STANDARDS-TRACK]1651    Klensin    Jul 94   SMTP Service ExtensionsThis memo defines a framework for extending the SMTP service by defininga means whereby a server SMTP can inform a client SMTP as to the serviceextensions it supports.  [STANDARDS-TRACK]1650    Kastenholz Aug 94   Definitions of Managed Objects for the                              Ethernet-like Interface Types using                              SMIv2This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it defines objects for managing ethernet-like objects.[STANDARDS-TRACK]1649    Hagens     Jul 94   Operational Requirements for X.400                              Management Domains in the GO-MHS                              CommunityThe goal of this document is to unite regionally operated X.400 serviceson the various continents into one GO-MHS Community (as seen from anend-user's point of view).  This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1648    Cargille   Jul 94   Postmaster Convention for X.400                              OperationsThis paper extends this concept to X.400 mail domains which haveregisteredRFC 1327 mapping rules, and which therefore appear to havenormalRFC822-style addresses.  [STANDARDS-TRACK]Elliott                      Informational                     [Page 11]

RFC 1699                  Summary of 1600-1699              January 19971647    Kelly      Jul 94   TN3270 EnhancementsThis document describes a protocol that more fully supports 3270 devicesthan do the existing tn3270 practices.  [STANDARDS-TRACK]1646    Graves     Jul 94   TN3270 Extensions for LUname and                              Printer SelectionThis document describes protocol extensions to TN3270.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1645    Gwinn      Jul 94   Simple Network Paging Protocol -                              Version 2This RFC suggests a simple way for delivering both alphanumeric andnumeric pages (one-way) to radio paging terminals.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1644    Braden     Jul 94   T/TCP -- TCP Extensions for Transactions                              Functional SpecificationThis memo specifies T/TCP, an experimental TCP extension for efficienttransaction-oriented (request/response) service.  This memo describes anExperimental Protocol for the Internet community.1643    Kastenholz Jul 94   Definitions of Managed Objects for the                              Ethernet-like Interface TypesThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it defines objects for managing ethernet-like objects.[STANDARDS-TRACK]1642    Goldsmith  Jul 94   A Mail-Safe Transformation Format of                              UnicodeThis document describes a new transformation format of Unicode thatcontains only 7-bit ASCII characters and is intended to be readable byhumans in the limiting case that the document consists of charactersfrom the US-ASCII repertoire.  This memo defines an ExperimentalProtocol for the Internet community.Elliott                      Informational                     [Page 12]

RFC 1699                  Summary of 1600-1699              January 19971641    Goldsmith  Jul 94   Using Unicode with MIMEThis document specifies the usage of Unicode within MIME.  This memodefines an Experimental Protocol for the Internet community.1640    Crocker    Jun 94   The Process for Organization of Internet                              Standards Working Group (POISED)This report, originally prepared in January 1993 provides a summary ofthe POISED WG, starting from the events leading to the formation of theWG to the end of 1992.  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1639    Piscitello Jun 94   FTP Operation Over Big Address Records                              (FOOBAR)This RFC specifies a method for assigning addresses other than 32-bitIPv4 addresses to data ports through the specification of a "long Port(LPRT)" command and "Long Passive (LPSV)" reply, each having as itsargument a <long-host-port>, which allows for additional addressfamilies, variable length network addresses and variable length portnumbers.  This memo defines an Experimental Protocol for the Internetcommunity.1638    Baker      Jun 94   PPP Bridging Control Protocol (BCP)This document defines the Network Control Protocol for establishing andconfiguring Remote Bridging for PPP links.  [STANDARDS-TRACK]1637    Manning    Jun 94   DNS NSAP Resource RecordsThis document defines the format of one new Resource Record (RR) for theDNS for domain name-to-NSAP mapping.  This memo defines an ExperimentalProtocol for the Internet community.Elliott                      Informational                     [Page 13]

RFC 1699                  Summary of 1600-1699              January 19971636    Braden     Jun 94   Report of IAB Workshop on Security in                              the Internet ArchitectureThis document is a report on an Internet architecture workshop,initiated by the IAB and held at USC Information Sciences Institute onFebruary 8-10, 1994.  This workshop generally focused on security issuesin the Internet architecture.  This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1635    Deutsch    May 94   How to Use Anonymous FTPThis document provides information for the novice Internet user aboutusing the File Transfer Protocol (FTP).  It explains what FTP is, whatanonymous FTP is, and what an anonymous FTP archive site is.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1634    Allen      May 94   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 toexchange necessary router to router information prior to exchangingstandard IPX routing information and traffic over WAN datalinks.  Thismemo provides information for the Internet community.  This memo doesnot specify an Internet standard of any kind.1633    Braden     Jun 94   Integrated Services in the Internet                              Architecture: an OverviewThis memo discusses a proposed extension to the Internet architectureand protocols to provide integrated services, i.e., to support real-timeas well as the current non-real-time service of IP.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.Elliott                      Informational                     [Page 14]

RFC 1699                  Summary of 1600-1699              January 19971632    Getchell   May 94   A Revised Catalog of Available X.500                              ImplementationsThis document is the result of a survey that gathered new or updateddescriptions of currently available implementations of X.500, includingcommercial products and openly available offerings. This document is arevision ofRFC 1292.  This memo provides information for the Internetcommunity.  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, thatcomplements CIDR or even makes it unnecessary. The address reusesolution is to place Network Address Translators (NAT) at the borders ofstub domains.  This memo provides information for the Internetcommunity.  This memo does not specify an Internet standard of any kind.1630    Berners-LeeJun 94   Universal Resource Identifiers in WWWThis document defines the syntax used by the World-Wide Web initiativeto encode the names and addresses of objects on the Internet.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1629    Colella    May 94   Guidelines for OSI NSAP Allocation in                              the InternetThis paper provides guidelines for allocating NSAP addresses in theInternet.  The guidelines provided in this paper have been the basis forinitial deployment of CLNP in the Internet, and have proven veryvaluable both as an aid to scaling of CLNP routing, and for addressadministration.  [STANDARDS-TRACK]1628    Case       May 94   UPS Management Information BaseThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it defines objects for managing uninterruptible power supply(UPS) systems.  [STANDARDS-TRACK]Elliott                      Informational                     [Page 15]

RFC 1699                  Summary of 1600-1699              January 19971627    Lear       Jul 94   Network 10 Considered Harmful                              (Some Practices Shouldn't be Codified)This document restates the arguments for maintaining a unique addressspace.  Concerns for Internet architecture and operations, as well asIETF procedure, are explored.  This memo provides information for theInternet community.  This memo does not specify an Internet standard ofany kind.1626    Atkinson   May 94   Default IP MTU for use over ATM AAL5There are a number of good reasons to have a reasonably large defaultMTU value for IP over ATM AAL5.  This paper presents the default IP MIUfor use over ATM AAL5.  [STANDARDS-TRACK]1625    St. Pierre Jun 94   WAIS over Z39.50-1988The purpose of this memo is to initiate a discussion for a migrationpath of the WAIS technology from Z39.50-1988 Information RetrievalService Definitions and Protocol Specification for Library Applications[1] to Z39.50-1992 [2] and then to Z39.50-1994 [3].  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1624    RijsinghaniMay 94   Computation of the Internet Checksum                              via Incremental UpdateThis memo describes an updated technique for incremental computation ofthe standard Internet checksum.  It updates the method described in RFC1141.  This memo provides information for the Internet community.Thismemo does not specify an Internet standard of any kind.1623    Kastenholz May 94   Definitions of Managed Objects for the                              Ethernet-like Interface TypesThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it defines objects for managing ethernet-like objects.[STANDARDS-TRACK]Elliott                      Informational                     [Page 16]

RFC 1699                  Summary of 1600-1699              January 19971622    Francis    May 94   Pip Header ProcessingThe purpose of this RFC and the companion RFC "Pip Near-termArchitecture" are to record the ideas (good and bad) of Pip.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1621    Francis    May 94   Pip Near-term ArchitectureThe purpose of this RFC and the companion RFC "Pip Header Processing"are to record the ideas (good and bad) of Pip.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1620    Braden     May 94   Internet Architecture Extensions for                              Shared MediaThis memo discusses alternative approaches to extending the Internetarchitecture to eliminate some or all unnecessary hops.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1619    Simpson    May 94   PPP over SONET/SDHThis 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 ISDNThis document describes the use of PPP over Integrated Services DigitalNetwork (ISDN) switched circuits.  [STANDARDS-TRACK]1617    Barker     May 94   Naming and Structuring Guidelines for                              X.500 Directory PilotsThis document defines a number of naming and structuring guidelinesfocused on White Pages usage. Alignment to these guidelines isrecommended for directory pilots.  This memo provides information forthe Internet community.  This memo does not specify an Internet standardof any kind.Elliott                      Informational                     [Page 17]

RFC 1699                  Summary of 1600-1699              January 19971616    RARE WG-MSGMay 94   A report by the RARE Task Force on                              X.400(1988) of the RARE Working Group on                              Mail & MessagingThe report documents the results of a task force on X.400(1988)deployment of the RARE Mails and Messaging Work Group during the periodfrom November 1992 until October 1993.  This memo provides informationfor the Internet community.  This memo does not specify an Internetstandard 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 whatproblems can be anticipated in the migration, especially considering themigration from the existing X.400(84) infrastructure created by theCOSINE MHS project to an X.400(88) infrastructure.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1614    Adie       May 94   Network Access to Multimedia InformationThis report summarises the requirements of research and academic networkusers for network access to multimedia information.  This memo providesinformation for the Internet community.  This memo does not specify anInternet 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 internetsby encapsulating the X.25 Packet Level in TCP packets.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.1612    Austein    May 94   DNS Resolver MIB ExtensionsThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it describes a set of extensions which instrument DNSresolver functions.  This memo was produced by the DNS working group.[STANDARDS-TRACK]Elliott                      Informational                     [Page 18]

RFC 1699                  Summary of 1600-1699              January 19971611    Austein    May 94   DNS Server MIB ExtensionsThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.  Inparticular, it describes a set of extensions which instrument DNS nameserver functions.  This memo was produced by the DNS working group.[STANDARDS-TRACK]1610    I.A.B      Jul 94   INTERNET OFFICIAL PROTOCOL STANDARDSThis memo describes the state of standardization of protocols used inthe Internet as determined by the Internet Architecture Board (IAB).[STANDARDS-TRACK]1609    Mansfield  Mar 94   Charting Networks in the X.500 DirectoryThis document presents a model in which a communication network with allits related details and descriptions can be represented in the X.500Directory.  This memo defines an Experimental Protocol for the Internetcommunity.1608    Johannsen  Mar 94   Representing IP Information in the X.500                              DirectoryThis document describes the objects necessary to include informationabout IP networks and IP numbers in the X.500 Directory. It extends thework "Charting networks in the X.500 Directory" [1] where a generalframework is presented for representing networks in the Directory byapplying it to IP networks.  This memo defines an Experimental Protocolfor the Internet community.1607    Cerf       Apr 94   A VIEW FROM THE 21ST CENTURYThis document is a composition of letters discussing a possible future.This memo provides information for the Internet community.  This memodoes not specify an Internet standard of any kind.Elliott                      Informational                     [Page 19]

RFC 1699                  Summary of 1600-1699              January 19971606    Onion      Apr 94   A Historical Perspective On The Usage Of                              IP Version 9This paper reviews the usages of the old IP version protocol. Itconsiders some of its successes and its failures.  This memo providesinformation for the Internet community.  This memo does not specify anInternet standard of any kind.1605    ShakespeareApr 94   SONET to Sonnet TranslationBecause Synchronous Optical Network (SONET) transmits data in frames ofbytes, it is fairly easy to envision ways to compress SONET frames toyield higher bandwidth over a given fiber optic link.  This memodescribes 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 ServiceThis memo defines an extension to the Management Information Base (MIB)for use with network management protocols in TCP/IP-based internets.  Inparticular, it defines objects for managing the Frame Relay Service.[STANDARDS-TRACK]1603    Huizer     Mar 94   IETF Working Group                              Guidelines and ProceduresThis document describes the guidelines and procedures for formation andoperation of IETF working groups. It describes the formal relationshipbetween 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 2This document is a revision ofRFC 1310, which defined the officialprocedures for creating and documenting Internet Standards.  This memoprovides information for the Internet community.  This memo does notspecify an Internet standard of any kind.Elliott                      Informational                     [Page 20]

RFC 1699                  Summary of 1600-1699              January 19971601    Huitema    Mar 94   Charter of the Internet Architecture                              Board (IAB)This memo documents the composition, selection, roles, and organizationof the Internet Architecture Board and its subsidiary organizations.This memo provides information for the Internet community.  This memodoes not specify an Internet standard of any kind.1600    I.A.B.     Mar 94   INTERNET OFFICIAL PROTOCOL STANDARDSThis memo describes the state of standardization of protocols used inthe 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:  (310) 822-1511   EMail: elliott@isi.eduElliott                      Informational                     [Page 21]