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

Warren Kumari <warren@kumari.net> Wed, 21 November 2018 17:34 UTC

Return-Path: <warren@kumari.net>
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 75F41130E1C for <dnsop@ietfa.amsl.com>; Wed, 21 Nov 2018 09:34:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.459
X-Spam-Level:
X-Spam-Status: No, score=-1.459 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 bTz4XRo9O8xL for <dnsop@ietfa.amsl.com>; Wed, 21 Nov 2018 09:34:20 -0800 (PST)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DA0D12426E for <dnsop@ietf.org>; Wed, 21 Nov 2018 09:34:20 -0800 (PST)
Received: by mail-wm1-x32b.google.com with SMTP id s11so6621575wmh.1 for <dnsop@ietf.org>; Wed, 21 Nov 2018 09:34:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hQfri6w1XnYkvXdaGDGBxuwz3O5G4R7Rdqqry6DFCJ4=; b=11DXwu06A/vu4QRi7QJWJXV3iVoBXafJvFO7dJUobZsZAuDeuJ27fEdADQf0m78sUB JTCzCiuLtlaD2heCu5mmY5IxxibT8i2DsAphpOlRs3PtZcsg7PkUhCO4uOj1l4CHj7MW TA+eaVHt/sd5heIwIME7jsVjFryMqIqg0xOt5CKtsf5OA/t2XaLriapHL3663kIyBrtp Y4QC0L7ckYV80DLVFa61nmTR4uBAmynFpizEHJUXbxARuXT+1LZct8j+w/nXZj0mYrEy gC+ulCD20M7+4WSR1pU9tP9tOYsn2DZbFF7XZkl8Wu2A968dLfjPfFYo0HHo/3gM9QMJ qUMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hQfri6w1XnYkvXdaGDGBxuwz3O5G4R7Rdqqry6DFCJ4=; b=jrRI8xDo+ah+C3rB6SP/b2opXOYQ02mhf7JtZgFs7wcr3Nv8yysYIPWjUnn6DjuWWq DO+R0JYXU2U+QXD7FRl81mcxh77SGkkucsSiiVzf5od7aSwO9VaMZtdSUUh8kaM6M0fD WnfsYC+/qEj9ZbBBoXywGmeszwo5B1ddHBe3TrR64hWtgxQdO6zGkJA5Y77Eo8txncW6 GGCuRl43mrwDDe3tcnxPgGMih9upEBGU+pZThTS3NjAibbzxeH31U2pCWQA/G8BlPF7c 8kNG7ahufoCnlwifM6yONXcukh+TMTPos6SGCBlxqxQ55xJjJUzeSVGYluaNnrZEeZ2y wAmg==
X-Gm-Message-State: AA+aEWZyJIg6CkZJxeFZEo7zP4MPvZC39cAh6Lj/A1u5aj+SWzyXibC3 7HJxpqmLIIovPjuRSpo2FtvRW1KWaAOnaouWU7SC6g==
X-Google-Smtp-Source: AFSGD/V04MAoGCLgQcrOpSnw24ooYile467sl0BZd8XM6jkUcsOn7JJtZ3rdwyac4KBf/JUC2uEMu9/8ylcmJ4Ep+Ic=
X-Received: by 2002:a1c:184:: with SMTP id 126mr2941596wmb.24.1542821658461; Wed, 21 Nov 2018 09:34:18 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <4D2E72B7-1EEE-4BD2-8200-B688074AE5E3@sinodun.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 21 Nov 2018 12:33:40 -0500
Message-ID: <CAHw9_iLuNYHHnMz_jgOA2JwTDNWUkRb9TVkT8zwKedNT9LUBmQ@mail.gmail.com>
To: Sara Dickinson <sara@sinodun.com>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, Tim Wicinski <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-dnsop-dns-capture-format@ietf.org, "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
Content-Type: multipart/alternative; boundary="000000000000e795d8057b30286a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/V4RcuAlIb0GuR6VMTgdhoImz-Kc>
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:34:23 -0000

[ - DNSOP (for clutter), +Heather / RFC Editor for sanity :-P ]

On Wed, Nov 21, 2018 at 9:47 AM Sara Dickinson <sara@sinodun.com> wrote:

>
>
> 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
>
> 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 (it seems to be under
the BSD license) and put it somewhere on 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....

W




>
> Sara.
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>


-- 
I don't think the execution is relevant when it was obviously a bad idea in
the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair of
pants.
   ---maf