Re: [DNSOP] The DNSOP WG has placed draft-wkumari-dnsop-multiple-responses in state "Candidate for WG Adoption"

Wes Hardaker <wjhns1@hardakers.net> Wed, 06 July 2016 19:35 UTC

Return-Path: <wjhns1@hardakers.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51EEF12D62D for <dnsop@ietfa.amsl.com>; Wed, 6 Jul 2016 12:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.327
X-Spam-Level:
X-Spam-Status: No, score=-3.327 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 eXShkoY3paWE for <dnsop@ietfa.amsl.com>; Wed, 6 Jul 2016 12:35:24 -0700 (PDT)
Received: from mail.hardakers.net (dawn.hardakers.net [IPv6:2001:470:1f00:187::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BBC412D5D2 for <dnsop@ietf.org>; Wed, 6 Jul 2016 12:35:24 -0700 (PDT)
Received: from localhost (50-1-20-198.dsl.static.fusionbroadband.com [50.1.20.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 2E1DF2ADE2; Wed, 6 Jul 2016 12:35:21 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: fujiwara@jprs.co.jp
References: <20160701075116.24678.59997.idtracker@ietfa.amsl.com> <20160706.180940.1170484542745240536.fujiwara@jprs.co.jp>
Date: Wed, 06 Jul 2016 12:35:19 -0700
In-Reply-To: <20160706.180940.1170484542745240536.fujiwara@jprs.co.jp> (fujiwara@jprs.co.jp's message of "Wed, 06 Jul 2016 18:09:40 +0900 (JST)")
Message-ID: <0lr3b6sgp4.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/24.5 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/WxmsXya6Se_mHbAJ3YnF6myKJUM>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] The DNSOP WG has placed draft-wkumari-dnsop-multiple-responses in state "Candidate for WG Adoption"
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: Wed, 06 Jul 2016 19:35:26 -0000

fujiwara@jprs.co.jp writes:

>   Using unstructured data (TXT format) is not good.

Thanks for the feedback on that.  I have wondered heavily on that
topic.  It was originally written as a text format, and we have a lot of
other cases where such text parsing exists (SPF being an example).  As
the world moves more and more to text based parsing for everything,
which I hardly say is a good thing, I wonder what the right format of
future DNS records should be.  It sounds like a good worthwhile
discussion in its own right.

In the mean time, a binary format for the record would be just fine in
my view and the record already lends itself to such a format since it's
very structured data.  It would be worth discussing once the concept in
the draft gets accepted for work by the WG.  I'm (personally) certainly
not opposed to a binary on-the-wire record format.

>   I think the multiple queries in one request is not related to DNSSEC
>   and TCP connection. They are separated elements.

We dropped the requirement for TCP in the latest version already (-03).

DNSSEC is necessary to avoid cache poisoning of illegal data (IE, to
prove you're the parent of the data as opposed to a grand parent).
-- 
Wes Hardaker
Parsons