Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id MAA17087; Fri, 8 Dec 1995 12:03:16 -0500
Received: by cs.cs.utk.edu (bulk_mailer v1.3); Fri, 8 Dec 1995 12:01:55 -0500
Received: from jekyll.piermont.com by CS.UTK.EDU with ESMTP (cf v2.9s-UTK)
	id MAA17009; Fri, 8 Dec 1995 12:01:46 -0500
Received: from localhost (perry@localhost) by jekyll.piermont.com (8.6.12/8.6.12) with SMTP id MAA17787; Fri, 8 Dec 1995 12:01:19 -0500
Message-Id: <199512081701.MAA17787@jekyll.piermont.com>
X-Authentication-Warning: jekyll.piermont.com: Host localhost didn't use HELO protocol
To: "Roger Fajman" <RAF@cu.nih.gov>
cc: drums@cs.utk.edu
Subject: Re: IPv6 address representation 
In-reply-to: Your message of "Fri, 08 Dec 1995 03:10:37 EST."
             <199512080810.DAA28823@linet02.li.net> 
Reply-To: perry@piermont.com
X-Reposting-Policy: redistribute only with permission
Date: Fri, 08 Dec 1995 12:01:18 -0500
From: "Perry E. Metzger" <perry@piermont.com>


"Roger Fajman" writes:
> > Just checking, but is there any agreement on how IPv6 address literals
> > are to be represented in email addresses?
> 
> No.  The colons are considered to be a serious problem.
> Any suggestions?

We *have* to solve this, and soon.

My suggestion is to send mail to a "[...]x.x.x.x.ip6.int" address and
have the mailers simply know to send any .ip6.int thing straight at
the other address. Note that this is *ugly*, since the ip6.int
addresses break a nybbles, and there are 32 nybbles in a 128 bit
address, meaning a ip6.int address is 71 characters long past the @.

Perry