Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id AAA04325; Wed, 24 Jan 1996 00:16:59 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.3); Wed, 24 Jan 1996 00:16:36 -0500 Received: from Tomobiki-Cho.CAC.Washington.EDU by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id AAA04240; Wed, 24 Jan 1996 00:16:34 -0500 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67f2/UW-NDC Revision: 2.27.MRC ) id AA00520; Tue, 23 Jan 96 21:16:11 -0800 Date: Tue, 23 Jan 1996 21:09:15 -0800 (PST) From: Mark Crispin Sender: Mark Crispin Subject: Re: A suggestion for IPv6 domain literals To: "Eric Norman (MACC)" Cc: Harald.T.Alvestrand@uninett.no, drums@cs.utk.edu In-Reply-To: <26012323015652@vms3.macc.wisc.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 23 Jan 96 23:01 CDT, Eric Norman (MACC) wrote: > I think domain literals should be eliminated. They've been > deprecated ever since day one; it's time to just say bye-bye to 'em. I object to this. Domain literals are invaluable when the DNS is broken, or for logging purposes. It may be alright to unify the IN-ADDR.ARPA and domain literals syntax, but the function itself is necessary. > There are other things that should go also. Two that I can > think of offhand are the Encrypted: header and the group:; > construct. I object *very* strongly to any move to deprecate group syntax. We use it. The Encrypted: header sure does seem to be useless. But, I recently came up with a possible use for it; as a *fast* way to determine whether a message has encrypted contents without looking deeper into the message's MIME structure.