CONTEXTO Proposal

[Mark Davis ⌛]

Good point. I don't think it matters a lot, since a registration or lookup
of anything of the form -xxx or xxx- would fail in the end anyway. But if we
need the property you want, the better way to do it (since we already have
special protocol language around HYPHEN), would be to change:
4.2.3.1. Consecutive Hyphens The Unicode string MUST NOT contain "--" (two
consecutive hyphens) in
the third and fourth character positions.

to
4.2.3.1.  Hyphen Restrictions
 The Unicode string MUST NOT contain "--" (two consecutive hyphens) in
the third and fourth character positions. The Unicode string MUST NOT start
or end with a "-" (hyphen).

What do others think?

Mark


On Mon, Jul 20, 2009 at 13:31, Andrew Sullivan <ajs at shinkuro.com> wrote:

> On Mon, Jul 20, 2009 at 01:09:06PM -0700, Mark Davis ⌛ wrote:
> >
> > Here are my recommendations in detail:
> > A. HYPHEN The rule on HYPHEN is unnecessary, since it is a requirement of
> > the DNS system anyway; this is completely redundant. So remove from
> Tables:
>
> I don't think I fully understand that argument.  If it is a
> requirement for the DNS, then surely there ought to be a rule
> restricting the character in that position.  No?  I thought the idea
> was that the IDNA2008 processing could be done effectively as a pipe,
> inputting to the DNS, and anything valid out of the IDNA2008
> processing should then be valid in DNS.  Your suggestion makes this a
> two-way interchange, I think?
>
> A
>
> --
> Andrew Sullivan
> ajs at shinkuro.com
> Shinkuro, Inc.
> _______________________________________________
> Idna-update mailing list
> Idna-update at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/idna-update
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/idna-update/attachments/20090720/c3043980/attachment.htm