Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ucla-cs!zen!ucbvax!GUNTER-ADAM.ARPA!AFDDN.TCP-IP
From: AFDDN.TCP-IP@GUNTER-ADAM.ARPA.UUCP
Newsgroups: comp.protocols.tcp-ip
Subject: Can of worms revisited
Message-ID: <8709240855.AA11291@ucbvax.Berkeley.EDU>
Date: Wed, 23-Sep-87 11:55:51 EDT
Article-I.D.: ucbvax.8709240855.AA11291
Posted: Wed Sep 23 11:55:51 1987
Date-Received: Sat, 26-Sep-87 10:17:33 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 20

To anyone who might know, especially Andy or Sharon,

  I've been trying to get someone(mostly DCA) to specify to me exactly
what a "packet" is in terms of the billing algorithm.  Since the
billing algorithm is based on the traffic stats gathered by the PSN's,
I'm really asking what are the packets reflected on the throughput
reports.  I make the differentiation between X.25 packets which can be
anywhere from 128 to 1024 bytes, and the subnet "packets" passed between
E-to-E in the PSNs.  If memory serves me, the EE's break "messages"
into 128 byte subnet "packets" for sending thru the backbone.  X.25 packets,
(basic that is) are viewed as messages, therefore a 1024 byte X.25 packet
is 8 subnet "packets".  With standard X.25, your message is a complete
packet sequence and is actually now the length of you IP datagrams.  But
the the datagram is still broken into 128 byte "packets" by EE.
  If all this is true then a you could calculate the minimum number of
"packets" to send x number of bytes thru the network.  Not really that easy,
but a place to start.
Darrel Beach
AF DDN PMO
-------