Off list request (was: Re: xml and txt submission on web page)
John C Klensin <john-ietf@jck.com> Fri, 15 June 2018 19:11 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74C7712785F for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2018 12:11:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 c20bFm6AxAhB for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2018 12:11:09 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D347F130E4F for <ietf@ietf.org>; Fri, 15 Jun 2018 12:11:09 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1fTu7o-000IbQ-Es; Fri, 15 Jun 2018 15:11:08 -0400
Date: Fri, 15 Jun 2018 15:11:01 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
cc: ietf@ietf.org
Subject: Off list request (was: Re: xml and txt submission on web page)
Message-ID: <FA55B27DE0468AAC9D1D33D5@PSB>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4zG7HxIzZbz3CqJW2vF5BX8tFnE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2018 19:11:14 -0000
Alexandre, In the light of the note Henrik posted after I started to write this, the note that follows may be irrelevant, but possibly worth reading anyway. In your tour of the problems that you have discussed on-list, you have identified a problem or three with xml2rdc that deserves a trouble report. I hope for better, but even if the only effect of that report is to make sure that bugs of xml2rfc v2 do not get carried forward into the production version of xml2rfc v3, that would be a positive step. I trust you are not surprised that these things, especially the file name and "suffix"/"file type" stuff have been noticed by, and irritated lots of others. We have just (eventually) learned what the problem is and then decided that remembering to not cause it is less trouble than asking for fixes (and maybe being necessary anyway). One problem is that such a complaint must be written carefully to avoid causing other problems. For example, if we were to complain that, in the <rfc> element, draft-<stuff>-nn is accepted but draft-<stuff>-nn.txt is not and produces incomprehensible messages, we might get a fix that would clearly reject not only the second case but names that do no9 contain exactly two digits before the end of the string. That would be a disaster for those of us who use assorted naming tricks to keep track of intermediate versions that are not intended for posting and that are intended to be seen only by the author(s) and a small circle of friends until there have been enough iteration in that group to make them fit for posting. You have also uncovered a great deal of confusion about things that may be worth getting documented (or at least flagged). For example, when you complained about not being able to submit an XML file for posting without a text one, I replied that the text one was required. It was at one point, but I was wrong; it seems that the tool will now accept XML and compile it. I make sufficiently many XML mistakes that I haven't had the nerve to try that or find out about it. Other comments in response to your notes have implied that the submission tool requires that the names of the file names that are uploaded must match the names that will be used in the Internet-Drafts directory. That isn't true. For example, if I have properly structured files for draft-ietf-example-example-00.txt and draft-ietf-example-example-00.xml but keep them in my file system as, e.g., examp-example-00.txt abd examp-example-00.xml the system will upload those files without problems an just proceed normally. This is a big advantage for those who use personal file naming conventions (perhaps, as above, for sub-version tracking and perhaps just because they are lazy about typing) and so on. Anyway, I cannot do more with this until mid-next-week, but, it you would find it helpful to work with me on a coherent list of specific issues (in either code or documentation) rather than just making iterative complaints of the IETF list, please get back to me. best, john
- Re: Off list request (was: Re: xml and txt submis… Spencer Dawkins at IETF
- Re: Off list request (was: Re: xml and txt submis… John C Klensin
- Off list request (was: Re: xml and txt submission… John C Klensin