Re: [secdir] Secdir review of draft-ietf-pkix-rfc5280-clarifications-08

Stephen Kent <kent@bbn.com> Mon, 10 September 2012 16:36 UTC

Return-Path: <kent@bbn.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5631321E8047 for <secdir@ietfa.amsl.com>; Mon, 10 Sep 2012 09:36:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, 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 dzLENX1S-ZzJ for <secdir@ietfa.amsl.com>; Mon, 10 Sep 2012 09:36:44 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id B94F521E8037 for <secdir@ietf.org>; Mon, 10 Sep 2012 09:36:41 -0700 (PDT)
Received: from dhcp89-089-153.bbn.com ([128.89.89.153]:50879) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1TB6yW-0001CK-BR; Mon, 10 Sep 2012 12:36:40 -0400
Message-ID: <504E1718.1030501@bbn.com>
Date: Mon, 10 Sep 2012 12:36:40 -0400
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <504DF506.5090107@isode.com>
In-Reply-To: <504DF506.5090107@isode.com>
Content-Type: multipart/alternative; boundary="------------010209010106020406090407"
Cc: secdir@ietf.org
Subject: Re: [secdir] Secdir review of draft-ietf-pkix-rfc5280-clarifications-08
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Sep 2012 16:36:45 -0000

Alexey,

Thanks for noting that ambiguity re "control characters."

Peter: please adopt Alexey's suggested text in Section 3, in v-10.

> The explicitText string SHOULD NOT include any *Unicode* Control
> characters (i.e., U+0000 to U+001F and U+007F to U+009F)
>
> You should also consider whether you should reference RFC 5198 here 
> (which restricts the set even further).
The goal the text here was to allow BMP string, based on deployment 
experience. The clarification
you suggested is good, as it avoids ambiguity re what was said in 5280. 
Citing 5198 and
adopting a more restrictive character set is too big a change for this doc.
> Section 5 only talks about IDNA 2003. What about IDNA 2008?
We're not prepared to move to IDNA 2008, at this time. This is a 
clarifications doc that
updates 5280; the switch to IDNA 2008 would be too big a change for this 
doc.

Steve