CC: undisclosed-recipients: ;
MIME-Version: 1.0
In-Reply-To: <rt-3.8.6-35159-1401293427-1839.36101-4-0@isc.org>
Content-Disposition: inline
References: <RT-Ticket-36101@isc.org> <1738085611.5809889.1401108711247.JavaMail.zimbra@redhat.com> <rt-3.8.6-35155-1401108714-1445.36101-3-0@isc.org> <20140526160753.GA58166@isc.org> <rt-3.8.6-35138-1401120473-1338.36101-5-0@isc.org> <2058734996.6124128.1401208390989.JavaMail.zimbra@redhat.com> <rt-3.8.6-35155-1401208394-747.36101-5-0@isc.org> <rt-3.8.6-35151-1401286425-498.36101-5-0@isc.org> <359623256.6442984.1401293423461.JavaMail.zimbra@redhat.com> <rt-3.8.6-35159-1401293427-1839.36101-4-0@isc.org>
Message-ID: <20140528163048.GA81134@isc.org>
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Received: from bikeshed.isc.org (bikeshed.isc.org [149.20.48.19]) by bugs.isc.org (Postfix) with ESMTP id 2B8572D20571 for <bind-suggest@bugs.isc.org>; Wed, 28 May 2014 16:30:48 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id 1F53D216C3B; Wed, 28 May 2014 16:30:48 +0000 (UTC)
Delivered-To: bind-suggest@bugs.isc.org
User-Agent: Mutt/1.4.2.3i
Subject: Re: [ISC-Bugs #36101] IDN support in host/dig/nslookup using GNU libidn(2)
Return-Path: <each@isc.org>
X-Original-To: bind-suggest@bugs.isc.org
Date: Wed, 28 May 2014 16:30:48 +0000
To: Tomas Hozza via RT <bind-suggest@isc.org>
From: Evan Hunt <each@isc.org>
RT-Message-ID: <rt-3.8.6-35151-1401294648-1361.36101-0-0@isc.org>
Content-Length: 347

> I'll wait for your opinion and work on the separate support in the meantime.

Your opinion is probably at least as well-informed as ours.  Nobody's
asked us about IDN in a while, which is why it hasn't been touched in
so long.  What does your specific customer use case require?

-- 
Evan Hunt -- each@isc.org
Internet Systems Consortium, Inc.