Re: [apps-discuss] WGLC: draft-faltstrom-5892bis-04.txt

Andrew Sullivan <ajs@shinkuro.com> Wed, 27 April 2011 14:58 UTC

Return-Path: <ajs@shinkuro.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9A17E07AD; Wed, 27 Apr 2011 07:58:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level:
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=-0.199, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dHxRfTe70iNt; Wed, 27 Apr 2011 07:58:03 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 66CE0E0721; Wed, 27 Apr 2011 07:58:03 -0700 (PDT)
Received: from shinkuro.com (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 6A7A31ECB41D; Wed, 27 Apr 2011 14:58:02 +0000 (UTC)
Date: Wed, 27 Apr 2011 10:58:00 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: Stéphane Lancel <stelancel@gmail.com>
Message-ID: <20110427145800.GI7329@crankycanuck.ca>
References: <503575932.12389@cnnic.cn> <87mxjc21vi.fsf@latte.josefsson.org> <BANLkTik9qxNX-rFL+2mmfxcZa2Hzn4teyw@mail.gmail.com> <20110427140644.GH7329@crankycanuck.ca> <BANLkTi=VvEgtqWuKJte+vDOBzFhsGg0L7w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <BANLkTi=VvEgtqWuKJte+vDOBzFhsGg0L7w@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: idna-update@alvestrand.no, internet users contributing group <iucg@ietf.org>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] WGLC: draft-faltstrom-5892bis-04.txt
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2011 14:58:04 -0000

[cc:s trimmed]

On Wed, Apr 27, 2011 at 04:49:18PM +0200, Stéphane Lancel wrote:

> I am sorry because I am not really expert in PVALID issues (changes, etc.),
> but I understood that PVALID once, PVALID for ever. I realize with this
> Draft that this means at character level not at codepoint level. Or am I
> wrong?

I think you're wrong in two ways.

First, it's true that the idea in IDNA2008 was that once something
would be PVALID, it would be PVALID forever.  But IDNA2008 depends on
Unicode and its properties.  If Unicode changes properties such that
something moves from PVALID to something else, then the desired state
is not achieved.

Now, one could just make a rule, "once PVALID then always PVALID."
But this is tantamount to sticking IDNA2008 to the Unicode version
that was around at the time of IDNA2008 publication.  We wanted to be
Unicode-version independent, and so that strategy doesn't meet the
goal.  

Second, I don't think "at character level not at codepoint level" is
right.  We're dealing in code points.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.