IETF Logo Mail Archive

Re: [Idna-update] Expiration impending: <draft-klensin-idna-rfc5891bis-01.txt>

Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 08 March 2018 19:37 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: idna-update@ietfa.amsl.com
Delivered-To: idna-update@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82B5D1270AC for <idna-update@ietfa.amsl.com>; Thu, 8 Mar 2018 11:37:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=NfsnEu+m; dkim=pass (1024-bit key) header.d=yitter.info header.b=T6gHk/uB
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 INivmLTTXoYV for <idna-update@ietfa.amsl.com>; Thu, 8 Mar 2018 11:37:49 -0800 (PST)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42536124BFA for <idna-update@ietf.org>; Thu, 8 Mar 2018 11:37:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 83923BE780 for <idna-update@ietf.org>; Thu, 8 Mar 2018 19:37:48 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1520537868; bh=7m+XafCaaXrXV1p81Wt91NC59TrcSlIGmkrDN29+Jos=; h=Date:From:To:Subject:References:In-Reply-To:From; b=NfsnEu+mvRc2zn74Wf4UJ/7N2xLfD7VkJywJ5IAj9HxtQ1Xt9xEkn54NAWDyKJxck ATxgmh9uk5p0g8t9+nXm/ddN3zOP7aalgJPK3u49E9jbKpFcUerQvPkbi09VLCQ/Gs pAt6gNSydkL3Ol/fCvq2JdTI5lG6Hh/IMJbLpyFo=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cTyrRHuJ7dtq for <idna-update@ietf.org>; Thu, 8 Mar 2018 19:37:47 +0000 (UTC)
Date: Thu, 8 Mar 2018 14:37:44 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1520537867; bh=7m+XafCaaXrXV1p81Wt91NC59TrcSlIGmkrDN29+Jos=; h=Date:From:To:Subject:References:In-Reply-To:From; b=T6gHk/uBCsDajjnjeNfsNGlL4lbBkUdtXZipGJg3ND2F8RadmZL44luhM0s79rhnf WTxaIGCyhO5G/5WbuGSFuJEM1+HeaC8QO4YhGQ66BQuHidocKPq2IpNR+b6m3y1/VQ l9p/QnXMf9jArEjCKLlSQ3YHxAjOtU+OiBbPklB8=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: idna-update@ietf.org
Message-ID: <20180308193744.rkyyz3omuxyd7ehg@mx4.yitter.info>
References: <C4FBCF12821031786F472AA2@PSB> <20180308174703.q3bffw7anrvjwzym@mx4.yitter.info> <2D4E04E4B3BB56404560C142@PSB>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2D4E04E4B3BB56404560C142@PSB>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/7uXhTx8_4qv_EZR611c8ey9o3qE>
Subject: Re: [Idna-update] Expiration impending: <draft-klensin-idna-rfc5891bis-01.txt>
X-BeenThere: idna-update@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Internationalized Domain Names in Applications \(IDNA\) implementation and update discussions" <idna-update.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idna-update>, <mailto:idna-update-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idna-update/>
List-Post: <mailto:idna-update@ietf.org>
List-Help: <mailto:idna-update-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idna-update>, <mailto:idna-update-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2018 19:37:50 -0000

On Thu, Mar 08, 2018 at 02:11:21PM -0500, John C Klensin wrote:
> 
> On the other hand, the same kind of thinking  that argues for a
> "troublesome characters" list (at least as I've understood it)
> -- more "you SHOULD NOT use these unless you are extra-sure you
> know what you are doing and what the implications might be" than
> any sort of absolute prohibition -- might imply a similar
> statement about combining sequences.

That actually doesn't seem like a terrible idea to me.  Of course,
that was _supposed_ to be the point of the general exhortation to have
a clue about the code points you were putting in a zone.  And that
doesn't seem to have panned out :-/

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com

v2.8.7 | Report a Bug | By Email