Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!MCL.UNISYS.COM!perry
From: perry@MCL.UNISYS.COM (Dennis Perry)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  Charging and aborted transfers
Message-ID: <8804262206.AA13680@LANAI.MCL.UNISYS.COM>
Date: 26 Apr 88 22:06:44 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 16

Jeffrey, I think you have hit on and important question that is not
asked very offten, namely, how does policy affect the architecture?
Certainly, this was answered when packet switching was chosen over
circuit switching.  Now that we have a network, new policy questions
may force us to reexamine the architecture we use.  This of course
may have some interesting consequences for the DoD.  For example, suppose
we go to pay per packet and the architecture is changed to minimize
costs.  Now we find that we are in conflict with survivability or
security or robustness policy issues.  What does the DoD do?  does
it want to recover cost, or develop technology which will survive
in a stress environment.

Oh well, in this case it may not matter, because if we get involved
in a stressed situation, there may not be anyone around to use the
net anyway.:-)

dennis