Re: drums2?

Keith Moore <moore@cs.utk.edu> Mon, 19 August 2002 17:52 UTC

Received: by above.proper.com (8.11.6/8.11.3) id g7JHqDr14151 for ietf-822-bks; Mon, 19 Aug 2002 10:52:13 -0700 (PDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7JHqBn14146 for <ietf-822@imc.org>; Mon, 19 Aug 2002 10:52:11 -0700 (PDT)
Received: from astro.cs.utk.edu (localhost [127.0.0.1]) by astro.cs.utk.edu (cf 8.9.3) with ESMTP id g7JHqA028041; Mon, 19 Aug 2002 13:52:10 -0400 (EDT)
Message-Id: <200208191752.g7JHqA028041@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Charles Lindsey <chl@clw.cs.man.ac.uk>
cc: ietf-822@imc.org
Subject: Re: drums2?
In-reply-to: (Your message of "Mon, 19 Aug 2002 10:02:10 GMT.") <H1357M.Er1@clw.cs.man.ac.uk>
Date: Mon, 19 Aug 2002 13:52:10 -0400
Sender: owner-ietf-822@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>

> You need therefore some foolproof way to distinguish between an encoded
> local-part and an unencoded one. This means placing some restriction on
> local-parts as presently defined.

you do the same thing that IDN did:

- you pick an encoding that is extremely unlikely to have been used in 
  a real local-part.

- you *always* use the encoded form on the wire.

it doesn't require a change to the message format.

Keith