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 14:47 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 9F17B1241F6; Wed, 21 Nov 2018 06:47:29 -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 ktE1ZGQkep2w; Wed, 21 Nov 2018 06:47:27 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86: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 C2EEA12D84D; Wed, 21 Nov 2018 06:47:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sinodun.com ; s=haggis-2018; h=To:Date:Subject:From; bh=fMqdjN2G63jWdHDJYMf7RAgju5b0x7JPdOeMemoaZpk=; b=o812k0v0vmDolDBonB+RBaJ1Qf l7WCfIrWCi2fyxOEMI5uqbDbUUR7ta1t9ma6FtpXLxmgWcFVtMa5sGBOP+Ql3UE12nMUlmqGb1Mfz MkjtzFhzC1XEgv1LEH93eG02dy8Nemc8+b0jeok+yyGyTOeHCsAgnnTyOow6iBXsSb9G46Lrm18u/ /41mYLLkzYGZrhNAAvlWOaujA3L2dGVRYdJrEkWUhsK07nA4lPbw+K7UmY+pBMQAsjon0jyvQaxfu fwDgXumxC4jAGgoFC1cECmyUg/b5/NDyuw4AfLFRCl5PjmzWYXJswonGXhb7jhWvcRg6wJuxFbwvw PcWq1laQ==;
Received: from [2001:b98:204:102:fffa::409] (port=54482) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <sara@sinodun.com>) id 1gPTml-0007WJ-IF; Wed, 21 Nov 2018 14:47:24 +0000
From: Sara Dickinson <sara@sinodun.com>
Message-Id: <4D2E72B7-1EEE-4BD2-8200-B688074AE5E3@sinodun.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4157690E-435D-4767-8309-334210000E5A"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Date: Wed, 21 Nov 2018 14:47:22 +0000
In-Reply-To: <1542811322.1310112.1584530512.0785569A@webmail.messagingengine.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-dnsop-dns-capture-format@ietf.org, Tim Wicinski <tjw.ietf@gmail.com>, dnsop-chairs@ietf.org, dnsop@ietf.org
To: Alexey Melnikov <aamelnikov@fastmail.fm>
References: <154265985064.16386.5550594646862412061.idtracker@ietfa.amsl.com> <BF3169F5-E68D-4C68-80D7-1772E7A9EDEA@sinodun.com> <1542811322.1310112.1584530512.0785569A@webmail.messagingengine.com>
X-Mailer: Apple Mail (2.3445.100.39)
X-BlackCat-Spam-Score: 14
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/1pfZG6trlkDBqhAgi5NTVCdio-U>
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 14:47:30 -0000


> On 21 Nov 2018, at 14:42, Alexey Melnikov <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? 

Sara.