Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id TAA10675; Mon, 29 May 1995 19:28:43 -0400 X-Resent-To: drums@CS.UTK.EDU ; Mon, 29 May 1995 19:28:41 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from wilma.cs.utk.edu by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id TAA10669; Mon, 29 May 1995 19:28:39 -0400 Received: from LOCALHOST by wilma.cs.utk.edu with SMTP (cf v2.11c-UTK) id TAA05275; Mon, 29 May 1995 19:28:37 -0400 Message-Id: <199505292328.TAA05275@wilma.cs.utk.edu> X-URI: http://www.cs.utk.edu/~moore/ From: Keith Moore To: perry@imsi.com cc: drums@CS.UTK.EDU, moore@CS.UTK.EDU Subject: Re: getting started In-reply-to: Your message of "Mon, 29 May 1995 18:36:58 EDT." <9505292236.AA13801@snark.imsi.com> Date: Mon, 29 May 1995 19:28:27 -0400 Sender: moore@CS.UTK.EDU > Essentially, we currently have a syntax for sending mail to IPv4 > addresses without knowing the name of the host, but have no comparable > mechanism for IPv6. It would seem to be a useful thing. However, are > we forbidden from doing this? I don't think this is a problem. It's not really new functionality in the mail protocols, it's just a matter of updating 822 to reflect changes in IP. I also don't think it's anything that should occupy a lot of our concern at this point. I've heard it suggested that a single WG should look at all of the places where IP addresses are used in higher protocols, and fix them all in the same way at the same time. If that were to happen, our only task would be to update the 822 grammar to reflect the new address format. Keith