IETF Logo Mail Archive

Re: [pkix] IDNA2008 and PKIX certificates

Sean Turner <sean@sn3rd.com> Wed, 23 November 2016 17:27 UTC

Return-Path: <sean@sn3rd.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 CF1C012A055 for <pkix@ietfa.amsl.com>; Wed, 23 Nov 2016 09:27:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
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 qOkvwO1R4oCs for <pkix@ietfa.amsl.com>; Wed, 23 Nov 2016 09:27:40 -0800 (PST)
Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C0B412A0F2 for <pkix@ietf.org>; Wed, 23 Nov 2016 09:27:29 -0800 (PST)
Received: by mail-qt0-x22a.google.com with SMTP id p16so17990319qta.0 for <pkix@ietf.org>; Wed, 23 Nov 2016 09:27:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=l8R06LGUJWSgWgH0bV8P3US5tOD9UuZ9MMHpJdTLNeA=; b=VFW7muN10cadIhFFCU9yuah6ocZE9RfNmFQ9kXFlBMwZTDaF5Qzg9kfrOhlIKqyOJc LDYjGnxsd92F2yTIsUzIOb3y45cCbLuYPtNO8QeRG/P8AdVcj1QepWG4PS73SA5zRoyZ p/poq3VS+0EgoBK21Av5szohu/Z0PWDhoJdH4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=l8R06LGUJWSgWgH0bV8P3US5tOD9UuZ9MMHpJdTLNeA=; b=AON6k/t/uMpbUkivim4CQF+UntZLuVGMBV4sVwRQmRL5LX8S/ZRtxAV4FOfaKlj/z9 y15x1iiu3ARzEDbPNww18v98p26O4bYptvmkuytnGmB/ME0RWztGCatCj2mzBfpHm8qh yURpgWrZ3ChcjGeAwVEeBcbzBAJLMawrknsbQZTRnT4oAq+inNEV5lwfFqe3SkGh6Y2n 9vK7IJZhU7udOJfNNqkao5VQpYeivNPPPnWQuhNSkTgOtrihGE2j2h000dcRC6ObtBYz ElDQBnAficxDEBwAlrLooGq+vPlNrMyK/8I1gB6bBcvIlbj4dUb5GVsRT59QV9g/VAA6 rR5A==
X-Gm-Message-State: AKaTC00EKmoPjvXGOOoj7U5PUM1TioNtOYcRGqxnkr5wQG1917jHhntW1TyWVXh9qnECDQ==
X-Received: by 10.237.61.98 with SMTP id h31mr3978838qtf.243.1479922048448; Wed, 23 Nov 2016 09:27:28 -0800 (PST)
Received: from [172.16.0.92] ([96.231.230.70]) by smtp.gmail.com with ESMTPSA id r6sm16824914qkr.3.2016.11.23.09.27.27 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 23 Nov 2016 09:27:27 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <1479901874.2563.32.camel@redhat.com>
Date: Wed, 23 Nov 2016 12:27:25 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <7950B277-C3BF-4F6C-B09B-1CB6B8961786@sn3rd.com>
References: <1479808931.31825.10.camel@redhat.com> <FFF8A1DB-6309-4500-BFF8-2A7575DBBCFF@sn3rd.com> <1479901874.2563.32.camel@redhat.com>
To: Nikos Mavrogiannopoulos <nmav@redhat.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/AuT1d4pGmH8WICuEfAY6zRVwqNU>
Cc: pkix@ietf.org
Subject: Re: [pkix] 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: Wed, 23 Nov 2016 17:27:42 -0000

Yes because if anybody is going to be able to answer the question it’ll be them.

spt

> On Nov 23, 2016, at 06:51, Nikos Mavrogiannopoulos <nmav@redhat.com> wrote:
> 
> Thank you Sean. Should I forward the initial question to the precis
> working group? (or at least a version of the question which asks their
> recommendation).
> 
> 
> On Wed, 2016-11-23 at 05:57 -0500, Sean Turner wrote:
>> Nikos,
>> 
>> I asked about this in 2011 and here’s the response I got from an
>> “apps” person (shared with permission):
>> 
>> spt
>> 
>>> 
>>> On Apr 13, 2011, at 14:51, Pete Resnick <presnick@qualcomm.com>
>>> wrote:
>>> 
>>>> 
>>>> I'm curious if there's something that lists the differences
>>>> between the IDNA 2003 and 2008 for a layman. I've got a WG that
>>>> wants to update the references, but I don't think it's just as
>>>> easy as that.
>>> 
>>> It is most certainly *not* as easy as that. You could send them to
>>> RFC 5894, but that's not a list of differences; it's an entirely
>>> new design philosophy. If you've got a WG that wants to update
>>> references, send them to PRECIS. We're here to help.™
>>> 
>>> pr
>> 
>> 
>>> 
>>> On Nov 22, 2016, at 05:02, Nikos Mavrogiannopoulos <nmav@redhat.com
>>>> wrote:
>>> 
>>> Hi,
>>>  RFC5280 and its update (6818), reference IDNA2003 (rfc3490) for
>>> storing internationalized DNS names. However, IDNA2003 is already
>>> obsolete standard (it seems it was already deprecated when RFC6818
>>> was
>>> published [0]) and in practice phased out. What is the current best
>>> practice on internationalized names with certificates?
>>> 
>>> Is it transparently switch to IDNA2008 (rfc5890), and let software
>>> figure out the reverse mappings to utf8 somehow?
>>> 
>>> Or is it store UTF-8 dns names on the certificate, and let the
>>> software
>>> comparing DNS names do any mapping it deems necessary prior to
>>> comparison?
>>> 
>>> regards,
>>> Nikos
>>> 
>>> [0]. https://www.ietf.org/mail-archive/web/pkix/current/msg28386.ht
>>> ml
>>> 
>>> _______________________________________________
>>> pkix mailing list
>>> pkix@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pkix
>> 
>

v2.23.0 | Report a Bug | By Email