IETF Logo Mail Archive

Re: [OPSAWG] New Version Notification for draft-tuexen-opsawg-pcapng-02.txt

Guy Harris <gharris@sonic.net> Mon, 28 September 2020 20:41 UTC

Return-Path: <gharris@sonic.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8D03A13E2 for <opsawg@ietfa.amsl.com>; Mon, 28 Sep 2020 13:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 wIXTs5Dw66ej for <opsawg@ietfa.amsl.com>; Mon, 28 Sep 2020 13:41:56 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (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 4934F3A0ABD for <opsawg@ietf.org>; Mon, 28 Sep 2020 13:41:56 -0700 (PDT)
Received: from [192.168.42.85] (173-228-4-241.dsl.dynamic.fusionbroadband.com [173.228.4.241]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id 08SKfpWr020209 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 28 Sep 2020 13:41:52 -0700
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Guy Harris <gharris@sonic.net>
In-Reply-To: <100954A4-FAA0-4E40-B592-5F208DAB5F68@fh-muenster.de>
Date: Mon, 28 Sep 2020 13:41:51 -0700
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, pcap-ng-format@winpcap.org, opsawg@ietf.org, Jasper Bongertz <jasper@packet-foo.com>, tcpdump-workers@lists.tcpdump.org, Fulvio Risso <fulvio.risso@polito.it>, Gerald Combs <gerald@wireshark.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9721F8A-B0D9-4D9A-8FB8-BD7C185A6F76@sonic.net>
References: <160131683320.30001.4858487168061369615@ietfa.amsl.com> <31134.1601317608@localhost> <100954A4-FAA0-4E40-B592-5F208DAB5F68@fh-muenster.de>
To: Michael Tuexen <tuexen@fh-muenster.de>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
X-Sonic-CAuth: UmFuZG9tSVZLuS474GHa7YZ/irIh5nC9rhehYExLEQtL7GuVHoHh2vCYLK+EtHYA6We1qfCLMHr/vKf/4VR6fDaQT9JPJpuJ
X-Sonic-ID: C;ONWTCcsB6xGiPP8/xdyLyg== M;QrvaCcsB6xGiPP8/xdyLyg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/4zKwu3PSFSq1zofaaojIP0aFrJ0>
X-Mailman-Approved-At: Wed, 30 Sep 2020 00:39:16 -0700
Subject: Re: [OPSAWG] New Version Notification for draft-tuexen-opsawg-pcapng-02.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Sep 2020 20:49:42 -0000

On Sep 28, 2020, at 12:06 PM, Michael Tuexen <tuexen@fh-muenster.de> wrote:

> On 28. Sep 2020, at 20:26, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
>> internet-drafts@ietf.org wrote:
>>> Diff:
>>> https://www.ietf.org/rfcdiff?url2=draft-tuexen-opsawg-pcapng-02
>> 
>> Hi, I have converted the xml to markdown.
> 
> Why? If we want to publish this, it will be published in xmlv3. So
> better to use that format earlier...

There are tools to convert Markdown to v2 or v3 RFC XML:

	https://www.rfc-editor.org/pubprocess/tools/

so:

	1) is it easier to edit Markdown or RFC XML?

	2) is Markdown rich enough to do everything we want to do?

For 2), I note that

	https://github.com/pcapng/pcapng/blob/master/draft-tuexen-opsawg-pcapng.md

has a bunch of stuff that GitHub isn't treating as markup, such as the stuff prior to the "Introduction" heading, and the tags such as "{::boilerplate bcp14}".  Is that an extension of Markdown not supported by GitHub's Markdown renderer but supported by some Markdown-to-RFC XML converter, or incomplete parts of the RFC XML to Markdown conversion?

In addition, the XML version at

	https://github.com/pcapng/pcapng/blob/master/reference-draft-tuexen-opsawg-pcapng.xml

has some additional Decryption Secrets Block secret formats.  Those have data formats that *themselves* call for figures, and I'd been trying, at one point, to determine how to do that in RFC XML v2 format - it might require v3 format.  Can that be handled with Markdown?

v2.23.0 | Report a Bug | By Email