Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!decwrl!ucbvax!tcp-ip
From: JNC@MIT-XX.ARPA ("J. Noel Chiappa")
Newsgroups: mod.protocols.tcp-ip
Subject: Re: Network Security
Message-ID: <12164728567.28.JNC@MIT-XX.ARPA>
Date: Thu, 5-Dec-85 13:09:48 EST
Article-I.D.: MIT-XX.12164728567.28.JNC
Posted: Thu Dec  5 13:09:48 1985
Date-Received: Sat, 7-Dec-85 01:42:46 EST
References: <8512051344.AA03870@mitre-bedford.ARPA>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 17
Approved: tcp-ip@sri-nic.arpa


	Various potential users of C Gateways have requested similar
capabilities, and we had set up a mailing list to discuss exactly what
mechanisms would be useful. However, due to lack of time on my part
nothing has happened there yet. I would caution that the TCP-IP mailing
list is a little big to conduct a discussion on; unfortunately I
don't know of a good substitute.
	I would suggest that you contact your gateway vendor and see
if he has any plans, or is setting up a customer discussion group. If
you built your own gateway, then you're out in the cold; as far as I
know, nobody has built any fancy access control mechanisms into
any gateways yet. I'm not sure I see any necessity for standardization
here; creating standards takes energy, of which there is a limited
amount, and there are more important things needing to be standardized.

	Noel
-------