Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id OAA22648; Wed, 24 Jan 1996 14:33:42 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.3); Wed, 24 Jan 1996 14:32:51 -0500 Received: from mulga.cs.mu.OZ.AU by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id OAA22503; Wed, 24 Jan 1996 14:32:48 -0500 Received: from muri.cs.mu.OZ.AU by mulga.cs.mu.OZ.AU with SMTP (5.83--+1.3.1+0.50); id AA11318 Thu, 25 Jan 1996 06:32:37 +1100 (from kre@munnari.OZ.AU) To: "Eric Norman (MACC)" Cc: drums@cs.utk.edu Subject: Re: A suggestion for IPv6 domain literals In-Reply-To: Your message of "Tue, 23 Jan 1996 23:01:00 CDT." <26012323015652@vms3.macc.wisc.edu> Date: Thu, 25 Jan 1996 06:32:53 +1100 Message-Id: <8200.822511973@munnari.OZ.AU> From: Robert Elz Date: Tue, 23 Jan 96 23:01 CDT From: "Eric Norman (MACC)" Message-ID: <26012323015652@vms3.macc.wisc.edu> I think domain literals should be eliminated. There are other things that should go also. Two that I can think of offhand are the Encrypted: header and the group:; construct. I suspect about as much has been said about this as needs to be said - we need domain literals, and group:; is useful. On Encrypted - I suspect it is useless, but what can we really do about it? I suspect that the most that can be done is a "don't send this header" warning, which would be fine, but of little benefit - after all, the reason it would be deprecated would be because no-one sends it, right? Receivers would still need to be able to handle it, just in case there is someone out there who is using it. Looks like no nett gain. kre