Re: prohibited characters per stringprep

From: Mark Davis (mark@macchiato.com)
Date: Mon Dec 08 2008 - 12:53:12 CST

• Next message: Sarasvati: "Public Review Issue #133: Proposed Draft UTS #46, Unicode IDNA Compatible Preprocesssing"
• Previous message: John H. Jenkins: "Re: HKSCS supplementary examples"
• In reply to: Chris Weber \(Casaba Security\): "prohibited characters per stringprep"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

The current, operant version of IDNA is described in
http://tools.ietf.org/html/rfc3490, http://tools.ietf.org/html/rfc3491, and
http://tools.ietf.org/html/rfc3454. There is a proposed revision of IDNA
being developed at http://tools.ietf.org/id/idnabis.
It is unclear what you are referring to by "older draft".

Mark

On Sun, Dec 7, 2008 at 23:54, Chris Weber (Casaba Security) <
chris@casabasecurity.com> wrote:

> 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: Sarasvati: "Public Review Issue #133: Proposed Draft UTS #46, Unicode IDNA Compatible Preprocesssing"
• Previous message: John H. Jenkins: "Re: HKSCS supplementary examples"
• In reply to: Chris Weber \(Casaba Security\): "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