Re: [DNSOP] Alexey Melnikov's Discuss on draft-ietf-dnsop-dns-capture-format-08: (with DISCUSS and COMMENT)

Sara Dickinson <sara@sinodun.com> Wed, 21 November 2018 17:58 UTC

Return-Path: <sara@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 8A25C130DC1; Wed, 21 Nov 2018 09:58:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sinodun.com
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 m7PosAyEY4Xz; Wed, 21 Nov 2018 09:58:12 -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 1411B128AFB; Wed, 21 Nov 2018 09:58:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sinodun.com ; s=balrog-2018; h=To:Date:Subject:From; bh=kHoPdDAxoHiMRF1Q9c9HpHFiq1VDCi98Yo0Mxh2+Aug=; b=jBSUZ0FCgzx+ahPiI4E/ff6Tcy lVp3ZKeHK6CSOQBcF61LeIj2LV2axi0h8X50cd0c1lLhVrt4OT7AoMfcI9WYgaCw6f19qeBQeTKdU B0xL1Cdw6htuVe+Af1JGCrHPrYO1GwdOs/rdJvPYhXrk0NgQgVxgQ3OVGYqIyEHKSoayBKgqfPvUa gGuzIzKN/vvLkRE3AmdqWmf1hgZH5lF9q06QaYlJdb3rh2G1G2XP5sFDfBmnhMPcR+PdcIcrYxfns UhIf5rMUOcaO+yQCRpasD34OAlm5cmedAtwap/eQu64nm4OuVIP4s+6+JBYox2PP6EFcRHNPyFAhA ++v4twwQ==;
Received: from [2001:b98:204:102:fffa::409] (port=55596) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <sara@sinodun.com>) id 1gPWlI-0004aT-H6; Wed, 21 Nov 2018 17:58:08 +0000
From: Sara Dickinson <sara@sinodun.com>
Message-Id: <7513F0ED-9F8D-4EB1-A23B-DC6E4350D49F@sinodun.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_BF9156D8-4887-4B3E-A955-46E623B705E4"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Date: Wed, 21 Nov 2018 17:57:58 +0000
In-Reply-To: <CAHw9_iLuNYHHnMz_jgOA2JwTDNWUkRb9TVkT8zwKedNT9LUBmQ@mail.gmail.com>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, draft-ietf-dnsop-dns-capture-format@ietf.org, Alexey Melnikov <aamelnikov@fastmail.fm>, dnsop <dnsop@ietf.org>, "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>, The IESG <iesg@ietf.org>
To: Warren Kumari <warren@kumari.net>
References: <154265985064.16386.5550594646862412061.idtracker@ietfa.amsl.com> <BF3169F5-E68D-4C68-80D7-1772E7A9EDEA@sinodun.com> <1542811322.1310112.1584530512.0785569A@webmail.messagingengine.com> <4D2E72B7-1EEE-4BD2-8200-B688074AE5E3@sinodun.com> <CAHw9_iLuNYHHnMz_jgOA2JwTDNWUkRb9TVkT8zwKedNT9LUBmQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.100.39)
X-BlackCat-Spam-Score: 14
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/8YgtDpDfb1Cqq3CUqssC3HzszxI>
Subject: Re: [DNSOP] Alexey Melnikov's Discuss on draft-ietf-dnsop-dns-capture-format-08: (with DISCUSS and COMMENT)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2018 17:58:16 -0000


> On 21 Nov 2018, at 17:33, Warren Kumari <warren@kumari.net> wrote:
> 
> [ - DNSOP (for clutter), +Heather / RFC Editor for sanity :-P ] 
> 
> On Wed, Nov 21, 2018 at 9:47 AM Sara Dickinson <sara@sinodun.com <mailto:sara@sinodun.com>> wrote:
> 
> 
>> On 21 Nov 2018, at 14:42, Alexey Melnikov <aamelnikov@fastmail.fm <mailto:aamelnikov@fastmail.fm>> wrote:
> 
> Thanks for the quick response.
> 
>> 
>> Hi Sara,
>>>> 
>>>> 1)
>>>> 
>>>> In 7.4.2:
>>>> 
>>>>   | filter           | O | T | "tcpdump" [pcap] style filter for      |
>>>>   |                  |   |   | input.                                 |
>>>> 
>>>> This makes the [pcap] reference Normative. If you don't want to do that, please
>>>> fully specify syntax in this document.
>>> 
>>> Is that true if it is an optional field? 
>> Yes, optionallity of a field doesn't make its full specification optional.
> 
> In which case it seems we can either include a more specific normative reference here to this page:
> http://www.tcpdump.org/manpages/pcap-filter.7.html <http://www.tcpdump.org/manpages/pcap-filter.7.html>
> 
> or reproduce this page in an appendix. I’d prefer the former unless a reference to such a web page would prove problematic as a normative reference? 
> 
> We discussed this on the telechat, and I took the action to try look into this.
> One of the concerns with a normative reference to the webpage is what happens if it is updated to add a new primitive - is it allowed? If someone implements this on Thursday, can they still claim conformance if a new primitive is added on Friday?
> 
> What we made up on the call was to simply grab a copy of http://www.tcpdump.org/manpages/pcap-filter.7.html <http://www.tcpdump.org/manpages/pcap-filter.7.html> (it seems to be under the BSD license) and put it somewhere on ietf.org <http://ietf.org/>, so we have a stable snapshot to reference, and ask you to point to that.
> But, this was simply us making stuff up on the fly - I'm hoping that the RFC Editor can tell us if this is sane or the worst idea ever, or what….

Thanks for the update, we’ll hold off till we hear more on this. 

Sara.