prohibited characters per stringprep

From: Chris Weber \(Casaba Security\) (chris@casabasecurity.com)
Date: Mon Dec 08 2008 - 01:54:52 CST

• Next message: Andrew West: "Re: HKSCS supplementary examples"
• Previous message: vunzndi@vfemail.net: "Re: HKSCS supplementary examples"
• Next in thread: Mark Davis: "Re: prohibited characters per stringprep"
• Reply: Mark Davis: "Re: prohibited characters per stringprep"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

It looks like an older draft of stringprep prohibited the output of
\u2024..\u2026, but the RFC prohibition tables do not. Does anyone know
what the reason might be for this change? In general, wouldn't this say to
software vendors that an IDN with one of these characters is well-formed and
acceptable?

Thanks,

Chris

• Next message: Andrew West: "Re: HKSCS supplementary examples"
• Previous message: vunzndi@vfemail.net: "Re: HKSCS supplementary examples"
• Next in thread: Mark Davis: "Re: prohibited characters per stringprep"
• Reply: Mark Davis: "Re: prohibited characters per stringprep"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2.1.5 : Fri Jan 02 2009 - 15:33:07 CST