RFC1859 on ISO Transport and Flow Control

"Joyce K. Reynolds" <jkrey@isi.edu> Thu, 19 October 1995 21:57 UTC

Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa20510; 19 Oct 95 17:57 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa20228; 19 Oct 95 17:57 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20488; 19 Oct 95 17:57 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa20440; 19 Oct 95 17:54 EDT
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa20140; 19 Oct 95 17:54 EDT
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-17) id <AA26816>; Thu, 19 Oct 1995 14:54:26 -0700
Message-Id: <199510192154.AA26816@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1859 on ISO Transport and Flow Control
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 19 Oct 1995 14:56:31 -0700
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

A new Request for Comments is now available in online RFC libraries.


        RFC 1859:

        Title:      ISO Transport Class 2 Non-use of Explicit Flow
                    Control over TCP RFC1006 extension
        Author:     Y. Pouffary
        Date:       October 1995
        Mailbox:    pouffary@taec.enet.dec.com
        Pages:      8
        Characters: 14,572
        Updates/Obsoletes:  none

        URL:        ftp://ds.internic.net/rfc/rfc1859.txt


This document is an extension to STD35, RFC1006, a standard for the
Internet community. The document does not duplicate the protocol
definitions contained in RFC1006 and in International Standard ISO
8073.  It supplements that information with the description of how to
implement ISO Transport Class 2 Non-use of Explicit Flow Control on
top of TCP.  The document should be used in conjunction with the
RFC1006 and ISO 8073.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  Distribution of
this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ds.internic.net/rfc/rfc1859.txt"><ftp://ds.internic.net/rfc/rfc1859.txt>