Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id SAA15246; Mon, 5 Jun 1995 18:35:51 -0400
X-Resent-To: drums@CS.UTK.EDU ; Mon, 5 Jun 1995 18:35:50 EDT
Errors-to: owner-drums@CS.UTK.EDU
Received: from SEARN.SUNET.SE by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id SAA15236; Mon, 5 Jun 1995 18:35:45 -0400
Message-Id: <199506052235.SAA15236@CS.UTK.EDU>
Received: from SEARN.SUNET.SE by SEARN.SUNET.SE (IBM VM SMTP V2R2)
   with BSMTP id 4028; Tue, 06 Jun 95 00:31:35 +0200
Received: from SEARN.SUNET.SE (NJE origin ERIC@SEARN) by SEARN.SUNET.SE (LMail V1.2a/1.8a) with RFC822 id 1899; Tue, 6 Jun 1995 00:31:34 +0200
Date:        Tue, 6 Jun 1995 00:29:09 +0200
From: Eric Thomas <ERIC@SEARN.SUNET.SE>
Subject:     Re: address syntax
To: John Gardiner Myers <jgm+@CMU.EDU>, Robert Elz <kre@munnari.oz.au>
cc: drums@CS.UTK.EDU
In-Reply-To: Message of Tue, 06 Jun 1995 07:50:21 +1000 from Robert Elz
             <kre@munnari.oz.au>

On Tue, 06 Jun 1995 07:50:21 +1000 Robert Elz <kre@munnari.oz.au> said:

>It seems that  822 allows ':' inside domain literals  (in fact, it seems
>to allow almost anything), which  was probably a very intelligent choice
>- meaning  that 822  isn't in  any way  tied to  any particular  form of
>transport addresses.

If you want my opinion, it was an oversight. Like:

                       joe@abc.[192.36.125.6].def

That's allowed,  too, but if you  ask me, it's because  whoever wrote the
specs didn't realize this was what he  was writing, as opposed to what he
was meaning. I'd be interested to know what the semantics are.

  Eric