[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Last Call summary for draft-ietf-pkix-cert-utf8



Looks good to me. 

> -----Original Message-----
> From: owner-ietf-pkix@xxxxxxxxxxxx 
> [mailto:owner-ietf-pkix@xxxxxxxxxxxx] On Behalf Of Michael Myers
> Sent: Thursday, April 13, 2006 2:04 PM
> To: Russ Housley; Ted Hardie
> Cc: iesg@xxxxxxxx; ietf-pkix@xxxxxxx
> Subject: RE: Last Call summary for draft-ietf-pkix-cert-utf8
> 
> 
> works for me
> 
> Mike
> 
> -----Original Message-----
> From: Russ Housley
> Sent: Thursday, April 13, 2006 8:11 AM
> 
> 
> Ted:
> 
> Thanks for the improved text.  Here it is all put together:
> 
> When strings are mapped from internal representations to 
> visual representations, sometimes two different strings will 
> have the same or similar visual representations. This can 
> happen for many different reasons, including use of similar 
> glyphs and use of composed characters (such as e + ' equaling 
> U+00E9, the Korean composed characters, and vowels above 
> consonant clusters in certain languages).  As a result of 
> this situation, people doing visual comparisons between two 
> different names may think they are the same when in fact they 
> are not.  Also, people may mistake one string for another.  
> Issuers of certificates and relying parties both need to be 
> aware of this situation.
> 
> This does not impose any untestable requirements.  Any 
> concerns with this text?
> 
> Russ
> 
> 
> 
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature