[rfc-i] rfc docName for drafts

rse at rfc-editor.org (Heather Flanagan (RFC Series Editor)) Thu, 09 June 2016 23:02 UTC

From: "rse at rfc-editor.org"
Date: Thu, 09 Jun 2016 16:02:31 -0700
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: <20a349e5-5cea-6883-95f7-5640d4e5e52e@rfc-editor.org>

On 6/9/16 3: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 think it's worth making sure that the guidance from the IESG is clear.
I've asked Sandy (RFC Editor Liaison to the IESG) to ping them about it.

-Heather