[yaco-idsubmit-tool] Testing notes / Henrik / March 11

Henrik Levkowetz <henrik@levkowetz.com> Fri, 11 March 2011 17:08 UTC

Return-Path: <henrik@levkowetz.com>
X-Original-To: yaco-idsubmit-tool@core3.amsl.com
Delivered-To: yaco-idsubmit-tool@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 4D7033A6916 for <yaco-idsubmit-tool@core3.amsl.com>; Fri, 11 Mar 2011 09:08:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.649
X-Spam-Status: No, score=-102.649 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id QcM9bWqfw9Z6 for <yaco-idsubmit-tool@core3.amsl.com>; Fri, 11 Mar 2011 09:08:23 -0800 (PST)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id E08BF3A6915 for <yaco-idsubmit-tool@ietf.org>; Fri, 11 Mar 2011 09:08:22 -0800 (PST)
Received: from localhost ([]:50239 helo=dyn-fg124.sth.netnod.se) by merlot.tools.ietf.org with esmtp (Exim 4.74) (envelope-from <henrik@levkowetz.com>) id 1Py5qJ-0003wm-Sw; Fri, 11 Mar 2011 18:09:35 +0100
Message-ID: <4D7A574F.8010406@levkowetz.com>
Date: Fri, 11 Mar 2011 18:09:35 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv: Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-SA-Exim-Rcpt-To: yaco-idsubmit-tool@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false
Subject: [yaco-idsubmit-tool] Testing notes / Henrik / March 11
X-BeenThere: yaco-idsubmit-tool@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of the Yaco / I-D Submission Tool Project <yaco-idsubmit-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool>, <mailto:yaco-idsubmit-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yaco-idsubmit-tool>
List-Post: <mailto:yaco-idsubmit-tool@ietf.org>
List-Help: <mailto:yaco-idsubmit-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool>, <mailto:yaco-idsubmit-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 17:08:24 -0000

Testing issue:

  * I'm not seeing any posting confirmation emails going out to the
    testing address, which makes it impossible for me to carry through
    the testing to a final post, and verify that the document is online.


  * Failed idnits run on second submission?  I did one upload of
    draft-ietf-dnsext-axfr-clarify-16.txt, which had some metadata
    flaws, fixed those and uploaded again.  The (failed) idnits results
    from the second upload is incomplete, showing only this:

	"idnits 2.12.07 


    Running idnits 2.12.07 locally on the draft produces the expected

  * Abstract extraction.  Processing draft-ietf-dnsext-axfr-clarify-16.txt
    gives an abstract which includes the first 2 paragraphs from the
    Introduction section.  You should probably add a condition which cuts
    the abstract when a line matching "^ *[0-9]+\.? " is found, to stop at
    the first numbered section.

  * Abstract extraction (II).  Processing draft-eastlake-sha2b-05 results
    in an abstract which is cut short.  The last line of the first paragraph,
    and the entire second paragraph of the abstract is missing.


  * It's unnecessarily hard to upload a fixed version of a draft after
    flaws has been found in a first upload.  You have to either remember
    to cancel on the check page, or follow the link provided to go back
    and do it later.  I'd prefer that for a failed upload (idnits or
    meta-data failures) a new upload would automatically cancel the
    previous one; at least a new upload from the same IP address.

  * Also, cancelling a submission with idnits or meta-data errors should
    not cause an 'Are You Sure' dialog.

  * When the draft name found in the text of an uploaded draft contains
    characters which are not permitted, there's an error message next to
    the upload filename box.  This can be misleading, especially if the
    filename of the upload doesn't violate the rule.  Please change the
    message "Filename contains non alpha-numeric character: %s" next to
    the upload filename box to be a metadata error on the check page,
    and change the text to something like "The draft name found in the
    document, '%s', contains one or more alphanumeric characters: '%s'."

  * On at least one occasion, (draft-ietf-v6ops-ipv6-cpe-router-08.txt),
    the first time I clicked the 'Post' button I was just returned to the
    same page.  A second click on 'Post' resulted in the submitter auth


  * On the check page, there's initially a large blank area above the
    Meta-Data area, which then (as the style sheet is read in??) reduces
    to a reasonable height.  Please make this appear the same from the
    start.  If this is caused by the idnits page element, you could maybe
    take it out of the regular html placement flow by giving it absolute
    placement from the start?  (Just guessing here as to the cause...)

  * If a draft name is found in multiple places on the first page, it would
    make it easier to correct for instance a bad revision number if the
    meta-data error message would quote the full line where the bad rev.
    number was found.

The notes above is what I have from testing 8 drafts which have been
troublesome in the past.  As soon as the first bug is fixed, so it's
possible to do repeat submissions with idnits fixes, I'll test more.