Re: [dnssd] UTF8 use in DNS populated by mDNS

Patrik Fältström <paf@frobbit.se> Fri, 21 November 2014 15:43 UTC

Return-Path: <paf@frobbit.se>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C9461A1A36 for <dnssd@ietfa.amsl.com>; Fri, 21 Nov 2014 07:43:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.545
X-Spam-Level:
X-Spam-Status: No, score=-2.545 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] 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 i6HppXk5J6OO for <dnssd@ietfa.amsl.com>; Fri, 21 Nov 2014 07:43:20 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C4261A1A39 for <dnssd@ietf.org>; Fri, 21 Nov 2014 07:43:10 -0800 (PST)
Received: from [192.168.3.214] (unknown [109.107.209.90]) by mail.frobbit.se (Postfix) with ESMTPSA id E6BC92276F; Fri, 21 Nov 2014 16:42:13 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Content-Type: multipart/signed; boundary="Apple-Mail=_0DABB839-5BD0-47E2-9F94-24917DA2FD31"; protocol="application/pgp-signature"; micalg="pgp-sha1"
X-Pgp-Agent: GPGMail 2.5b2
From: Patrik Fältström <paf@frobbit.se>
In-Reply-To: <20141120221150.GA2345@mx1.yitter.info>
Date: Fri, 21 Nov 2014 16:42:18 +0100
Message-Id: <DA79FBC9-22AE-41B3-A9F4-6FB4A8D736E5@frobbit.se>
References: <0996A6E1-5218-4AFB-8646-D1047266C9ED@gmail.com> <20141120221150.GA2345@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/ohDuVojmcDTOwJyX-vdCIgHzWrY
Cc: dnssd@ietf.org
Subject: Re: [dnssd] UTF8 use in DNS populated by mDNS
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2014 15:43:29 -0000

> On 20 nov 2014, at 23:11, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> 
> On Wed, Nov 19, 2014 at 04:50:39PM -0800, Douglas Otis wrote:
>> If UTF-8 is to be permitted in DNS populated using mDNS inputs, a
>> superset of rules directly and indirectly established to support
>> safe use of IDNA labels are necessary, otherwise omitting such
>> requirements would permit trivial spoofing.  The requirements should
>> include IDNA2008 considerations that restrict permitted code points.
> 
> In which part of the DNS-SD name do you want these restrictions?  I
> think there is considerable discussion of the different parts of those
> names in the draft I discussed in Honolulu.
> 
> Note that there is _already_ a standard for putting "UTF-8 labels" in
> the DNS (going back to STD 13 and reiterated by RFC 2181).  In effect,
> they're not "UTF-8 labels" but rather series of octets.

FWIW I agree. One either have to add some kind of restriction on Unicode Codepoints or not, and if you start to go down the path of choosing code points (including normalization forms to use etc) that also impacts matching, then you have something much more complicated than what DNSSD was intended to do (according to my view).

So, I can not personally recommend any more work be done regarding specification on Unicode and DNSSD unless there are very compelling arguments on what problems there are to solve and why.

   Patrik