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

Warren Kumari <> Tue, 27 November 2018 02:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C1C30130E18 for <>; Mon, 26 Nov 2018 18:05:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.359
X-Spam-Status: No, score=-3.359 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, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id XvfvJe_0ipDO for <>; Mon, 26 Nov 2018 18:05:53 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::434]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BC87E130E16 for <>; Mon, 26 Nov 2018 18:05:51 -0800 (PST)
Received: by with SMTP id t27so13021798wra.6 for <>; Mon, 26 Nov 2018 18:05:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1ScqQFCJYtX9751tvpAmV0R7C1JXURgMbeUl6PkCCPs=; b=QY8PepToR0gGaxPtFHvsCAszHleAzGYY9yBYzPsYaAUH/CA51fy0l2mLZzI1iZL+pn zqDy+9d8PUAsOGv6KLZBs4tp1ZnRdN0M/rAY/LkrzGpJiVW/tmqIL6NAzqy3/b0elr4o qAmDGTLEu2WJ5OUkFcZI29Z3iU6fsu/wgmrEW+PGyxb6P+D6N4AAUZI2byib51ZthjhR QuMhvNeIBm2TcUGAvAgErL6SurrzcXSTTVbU6/zxbIuk1FqsJb984yy7K4wVct4+HJbr xffevRknlAcIHc6KskqQ55yu7VhXcehzO+qXqAFmLjtG+3GZosmJwotH6l8uFNQ//D4g 5ykw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1ScqQFCJYtX9751tvpAmV0R7C1JXURgMbeUl6PkCCPs=; b=cMCWd8htD/l7gEs91+ZmDiyC0FqPXAQhrkE1kjHd8vLluWvH09cILBnA780LCb+NQn ZcCcttbAueYt+5po13yJ46t7dUClAS4hImyZNT7mAntYWPeR7uqF6RVrTfNFHryVMf3I XZcgo1GXoYrY0JPXyUYTx3eMDIz7vZwTKkVTprl7TPZq6N8Aff8nt84lPC9+25BXsyyA BfF53MbTJclUyamk8xWnQIEJto/Zu1HaTpd6chQ+jOXuYkO4fbSGqc+WGenA7nqhhTKN VgooPaDKlFPvbaNP9/ggZES6vs17u097gei7IzPXevRUE8k3C4NAcRgZjsXe+MZyzNcN gOgA==
X-Gm-Message-State: AA+aEWZY/1PNkJe580UBFbLmOGj3fET7FMr3OlyL8q4q9c6wcTlAcfwp BPEaDavnxIaF475e/VdkLR2k84Qh40obzVDItQr7gQ==
X-Google-Smtp-Source: AFSGD/UPRXJbRtlajo3d/9pp5XfOueIQZNtJZzvLKSW2k29U1b9TSt0dSZNkjJ7R3gJy/g8qxydCUn8eY66UYsI8gAw=
X-Received: by 2002:adf:f0c5:: with SMTP id x5mr380324wro.77.1543284349760; Mon, 26 Nov 2018 18:05:49 -0800 (PST)
MIME-Version: 1.0
References: <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
From: Warren Kumari <>
Date: Mon, 26 Nov 2018 21:05:13 -0500
Message-ID: <>
To: Paul Hoffman <>
Cc: Alexey Melnikov <>, dnsop <>, The IESG <>
Content-Type: multipart/alternative; boundary="000000000000748fcc057b9be3aa"
Archived-At: <>
Subject: Re: [DNSOP] [Ext] Alexey Melnikov's Discuss on draft-ietf-dnsop-dns-capture-format-08: (with DISCUSS and COMMENT)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 27 Nov 2018 02:05:55 -0000

On Mon, Nov 26, 2018 at 8:58 PM Paul Hoffman <> wrote:

> On Nov 26, 2018, at 5:44 PM, Warren Kumari <> wrote:
> > Actually, there is - the tcpdump man pages (and actually all of their
> documentation!) lives in github - the version that this document references
> is:
> >
> Note that this URL is basically useless in an RFC that uses the current
> format: it is 135 characters long. It's cute that it points to the correct
> man page, but really not useful as a reference in an RFC as they are
> currently constituted.
> Going back to Warren's original concern:
> > 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?
> For the CollectionParameters map, a "filters" item lists the filters that
> are used for this capture file. It truly doesn't matter if the reference is
> updated later: the capture still has the same filter string.
> Thus, it is quite sufficient for this reference to be:
> That is a useful reference for an implementer, and it fits in an RFC.

... 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.


> --Paul Hoffman

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