IETF Logo Mail Archive

Re: [DNSOP] DNS-in-JSON draft

Tony Finch <dot@dotat.at> Tue, 06 September 2016 13:40 UTC

Return-Path: <dot@dotat.at>
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 8314A12B559 for <dnsop@ietfa.amsl.com>; Tue, 6 Sep 2016 06:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_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 jDiGdXUCgGY4 for <dnsop@ietfa.amsl.com>; Tue, 6 Sep 2016 06:40:19 -0700 (PDT)
Received: from ppsw-30.csi.cam.ac.uk (ppsw-30.csi.cam.ac.uk [131.111.8.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C27E12B652 for <dnsop@ietf.org>; Tue, 6 Sep 2016 06:29:27 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:60107) by ppsw-30.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1bhGRI-000bM8-fB (Exim 4.86_36-e07b163) (return-path <dot@dotat.at>); Tue, 06 Sep 2016 14:29:24 +0100
Date: Tue, 06 Sep 2016 14:29:24 +0100
From: Tony Finch <dot@dotat.at>
To: Shane Kerr <shane@time-travellers.org>
In-Reply-To: <20160906123841.2bd451af@pallas.home.time-travellers.org>
Message-ID: <alpine.DEB.2.11.1609061427050.32067@grey.csi.cam.ac.uk>
References: <DB336274-A631-471E-8277-D6690A87C834@vpnc.org> <20160905154737.5a1c67e5@pallas.home.time-travellers.org> <alpine.DEB.2.11.1609051121080.28546@grey.csi.cam.ac.uk> <20160906123841.2bd451af@pallas.home.time-travellers.org>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ULM-QnEXw2Wj4s64vWnrntpqyCE>
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] DNS-in-JSON draft
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: Tue, 06 Sep 2016 13:40:23 -0000

Shane Kerr <shane@time-travellers.org> wrote:
> At 2016-09-05 11:22:48 +0100
> Tony Finch <dot@dotat.at> wrote:
> > Shane Kerr <shane@time-travellers.org> wrote:
> > >
> > > It occurs to me that maybe we want an option to have arrays of RRset
> > > instead of arrays of RRs?
> >
> > If you do that, how do you represent the covering signature(s)?
>
> I'm not sure I understand the question? An RRSIG is for an entire
> RRset, so either one could add the signature to the RRset object or
> leave them as separate RR.

Well, yes, that's the question :-) And if you make them part of the RRset
object, how do you do so? and if they aren't part of the RRset object then
you have to have a special way to separate RRSIGs based on their
type-covered field. etc.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Plymouth, North Biscay: Variable 3 or 4, becoming easterly or southeasterly 4
or 5 later. Moderate, occasionally slight. Fog patches. Moderate, occasionally
very poor.

v2.23.0 | Report a Bug | By Email