[DNSOP] Comments on draft-ietf-dnsop-alt-tld-05

Federico Santandrea <federico@xylant.net> Sun, 09 October 2016 06:27 UTC

Return-Path: <federico@xylant.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 539E41294A3 for <dnsop@ietfa.amsl.com>; Sat, 8 Oct 2016 23:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id D5ixP7Pha946 for <dnsop@ietfa.amsl.com>; Sat, 8 Oct 2016 23:27:24 -0700 (PDT)
Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A351129435 for <dnsop@ietf.org>; Sat, 8 Oct 2016 23:27:24 -0700 (PDT)
Received: from mfilter15-d.gandi.net (mfilter15-d.gandi.net []) by relay2-d.mail.gandi.net (Postfix) with ESMTP id 85E2EC5A44; Sun, 9 Oct 2016 08:27:22 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter15-d.gandi.net
Received: from relay2-d.mail.gandi.net ([IPv6:::ffff:]) by mfilter15-d.gandi.net (mfilter15-d.gandi.net [::ffff:]) (amavisd-new, port 10024) with ESMTP id T0MHXD-6wGKU; Sun, 9 Oct 2016 08:24:27 +0200 (CEST)
Received: from [] (unknown []) (Authenticated sender: federico@xylant.net) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id 65103C5A43; Sun, 9 Oct 2016 08:24:26 +0200 (CEST)
From: Federico Santandrea <federico@xylant.net>
To: dnsop@ietf.org
Message-ID: <a63bb766-527b-c752-22a1-fccae8535ddc@xylant.net>
Date: Sun, 09 Oct 2016 08:24:22 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/GOCB4jSDkGM6w5m-kVdTjHblOtA>
Cc: asullivan@dyn.com
Subject: [DNSOP] Comments on draft-ietf-dnsop-alt-tld-05
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 09 Oct 2016 06:27:26 -0000


I have read, and I support this draft in its current form.

I propose these two additions to it:

1)  applications may query for "alt." for some RR. If the
    resolver is not "alt-tld aware", or alt-tld functionality
    has been disabled, then the request will return NXDOMAIN;
    if instead the mechanism is supported, it would return
    NOERROR with an empty answer. Note that this is backwards
    compatible with non-alt-aware implementations since they
    would leak in DNS and NXDOMAIN will be returned by some
    other server.

2a) applications may also query for "<something>.alt" in the
    same way as above, to determine whether an handler for
    that particular namespace is available or not.

-- or alternatively --

2b) as above, but it might be specified that the query is
     to be done on a TXT RR specifically and that, instead
     of the empty answer, a record might be returned with
     contents that can be used to in some way ascertain that
     the handler is actually for the implementation we expect
     it to be (for example a software name or version, or
     protocol "UUID"?)

This allows applications to determine both if the alt mechanism
is generally supported and if the particular namespace is
supported (for example, to choose between showing instructions
suggestions to download a plugin and to upgrade the underlying
software platform). Also it avoids everyone choosing "magic"
values to check whether handlers for their namespace have
been installed or not.

Just a rough idea... of course if you find it useful I would
I would need to fix it in form and language.

Let me know what you think about this.