IETF Logo Mail Archive

Re: [pkix] [Spasm] IDNA2008 and PKIX certificates

Nikos Mavrogiannopoulos <nmav@redhat.com> Tue, 03 January 2017 09:07 UTC

Return-Path: <nmav@redhat.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAF5D129494; Tue, 3 Jan 2017 01:07:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.022
X-Spam-Level:
X-Spam-Status: No, score=-10.022 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 NfsVhisdQPUc; Tue, 3 Jan 2017 01:07:40 -0800 (PST)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BCC912943F; Tue, 3 Jan 2017 01:07:40 -0800 (PST)
Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C87A681F03; Tue, 3 Jan 2017 09:07:40 +0000 (UTC)
Received: from dhcp-10-40-1-102.brq.redhat.com ([10.40.3.141]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id v0397cGn011423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 3 Jan 2017 04:07:39 -0500
Message-ID: <1483434457.2956.5.camel@redhat.com>
From: Nikos Mavrogiannopoulos <nmav@redhat.com>
To: Russ Housley <housley@vigilsec.com>
Date: Tue, 03 Jan 2017 10:07:37 +0100
In-Reply-To: <1483368902.3167.9.camel@redhat.com>
References: <1480062929.2875.5.camel@redhat.com> <74E53F2B-A88D-4889-8929-9F0E1EAD60A2@vigilsec.com> <1483368902.3167.9.camel@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Tue, 03 Jan 2017 09:07:40 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/2bfIN7zrxrlQBUUZ7ZMOQItfA6I>
Cc: SPASM <spasm@ietf.org>, IETF PKIX <pkix@ietf.org>
Subject: Re: [pkix] [Spasm] IDNA2008 and PKIX certificates
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jan 2017 09:07:42 -0000

On Mon, 2017-01-02 at 15:55 +0100, Nikos Mavrogiannopoulos wrote:
> On Mon, 2016-12-19 at 12:17 -0500, Russ Housley wrote:
> > Nikos:
> > 
> > RFC 5280 only needs to convert to punycode.  The punycode form is
> > carried in certificate, and the punycode form is used to compare
> > two domain names.

Note that RFC5280 requires the reverse too. Section 7.2 says
"Implementations should convert IDNs to Unicode before display."
and that's a valid requirement. The punycode is not human readable.

> > RFC 5280 refers to Section 4 of RFC 3490 for the conversion.  In
> > addition, Section 7.2 of RFC 5280 provides some guidance about the
> > flags
> > used in that process.
> 
> You may be right. The "obsoleted by" header in the referenced
> rfc3490, is probably sufficient.

However, that leaves an transitional use such TR46 [0] as an
exercise to the reader.

regards,
Nikos

[0]. http://unicode.org/reports/tr46/

v2.23.0 | Report a Bug | By Email