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

Alexey Melnikov <aamelnikov@fastmail.fm> Tue, 27 November 2018 11:05 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 09C2E128DFD; Tue, 27 Nov 2018 03:05:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=aVCLH9LA; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ynYxnIjj
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 A8Pb9bKMAw5i; Tue, 27 Nov 2018 03:05:55 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B5D5128CE4; Tue, 27 Nov 2018 03:05:55 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 5811221F24; Tue, 27 Nov 2018 06:05:54 -0500 (EST)
Received: from web5 ([10.202.2.215]) by compute7.internal (MEProxy); Tue, 27 Nov 2018 06:05:54 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= message-id:from:to:cc:mime-version:content-transfer-encoding :content-type:date:subject:references:in-reply-to; s=fm1; bh=K6L cfBtYRCCjukwC4prviFa8v5lj5OG1XloeWAB8n3A=; b=aVCLH9LAKXpnBXbf05U KOOOxqFM7uB1RaeR4cuE2PKyQEo5RWPPfDJY2aora1womBAj/uJnQ+CHWeIbt+Hs SOL1aQyC18n0IEYjML0I0yaRYz5x9vdCvwSnnIjCvXrI0ubviEDQByanaLDW1u5Y LiHDw6Tagg26etdQSYPY9mfdyQMEXrmvBwNoZKDcfXWLBfVYJoKKAmgB/AXzKVog gV2463WZvBphcLmeg5t1hDvAnCSiEaSao50g0aJ5vGJ9KUo1b3osf+BbyUdKwf/N KiCkKlx4V21JS5YqPsBVX9bYzuSZuWyfyHEBusphO/DuE/51oC+XaQRmQ0QBtjEG uyw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=K6LcfBtYRCCjukwC4prviFa8v5lj5OG1XloeWAB8n 3A=; b=ynYxnIjjgvKNjUCsTpN1QkVV27kqr73+lKfQSPs9BexPsAuB1U1p7z0sH qbs1Npjk1+TkKqMrokxFvxkXiYVD73epU+7kSBLqq+ocH7LgwZzfw+u5ppmAeedh 7Vz7XrlMlRrlQ/GTwUxZUj7afQqHI6YwpQp3li3GXknZhT9gSLIYDUAo7DTCB7Xu bzqEnDyc3Y98dQkc6Z+A/yVBFLADpwAgTWJe4+Ppyje1MQWkl23lcLhZsXrIE+VL 2jL0u5WbbRAoYxHxTZTfwJcq7k2XQlRtApPRibkQpqqIbHQ2uk5KDX4QxmHWp4gI Ms1DiSOPm/YWPanPt12SPwuAVbRMg==
X-ME-Sender: <xms:ESX9W0Hizqhg4c12HSCsCjXRZnht7LSAWqTKM5mr1M5mJB-z71AzzQ>
X-ME-Proxy: <xmx:ESX9W2mkDscKdyhS9JV0KzxZJfE4AHBGVpMRlixqlPx_rIrhpxcfMQ> <xmx:ESX9W3LGq2ulTI0KrjycgNDAZ3xCgVsm_PHLHP1Lgnk5kG79bTqcAQ> <xmx:EiX9W765-18XEuIawb5nOM5p5sxLMYrVwyn3iR2Q1_etXwQ0iX4M7w> <xmx:EiX9W73oZpV_NX3Z6NtRTK41cRolNQmZYzD4eEPkEInej8C3x9Ggdw> <xmx:EiX9WxddL5TZc8KWvzG0t_b8npUkh6dcRvnrN-ebwuPZUoGeJrjt6g> <xmx:EiX9W-x44Hy1EwGk6B6U3B5qc9A2-KX6ziaeKRsdjCb4-Pw8o2p8TA>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id D96089E28C; Tue, 27 Nov 2018 06:05:53 -0500 (EST)
Message-Id: <1543316753.3027969.1590279856.6CEC8EC7@webmail.messagingengine.com>
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: Paul Hoffman <paul.hoffman@icann.org>, Warren Kumari <warren@kumari.net>
Cc: dnsop <dnsop@ietf.org>, The IESG <iesg@ietf.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-3449945b
Date: Tue, 27 Nov 2018 11:05:53 +0000
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> <ca821f6f-26de-f2f8-7e63-d9cb8dcfdf60@rfc-editor.org> <CAHw9_i+6MRiGOeDh5+5tVwajFhCCbgRgSnio04yqUGLbHKyHEw@mail.gmail.com> <CAHw9_iLxsEw4PQ4=Vu1ghhGGEPvS8pBuB9G7buiFMDjNB=m1cg@mail.gmail.com> <FA6BBBB2-D535-4597-8923-5307390D9462@icann.org> <CAHw9_iKEsfjpC2FzjKaaUz=oR_S9WNPNg+EuvBmi_n_CUpC8mQ@mail.gmail.com> <7E59D98E-7350-43FB-BE47-4E2691D5872F@icann.org>
In-Reply-To: <7E59D98E-7350-43FB-BE47-4E2691D5872F@icann.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/-9unmvte5LcLsN1zkJEEIdS1m80>
Subject: Re: [DNSOP] [Ext] 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: Tue, 27 Nov 2018 11:05:57 -0000

Hi Paul,

On Tue, Nov 27, 2018, at 2:10 AM, Paul Hoffman wrote:
>    | filter           | O | T | "tcpdump" [pcap] style filter for      |
>    |                  |   |   | input.                                 |
> 
> 
> On Nov 26, 2018, at 6:05 PM, Warren Kumari <warren@kumari.net> wrote:
> > ... that is where we started.
> > The concern was what happens if there are new filters added, and implementations written don't know how to deal with them.
> 
> New filters being added to tcpdump (or even removed) doesn't affect a C-
> DNS application from reading or writing that field. It's just a text 
> string. 

I think this depends on how the field is used.

If you want to write an application that validates or does something with this field, that wouldn't be true.
If you think that writing such an application is a dumb idea, then the draft should clearly state that.

Best Regards,
Alexey