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

Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 20 November 2014 22:12 UTC

Return-Path: <ajs@anvilwalrusden.com>
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 AB2D41A87BC for <dnssd@ietfa.amsl.com>; Thu, 20 Nov 2014 14:12:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level:
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
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 RnkpCnnknI97 for <dnssd@ietfa.amsl.com>; Thu, 20 Nov 2014 14:12:08 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07F261A87A5 for <dnssd@ietf.org>; Thu, 20 Nov 2014 14:12:03 -0800 (PST)
Received: from mx1.yitter.info (unknown [50.189.173.0]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 2D0838A031 for <dnssd@ietf.org>; Thu, 20 Nov 2014 22:11:59 +0000 (UTC)
Date: Thu, 20 Nov 2014 17:11:51 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnssd@ietf.org
Message-ID: <20141120221150.GA2345@mx1.yitter.info>
References: <0996A6E1-5218-4AFB-8646-D1047266C9ED@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <0996A6E1-5218-4AFB-8646-D1047266C9ED@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/tvLg1xeUryPSORZuA8tlc_io0dI
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: Thu, 20 Nov 2014 22:12:12 -0000

Hi,

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.

> It seems some advocate use of spaces in a domain name label be
> permitted.  Even this minor change may confuse users about the
> specific domain when seen with respect to commandline based
> applications.

This is already permitted, of course, just like anything else in
labels.

But as I guess is plain from my work on the mdns-dns compatibility
I-D, I do think there is a long-term problem here, which is why I
recommend the minimal interoperable subset.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com