[xml2rfc] V3 running headers can thwart rfcdiff
Carsten Bormann <cabo@tzi.org> Mon, 24 August 2020 05:09 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E344B3A0A1C for <xml2rfc@ietfa.amsl.com>; Sun, 23 Aug 2020 22:09:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level:
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 KFmCQMLNJNYt for <xml2rfc@ietfa.amsl.com>; Sun, 23 Aug 2020 22:09:16 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13E1D3A0A13 for <xml2rfc@ietf.org>; Sun, 23 Aug 2020 22:09:15 -0700 (PDT)
Received: from [192.168.217.102] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4BZgCD0BYpzyTd; Mon, 24 Aug 2020 07:09:12 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 619938551.6495039-781b2303b22bbb8a0de1708e9aa32ebb
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Date: Mon, 24 Aug 2020 07:09:11 +0200
Message-Id: <B7C10A7E-87E7-4D0E-AADB-BA71DD004CDB@tzi.org>
To: XML2RFC Interest Group <xml2rfc@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/D2-0phsOqDE3zsDUNYofdUnwhQc>
Subject: [xml2rfc] V3 running headers can thwart rfcdiff
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Aug 2020 05:09:20 -0000
draft-foudil-securitytxt-09.txt (apparently V2): Internet-DraftA File Format to Aid in Security VulnerabilitFebruary 2020 draft-foudil-securitytxt-10.txt (apparently V3): Internet-DrafA File Format to Aid in Security Vulnerability August 2020 Slightly broken rfcdiff output: https://www.ietf.org/rfcdiff?url2=draft-foudil-securitytxt-10 I think I would help if the V3 output could maintain the full “Internet-Draft” like V2 apparently did. (I know that Yakov should set an abbrev in the title, but he didn’t.) Grüße, Carsten
- [xml2rfc] V3 running headers can thwart rfcdiff Carsten Bormann
- Re: [xml2rfc] V3 running headers can thwart rfcdi… Henrik Levkowetz
- Re: [xml2rfc] V3 running headers can thwart rfcdi… Carsten Bormann