IETF Logo Mail Archive

Re: [DNSOP] Terminology: IDN

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 04 May 2015 15:40 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 803411A1BC3 for <dnsop@ietfa.amsl.com>; Mon, 4 May 2015 08:40:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 NGW38WXu97-v for <dnsop@ietfa.amsl.com>; Mon, 4 May 2015 08:40:50 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [IPv6:2600:3c03::f03c:91ff:fedf:cfab]) by ietfa.amsl.com (Postfix) with ESMTP id 318F51A1BBB for <dnsop@ietf.org>; Mon, 4 May 2015 08:40:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 8B8EC106B3 for <dnsop@ietf.org>; Mon, 4 May 2015 15:40:49 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vq84oI-Auoad for <dnsop@ietf.org>; Mon, 4 May 2015 15:40:48 +0000 (UTC)
Received: from mx2.yitter.info (host86-187-37-6.range86-187.btcentralplus.com [86.187.37.6]) by mx2.yitter.info (Postfix) with ESMTPSA id 7E3D81036C for <dnsop@ietf.org>; Mon, 4 May 2015 15:40:48 +0000 (UTC)
Date: Mon, 04 May 2015 16:40:50 +0100
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20150504154050.GJ69915@mx2.yitter.info>
References: <3FB18AE0-8769-4B73-9964-8F0D1AB1FA54@vpnc.org> <D16D027D.B573%edward.lewis@icann.org> <A4A329B9-6E42-43A4-B7D4-F02788EFAD62@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <A4A329B9-6E42-43A4-B7D4-F02788EFAD62@vpnc.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/mEtulv2HX3849wqi8IVZbxfYSf0>
Subject: Re: [DNSOP] Terminology: IDN
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 May 2015 15:40:52 -0000

On Mon, May 04, 2015 at 08:24:10AM -0700, Paul Hoffman wrote:
> IDNA2008 is a set of standards-track documents.

This is true.

> It is the only standardized way to convert between DNS names and representation of non-ASCII characters in the DNS.
> 

This is not quite true, and anyway not convincing.  What is true is
that there is no real standard way to interpret a bag of bits in a DNS
label except as an ASCII character, so IDNA is the only
fully-developed IETF standard for this.  But DNS-SD (RFC 6763)
actually says that you should interpret such labels as UTF-8.  It is
also well-known that some widely-deployed systems that rely on DNS
names interpret a label with a high bit as UTF-8.  And such uses are
entirely in keeping with STD 13.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

v2.23.0 | Report a Bug | By Email