IETF Logo Mail Archive

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

Eric Rescorla <ekr@rtfm.com> Tue, 27 November 2018 15:02 UTC

Return-Path: <ekr@rtfm.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 8715E130E98 for <dnsop@ietfa.amsl.com>; Tue, 27 Nov 2018 07:02:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.358
X-Spam-Level:
X-Spam-Status: No, score=-3.358 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.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 x7fiFtgTGkLh for <dnsop@ietfa.amsl.com>; Tue, 27 Nov 2018 07:02:41 -0800 (PST)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (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 CB544130EB2 for <dnsop@ietf.org>; Tue, 27 Nov 2018 07:02:40 -0800 (PST)
Received: by mail-lj1-x229.google.com with SMTP id u6-v6so20340537ljd.1 for <dnsop@ietf.org>; Tue, 27 Nov 2018 07:02:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qUxfbCbWx6zT3PLP/IUFpOTOUnY87m1v4OvytbQLOpE=; b=1hg5/5Sbtw8KTwH0fQ51r1jQPMt2+uYGvXHy95nsK9CeSYOzYy8x5RGor3/43J/ux+ 21oZCRAO6MaydDvRc0mC/nm1KzOw0iePVlLUGGsI3IfL6XVzbuSpwm4qt/pEX/dtTwvC PgjitEOybUtv6vpLHOYT2uCboGTuVDJW58kasHkXEiHrchXyS/2M7MDu9lLlI5WjU58I NseEoUbC/RJxXDo5MaQBWkNRdmieCdjUUdS9ZzK34U3jKTITuPyokhikhISDRgVx6LVN +sgM4osULhB3KTylSVx7Se/BYjmw6qcgLuWOBNKcrcWKgYdE79JME1xDcABkCdV9Kygy pvGA==
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=qUxfbCbWx6zT3PLP/IUFpOTOUnY87m1v4OvytbQLOpE=; b=YuFbH9tg719ZYcfXoISu3kF99aQlKlXK/16JSb+IAZ3WOvDBLNVjzaXSvGuXTt9y5d e3RGS8g0OPHRq7u+LUoF19vgmssdIP1feVoAyHsfQfi6CQr3hndg0nG3/NfcaiN68KAf h+OU7R9DB7lt/nNVNpqmph4dhffj4im2fQmvTrdA9lSjpCcuO4tFM65v0TZxv+90zmrm Zj169M78edWRNetFgWc0qgSBoAey665wvDzahLmz/thbtjEHvtuby2JiQ6yS1mP9dDrQ PwKan7i7fEDO8xgJaLAZ33EFDNM1q/9UzUIWr7DC3nMXWaQ0Fy14F+MpaLcLwkUn7+SW CGdg==
X-Gm-Message-State: AA+aEWYoJpHjqPcYL0LweayNpmd57/pSxL4/DDWf8m5CGbzYXKQWWdLm U0CdGg7y++EA1cv00MEsxM314Q9Z+LBibCQUIcpsUg==
X-Google-Smtp-Source: AFSGD/WrtpaCY+yHxMSo/jwHchh1+pLb0bZVLi9W88qMBQLDbRZkXCK9B4UUESqEWDqIcILN/op9Q/AOT+i5tOQI03U=
X-Received: by 2002:a2e:6503:: with SMTP id z3-v6mr19720878ljb.153.1543330958925; Tue, 27 Nov 2018 07:02:38 -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> <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> <1543316753.3027969.1590279856.6CEC8EC7@webmail.messagingengine.com> <88A3AB64-7E17-4EB8-A6FC-1D425F3F7AFF@icann.org>
In-Reply-To: <88A3AB64-7E17-4EB8-A6FC-1D425F3F7AFF@icann.org>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 27 Nov 2018 07:02:01 -0800
Message-ID: <CABcZeBPD-mgQpLmn9YSUJDzUP9dGEzjN6HsAdQ57+Dgwe4yOuQ@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@icann.org>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, dnsop WG <dnsop@ietf.org>, Warren Kumari <warren@kumari.net>, IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000093f810057ba6bd4d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ThJOHUtm2I4I3hZIKIBzFPvjgBM>
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 15:02:54 -0000

On Tue, Nov 27, 2018 at 7:00 AM Paul Hoffman <paul.hoffman@icann.org> wrote:

> On Nov 27, 2018, at 3:05 AM, Alexey Melnikov <aamelnikov@fastmail.fm>
> wrote:
> >
> > 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.
>
> My interpretation of the spec has been all along that this field, as well
> as the other fields in CollectionParameters, were informational for
> whomever is looking at the particular capture. "Parameters relating to how
> data in the file was collected" seemed sufficient for that. If the authors
> added "These parameters are informational are only informational and cannot
> necessarily be validated by looking in the data captured", would that
> satisfy your concern?
>

Hmm... I don't really think so. It seems to me that the semantics here are
"this is the filter string that was applied" and because that's effectively
a program, in order to interpret it you need to know what language it was
in.

-Ekr


> --Paul Hoffman

v2.23.0 | Report a Bug | By Email