Re: [lamps] Spencer Dawkins' No Objection on draft-ietf-lamps-rfc5280-i18n-update-03: (with COMMENT)

Russ Housley <housley@vigilsec.com> Fri, 06 October 2017 14:11 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4E411349D6 for <spasm@ietfa.amsl.com>; Fri, 6 Oct 2017 07:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id njNw-HrRtUOR for <spasm@ietfa.amsl.com>; Fri, 6 Oct 2017 07:11:15 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DBC41349D3 for <spasm@ietf.org>; Fri, 6 Oct 2017 07:11:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id BD3593005AD for <spasm@ietf.org>; Fri, 6 Oct 2017 10:02:31 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id BNRR0H386bOM for <spasm@ietf.org>; Fri, 6 Oct 2017 10:02:24 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 921C530026A; Fri, 6 Oct 2017 10:02:24 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <150725438252.5833.1845084525614926868.idtracker@ietfa.amsl.com>
Date: Fri, 6 Oct 2017 10:02:23 -0400
Cc: IESG <iesg@ietf.org>, draft-ietf-lamps-rfc5280-i18n-update@ietf.org, Phillip Hallam-Baker <phill@hallambaker.com>, lamps-chairs@ietf.org, spasm@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <ECFA352F-3C46-434D-9193-53CB9CCDE8CA@vigilsec.com>
References: <150725438252.5833.1845084525614926868.idtracker@ietfa.amsl.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/j4GmcTuEsy_WRs6UotyrA4snON8>
Subject: Re: [lamps] Spencer Dawkins' No Objection on draft-ietf-lamps-rfc5280-i18n-update-03: (with COMMENT)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Oct 2017 14:11:17 -0000

Spencer:

Two things are going on in this document:

(1)  This update aligns with IDNA2008.

(2)  Add support for EAI.

So, it might be better to say:

   These updates to RFC 5280 provide alignment with the 2008 specification
   for Internationalized Domain Names (IDNs) and add support for
   Internationalized Email Addresses in X.509 Certificates.

Russ


> On Oct 5, 2017, at 9:46 PM, Spencer Dawkins <spencerdawkins.ietf@gmail.com> wrote:
> 
> Spencer Dawkins has entered the following ballot position for
> draft-ietf-lamps-rfc5280-i18n-update-03: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc5280-i18n-update/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> You folks would know best what's actually clear to your intended audience, but
> the use of  "provide clarity on the handling of" in the Abstract,
> 
>   These updates to RFC 5280 provide clarity on the handling of
>   Internationalized Domain Names (IDNs) and Internationalized Email
>   Addresses in X.509 Certificates.
> 
> and in the first paragraph of the Introduction,
> 
>   This document updates RFC 5280 [RFC5280].  The Introduction in
>   Section 1, the Name Constraints certificate extension discussion in
>   Section 4.2.1.10, and the Processing Rules for Internationalized
>   Names in Section 7 are updated to provide clarity on the handling of
>   Internationalized Domain Names (IDNs) and Internationalized Email
>   Addresses in X.509 Certificates.
> 
> wasn't particularly helpful to me.  Are there a few words that would describe
> (at a high level) what the problem with RFC 5280 was, that required this
> document (I'm suggesting saying "so if you implemented RFC 5280, you can expect
> problems A and B, so you probably want to implement this specification as
> well", but in different words)?
> 
>