IETF Logo Mail Archive

Re: [DNSOP] DNS-in-JSON draft

Shane Kerr <shane@time-travellers.org> Tue, 06 September 2016 04:38 UTC

Return-Path: <shane@time-travellers.org>
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 551AD12B12F for <dnsop@ietfa.amsl.com>; Mon, 5 Sep 2016 21:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 EQQoLYSsQ2cp for <dnsop@ietfa.amsl.com>; Mon, 5 Sep 2016 21:38:52 -0700 (PDT)
Received: from time-travellers.nl.eu.org (c.time-travellers.nl.eu.org [IPv6:2a02:2770::21a:4aff:fea3:eeaa]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B348B12B125 for <dnsop@ietf.org>; Mon, 5 Sep 2016 21:38:51 -0700 (PDT)
Received: from [240c:f:1:4000:8a63:3b33:66a5:1600] (helo=pallas.home.time-travellers.org) by time-travellers.nl.eu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <shane@time-travellers.org>) id 1bh89o-00075k-4c; Tue, 06 Sep 2016 04:38:48 +0000
Date: Tue, 06 Sep 2016 12:38:41 +0800
From: Shane Kerr <shane@time-travellers.org>
To: Tony Finch <dot@dotat.at>
Message-ID: <20160906123841.2bd451af@pallas.home.time-travellers.org>
In-Reply-To: <alpine.DEB.2.11.1609051121080.28546@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>
X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.30; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; boundary="Sig_/Ttnwr4luyQ_MP9K/cvdeBla"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/48A0LtEj_TPcf7wLIcXFKVHG0t4>
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 04:38:53 -0000

Tony,

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.

Probably it makes sense to include an example though.

Cheers,

--
Shane

v2.23.0 | Report a Bug | By Email