Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-capture-format-05.txt

Jim Hague <jim@sinodun.com> Wed, 28 February 2018 15:56 UTC

Return-Path: <jim@sinodun.com>
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 DBCDE12EB10 for <dnsop@ietfa.amsl.com>; Wed, 28 Feb 2018 07:56:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 RVxa2TgUHQIw for <dnsop@ietfa.amsl.com>; Wed, 28 Feb 2018 07:56:20 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 769FF12EB27 for <dnsop@ietf.org>; Wed, 28 Feb 2018 07:56:16 -0800 (PST)
Received: from [2001:b98:204:102:fff1::11] (port=61642 helo=Jims-iMac.local) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <jim@sinodun.com>) id 1er45X-0004vd-2x; Wed, 28 Feb 2018 15:56:15 +0000
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Sara Dickinson <sara@sinodun.com>
Cc: IETF DNSOP WG <dnsop@ietf.org>
References: <151930246857.21149.14743687777831082425@ietfa.amsl.com> <522CCFCA-F01F-4D68-A7FB-D14B0F14C07D@sinodun.com> <20180223125621.ec7ndguzy4obj5na@nic.fr>
From: Jim Hague <jim@sinodun.com>
Organization: Sinodun Internet Technologies Ltd.
Message-ID: <f06601c8-c80d-c288-81ee-49a16cbf0c43@sinodun.com>
Date: Wed, 28 Feb 2018 15:56:11 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <20180223125621.ec7ndguzy4obj5na@nic.fr>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-BlackCat-Spam-Score: 0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/zQYcUDSOiumq37dzkK6leuzPAd8>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-capture-format-05.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 28 Feb 2018 15:56:22 -0000

On 23/02/2018 12:56, Stephane Bortzmeyer wrote:
> On Thu, Feb 22, 2018 at 12:31:29PM +0000,
>  Sara Dickinson <sara@sinodun.com> wrote 
>  a message of 51 lines which said:
> 
>> We have an update to draft which we hope captures all the comments
>> to-date.
> 
> I think so, too. At least, it captured mine :-)

Good. And thanks for the feedback. We've noted your answers to our
'QUESTIONS' and other comments.

>>  QUESTION: No EDNS(0) option currently includes a name, however if one
>>  were to include a name and permit name compression then both these
>>  mechanisms would fail.
> 
> Is it even possible? RFC 6891 does not mention it. But it says
> "OPTION-DATA. MUST be treated as a bit field." which seems to imply
> that storing the entire OPT RR, or the option data, as a blob, is
> perfectly OK.

I am also unclear as to whether storing a compressed name in an option
is permitted. As you say, the language seems to imply treating the data
as a blob is the only option, which suggests that it's not permitted.
We'd be interested in any contrary opinions.
-- 
Jim Hague - jim@sinodun.com          Never trust a computer you can't lift.