Re: [jose] Stephen Farrell's Discuss on draft-ietf-jose-json-web-key-33: (with DISCUSS and COMMENT)
Ted Lemon <Ted.Lemon@nominum.com> Mon, 06 October 2014 20:34 UTC
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9B171A89B1; Mon, 6 Oct 2014 13:34:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level:
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 5sblAlJolTPf; Mon, 6 Oct 2014 13:34:13 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEF2D1A89BB; Mon, 6 Oct 2014 13:34:09 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D92E81B81AB; Mon, 6 Oct 2014 13:34:09 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id CF1A653E070; Mon, 6 Oct 2014 13:34:09 -0700 (PDT)
Received: from [10.0.10.40] (71.233.43.215) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 6 Oct 2014 13:34:10 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <00c601cfe1a4$15d32900$41797b00$@augustcellars.com>
Date: Mon, 06 Oct 2014 16:34:06 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <7ABF79CB-61C8-490B-A727-465530222F0B@nominum.com>
References: <20141002111501.6046.52416.idtracker@ietfa.amsl.com> <4E1F6AAD24975D4BA5B16804296739439BAF0C1E@TK5EX14MBXC286.redmond.corp.microsoft.com> <00c601cfe1a4$15d32900$41797b00$@augustcellars.com>
To: Jim Schaad <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: http://mailarchive.ietf.org/arch/msg/jose/2rDFaJxigUl4-lzd9AUJh9Me5AM
Cc: jose-chairs@tools.ietf.org, Mike Jones <Michael.Jones@microsoft.com>, The IESG <iesg@ietf.org>, jose@ietf.org, draft-ietf-jose-json-web-key@tools.ietf.org, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [jose] Stephen Farrell's Discuss on draft-ietf-jose-json-web-key-33: (with DISCUSS and COMMENT)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/jose/>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Oct 2014 20:34:14 -0000
On Oct 6, 2014, at 4:28 PM, Jim Schaad <ietf@augustcellars.com> wrote: > I worry that if we starting providing guidance to DNS names, then we need to > worry about the I18N implications. I don't remember if these are both case > sensitive and easy to do the case conversion on. Isn't this a solved problem? You convert to the unicode presentation and then convert to the canonical case as defined in the unicode standard. The worst case scenario is that you encounter some script where this rule doesn't work, and that script is then in the position that all scripts are in now.
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Mike Jones
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Mike Jones
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Jim Schaad
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Ted Lemon
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Jim Schaad
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Stephen Farrell
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Jim Schaad
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Stephen Farrell
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Mike Jones
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Ted Lemon
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Ted Lemon
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Jim Schaad
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Mike Jones
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Stephen Farrell
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Mike Jones
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Barry Leiba
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Mike Jones
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Ted Lemon
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Barry Leiba
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Mike Jones
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Stephen Farrell
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Mike Jones
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Mike Jones
- Re: [jose] Stephen Farrell's Discuss on draft-iet… Mike Jones