Path: utzoo!attcan!uunet!convex!killer!osu-cis!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!hc!ames!pasteur!ucbvax!MITRE.ARPA!mckee
From: mckee@MITRE.ARPA (H. Craig McKee)
Newsgroups: comp.protocols.tcp-ip
Subject: ISO Flow Control
Message-ID: <8811231614.AA25816@mitre.arpa>
Date: 23 Nov 88 16:13:58 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The MITRE Corp., Washington, D.C.
Lines: 14

In a recent paper for the ACM, "The Design Philosophy of the DARPA
Internet Protocols" David Clark notes that: "The original ARPANET 
host-to-host protocol provided flow control based on both bytes and
packets.  This seemed overly complex, and the designers of TCP felt
that only one form of regulation would be sufficient"
    He then describes the strengths and weaknesses of byte versus packet
flow control and acknowledgement.
    He concludes by observing, "In retrospect, the correct design
decision may have been that if TCP is to provide effective support of
a variety of services, both packets and bytes must be regulated, as was
done in the original ARPANET protocols."

What flow control/acknowledgement procedure did ISO adopt for
Transport and Connectionless Mode services?