Re: [newprep] WG Review: Stringprep after IDNA2008 WG (newprep)

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 11 June 2010 09:06 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: newprep@core3.amsl.com
Delivered-To: newprep@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC6743A68DF; Fri, 11 Jun 2010 02:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.621
X-Spam-Level:
X-Spam-Status: No, score=-0.621 tagged_above=-999 required=5 tests=[AWL=-0.622, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MecmqpAjXAk2; Fri, 11 Jun 2010 02:06:14 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 9F7CE3A68B5; Fri, 11 Jun 2010 02:06:13 -0700 (PDT)
Received: from [172.16.2.172] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TBH8ggAJf2cd@rufus.isode.com>; Fri, 11 Jun 2010 10:06:13 +0100
Message-ID: <4C11FC7B.4020108@isode.com>
Date: Fri, 11 Jun 2010 10:06:03 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Sam Hartman <hartmans-ietf@mit.edu>
References: <20100511173002.3EB993A6D0F@core3.amsl.com> <tslzkzxjfmh.fsf@mit.edu> <4BF2D57F.8090807@viagenie.ca> <tsltyq5hxq5.fsf@mit.edu> <4BF2DD30.8030702@viagenie.ca> <4BF3EA68.6050103@stpeter.im> <4BF3EAD6.3010108@viagenie.ca> <tsl1vd7hmrf.fsf@mit.edu> <4BFC8FA3.9030807@stpeter.im> <tslzkzl1g73.fsf@mit.edu> <475012020.21148@cnnic.cn> <tsl63209bsl.fsf@mit.edu>
In-Reply-To: <tsl63209bsl.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: ietf-krb-wg@anl.gov, ietf@ietf.org, aland@freeradius.org, newprep@ietf.org, iesg@ietf.org
Subject: Re: [newprep] WG Review: Stringprep after IDNA2008 WG (newprep)
X-BeenThere: newprep@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Stringprep after IDNA2008 <newprep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/newprep>, <mailto:newprep-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/newprep>
List-Post: <mailto:newprep@ietf.org>
List-Help: <mailto:newprep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/newprep>, <mailto:newprep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jun 2010 09:06:15 -0000

Sam Hartman wrote:

>>>>>>"Jiankang" == Jiankang YAO <yaojk@cnnic.cn> writes:
>>>>>>            
>>>>>>
>    Jiankang> If there are many things we must do, we(WGs) normally
>    Jiankang> prioritize the things.  sometimes, the easier one first;
>    Jiankang> sometimes, the difficult one first.
>Sure.
>That's fine for the WG to do.
>I don't think it is good to do in the charter without  some fairness
>criteria.
>All items brought up by the time external review of the charter
>concluded seems like a reasonable fairness criteria.
>Putting the cutoff before that seems unreasonable.
>
>Obviously, the WG can internally prioritize (and change its priorities)
>within its normal administrative processes.
>
>    Jiankang> If peter's list is not ok for you, could you kindly give
>    Jiankang> us your list?
>
>The list in the charter plus:
>
>1) Considering Kerberos implications for SASLPREP revisions
>  
>
Sam,
I think this is granted. I don't think this needs to be written into the 
charter, especially considering that there is a good deal of overlap 
between people active in Kerberos and SASL WGs.

>2) Considering RFC 4282.
>  
>
Do you consider RFC 4282 to be a stringprep profile? My quick scan of 
the document (in particular Section 2.4) is not conclusive.

>Both of these are stringprep issues.  Kerberos has been intending to use
>SASLPREP; if you revise SASLPREP without considering what happens for
>Kerberos, then you'll just end up revising it yet again later.
>
>NAIs seem to use more of the IDNA2003 rules than just the IDNA 2003
>stringprep profile, but they do use that profile as well.
>  
>