Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!umd5!purdue!decwrl!ucbvax!SRI-NIC.ARPA!STJOHNS
From: STJOHNS@SRI-NIC.ARPA
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Packet accounting and a place to do it
Message-ID: <[SRI-NIC.ARPA]Fri,.22.Apr.88.07:57:38.PDT.STJOHNS>
Date: 22 Apr 88 14:57:00 GMT
References: <2466@utah-gr.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 24


	
    Date: 21 Apr 88 17:14:25 GMT
    From: haas@gr.utah.edu  (Walt Haas)
    To: tcp-ip@sri-nic.arpa
    Subject: Re: Packet accounting and a place to do it
    
    It seems to me that the most sensible way to do packet accounting is
    the way that the public networks (Telenet, Tymnet) do it - that is,
    all packets on a virtual circuit are charged to whoever established
    that VC unless the call was placed and accepted as "collect", in which
    case the recipient pays for it.  ....
    
    Cheers  -- Walt Haas    haas@cs.utah.edu    utah-cs!haas
    
	      --------------------
		
One small problem with this approach - during the life of a TCP
connection, many X.25 connections may come and go.  The X.25
connections may be closed down due to idleness or resource
reallocation, and may be reopened from either end of the pipe.  Also,
an X.25 connection may carry data from more than one TCP session.  And
it may also have UDP traffic mixed in.  Who gets the bill?

Mike