rfc1099.txt

RFC 的详细文档！

replies used in HEMS.  This memo assumes knowledge of the HEMS system
described in RFC-1021, and of the ISO data encoding standard, ASN.1.


1022    Partridge       Oct 87     The High-Level Entity Management
                                   Protocol (HEMP)

This memo presents an application protocol for managing network entities
such as hosts, gateways, and front end machines.  This protocol is a
component of the High-level Entity Management System HEMS), described is
RFC-1021.  This memo also assumes a knowledge of the ISO data encoding
standard, ASN.1.


1021    Partridge       Oct 87     The High-Level Entity Management
                                   System (HEMS)

This memo provides a general overview of the High-level Entity
management system (HEMS).  This system is experimental, and is currently
being tested in portions of the Internet.






Reynolds                                                       [Page 17]

RFC 1099                  Summary of 1000-1099             December 1991


1020    Romano          Nov 87     Internet Numbers

This RFC is a list of the Assigned IP Network Numbers and EGP Autonomous
System Numbers.  This RFC obsoletes RFC-997.


1019    Arnon           Sep 87     Report of the Workshop on
                                   Environments for Computational
                                   Mathematics

This memo is a report on the discussion of the representation of
equations in a workshop at the ACM SIGGRAPH Conference held in Anaheim,
California on 30 July 1987.


1018    McKenzie        Aug 87     Some Comments on SQuID

This memo is a discussion of some of the ideas expressed in RFC-1016 on
Source Quench.  This memo introduces the distinction of the cause of
congestion in a gateway between the effects of "Funneling" and
Mismatch".  It is offered in the same spirit as RFC-1016; to stimulate
discussion.  The opinions offered are personal, not corporate, opinions.


1017    Leiner          Aug 87     Network Requirements for Scientific
                                   Research

This RFC identifies the requirements on communication networks for
supporting scientific research.  It proposes some specific areas for
near term work, as well as some long term goals.  This is an "idea"
paper and discussion is strongly encouraged.


1016    Prue            July 87    Something a Host Could Do with Source
                                   Quench:  The Source Quench Introduced
                                   Delay (SQuID)

The memo is intended to explore the issue of what a host could do with a
source quench.  The proposal is for each source host IP module to
introduce some delay between datagrams sent to the same destination
host.  This is a "crazy idea paper" and discussion is essential.


1015    Leiner          July 87    Implementation Plan for Interagency
                                   Research Internet

This RFC proposes an Interagency Research Internet as the natural
outgrowth of the current Internet.  This is an "idea paper" and



Reynolds                                                       [Page 18]

RFC 1099                  Summary of 1000-1099             December 1991


discussion is strongly encouraged.


1014    Sun             Jun 87     XDR: External Data Representation
                                   Standard

XDR is a standard for the description and encoding of data.  It is
useful for transferring data between different computer architectures.
XDR fits into ISO presentation layer, and is roughly analogous in
purpose to X.409, ISO Abstract Syntax Notation.  The major difference
between these two is that XDR uses implicit typing, while X.409 uses
explicit typing.  This RFC is distributed for information only, it does
not establish a Internet standard.


1013    Scheifler       Jun 87     X Window System Protocol,
                                   Version 11-Beta

This RFC is distributed to the Internet community for information only.
It does not establish an Internet standard.  The X window system has
been widely reviewed and tested.  The Internet community is encouraged
to experiment with it.


1012    Reynolds        Jun 87     Bibliography of Requests for
                                   Comments 1-999

This RFC is a reference guide for the Internet community which provides
a bibliographic summary of the Request for Comments numbers 1 through
999 issued between the years 1969-1987.


1011    Reynolds        May 87     Official Internet Protocols

This memo is an official status report on the protocols used in the
Internet community.  It identifies the documents specifying the official
protocols used in the Internet.  Comments indicate any revisions or
changes planned.


1010    Reynolds        May 87     Assigned Numbers

This memo is an official status report on the numbers used in protocols
in the Internet community.  It documents the currently assigned values
from several series of numbers including link, socket, port, and
protocol, used in network protocol implementations.





Reynolds                                                       [Page 19]

RFC 1099                  Summary of 1000-1099             December 1991


1009     Braden         Jun 87     Requirements for Internet Gateways

This RFC summarizes the requirements for gateways to be used between
networks supporting the Internet protocols.  This document is a formal
statement of the requirements to be met by gateways used in the Internet
system.  As such, it is an official specification for the Internet
community.


1008     McCoy          Jun 87     Implementation Guide for the ISO
                                   Transport Protocol

This RFC is being distributed to members of the Internet community in
order to solicit comments on the Implementors Guide.  While this
document may not be directly relevant to the research problems of the
Internet, it may be of some interest to a number of researchers and
implementors.


1007     McCoy          Jun 87     Military Supplement to the ISO
                                   Transport Protocol

This document supplements the Transport Service and Protocol of the
International Standards Organization (ISO), IS 8072 and IS 8073,
respectively, and their formal descriptions by providing conventions,
option selections and parameter values.  This RFC is being distributed
to members of the Internet community in order to solicit comments on the
Draft Military Supplement.  While this document may not be directly
relevant to the research problems of the Internet, it may be of some
interest to a number of researchers and implementors.


1006     Rose           May 87     ISO Transport Services on top of
                                   the TCP Version: 3

This memo specifies a standard for the Internet community.  Hosts on the
Internet that choose to implement ISO transport services on top of the
TCP are expected to adopt and implement this standard.  TCP port 102 is
reserved for hosts which implement this standard.  This memo specifies
version 3 of the protocol and supersedes RFC-983.  Changes between the
protocol is described in RFC-983 and this memo are minor, but
unfortunately incompatible.


1005     Khanna         May 87     The ARPANET AHIP-E Host Access
                                   Protocol (Enhanced AHIP)

This RFC is a proposed specification for the encoding of Class A IP



Reynolds                                                       [Page 20]

RFC 1099                  Summary of 1000-1099             December 1991


addresses for use on ARPANET-style networks such as the Milnet and
Arpanet, and for enhancements to the ARPANET AHIP Host Access Protocol
(AHIP; formerly known as 1822).  These enhancements increase the size of
the PSN field, allow ARPANET hosts to use logical names to address each
other, allow for the communication of type-of-service information from
the host to the PSN and enable the PSN to provide congestion feedback to
the host on a connection basis.


1004     Mills          Apr 87     A Distributed-Protocol
                                   Authentication Scheme

The purpose of this RFC is to focus discussion on authentication
problems in the Internet and possible methods of solution.  The proposed
solutions this document are not intended as standards for the Internet
at this time.  Rather, it is hoped that a general consensus will emerge
as to the appropriate solution to authentication problems, leading
eventually to the adoption of standards.  This document suggests
mediated access-control and authentication procedures suitable for those
cases when an association is to be set up between users belonging to
different trust environments.


1003     Katz           Mar 87     Issues in Defining an Equations
                                   Representation Standard

This memo is intended to identify and explore issues in defining a
standard for the exchange of mathematical equations.  No attempt is made
at a complete definition and more questions are asked than are answered.
Questions about the user interface are only addressed to the extent that
they affect interchange issues.


1002    NETBIOS         Mar 87     Protocol Standard for A NetBIOS
                                   Service on a TCP/UDP Transport:
                                   Detailed Specifications

This RFC defines a proposed standard protocol to support NetBIOS
services in a TCP/IP environment.  Both local network and internet
operation are supported.  Various node types are defined to accommodate
local and internet topologies and to allow operation with or without the
use of IP broadcast.  This RFC gives the detailed specifications of the
netBIOS-over-TCP packets, protocols, and defined constants and
variables.  A more general overview is found in a companion RFC,
"Protocol Standard For NetBIOS Service on TCP/UDP Transport: Concepts
and Methods".





Reynolds                                                       [Page 21]

RFC 1099                  Summary of 1000-1099             December 1991


1001    NETBIOS         Mar 87     Protocol Standard for A NetBIOS
                                   Service on a TCP/UDP Transport:
                                   Concepts and Methods

This RFC defines a proposed standard protocol to support NetBIOS
services in a TCP/IP environment.  Both local network and internet
operation are supported.  Various node types are defined to accommodate
local and internet topologies and to allow operation with or without the
use of IP broadcast.  This RFC describes the NetBIOS-over-TCP protocols
in a general manner, emphasizing the underlying ideas and techniques.
Detailed specifications are found in a companion RFC, "Protocol Standard
For a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications".


1000    Reynolds        Aug 87     The Request for Comments Reference
                                   Guide

This RFC Reference Guide is intended to provide a historical account by
categorizing and summarizing of the Request for Comments numbers 1
through 999 issued between the years 1969-1987.  These documents have
been crossed referenced to indicate which RFCs are current, obsolete, or
revised.


Security Considerations

   Security issues are not discussed in this memo.

Author's Address

   Joyce K. Reynolds
   University of Southern California
   Information Sciences Institute
   4676 Admiralty Way
   Marina del Rey, CA 90292

   Phone:  [phone]

   EMail:  [e-mail]












Reynolds                                                       [Page 22]