Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!mit-eddie!genrad!decvax!decwrl!ucbvax!A.ISI.EDU!CERF From: CERF@A.ISI.EDU.UUCP Newsgroups: mod.protocols.tcp-ip Subject: Re: Access control and accountability Message-ID: <[A.ISI.EDU].7-Apr-87.08:58:49.CERF> Date: Tue, 7-Apr-87 07:58:00 EST Article-I.D.: <[A.ISI.EDU].7-Apr-87.08:58:49.CERF> Posted: Tue Apr 7 07:58:00 1987 Date-Received: Fri, 10-Apr-87 04:01:33 EST References: Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 17 Approved: tcp-ip@sri-nic.arpa Hank, Little has been developed for access control and accounting. Some gateways (e.g. BBN?) can filter IP packets based on source/destination address. I don't know of any which filter with knowledge of the protocol being used. I do not know of any gateways that provide accounting data, although such information as packet counts from a given host can be obtained from, e.g. the ARPANET. I would not be surprised to hear that some gateways and even some bridges keep some statistics about traffic loads, but probably not by source or destination. Thus far, the TCP/IP software has gone into private or gov't-owned systems which have not demanded much inthe way of accounting (or of access control). Vint