[pcap-ng-format] New Version Notification for draft-tuexen-opsawg-pcapng-02.txt

Michael Tuexen tuexen at fh-muenster.de
Sun Oct 18 09:56:01 UTC 2020


> On 18. Oct 2020, at 10:47, Guy Harris <gharris at sonic.net> wrote:
> 
> On Oct 18, 2020, at 1:32 AM, Michael Tuexen <tuexen at fh-muenster.de> wrote:
> 
>> Just a note. I'm using the .xml format and put a link in the README.md, which shows the .txt or .html file based on the current .xml.
> 
> Yes, that's what we were doing for the pcapng draft before switching to kramdown-rfc2629, and what we're still doing for the pcap draft, because I haven't yet switched it to kramdown-rfc2629.
> 
> That works for xml2rfc XML; it doesn't work for kramdown-rfc2629, because xml2rfc.tools.ietf.org doesn't have a converter that goes from kramdown-rfc2629 directly to HTML/PDF/text.
Yepp. Since the RFC Editor works with .xml I can understand that.

Have you given up on using .xml for the pcap ID or would you accept a PR to bring it in sync with
v3 of .xml.

Best regards
Michael

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5257 bytes
Desc: not available
URL: <http://www.winpcap.org/pipermail/pcap-ng-format/attachments/20201018/c81a272c/attachment-0001.bin>


More information about the pcap-ng-format mailing list