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

Paul Hoffman <> Tue, 27 November 2018 01:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 98ED5130E04; Mon, 26 Nov 2018 17:58:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ftzMtgg-jMeu; Mon, 26 Nov 2018 17:58:10 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A608D130E08; Mon, 26 Nov 2018 17:58:10 -0800 (PST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 26 Nov 2018 17:58:08 -0800
Received: from ([]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([]) with mapi id 15.00.1367.000; Mon, 26 Nov 2018 17:58:08 -0800
From: Paul Hoffman <>
To: Warren Kumari <>, Alexey Melnikov <>
CC: dnsop <>, The IESG <>
Thread-Topic: [Ext] [DNSOP] Alexey Melnikov's Discuss on draft-ietf-dnsop-dns-capture-format-08: (with DISCUSS and COMMENT)
Thread-Index: AQHUhfSk5+4JD+NCAkiO0OSY4uznIQ==
Date: Tue, 27 Nov 2018 01:58:08 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/signed; boundary="Apple-Mail=_5A5AB608-FBB7-4647-8F70-59D2F6A1CA82"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
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 01:58:13 -0000

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.

--Paul Hoffman