MIME-Version: 1.0 X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.0 In-Reply-To: <1807512246.5806763.1401107982420.JavaMail.zimbra@redhat.com> X-Mailer: Zimbra 8.0.6_GA_5922 (ZimbraWebClient - FF29 (Linux)/8.0.6_GA_5922) Content-Type: text/plain; charset=utf-8 Message-ID: <1738085611.5809889.1401108711247.JavaMail.zimbra@redhat.com> Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) by bugs.isc.org (Postfix) with ESMTP id 1DAEC2D20571 for ; Mon, 26 May 2014 12:51:53 +0000 (UTC) Received: from mx5-phx2.redhat.com (mx5-phx2.redhat.com [209.132.183.37]) by mx.pao1.isc.org (Postfix) with ESMTP id 45DA13494AC for ; Mon, 26 May 2014 12:51:52 +0000 (UTC) (envelope-from thozza@redhat.com) Received: from zmail19.collab.prod.int.phx2.redhat.com (zmail19.collab.prod.int.phx2.redhat.com [10.5.83.22]) by mx5-phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s4QCppuR017844 for ; Mon, 26 May 2014 08:51:51 -0400 Delivered-To: bind-suggest@bugs.isc.org Subject: IDN support in host/dig/nslookup using GNU libidn(2) Return-Path: X-Original-To: bind-suggest@bugs.isc.org Thread-Index: 7La5zHfy2GgN8kUVLJV3fMnkGZTh8w== Date: Mon, 26 May 2014 08:51:51 -0400 (EDT) Thread-Topic: IDN support in host/dig/nslookup using GNU libidn(2) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mx.pao1.isc.org X-Originating-Ip: [10.5.82.11] To: bind-suggest@isc.org Content-Transfer-Encoding: 7bit From: Tomas Hozza X-RT-Original-Encoding: utf-8 Content-Length: 1311 Hi. We maintain like 5 Fedora/RHEL specific patches that are modifying host/dig/nslookup to use libidn instead of idnkit. The change was made by the previous maintainer Adam Tkac, but I guess the reason was that the idnkit is not included in Fedora/RHEL and we don't want to build software using bundled libraries (it is against Fedora policy). I'm not sure if there is already a ISC-Bugs # number for this. However I would like to know if you would be interested in adding support for libidn. I consider it more a feature request than a Bug. My suggestion is to: - introduce new configure option to turn on the usage of GNU libidn (something like --with-gnu-libidn) - use libidn2 for IDN -> ACE conversion (as libidn2 suppoerts IDNA2008 [1] whereas libidn supports only IDNA2003) - use libidn for ACE -> IDN conversion where needed (as libidn2 apparently does not include support for this) I am willing to make the contribution and work with you and incorporate your feedback to make the patch acceptable. Please let me know what do you think about this. Thank you. [1] http://www.icann.org/en/resources/idn/idn-guidelines-02sep11-en.htm Regards, -- Tomas Hozza Software Engineer - EMEA ENG Developer Experience PGP: 1D9F3C2D Red Hat Inc. http://cz.redhat.com