[rfc-i] rfc docName for drafts
pkyzivat at alum.mit.edu (Paul Kyzivat) Fri, 10 June 2016 00:19 UTC
From: "pkyzivat at alum.mit.edu"
Date: Thu, 09 Jun 2016 20:19:48 -0400
Subject: [rfc-i] rfc docName for drafts
In-Reply-To: <E73ED898-BE56-4CEC-9475-CD94320252DE@cisco.com>
References: <ebbe94a6-f9a5-c20d-6a4a-890e0ec50e02@alum.mit.edu> <E73ED898-BE56-4CEC-9475-CD94320252DE@cisco.com>
Message-ID: <4110721b-0bc4-fc00-784a-dc4f14989fd4@alum.mit.edu>
On 6/9/16 6:42 PM, Joe Hildebrand (jhildebr) wrote: > I think it depends on the tools that you're using to produce the I-D today. For example, I'm not seeing ".txt" in the draft name in draft-hildebrand-deth-00, neither in the version that I see in the I-D repo I rsync from ftp.rfc-editor.org::ids-text-only, nor nor in the versions I get from the datatracker at https://datatracker.ietf.org/doc/draft-hildebrand-deth/. I used the Python version of xml2rfc to produce that text. I'm not using any special tool to produce the xml. The <rfc docName="whatever" ...> is manually entered. I *could* put something else, but have been following the observed precedent. Also, IIRC, if you don't do this idnits may generate a warning. (But I haven't tried that recently.) Thanks, Paul
- [rfc-i] rfc docName for drafts Paul Kyzivat
- [rfc-i] rfc docName for drafts Joe Hildebrand jhildebr
- [rfc-i] rfc docName for drafts Heather Flanagan RFC Series Editor
- [rfc-i] rfc docName for drafts Paul Kyzivat
- [rfc-i] rfc docName for drafts Julian Reschke
- [rfc-i] rfc docName for drafts Paul Kyzivat