[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[idn] Re: Document Status?
- To: Dave Crocker <dhc@xxxxxxxxxxxx>
- Subject: [idn] Re: Document Status?
- From: Simon Josefsson <jas@xxxxxxxxxxx>
- Date: Wed, 04 Sep 2002 04:53:03 +0200
- Cc: idn@xxxxxxxxxxxx
- In-reply-to: <> (Dave Crocker's message of "Tue, 03 Sep 2002 19:28:25 -0700")
- References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
- Sender: owner-idn@xxxxxxxxxxxx
- User-agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.3.50 (i686-pc-linux-gnu)
Dave Crocker <dhc@xxxxxxxxxxxx> writes:
> At 10:57 AM 9/4/2002 +0900, Soobok Lee wrote:
>> MIME (and even RFC2047)encodes texts or descriptors , not ciritical
>> identifiers
>>like domain names as far as i understand.
>
> How does that difference matter? What is it about that difference
> that makes experience with MIME not apply for IDNA?
If I press the PRINT button on a MIME part in my mail reader, noone
cares that the rendered MIME body, which is printed, is infeasible to
put back into the original MIME part.
If I press the PRINT button on an IDNA in my mail reader, it is
important that people are able to put it back into the original IDNA
[given some reasonable assumptions about the people].
IDNA will be used to identify entities. If there is any confusion as
to which identity a certain IDNA really points at, there will be
security consequences. MIME doesn't have this property.