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

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Fri, 06 October 2017 01:46 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: spasm@ietf.org
Delivered-To: spasm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A32D1326FE; Thu, 5 Oct 2017 18:46:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-lamps-rfc5280-i18n-update@ietf.org, Phillip Hallam-Baker <phill@hallambaker.com>, Russ Housley <housley@vigilsec.com>, lamps-chairs@ietf.org, phill@hallambaker.com, spasm@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150725438252.5833.1845084525614926868.idtracker@ietfa.amsl.com>
Date: Thu, 05 Oct 2017 18:46:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/utS3ccsz_ecazyXlaeZwIxe0y_Y>
Subject: [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
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 01:46:22 -0000

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)?