
From esanchez@yaco.es  Tue Mar  1 00:05:57 2011
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-idsubmit-tool@core3.amsl.com
Delivered-To: yaco-idsubmit-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B565E3A6A43 for <yaco-idsubmit-tool@core3.amsl.com>; Tue,  1 Mar 2011 00:05:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.817
X-Spam-Level: 
X-Spam-Status: No, score=-1.817 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EegqPy8ezr8R for <yaco-idsubmit-tool@core3.amsl.com>; Tue,  1 Mar 2011 00:05:56 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 5D7F93A6A97 for <yaco-idsubmit-tool@ietf.org>; Tue,  1 Mar 2011 00:05:56 -0800 (PST)
Received: by bwz13 with SMTP id 13so5061048bwz.31 for <yaco-idsubmit-tool@ietf.org>; Tue, 01 Mar 2011 00:06:58 -0800 (PST)
Received: by 10.204.122.68 with SMTP id k4mr5722717bkr.153.1298966818009; Tue, 01 Mar 2011 00:06:58 -0800 (PST)
Received: from [192.168.0.192] ([77.227.215.107]) by mx.google.com with ESMTPS id j11sm371854bka.0.2011.03.01.00.06.56 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 Mar 2011 00:06:57 -0800 (PST)
Message-ID: <4D6CA91F.7040500@yaco.es>
Date: Tue, 01 Mar 2011 09:06:55 +0100
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez_L=F3pez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <AANLkTik_1HmvVcSmvrOokS4Vg4kkAbh7yqqO36L7bhdu@mail.gmail.com> <4D683EB9.1090606@levkowetz.com>
In-Reply-To: <4D683EB9.1090606@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [yaco-idsubmit-tool] Test driving the new id-submission tool
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: Tue, 01 Mar 2011 08:05:57 -0000

    Hi,

    I have updated the version of idnits used on the beta server.

    Please note that if your draft is not validated by idnits you could 
request that the secretariat does a manual post of it. You have to click 
on the 'Adjust metada' button and proceed to the next form.

    But I think that with the new version of idnits your submission will 
be ok and ready to auto post.

    Regards,

El 26/02/11 00:43, Henrik Levkowetz escribió:
> Hi Varun,
>
> The idnits version is old, and should be updated.  I don't know if
> that will make the test submission with your particular test document
> go better, but if it's produced with a current version of xml2rfc it
> shouldn't have any troubles.  Please try again as soon as the version
> of idnits used on the beta server has been updated, and let us know
> how things go.
>
>
> Best,
>
> 	Henrik
>
> On 2011-02-25 22:28 varun singh said the following:
>> Hi,
>>
>> I tried submitting the document using the new submission tool but the
>> page didn't proceed beyond the meta data page. I guess due to errors
>> as there were no visible indicators if something failed except
>>
>>> Check Page
>>>
>>> Your draft has NOT been verified to meet IDNITS requirements. (View IDNITS Results)
>>
>> On clicking the IDINITS results page it shows (4 errors):
>> idnits 2.09.01 (09 Oct 2008)
>> /var/www/docs/staging/draft-singh-avtcore-mprtp-00.txt:
>>
>> Instead of pasting the errors in the mail, I've posted them at:
>> http://pastebin.com/fdFY76HK. I get the same IDNITS errors for the
>> xml2rfc installed on my mac v1.35 and the web version. Perhaps there
>> is some error in my xml template?
>>
>>
>> Not knowing how to proceed, I decided to cancel the submission.
>>
>> Regards,
>> Varun
>> _______________________________________________
>> yaco-idsubmit-tool mailing list
>> yaco-idsubmit-tool@ietf.org
>> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool
>>
> _______________________________________________
> yaco-idsubmit-tool mailing list
> yaco-idsubmit-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool


-- 
Emilio A. Sánchez
esanchez@yaco.es

From esanchez@yaco.es  Tue Mar  1 00:14:40 2011
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-idsubmit-tool@core3.amsl.com
Delivered-To: yaco-idsubmit-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 30D023A6ACB for <yaco-idsubmit-tool@core3.amsl.com>; Tue,  1 Mar 2011 00:14:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.817
X-Spam-Level: 
X-Spam-Status: No, score=-1.817 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AHN33SsLCPak for <yaco-idsubmit-tool@core3.amsl.com>; Tue,  1 Mar 2011 00:14:38 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 5F2A93A69C2 for <yaco-idsubmit-tool@ietf.org>; Tue,  1 Mar 2011 00:14:38 -0800 (PST)
Received: by bwz13 with SMTP id 13so5066162bwz.31 for <yaco-idsubmit-tool@ietf.org>; Tue, 01 Mar 2011 00:15:40 -0800 (PST)
Received: by 10.205.23.208 with SMTP id rb16mr5651389bkb.130.1298967340181; Tue, 01 Mar 2011 00:15:40 -0800 (PST)
Received: from [192.168.0.192] ([77.227.215.107]) by mx.google.com with ESMTPS id q18sm466081bka.3.2011.03.01.00.15.38 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 Mar 2011 00:15:39 -0800 (PST)
Message-ID: <4D6CAB2A.1030606@yaco.es>
Date: Tue, 01 Mar 2011 09:15:38 +0100
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez_L=F3pez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <4D6B10DE.3010908@att.com>
In-Reply-To: <4D6B10DE.3010908@att.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [yaco-idsubmit-tool] minor comment on idsubmit
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: Tue, 01 Mar 2011 08:14:40 -0000

El 28/02/11 04:05, Tony Hansen escribió:
> 1) The "Upload" button does not look like it's active, but instead looks
> like it is grayed out and not clickable.
>
> Suggestion: have the button start out looking clickable. If javascript
> is enabled, on page load, disable the button. When the text file field
> is filled in, enable the button.

    You are right, that button style is pretty far from how a button may 
looks like. I'm going to fix it.

> 2) if you click on the Upload button without filling in an text file,
> you get a rather unusable message.

    It seems a bug, if you don't fill the text file input the form must 
warn you. I'm going to fix this one too.

> 3) If you click Upload on a draft, but it gives idnits errors, you are
> then blocked from uploading another version of the document with the
> same name. The error message says "Please correct the errors below.
> Duplicate Internet-Draft submission is currently in process", but
> there's no way to correct the error.

    If you get idnits errors you have two options:

    * Request a manual post from the secretariat using the 'Adjust 
metadata' button
    * Cancel the submission

    If you don't choose any of these option you can not resend the same 
draft cause previous submission is still on hold.

    I think that could be a good idea to include a link to the previous 
submission in the message that says "Duplicate Internet-Draft submission 
is currently in process" so you can cancel it if suitable.

    Best,

> Tony Hansen
> _______________________________________________
> yaco-idsubmit-tool mailing list
> yaco-idsubmit-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool


-- 
Emilio A. Sánchez
esanchez@yaco.es

From esanchez@yaco.es  Tue Mar  1 00:36:32 2011
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-idsubmit-tool@core3.amsl.com
Delivered-To: yaco-idsubmit-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 441073A6ACC for <yaco-idsubmit-tool@core3.amsl.com>; Tue,  1 Mar 2011 00:36:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.817
X-Spam-Level: 
X-Spam-Status: No, score=-1.817 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CMZeV0HUv+4s for <yaco-idsubmit-tool@core3.amsl.com>; Tue,  1 Mar 2011 00:36:31 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 2EF473A6AB7 for <yaco-idsubmit-tool@ietf.org>; Tue,  1 Mar 2011 00:36:30 -0800 (PST)
Received: by bwz13 with SMTP id 13so5077844bwz.31 for <yaco-idsubmit-tool@ietf.org>; Tue, 01 Mar 2011 00:37:33 -0800 (PST)
Received: by 10.204.135.217 with SMTP id o25mr5779405bkt.15.1298968652834; Tue, 01 Mar 2011 00:37:32 -0800 (PST)
Received: from [192.168.0.192] ([77.227.215.107]) by mx.google.com with ESMTPS id b7sm1084878bkb.6.2011.03.01.00.37.31 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 Mar 2011 00:37:32 -0800 (PST)
Message-ID: <4D6CB04A.3010306@yaco.es>
Date: Tue, 01 Mar 2011 09:37:30 +0100
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez_L=F3pez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <4D6B10DE.3010908@att.com> <4D6CAB2A.1030606@yaco.es>
In-Reply-To: <4D6CAB2A.1030606@yaco.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [yaco-idsubmit-tool] minor comment on idsubmit
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: Tue, 01 Mar 2011 08:36:32 -0000

    Hi,

    The fixes are done [1] and the beta server has been updated with the 
last changes.

    Thanks Tony for your comments.

    Regards,

[1] http://wiki.tools.ietf.org/tools/ietfdb/ticket/603

El 01/03/11 09:15, "Emilio A. Sánchez López" escribió:
> El 28/02/11 04:05, Tony Hansen escribió:
>> 1) The "Upload" button does not look like it's active, but instead looks
>> like it is grayed out and not clickable.
>>
>> Suggestion: have the button start out looking clickable. If javascript
>> is enabled, on page load, disable the button. When the text file field
>> is filled in, enable the button.
>
> You are right, that button style is pretty far from how a button may
> looks like. I'm going to fix it.
>
>> 2) if you click on the Upload button without filling in an text file,
>> you get a rather unusable message.
>
> It seems a bug, if you don't fill the text file input the form must warn
> you. I'm going to fix this one too.
>
>> 3) If you click Upload on a draft, but it gives idnits errors, you are
>> then blocked from uploading another version of the document with the
>> same name. The error message says "Please correct the errors below.
>> Duplicate Internet-Draft submission is currently in process", but
>> there's no way to correct the error.
>
> If you get idnits errors you have two options:
>
> * Request a manual post from the secretariat using the 'Adjust metadata'
> button
> * Cancel the submission
>
> If you don't choose any of these option you can not resend the same
> draft cause previous submission is still on hold.
>
> I think that could be a good idea to include a link to the previous
> submission in the message that says "Duplicate Internet-Draft submission
> is currently in process" so you can cancel it if suitable.
>
> Best,
>
>> Tony Hansen
>> _______________________________________________
>> yaco-idsubmit-tool mailing list
>> yaco-idsubmit-tool@ietf.org
>> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool
>
>


-- 
Emilio A. Sánchez
esanchez@yaco.es

From vsingh.ietf@gmail.com  Wed Mar  2 07:53:27 2011
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: yaco-idsubmit-tool@core3.amsl.com
Delivered-To: yaco-idsubmit-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C3083A6840 for <yaco-idsubmit-tool@core3.amsl.com>; Wed,  2 Mar 2011 07:53:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HCY3bS7P22nj for <yaco-idsubmit-tool@core3.amsl.com>; Wed,  2 Mar 2011 07:53:26 -0800 (PST)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id CB8F53A683E for <yaco-idsubmit-tool@ietf.org>; Wed,  2 Mar 2011 07:53:25 -0800 (PST)
Received: by ewy9 with SMTP id 9so33592ewy.31 for <yaco-idsubmit-tool@ietf.org>; Wed, 02 Mar 2011 07:54:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=EntDAQ7OzHhj8N8WX0xl2ls3+Ackd7hXPqwuupGmW1Y=; b=j6iavz/e7zH3WBwF3XleSdHQK25Gz+yIm4zo6Cd2MJgu1yFiAISpfA3Pm2m1ulCP9O dKdxRqOI2zv2l5CeSGwA5LpixCD+jtrVpJYgzvshBVwcnUbKYO9o/IKUlwfhO04sqFH2 NIGO6AWC9iSfMmC+SOELq9pCegFAp2hnGrvSM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=RfgkhM1pBKEsfaLNbeWRvLShKQMg5pYpyaoIjtRB2PMQSSV4cWnXJcKre2wucZlt6J DJNn5IVwl4zmxkmJ5vKP2/ItR8U7KTYHk3XLyPcKTpxLjM/s0XzrmanMucS04EZ6rI3K IQ8qN80Ai8Td3dGxbOmtw0u7FvjDtvVaGQVcA=
Received: by 10.223.29.28 with SMTP id o28mr49342fac.61.1299081260060; Wed, 02 Mar 2011 07:54:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.49.87 with HTTP; Wed, 2 Mar 2011 07:51:03 -0800 (PST)
In-Reply-To: <4D6CA91F.7040500@yaco.es>
References: <AANLkTik_1HmvVcSmvrOokS4Vg4kkAbh7yqqO36L7bhdu@mail.gmail.com> <4D683EB9.1090606@levkowetz.com> <4D6CA91F.7040500@yaco.es>
From: varun singh <vsingh.ietf@gmail.com>
Date: Wed, 2 Mar 2011 17:51:03 +0200
Message-ID: <AANLkTi=yVVhU=bjCuBOx=81+2BsiiyfiW7h=w2B5YU5e@mail.gmail.com>
To: =?ISO-8859-1?Q?Emilio_A=2E_S=E1nchez_L=F3pez?= <esanchez@yaco.es>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: yaco-idsubmit-tool@ietf.org
Subject: Re: [yaco-idsubmit-tool] Test driving the new id-submission tool
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: Wed, 02 Mar 2011 15:53:27 -0000

On a related note: I tried to submit to XRBLOCK WG
(http://datatracker.ietf.org/wg/xrblock/) and it gave the following
errors:

Please correct the errors below.
There is no active group with acronym 'xrblock', please rename your draft

Possibly, xrblock is not yet in the tool's wg checklist?


On Tue, Mar 1, 2011 at 10:06, "Emilio A. S=E1nchez L=F3pez"
<esanchez@yaco.es> wrote:
> =A0 Hi,
>
> =A0 I have updated the version of idnits used on the beta server.
>
> =A0 Please note that if your draft is not validated by idnits you could
> request that the secretariat does a manual post of it. You have to click =
on
> the 'Adjust metada' button and proceed to the next form.
>
> =A0 But I think that with the new version of idnits your submission will =
be ok
> and ready to auto post.
>
> =A0 Regards,
>
> El 26/02/11 00:43, Henrik Levkowetz escribi=F3:
>>
>> Hi Varun,
>>
>> The idnits version is old, and should be updated. =A0I don't know if
>> that will make the test submission with your particular test document
>> go better, but if it's produced with a current version of xml2rfc it
>> shouldn't have any troubles. =A0Please try again as soon as the version
>> of idnits used on the beta server has been updated, and let us know
>> how things go.
>>
>>
>> Best,
>>
>> =A0 =A0 =A0 =A0Henrik
>>
>> On 2011-02-25 22:28 varun singh said the following:
>>>
>>> Hi,
>>>
>>> I tried submitting the document using the new submission tool but the
>>> page didn't proceed beyond the meta data page. I guess due to errors
>>> as there were no visible indicators if something failed except
>>>
>>>> Check Page
>>>>
>>>> Your draft has NOT been verified to meet IDNITS requirements. (View
>>>> IDNITS Results)
>>>
>>> On clicking the IDINITS results page it shows (4 errors):
>>> idnits 2.09.01 (09 Oct 2008)
>>> /var/www/docs/staging/draft-singh-avtcore-mprtp-00.txt:
>>>
>>> Instead of pasting the errors in the mail, I've posted them at:
>>> http://pastebin.com/fdFY76HK. I get the same IDNITS errors for the
>>> xml2rfc installed on my mac v1.35 and the web version. Perhaps there
>>> is some error in my xml template?
>>>
>>>
>>> Not knowing how to proceed, I decided to cancel the submission.
>>>
>>> Regards,
>>> Varun
>>> _______________________________________________
>>> yaco-idsubmit-tool mailing list
>>> yaco-idsubmit-tool@ietf.org
>>> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool
>>>
>> _______________________________________________
>> yaco-idsubmit-tool mailing list
>> yaco-idsubmit-tool@ietf.org
>> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool
>
>
> --
> Emilio A. S=E1nchez
> esanchez@yaco.es
> _______________________________________________
> yaco-idsubmit-tool mailing list
> yaco-idsubmit-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool
>

From esanchez@yaco.es  Wed Mar  2 08:52:55 2011
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-idsubmit-tool@core3.amsl.com
Delivered-To: yaco-idsubmit-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8CA143A67B8 for <yaco-idsubmit-tool@core3.amsl.com>; Wed,  2 Mar 2011 08:52:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.067
X-Spam-Level: 
X-Spam-Status: No, score=-2.067 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25SGzRuMSUvF for <yaco-idsubmit-tool@core3.amsl.com>; Wed,  2 Mar 2011 08:52:54 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 139773A67B3 for <yaco-idsubmit-tool@ietf.org>; Wed,  2 Mar 2011 08:52:53 -0800 (PST)
Received: by bwz13 with SMTP id 13so391025bwz.31 for <yaco-idsubmit-tool@ietf.org>; Wed, 02 Mar 2011 08:53:59 -0800 (PST)
Received: by 10.204.54.69 with SMTP id p5mr245491bkg.82.1299084839001; Wed, 02 Mar 2011 08:53:59 -0800 (PST)
Received: from [192.168.0.192] ([77.227.215.107]) by mx.google.com with ESMTPS id b7sm105050bkb.6.2011.03.02.08.53.55 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 02 Mar 2011 08:53:58 -0800 (PST)
Message-ID: <4D6E7623.7010402@yaco.es>
Date: Wed, 02 Mar 2011 17:53:55 +0100
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez_L=F3pez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <AANLkTik_1HmvVcSmvrOokS4Vg4kkAbh7yqqO36L7bhdu@mail.gmail.com> <4D683EB9.1090606@levkowetz.com> <4D6CA91F.7040500@yaco.es> <AANLkTi=yVVhU=bjCuBOx=81+2BsiiyfiW7h=w2B5YU5e@mail.gmail.com>
In-Reply-To: <AANLkTi=yVVhU=bjCuBOx=81+2BsiiyfiW7h=w2B5YU5e@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [yaco-idsubmit-tool] Test driving the new id-submission tool
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: Wed, 02 Mar 2011 16:52:55 -0000

    Hi,

    The database of the beta server is a bit outdated. That working 
group does not exists in the beta server 
(http://beta.submit.yaco.es/wg/xrblock/ returns a 404).

    I think that is not a big problem that the database is outdated case 
the beta server is used for testing purposes and you can try with any of 
the available groups at http://beta.submit.yaco.es/wg/

    Best,

El 02/03/11 16:51, varun singh escribió:
> On a related note: I tried to submit to XRBLOCK WG
> (http://datatracker.ietf.org/wg/xrblock/) and it gave the following
> errors:
>
> Please correct the errors below.
> There is no active group with acronym 'xrblock', please rename your draft
>
> Possibly, xrblock is not yet in the tool's wg checklist?
>
>
> On Tue, Mar 1, 2011 at 10:06, "Emilio A. Sánchez López"
> <esanchez@yaco.es>  wrote:
>>    Hi,
>>
>>    I have updated the version of idnits used on the beta server.
>>
>>    Please note that if your draft is not validated by idnits you could
>> request that the secretariat does a manual post of it. You have to click on
>> the 'Adjust metada' button and proceed to the next form.
>>
>>    But I think that with the new version of idnits your submission will be ok
>> and ready to auto post.
>>
>>    Regards,
>>
>> El 26/02/11 00:43, Henrik Levkowetz escribió:
>>>
>>> Hi Varun,
>>>
>>> The idnits version is old, and should be updated.  I don't know if
>>> that will make the test submission with your particular test document
>>> go better, but if it's produced with a current version of xml2rfc it
>>> shouldn't have any troubles.  Please try again as soon as the version
>>> of idnits used on the beta server has been updated, and let us know
>>> how things go.
>>>
>>>
>>> Best,
>>>
>>>         Henrik
>>>
>>> On 2011-02-25 22:28 varun singh said the following:
>>>>
>>>> Hi,
>>>>
>>>> I tried submitting the document using the new submission tool but the
>>>> page didn't proceed beyond the meta data page. I guess due to errors
>>>> as there were no visible indicators if something failed except
>>>>
>>>>> Check Page
>>>>>
>>>>> Your draft has NOT been verified to meet IDNITS requirements. (View
>>>>> IDNITS Results)
>>>>
>>>> On clicking the IDINITS results page it shows (4 errors):
>>>> idnits 2.09.01 (09 Oct 2008)
>>>> /var/www/docs/staging/draft-singh-avtcore-mprtp-00.txt:
>>>>
>>>> Instead of pasting the errors in the mail, I've posted them at:
>>>> http://pastebin.com/fdFY76HK. I get the same IDNITS errors for the
>>>> xml2rfc installed on my mac v1.35 and the web version. Perhaps there
>>>> is some error in my xml template?
>>>>
>>>>
>>>> Not knowing how to proceed, I decided to cancel the submission.
>>>>
>>>> Regards,
>>>> Varun
>>>> _______________________________________________
>>>> yaco-idsubmit-tool mailing list
>>>> yaco-idsubmit-tool@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool
>>>>
>>> _______________________________________________
>>> yaco-idsubmit-tool mailing list
>>> yaco-idsubmit-tool@ietf.org
>>> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool
>>
>>
>> --
>> Emilio A. Sánchez
>> esanchez@yaco.es
>> _______________________________________________
>> yaco-idsubmit-tool mailing list
>> yaco-idsubmit-tool@ietf.org
>> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool
>>


-- 
Emilio A. Sánchez
esanchez@yaco.es

From henrik@levkowetz.com  Fri Mar 11 09:08:24 2011
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 [127.0.0.1]) 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-Level: 
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (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 ([127.0.0.1]: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:1.9.2.15) 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-Connect-IP: 127.0.0.1
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.

Bugs:

  * 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 

	/var/www/staging/draft-ietf-dnsext-axfr-clarify-07.txt:"

    Running idnits 2.12.07 locally on the draft produces the expected
    output.

  * 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.


Flaws:

  * 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
    page.

Nits:

  * 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.


Best,

	Henrik

From esanchez@yaco.es  Sat Mar 12 09:32:53 2011
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-idsubmit-tool@core3.amsl.com
Delivered-To: yaco-idsubmit-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EDE443A69F7 for <yaco-idsubmit-tool@core3.amsl.com>; Sat, 12 Mar 2011 09:32:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.96
X-Spam-Level: 
X-Spam-Status: No, score=-1.96 tagged_above=-999 required=5 tests=[AWL=-0.143,  BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zeiW4Ngddf0L for <yaco-idsubmit-tool@core3.amsl.com>; Sat, 12 Mar 2011 09:32:52 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 8D3D63A69D1 for <yaco-idsubmit-tool@ietf.org>; Sat, 12 Mar 2011 09:32:51 -0800 (PST)
Received: by wyb42 with SMTP id 42so3688229wyb.31 for <yaco-idsubmit-tool@ietf.org>; Sat, 12 Mar 2011 09:34:11 -0800 (PST)
Received: by 10.216.142.165 with SMTP id i37mr857731wej.106.1299951251413; Sat, 12 Mar 2011 09:34:11 -0800 (PST)
Received: from [192.168.0.192] ([77.227.215.107]) by mx.google.com with ESMTPS id t11sm2843975wes.17.2011.03.12.09.34.09 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 12 Mar 2011 09:34:10 -0800 (PST)
Message-ID: <4D7BAE92.2070908@yaco.es>
Date: Sat, 12 Mar 2011 18:34:10 +0100
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez_L=F3pez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <4D7A574F.8010406@levkowetz.com>
In-Reply-To: <4D7A574F.8010406@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [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: Sat, 12 Mar 2011 17:32:53 -0000

    Hi Henrik,

El 11/03/11 18:09, Henrik Levkowetz escribió:
>
> 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.

    The testing address is redefined in the settings_local of beta using 
EMAIL_COPY_TO so I can have access to the emails. I can revert to the 
original configuration or better add the two email addresses.

> Bugs:
>
>    * 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
>
> 	/var/www/staging/draft-ietf-dnsext-axfr-clarify-07.txt:"
>
>      Running idnits 2.12.07 locally on the draft produces the expected
>      output.

    Fixed at http://wiki.tools.ietf.org/tools/ietfdb/ticket/611

>    * 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.

    The only problem with this regular expression is that some drafts 
contain lines beginning with a number, an optional dot and a space like in:

    http://tools.ietf.org/id/draft-ietf-dnsop-default-local-zones-14.txt
    http://tools.ietf.org/id/draft-ietf-hokey-ldn-discovery-06.txt

    But it works pretty well if we check that the previous line was a 
blank line.

>    * 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.

    I have extended the abstract extraction to fix that bug and the 
previous one at http://wiki.tools.ietf.org/tools/ietfdb/ticket/612

> Flaws:
>
>    * 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.

    Added at http://wiki.tools.ietf.org/tools/ietfdb/ticket/613

>    * 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'."

    That error is a critical error (critical errors are the ones that do 
not allow to reach the status page). If some extrange caracters apear in 
the draft name then draft.py is unable to extract name and revision. 
Also the draft name is used as filename to the files when saved into the 
stagin area so it's a bad idea if the have non alpha characters.

    In the old tool this one was also a critical error that doesn't 
allow to proceed to status page. Do you really need to reach the status 
page in these cases? Maybe will be enough if we change the error message.

>    * 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
>      page.

    It's a reproducible bug, that is good.

    Fixed at http://wiki.tools.ietf.org/tools/ietfdb/ticket/613

> Nits:
>
>    * 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...)

    Wow, you have a fast eye. I had to try with different browsers until 
I see this behavior.

    Fixed at http://wiki.tools.ietf.org/tools/ietfdb/ticket/615

>    * 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.


    I have decorated the two pages dialog so it highlights the draft 
name that contains the error. I think this way is fast and more graphical.

    See at http://wiki.tools.ietf.org/tools/ietfdb/ticket/616


> 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.

    I have applied all the fixes and added the original testing email 
address to settings_local in the beta server.

    Best,

>
> Best,
>
> 	Henrik
> _______________________________________________
> yaco-idsubmit-tool mailing list
> yaco-idsubmit-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool


-- 
Emilio A. Sánchez
esanchez@yaco.es

From henrik@levkowetz.com  Sun Mar 13 10:03:23 2011
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 [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62C5E3A6A00 for <yaco-idsubmit-tool@core3.amsl.com>; Sun, 13 Mar 2011 10:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4sOt4fjlkh7G for <yaco-idsubmit-tool@core3.amsl.com>; Sun, 13 Mar 2011 10:03:22 -0700 (PDT)
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 D7B9A3A69FA for <yaco-idsubmit-tool@ietf.org>; Sun, 13 Mar 2011 10:03:21 -0700 (PDT)
Received: from 90-230-136-60-no45.tbcn.telia.com ([90.230.136.60]:59642 helo=[192.168.1.70]) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.74) (envelope-from <henrik@levkowetz.com>) id 1PyoiY-0006Kv-SX; Sun, 13 Mar 2011 18:04:36 +0100
Message-ID: <4D7CF91D.6060704@levkowetz.com>
Date: Sun, 13 Mar 2011 18:04:29 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez_L=F3pez=22?= <esanchez@yaco.es>
References: <4D7A574F.8010406@levkowetz.com> <4D7BAE92.2070908@yaco.es>
In-Reply-To: <4D7BAE92.2070908@yaco.es>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-SA-Exim-Connect-IP: 90.230.136.60
X-SA-Exim-Rcpt-To: esanchez@yaco.es, yaco-idsubmit-tool@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: yaco-idsubmit-tool@ietf.org
Subject: Re: [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: Sun, 13 Mar 2011 17:03:23 -0000

Hi Emilio,

On 2011-03-12 18:34 "Emilio A. S=E1nchez L=F3pez" said the following:
>     Hi Henrik,
>=20
> El 11/03/11 18:09, Henrik Levkowetz escribi=F3:
>>
>> Testing issue:
>>
>>    * I'm not seeing any posting confirmation emails going out to the
>>      testing address, which makes it impossible for me to carry throug=
h
>>      the testing to a final post, and verify that the document is onli=
ne.
>=20
>     The testing address is redefined in the settings_local of beta usin=
g=20
> EMAIL_COPY_TO so I can have access to the emails. I can revert to the=20
> original configuration or better add the two email addresses.

Yes, please; that would make testing all the way through to posted docume=
nt
possible.

>> Bugs:
>>
>>    * 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 resul=
ts
>>      from the second upload is incomplete, showing only this:
>>
>> 	"idnits 2.12.07
>>
>> 	/var/www/staging/draft-ietf-dnsext-axfr-clarify-07.txt:"
>>
>>      Running idnits 2.12.07 locally on the draft produces the expected=

>>      output.
>=20
>     Fixed at http://wiki.tools.ietf.org/tools/ietfdb/ticket/611

Thanks.

>>    * Abstract extraction.  Processing draft-ietf-dnsext-axfr-clarify-1=
6.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 st=
op at
>>      the first numbered section.
>=20
>     The only problem with this regular expression is that some drafts=20
> contain lines beginning with a number, an optional dot and a space like=
 in:
>=20
>     http://tools.ietf.org/id/draft-ietf-dnsop-default-local-zones-14.tx=
t
>     http://tools.ietf.org/id/draft-ietf-hokey-ldn-discovery-06.txt

Ah.  Right.

>     But it works pretty well if we check that the previous line was a=20
> blank line.

Right.  Very good.

>>    * Abstract extraction (II).  Processing draft-eastlake-sha2b-05 res=
ults
>>      in an abstract which is cut short.  The last line of the first pa=
ragraph,
>>      and the entire second paragraph of the abstract is missing.
>=20
>     I have extended the abstract extraction to fix that bug and the=20
> previous one at http://wiki.tools.ietf.org/tools/ietfdb/ticket/612

Thanks.

>> Flaws:
>>
>>    * It's unnecessarily hard to upload a fixed version of a draft afte=
r
>>      flaws has been found in a first upload.  You have to either remem=
ber
>>      to cancel on the check page, or follow the link provided to go ba=
ck
>>      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 sho=
uld
>>      not cause an 'Are You Sure' dialog.
>=20
>     Added at http://wiki.tools.ietf.org/tools/ietfdb/ticket/613



>>    * When the draft name found in the text of an uploaded draft contai=
ns
>>      characters which are not permitted, there's an error message next=
 to
>>      the upload filename box.  This can be misleading, especially if t=
he
>>      filename of the upload doesn't violate the rule.  Please change t=
he
>>      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 th=
e
>>      document, '%s', contains one or more alphanumeric characters: '%s=
'."
>=20
>     That error is a critical error (critical errors are the ones that d=
o=20
> not allow to reach the status page). If some extrange caracters apear i=
n=20
> the draft name then draft.py is unable to extract name and revision.=20
> Also the draft name is used as filename to the files when saved into th=
e=20
> stagin area so it's a bad idea if the have non alpha characters.
>=20
>     In the old tool this one was also a critical error that doesn't=20
> allow to proceed to status page. Do you really need to reach the status=
=20
> page in these cases? Maybe will be enough if we change the error messag=
e.

I understand your reasoning, and if the draft can't be saved in the stagi=
ng
area you shouldn't really go on to the check page.  However, the error me=
ssage
needs to be different, as you say; and I also think it shouldn't be prese=
nted
as an error related to the upload form entry -- that gave me the impressi=
on that
the upload hadn't succeeded.  Better make it an error message presented j=
ust
above the set of upload form entries, and say that the upload succeeded, =
but
the file could not be saved in the staging area because <reason>, where <=
reason>
could be that no document filename was found in the document, or that the=

document filename found contained disallowed characters, or ...

>>    * On at least one occasion, (draft-ietf-v6ops-ipv6-cpe-router-08.tx=
t),
>>      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 au=
th
>>      page.
>=20
>     It's a reproducible bug, that is good.
>=20
>     Fixed at http://wiki.tools.ietf.org/tools/ietfdb/ticket/613

Thanks.

>> Nits:
>>
>>    * 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??) redu=
ces
>>      to a reasonable height.  Please make this appear the same from th=
e
>>      start.  If this is caused by the idnits page element, you could m=
aybe
>>      take it out of the regular html placement flow by giving it absol=
ute
>>      placement from the start?  (Just guessing here as to the cause...=
)
>=20
>     Wow, you have a fast eye. I had to try with different browsers unti=
l=20
> I see this behavior.

Longer load time at a distance is more likely the reason, I think :-)

>     Fixed at http://wiki.tools.ietf.org/tools/ietfdb/ticket/615

Thanks.

>>    * 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 t=
he
>>      meta-data error message would quote the full line where the bad r=
ev.
>>      number was found.
>=20
>=20
>     I have decorated the two pages dialog so it highlights the draft=20
> name that contains the error. I think this way is fast and more graphic=
al.
>=20
>     See at http://wiki.tools.ietf.org/tools/ietfdb/ticket/616

Excellent.  Thanks.

>> 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.
>=20
>     I have applied all the fixes and added the original testing email=20
> address to settings_local in the beta server.

Splendid!  Thanks.


Best regards,

	Henrik


From tony@att.com  Sun Mar 13 12:03:39 2011
Return-Path: <tony@att.com>
X-Original-To: yaco-idsubmit-tool@core3.amsl.com
Delivered-To: yaco-idsubmit-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77C5D3A6B5F for <yaco-idsubmit-tool@core3.amsl.com>; Sun, 13 Mar 2011 12:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.476
X-Spam-Level: 
X-Spam-Status: No, score=-106.476 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rO86cLcLtzBG for <yaco-idsubmit-tool@core3.amsl.com>; Sun, 13 Mar 2011 12:03:38 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by core3.amsl.com (Postfix) with ESMTP id BBB6B3A6B32 for <yaco-idsubmit-tool@ietf.org>; Sun, 13 Mar 2011 12:03:38 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-10.tower-120.messagelabs.com!1300043100!7690301!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 32504 invoked from network); 13 Mar 2011 19:05:00 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-10.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Mar 2011 19:05:00 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p2DJ5NtC026552 for <yaco-idsubmit-tool@ietf.org>; Sun, 13 Mar 2011 15:05:24 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p2DJ5HoV026521 for <yaco-idsubmit-tool@ietf.org>; Sun, 13 Mar 2011 15:05:17 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p2DJ4rA6005570 for <yaco-idsubmit-tool@ietf.org>; Sun, 13 Mar 2011 15:04:53 -0400
Received: from dns.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p2DJ4mIR005517 for <yaco-idsubmit-tool@ietf.org>; Sun, 13 Mar 2011 15:04:48 -0400
Received: from [135.70.172.177] (vpn-135-70-172-177.vpn.mwst.att.com[135.70.172.177]) by maillennium.att.com (mailgw1) with ESMTP id <20110313190448gw100e4l0le> (Authid: tony); Sun, 13 Mar 2011 19:04:48 +0000
X-Originating-IP: [135.70.172.177]
Message-ID: <4D7D154F.3060204@att.com>
Date: Sun, 13 Mar 2011 15:04:47 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <4D7A574F.8010406@levkowetz.com> <4D7BAE92.2070908@yaco.es> <4D7CF91D.6060704@levkowetz.com>
In-Reply-To: <4D7CF91D.6060704@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [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: Sun, 13 Mar 2011 19:03:39 -0000

Here's a difficult one for the tool:

draft-ietf-yam-pre-evaluation-template-04.txt
draft-ietf-yam-pre-evaluation-template-04.xml

(I adjusted the dates to get past the date checks.)

The title is being picked up as

     Group

instead of as

  Preliminary Evaluation of RFC XXX "[PLACEHOLDER: INSERT TITLE HERE]",
for advancement from Draft Standard to Full Standard by the YAM Working
                                  Group

Obviously, the long lines that are part of the title are messing things 
up and the submission tool is only picking up the last line.

Given that the XML is also being uploaded, why aren't the title, 
abstract, and author info being extracted from there? I thought that was 
going to be one of the enhancements being put into the new I-D 
submission tool? That would avoid all issues with the issue-prone patterns.

     Tony Hansen

From henrik@levkowetz.com  Mon Mar 14 04:53:21 2011
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 [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D70C93A69FF for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 14 Mar 2011 04:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.644
X-Spam-Level: 
X-Spam-Status: No, score=-102.644 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vkCWJaalYG-l for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 14 Mar 2011 04:53:21 -0700 (PDT)
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 B76153A6928 for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 04:53:20 -0700 (PDT)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:58249 helo=dyn-fg124.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.74) (envelope-from <henrik@levkowetz.com>) id 1Pz6M7-00035G-MI; Mon, 14 Mar 2011 12:54:37 +0100
Message-ID: <4D7E01FB.2010105@levkowetz.com>
Date: Mon, 14 Mar 2011 12:54:35 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Tony Hansen <tony@att.com>
References: <4D7A574F.8010406@levkowetz.com> <4D7BAE92.2070908@yaco.es>	<4D7CF91D.6060704@levkowetz.com> <4D7D154F.3060204@att.com>
In-Reply-To: <4D7D154F.3060204@att.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: tony@att.com, yaco-idsubmit-tool@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: yaco-idsubmit-tool@ietf.org
Subject: Re: [yaco-idsubmit-tool] Title extraction failure
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: Mon, 14 Mar 2011 11:53:22 -0000

(I changed the subject line to match the new issue)

On 2011-03-13 20:04 Tony Hansen said:
> Here's a difficult one for the tool:
> 
> draft-ietf-yam-pre-evaluation-template-04.txt
> draft-ietf-yam-pre-evaluation-template-04.xml
> 
> (I adjusted the dates to get past the date checks.)
> 
> The title is being picked up as
> 
>      Group
> 
> instead of as
> 
>   Preliminary Evaluation of RFC XXX "[PLACEHOLDER: INSERT TITLE HERE]",
> for advancement from Draft Standard to Full Standard by the YAM Working
>                                   Group
> 
> Obviously, the long lines that are part of the title are messing things 
> up and the submission tool is only picking up the last line.

Yes.

Emilio, I'd suggest changing the regex to require one or more blank
lines before and after the title, and making the first group explicitly
include all lines of the {1, 3} repeat (this is what messes up this
case).  Also, we should strip out newlines and extra space from the title.

Suggested patch:

12:44 ~/src/db/yaco/idsubmit/ietf/utils
henrik@merlot $ svn diff draft.py 
Index: draft.py
===================================================================
--- draft.py	(revision 2886)
+++ draft.py	(working copy)
@@ -575,11 +575,12 @@
     def get_title(self):
         if self._title:
             return self._title
-        title_re = re.compile('(.+\n){1,3}(\s+<?draft-\S+\s*\n)')
+        title_re = re.compile('(?:\n\s*\n\s*)((.+\n){1,3})(\s+<?draft-\S+\s*\n)\s*\n')
         match = title_re.search(self.pages[0])
         if match:
             title = match.group(1)
             title = title.strip()
+            title = re.sub('\s*\n\s*', ' ', title)
             self._title = title
             return self._title
         # unusual title extract

12:45 ~/src/db/yaco/idsubmit/ietf/utils
henrik@merlot $ 

> Given that the XML is also being uploaded, why aren't the title, 
> abstract, and author info being extracted from there? I thought that was 
> going to be one of the enhancements being put into the new I-D 
> submission tool? That would avoid all issues with the issue-prone patterns.

Yes, but it's not part of this work order -- what we're trying to do with
this round is to replace the old tool as soon as possible, both to relieve
the pain of the old one, and to make it possible to migrate to the new
database schema.  There will more work done on the submission tool, to
cover _all_ of the requirements of RFC 4228, but that will come after we
have this round deployed.  Metadata extraction from XML files, if available,
is among the remaining 4228 requirements to be handled in the next round.

At least this has been the plan so far ...


Best,

	Henrik


From esanchez@yaco.es  Mon Mar 14 07:48:06 2011
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-idsubmit-tool@core3.amsl.com
Delivered-To: yaco-idsubmit-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1986C3A68EF for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 14 Mar 2011 07:48:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.942
X-Spam-Level: 
X-Spam-Status: No, score=-1.942 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7wIwy1VAShuS for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 14 Mar 2011 07:48:05 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 1065A3A6D6B for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 07:48:04 -0700 (PDT)
Received: by wyb42 with SMTP id 42so4934321wyb.31 for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 07:49:28 -0700 (PDT)
Received: by 10.227.166.15 with SMTP id k15mr2213088wby.204.1300114167951; Mon, 14 Mar 2011 07:49:27 -0700 (PDT)
Received: from [192.168.0.192] ([77.227.215.107]) by mx.google.com with ESMTPS id w25sm6196953wbd.11.2011.03.14.07.49.24 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 14 Mar 2011 07:49:25 -0700 (PDT)
Message-ID: <4D7E2B06.3020203@yaco.es>
Date: Mon, 14 Mar 2011 15:49:42 +0100
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez_L=F3pez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <4D7A574F.8010406@levkowetz.com>	<4D7BAE92.2070908@yaco.es>	<4D7CF91D.6060704@levkowetz.com>	<4D7D154F.3060204@att.com> <4D7E01FB.2010105@levkowetz.com>
In-Reply-To: <4D7E01FB.2010105@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [yaco-idsubmit-tool] Title extraction failure
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: Mon, 14 Mar 2011 14:48:06 -0000

    Hi all,

El 14/03/11 12:54, Henrik Levkowetz escribió:
> Emilio, I'd suggest changing the regex to require one or more blank
> lines before and after the title, and making the first group explicitly
> include all lines of the {1, 3} repeat (this is what messes up this
> case).  Also, we should strip out newlines and extra space from the title.
>

    I do some testing with the patch and it seems to be perfect. Thank 
you Henrik.

    I have committed it [1] and applied in beta server.

    Best,

[1] http://wiki.tools.ietf.org/tools/ietfdb/ticket/617

-- 
Emilio A. Sánchez
esanchez@yaco.es

From henrik@levkowetz.com  Mon Mar 14 09:01:06 2011
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 [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD6033A6D4E for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 14 Mar 2011 09:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.479
X-Spam-Level: 
X-Spam-Status: No, score=-102.479 tagged_above=-999 required=5 tests=[AWL=-0.179, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yHr29hDWSGF2 for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 14 Mar 2011 09:01:05 -0700 (PDT)
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 4C93D3A6DA7 for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 09:01:02 -0700 (PDT)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:59907 helo=dyn-fg124.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.74) (envelope-from <henrik@levkowetz.com>) id 1PzADk-0007qC-Hf; Mon, 14 Mar 2011 17:02:17 +0100
Message-ID: <4D7E3C04.5020603@levkowetz.com>
Date: Mon, 14 Mar 2011 17:02:12 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez_L=F3pez=22?= <esanchez@yaco.es>
References: <4D7A574F.8010406@levkowetz.com>	<4D7BAE92.2070908@yaco.es>	<4D7CF91D.6060704@levkowetz.com>	<4D7D154F.3060204@att.com>	<4D7E01FB.2010105@levkowetz.com> <4D7E2B06.3020203@yaco.es>
In-Reply-To: <4D7E2B06.3020203@yaco.es>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: esanchez@yaco.es, yaco-idsubmit-tool@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: yaco-idsubmit-tool@ietf.org
Subject: Re: [yaco-idsubmit-tool] Title extraction failure
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: Mon, 14 Mar 2011 16:01:06 -0000

Hi Emilio,

On 2011-03-14 15:49 "Emilio A. Sánchez López" said:
>     Hi all,
> 
> El 14/03/11 12:54, Henrik Levkowetz escribió:
>> Emilio, I'd suggest changing the regex to require one or more blank
>> lines before and after the title, and making the first group explicitly
>> include all lines of the {1, 3} repeat (this is what messes up this
>> case).  Also, we should strip out newlines and extra space from the title.
>>
> 
>     I do some testing with the patch and it seems to be perfect. Thank 
> you Henrik.
> 
>     I have committed it [1] and applied in beta server.
> 
>     Best,
> 
> [1] http://wiki.tools.ietf.org/tools/ietfdb/ticket/617

Thanks!

Best,

	Henrik

From tony@att.com  Mon Mar 14 09:46:38 2011
Return-Path: <tony@att.com>
X-Original-To: yaco-idsubmit-tool@core3.amsl.com
Delivered-To: yaco-idsubmit-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA3FC3A6E2E for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 14 Mar 2011 09:46:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.672
X-Spam-Level: 
X-Spam-Status: No, score=-106.672 tagged_above=-999 required=5 tests=[AWL=-0.073, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oewlaXVFsFOK for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 14 Mar 2011 09:46:38 -0700 (PDT)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by core3.amsl.com (Postfix) with ESMTP id 2E7773A6E37 for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 09:46:34 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-13.tower-119.messagelabs.com!1300121277!8797872!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 6182 invoked from network); 14 Mar 2011 16:47:57 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-13.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Mar 2011 16:47:57 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p2EGmLgk001655 for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 12:48:21 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p2EGmECu001518 for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 12:48:14 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p2EGlnxZ006526 for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 12:47:50 -0400
Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p2EGljwM006413 for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 12:47:46 -0400
Received: from [135.91.110.95] (dn135-91-110-95.dhcpn.ugn.att.com[135.91.110.95]) by maillennium.att.com (mailgw1) with ESMTP id <20110314164745gw100e4l25e> (Authid: tony); Mon, 14 Mar 2011 16:47:45 +0000
X-Originating-IP: [135.91.110.95]
Message-ID: <4D7E46B1.8060209@att.com>
Date: Mon, 14 Mar 2011 12:47:45 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <4D7A574F.8010406@levkowetz.com>	<4D7BAE92.2070908@yaco.es>	<4D7CF91D.6060704@levkowetz.com>	<4D7D154F.3060204@att.com>	<4D7E01FB.2010105@levkowetz.com>	<4D7E2B06.3020203@yaco.es> <4D7E3C04.5020603@levkowetz.com>
In-Reply-To: <4D7E3C04.5020603@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [yaco-idsubmit-tool] Title extraction failure
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: Mon, 14 Mar 2011 16:46:38 -0000

Much better -- I uploaded draft-ietf-yam-pre-evaluation-template-04 just =

fine now.

     Tony

On 3/14/2011 12:02 PM, Henrik Levkowetz wrote:
> Hi Emilio,
>
> On 2011-03-14 15:49 "Emilio A. S=E1nchez L=F3pez" said:
>>      Hi all,
>>
>> El 14/03/11 12:54, Henrik Levkowetz escribi=F3:
>>> Emilio, I'd suggest changing the regex to require one or more blank
>>> lines before and after the title, and making the first group explicit=
ly
>>> include all lines of the {1, 3} repeat (this is what messes up this
>>> case).  Also, we should strip out newlines and extra space from the t=
itle.
>>>
>>      I do some testing with the patch and it seems to be perfect. Than=
k
>> you Henrik.
>>
>>      I have committed it [1] and applied in beta server.
>>
>>      Best,
>>
>> [1] http://wiki.tools.ietf.org/tools/ietfdb/ticket/617
> Thanks!
>
> Best,
>
> 	Henrik
> _______________________________________________
> yaco-idsubmit-tool mailing list
> yaco-idsubmit-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool


From tony@att.com  Mon Mar 14 09:56:51 2011
Return-Path: <tony@att.com>
X-Original-To: yaco-idsubmit-tool@core3.amsl.com
Delivered-To: yaco-idsubmit-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D5F9C3A6DA0 for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 14 Mar 2011 09:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.665
X-Spam-Level: 
X-Spam-Status: No, score=-106.665 tagged_above=-999 required=5 tests=[AWL=-0.066, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X62TLEmNESn6 for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 14 Mar 2011 09:56:51 -0700 (PDT)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by core3.amsl.com (Postfix) with ESMTP id F10EB3A6D87 for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 09:56:50 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-12.tower-119.messagelabs.com!1300121894!8812362!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 25795 invoked from network); 14 Mar 2011 16:58:14 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-12.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Mar 2011 16:58:14 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p2EGwbll015708 for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 12:58:38 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p2EGwVZL015597 for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 12:58:31 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p2EGw7e5029085 for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 12:58:07 -0400
Received: from dns.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p2EGw0dw028896 for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 12:58:01 -0400
Received: from [135.91.110.95] (dn135-91-110-95.dhcpn.ugn.att.com[135.91.110.95]) by maillennium.att.com (mailgw1) with ESMTP id <20110314165800gw100e4l27e> (Authid: tony); Mon, 14 Mar 2011 16:58:00 +0000
X-Originating-IP: [135.91.110.95]
Message-ID: <4D7E4918.5000302@att.com>
Date: Mon, 14 Mar 2011 12:58:00 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <4D7A574F.8010406@levkowetz.com>	<4D7BAE92.2070908@yaco.es>	<4D7CF91D.6060704@levkowetz.com>	<4D7D154F.3060204@att.com>	<4D7E01FB.2010105@levkowetz.com>	<4D7E2B06.3020203@yaco.es> <4D7E3C04.5020603@levkowetz.com>
In-Reply-To: <4D7E3C04.5020603@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [yaco-idsubmit-tool] Invalid version number? canceling post-email?
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: Mon, 14 Mar 2011 16:56:51 -0000

I uploaded a new version of draft-ietf-yam-pre-evaluation-template (-05) 
and it complains about an invalid version number, saying version 04 
expected. If I click on View Error, it shows an extract of the txt file 
with the draft name highlighted. However, it does not explain *why* it 
thinks that version number is in error and why version 04 is expected.

I changed the name of the file slightly and now it says that version 00 
is expected. However, it does not explain *why* it thinks that version 
number is in error and why version 00 is expected.

Another item: once the state has entered

     Status of the submission: Submitter Authentication Required

there appears to be no way to cancel a submission from the web without 
using information from the email message. This has the effect that if 
there's an issue with the email address that isn't caught until after 
clicking "Submit" on the form, it evidently cannot be corrected without 
operator intervention of some form via sending email to 
ietf-action@ietf.org.

     Tony Hansen

From henrik@levkowetz.com  Mon Mar 14 10:52:27 2011
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 [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9CCA53A6DEB for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 14 Mar 2011 10:52:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.612
X-Spam-Level: 
X-Spam-Status: No, score=-102.612 tagged_above=-999 required=5 tests=[AWL=-0.012, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9tc-LX8nnhr2 for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 14 Mar 2011 10:52:26 -0700 (PDT)
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 ED15A3A6A31 for <yaco-idsubmit-tool@ietf.org>; Mon, 14 Mar 2011 10:52:25 -0700 (PDT)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:60651 helo=dyn-fg124.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.74) (envelope-from <henrik@levkowetz.com>) id 1PzBxe-0002Du-Bn; Mon, 14 Mar 2011 18:53:42 +0100
Message-ID: <4D7E5626.9050504@levkowetz.com>
Date: Mon, 14 Mar 2011 18:53:42 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <4D7A574F.8010406@levkowetz.com>	<4D7BAE92.2070908@yaco.es>	<4D7CF91D.6060704@levkowetz.com>	<4D7D154F.3060204@att.com>	<4D7E01FB.2010105@levkowetz.com>	<4D7E2B06.3020203@yaco.es>	<4D7E3C04.5020603@levkowetz.com> <4D7E4918.5000302@att.com>
In-Reply-To: <4D7E4918.5000302@att.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: yaco-idsubmit-tool@ietf.org, tony@att.com, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Subject: Re: [yaco-idsubmit-tool] Invalid version number? canceling	post-email?
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: Mon, 14 Mar 2011 17:52:27 -0000

On 2011-03-14 17:58 Tony Hansen said:
> I uploaded a new version of draft-ietf-yam-pre-evaluation-template (-05) 
> and it complains about an invalid version number, saying version 04 
> expected. If I click on View Error, it shows an extract of the txt file 
> with the draft name highlighted. However, it does not explain *why* it 
> thinks that version number is in error and why version 04 is expected.
> 
> I changed the name of the file slightly and now it says that version 00 
> is expected. However, it does not explain *why* it thinks that version 
> number is in error and why version 00 is expected.
> 
> Another item: once the state has entered
> 
>      Status of the submission: Submitter Authentication Required
> 
> there appears to be no way to cancel a submission from the web without 
> using information from the email message. This has the effect that if 
> there's an issue with the email address that isn't caught until after 
> clicking "Submit" on the form, it evidently cannot be corrected without 
> operator intervention of some form via sending email to 
> ietf-action@ietf.org.

Right.  It should be possible both to cancel a hung submission where
confirmation is impossible due to an email problem, and to request that
a new confirmation email be sent (with the appropriate rate limiting).


	Henrik

From esanchez@yaco.es  Thu Mar 17 05:28:05 2011
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-idsubmit-tool@core3.amsl.com
Delivered-To: yaco-idsubmit-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FB413A68BF for <yaco-idsubmit-tool@core3.amsl.com>; Thu, 17 Mar 2011 05:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.928
X-Spam-Level: 
X-Spam-Status: No, score=-1.928 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tTqID46Diq9h for <yaco-idsubmit-tool@core3.amsl.com>; Thu, 17 Mar 2011 05:28:04 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 7BCA43A687A for <yaco-idsubmit-tool@ietf.org>; Thu, 17 Mar 2011 05:28:03 -0700 (PDT)
Received: by wwa36 with SMTP id 36so2299935wwa.13 for <yaco-idsubmit-tool@ietf.org>; Thu, 17 Mar 2011 05:29:30 -0700 (PDT)
Received: by 10.227.139.72 with SMTP id d8mr1374540wbu.168.1300364969043; Thu, 17 Mar 2011 05:29:29 -0700 (PDT)
Received: from [192.168.0.192] ([77.227.215.107]) by mx.google.com with ESMTPS id b20sm623825wbb.16.2011.03.17.05.29.27 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 Mar 2011 05:29:28 -0700 (PDT)
Message-ID: <4D81FED4.4060009@yaco.es>
Date: Thu, 17 Mar 2011 13:30:12 +0100
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez_L=F3pez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <4D7A574F.8010406@levkowetz.com>	<4D7BAE92.2070908@yaco.es>	<4D7CF91D.6060704@levkowetz.com>	<4D7D154F.3060204@att.com>	<4D7E01FB.2010105@levkowetz.com>	<4D7E2B06.3020203@yaco.es>	<4D7E3C04.5020603@levkowetz.com>	<4D7E4918.5000302@att.com> <4D7E5626.9050504@levkowetz.com>
In-Reply-To: <4D7E5626.9050504@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [yaco-idsubmit-tool] Invalid version number? canceling	post-email?
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: Thu, 17 Mar 2011 12:28:05 -0000

    Hi.

    I updated the beta server with the new functionality [1]

    Now you only can edit metadata, post or cancel from an special url 
that contains a generated hash. You will reach this url after uploading 
your files so if you are the submitter you have the url in your browser 
history. This url could be share with other people.

    Remember that you can find the last submission of a draft using the 
search url [2]. But using this searcher you will go to a non privileged 
url where you can not cancel neither modify the submission.

    In this non privileged view you have a button to request the full 
url. If you click that button an email will be sent to draft authors and 
to the submitter (if he or she has filled its personal info) with the 
full access url.

    Now, from the full access url, you can cancel a submission that is 
waiting for submitter authentication.

    Secretariat users could perform any action from any of the status urls.

    By the way, we have to thank Henrik cause the hash url system is his 
idea.

[1] http://wiki.tools.ietf.org/tools/ietfdb/ticket/618
[2] http://beta.submit.yaco.es/submit/status/

El 14/03/11 18:53, Henrik Levkowetz escribió:
>
> On 2011-03-14 17:58 Tony Hansen said:
>> I uploaded a new version of draft-ietf-yam-pre-evaluation-template (-05)
>> and it complains about an invalid version number, saying version 04
>> expected. If I click on View Error, it shows an extract of the txt file
>> with the draft name highlighted. However, it does not explain *why* it
>> thinks that version number is in error and why version 04 is expected.
>>
>> I changed the name of the file slightly and now it says that version 00
>> is expected. However, it does not explain *why* it thinks that version
>> number is in error and why version 00 is expected.
>>
>> Another item: once the state has entered
>>
>>       Status of the submission: Submitter Authentication Required
>>
>> there appears to be no way to cancel a submission from the web without
>> using information from the email message. This has the effect that if
>> there's an issue with the email address that isn't caught until after
>> clicking "Submit" on the form, it evidently cannot be corrected without
>> operator intervention of some form via sending email to
>> ietf-action@ietf.org.
>
> Right.  It should be possible both to cancel a hung submission where
> confirmation is impossible due to an email problem, and to request that
> a new confirmation email be sent (with the appropriate rate limiting).
>
>
> 	Henrik
> _______________________________________________
> yaco-idsubmit-tool mailing list
> yaco-idsubmit-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool


-- 
Emilio A. Sánchez
esanchez@yaco.es

From henrik@levkowetz.com  Sat Mar 19 15:06:49 2011
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 [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09D1D3A69B8 for <yaco-idsubmit-tool@core3.amsl.com>; Sat, 19 Mar 2011 15:06:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.669
X-Spam-Level: 
X-Spam-Status: No, score=-102.669 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_24=0.6, J_CHICKENPOX_25=0.6, J_CHICKENPOX_57=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qdI12L-pJiaK for <yaco-idsubmit-tool@core3.amsl.com>; Sat, 19 Mar 2011 15:06:47 -0700 (PDT)
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 60F9D3A69B3 for <yaco-idsubmit-tool@ietf.org>; Sat, 19 Mar 2011 15:06:46 -0700 (PDT)
Received: from 90-230-136-60-no45.tbcn.telia.com ([90.230.136.60]:62836 helo=vigonier.lan) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.74) (envelope-from <henrik@levkowetz.com>) id 1Q14JS-0006AI-JC; Sat, 19 Mar 2011 23:08:04 +0100
Message-ID: <4D852938.80708@levkowetz.com>
Date: Sat, 19 Mar 2011 23:07:52 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
Content-Type: multipart/mixed; boundary="------------080809090707050005040004"
X-SA-Exim-Connect-IP: 90.230.136.60
X-SA-Exim-Rcpt-To: yaco-idsubmit-tool@ietf.org, esanchez@yaco.es, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Subject: [yaco-idsubmit-tool] Testing Notes / Henrik / 17 March
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: Sat, 19 Mar 2011 22:06:49 -0000

This is a multi-part message in MIME format.
--------------080809090707050005040004
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Hi,

Here are some additional testing notes.  I've already covered some of these
with Emilio (the developer) on jabber; but also send them to the list for
info and for the record.  This testing covers author extraction from 191
drafts, including all of the drafts which wasn't accepted for automatic
posting by the current submission tool during the period leading up to the
Prague meeting posting cut-off.

Already covered:

   * The author extraction code supplied to Yaco handles obfuscated
     email addresses such as "joe (at) example.com", but does not handle
     the case "joe at example.com" which it probably should.

   * The upload form should also catch possible exceptions from the
     author extraction code, to let people know there's a problem in
     a better format than a 'Server 500' error.  Pointed out by Emilio.

   * All -00 submissions were treated the same way, requiring WG Chair
     permissions to post -- but this should not apply to individual
     submissions, only to new WG documents.

New:

   (For the issues below which affect the ietf/utils/draft.py module,
   a patch file is enclosed.)

   * Extraction of Title which don't have the draft name on a separate
     page fails.  See for instance this example:
     http://www.ietf.org/staging/draft-ma-cdni-publisher-use-cases-00.txt
     The regex should maybe be updated to permit but not require a newline
     before the draft filename:
     '(?:\n\s*\n\s*)((.+\n){1,2}(.+\n?))(\s+<?draft-\S+\s*\n)\s*\n'
     Fixed in patch.

   * If there are blank lines before the start of the author list on the
     first page, the author extraction will fail.  This sometimes happens
     when there's junk at the start of a draft, see for instance
     http://www.ietf.org/id/draft-ietf-mpls-tp-process-00.txt .  Fixed in
     patch.

   * Sometimes the Authors' Addresses section lists authors with the same
     workplace address on the same line: "Sam Spade and Joe Smith".  This
     needs a fix in the author extraction code.  Provided in the patch.

   * Sometimes the order of first name, surname is different on the first
     page and in the author list, and sometimes the surname is uppercase
     in one place, but not in the other.  This also needs a fix in the
     author extraction code.  Provided in the patch.

   * The header stripping code had a bug, where multiple blank lines could
     be replaced by a single blank line in the stripped text, which could
     mess up title extraction.  Fixed in the patch.

   * Title space normalization should be done also for titles from the
     'unusual title format' code branch of the title extraction code.
     Fix provided in the patch.

   * Company names on the first page are sometimes rendered with different
     case than in the Authors' Addresses section.  Fixed in the patch.

   * Some drafts list the draft filename _before_ the title, rather than
     after the title.  Permit this too. Covered in the patch.

   * Spanish names can be shown as either
	<given_name> <fathers_first_surname> <mothers_first_surname>
     or less formally as
	<given_name> <fathers_first_surname>
     If the first form is used in the Authors' Addresses section, but the
     second form (with the given name possibly abbreviated to its first
     letter) the author extraction will fail.  Fix provided in patch.

   * Drafts containing tabs will be caught by idnits during I-D submission,
     but in case the drafts.py module is used independently from idnits,
     convert tabs to spaces in order for the author extraction and other
     methods to work as expected.  Example: recently submitted draft
     draft-bergeron-payload-rtpfec-rs-00.txt.  Fix provided in patch.

   * Found a draft with a previously unhandled header/footer format:
     draft-fang-mpls-tp-oam-toolset-01.txt.  Tweak needed for header/footer
      stripping.  Fix provided in patch.

   

The patch also includes code to extract lists of references used in the
document.  This is not expected to be of use for the submission tool, but
later in other parts of the datatracker.


Best,

	Henrik

--------------080809090707050005040004
Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0";
 name="2011-03-19-ietf-utils-draft.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="2011-03-19-ietf-utils-draft.patch"

43c43
< version = "0.13"
---
> version = "0.16"
68c68
<     "Ned": "Edward" ,
---
>     "Ned": "Edward",
102a103
>     text = text.expandtabs()
153c154,155
<         haveblank = False
---
>         blankcount = 0
>         linecount = 0
167a170
>             linecount += 1
190c193
<             if re.search(".{60,}(Jan|Feb|Mar|March|Apr|April|May|Jun|June|Jul|July|Aug|Sep|Oct|Nov|Dec) (19[89][0-9]|20[0-9][0-9]) *$", line, re.I):
---
>             if linecount > 15 and re.search(".{58,}(Jan|Feb|Mar|March|Apr|April|May|Jun|June|Jul|July|Aug|Sep|Oct|Nov|Dec) (19[89][0-9]|20[0-9][0-9]) *$", line, re.I):
203,205c206,208
<                     if haveblank:
<                         stripped += [""]
<                 haveblank = False
---
>                     if blankcount:
>                         stripped += [""]*blankcount
>                 blankcount = 0
211c214
<                 haveblank = True
---
>                 blankcount += 1
276c279
<         header_re = re.compile("^(\s*)([0-9]+\.? |Appendix|Status of|Table of|Full Copyright|Copyright|Intellectual Property|Acknowled|Author|Index).*", re.I)
---
>         header_re = re.compile("^(\s*)([0-9]+\.? |Appendix|Status of|Table of|Full Copyright|Copyright|Intellectual Property|Acknowled|Author|Index|Disclaimer).*", re.I)
341a345,349
>         def acronym_match(s, l):
>             acronym = re.sub("[^A-Z]", "", l)
>             #_debug(" s:%s; l:%s => %s; %s" % (s, l, acronym, s==acronym)) 
>             return s == acronym
> 
347c355
<                 "honor" : r"(?:Dr\.?|Prof(?:\.?|essor)|Sir|Lady|Dame)",
---
>                 "honor" : r"(?:Dr\.?|Prof(?:\.?|essor)|Sir|Lady|Dame|Sri)",
349c357
<                 "suffix": r"(jr|II|2nd|III|3rd|IV|4th)",
---
>                 "suffix": r"(jr.?|Jr.?|II|2nd|III|3rd|IV|4th)",
355c363
<                 r" {6}(((%(prefix)s )?%(last)s)( %(suffix)s)?, %(first)s)([, ]([Ee]d\.?|\([Ee]d\.?\)))?$" % aux,
---
>                 r" {6}(((%(prefix)s )?%(last)s)( %(suffix)s)?, %(first)s)?$" % aux,
357a366,374
>             multiauthformats = [
>                 (
>                     r" {6}(%(first)s[ \.]{1,3}((%(prefix)s )?%(last)s)( %(suffix)s)?)(, ?%(first)s[ \.]{1,3}((%(prefix)s )?%(last)s)( %(suffix)s)?)+$" % aux,
>                     r"(%(first)s[ \.]{1,3}((%(prefix)s )?%(last)s)( %(suffix)s)?)" % aux
>                 ),
>             ]
>             editorformats = [
>                 r"(?:, | )([Ee]d\.?|\([Ee]d\.?\)|[Ee]ditor)$",
>                 ]
382a400
>                         _debug("Breaking for centered line")
384,385c402,407
<                     for authformat in authformats:
<                         match = re.search(authformat, line)
---
>                     for editorformat in editorformats:
>                         if re.search(editorformat, line):
>                             line = re.sub(editorformat, "", line)
>                             break
>                     for lineformat, authformat in multiauthformats:
>                         match = re.search(lineformat, line)
387,388c409,411
<                             author = match.group(1)
<                             authors += [ author ]
---
>                             _debug("Multiauth format: '%s'" % lineformat)
>                             author_list = re.findall(authformat, line)
>                             authors += [ a[0] for a in author_list ]
391c414,425
<                             _debug("Author: '%s'" % author)
---
>                             for author in author_list:
>                                 _debug("Author: '%s'" % author[0])
>                     else:
>                         for authformat in authformats:                        
>                             match = re.search(authformat, line)
>                             if match:
>                                 _debug("Auth format: '%s'" % authformat)
>                                 author = match.group(1)
>                                 authors += [ author ]
>                                 #_debug("\nLine:   " + line)
>                                 #_debug("Format: " + authformat)
>                                 _debug("Author: '%s'" % author)
393c427
<                     if prev_blankline:
---
>                     if prev_blankline and authors:
421a456,460
>                 prefix_match = re.search(" %(prefix)s$" % aux, first)
>                 if prefix_match:
>                     prefix = prefix_match.group(1)
>                     first = first[:-len(prefix)].strip()
>                     last = prefix+" "+last
423c462
<                 for author in [ "%s %s"%(first,last), "%s %s"%(last,first), ]:
---
>                 for author in [ "%s %s"%(first,last), "%s %s"%(last,first), "%s %s"%(first,last.upper()), "%s %s"%(last,first.upper()), ]:
434c473,474
<                     authpat = re.sub("-", ".*?-", authpat)
---
>                     if not "[A-Z]" in authpat:
>                         authpat = re.sub("-", ".*?-", authpat)
438c478
<                     authpat = "^(?:%s ?)?(%s)( *\(.*\)|,( [A-Z][-A-Za-z0-9]*)?)?" % (aux["honor"], authpat)
---
>                     authpat = "(?:^| and )(?:%s ?)?(%s)( *\(.*\)|,( [A-Z][-A-Za-z0-9]*)?| %s| [A-Z][a-z]+)?" % (aux["honor"], authpat, aux["suffix"])
444,488c484,533
<                     try:
<                         for j in range(len(self.lines)-1, 15, -1):
<                             line = self.lines[j].strip()
<                             forms = [ line ] + [ line.replace(short, longform[short]) for short in longform if short in line ]
<                             for line in forms:
<                                 try:
<                                     if re.search(authpat, line):
<                                         start = j
<                                         _debug( " ==>   " + line.strip())
<                                         # The author info could be formatted in multiple columns...
<                                         columns = re.split("(    +)", line)
<                                         # _debug( "Columns:" + columns; sys.stdout.flush())
<                                         # Find which column:
<                                         #_debug( "Col range:" + range(len(columns)); sys.stdout.flush())
< 
<                                         cols = [ c for c in range(len(columns)) if re.search(authpat+r"$", columns[c].strip()) ]
<                                         if cols:
<                                             col = cols[0]
<                                             if not (start, col) in found_pos:
<                                                 found_pos += [ (start, col) ]
<                                                 _debug( "Col:   %d" % col)
<                                                 beg = len("".join(columns[:col]))
<                                                 _debug( "Beg:   %d '%s'" % (beg, "".join(columns[:col])))
<                                                 _debug( "Len:   %d" % len(columns))
<                                                 if col == len(columns) or col == len(columns)-1:
<                                                     end = None
<                                                     _debug( "End1:  %s" % end)
<                                                 else:
<                                                     end = beg + len("".join(columns[col:col+2]))
<                                                     _debug( "End2:  %d '%s'" % (end, "".join(columns[col:col+2])))
<                                                 _debug( "Cut:   '%s'" % line[beg:end])
<                                                 author = re.search(authpat, columns[col].strip()).group(1)
<                                                 if author in companies:
<                                                     authors[i] = None
<                                                 else:
<                                                     authors[i] = author
<                                                 #_debug( "Author: %s: %s" % (author, authors[author]))
<                                                 # We need to exit 2 for loops -- a break isn't sufficient:
<                                                 raise StopIteration("Found Author")
<                                 except AssertionError, e:
<                                     sys.stderr.write("filename: "+self.filename+"\n")
<                                     sys.stderr.write("authpat: "+authpat+"\n")
<                                     raise
<                     except StopIteration:
<                         pass
---
>                     # Scan towards the front from the end of the file, looking for a match to authpath
>                     for j in range(len(self.lines)-1, 15, -1):
>                         line = self.lines[j]
>                         forms = [ line ] + [ line.replace(short, longform[short]) for short in longform if short in line ]
>                         for form in forms:
>                             try:
>                                 if re.search(authpat, form.strip()) and not j in found_pos:
>                                     start = j
>                                     found_pos += [ start ]
>                                     _debug( " ==> start %s, normalized '%s'" % (start, form.strip()))
>                                     # The author info could be formatted in multiple columns...
>                                     columns = re.split("(    +| and )", form)
>                                     # _debug( "Columns:" + columns; sys.stdout.flush())
>                                     # Find which column:
>                                     #_debug( "Col range:" + range(len(columns)); sys.stdout.flush())
> 
>                                     cols = [ c for c in range(len(columns)) if re.search(authpat+r"( and |, |$)", columns[c].strip()) ]
>                                     if cols:
>                                         col = cols[0]
>                                         if not (start, col) in found_pos:
>                                             found_pos += [ (start, col) ]
>                                             _debug( "Col:   %d" % col)
>                                             beg = len("".join(columns[:col]))
>                                             _debug( "Beg:   %d '%s'" % (beg, "".join(columns[:col])))
>                                             _debug( "Len:   %d" % len(columns))
>                                             if col == len(columns) or col == len(columns)-1:
>                                                 end = None
>                                                 _debug( "End1:  %s" % end)
>                                             else:
>                                                 end = beg + len("".join(columns[col:col+2]))
>                                                 _debug( "End2:  %d '%s'" % (end, "".join(columns[col:col+2])))
>                                             _debug( "Cut:   '%s'" % form[beg:end])
>                                             author_match = re.search(authpat, columns[col].strip()).group(1)
>                                             _debug( "AuthMatch: '%s'" % (author_match,))
>                                             if author_match in companies:
>                                                 authors[i] = None
>                                             else:
>                                                 for name in [first, last]:
>                                                     if name.upper() in author_match:
>                                                         author_match = author_match.replace(name.upper(), name)
>                                                         break
>                                                 authors[i] = author_match
>                                             #_debug( "Author: %s: %s" % (author_match, authors[author_match]))
>                                             break
>                             except AssertionError, e:
>                                 sys.stderr.write("filename: "+self.filename+"\n")
>                                 sys.stderr.write("authpat: "+authpat+"\n")
>                                 raise
>                         if start and col != None:
>                             break
497c542
<                     count = 0
---
>                     nonblank_count = 0
511c556
<                             count += 1                    
---
>                             nonblank_count += 1                    
518c563
<                         authmatch = [ a for a in authors[i+1:] if a and not a in companies and re.search((r"(^|\W)"+re.sub("\.? ", ".* ", a)+"(\W|$)"), line.strip()) ]
---
>                         authmatch = [ a for a in authors[i+1:] if a and not a.lower() in companies and (re.search((r"(?i)(^|\W)"+re.sub("\.? ", ".* ", a)+"(\W|$)"), line.strip()) or acronym_match(a, line.strip()) )]
522c567
<                             if count == 1 or (count == 2 and not blanklines):
---
>                             if nonblank_count == 1 or (nonblank_count == 2 and not blanklines):
524,525c569,570
<                                 companies += authmatch
<                                 companies += [ line.strip() ] # XXX fix this for columnized author list
---
>                                 companies += [ c.lower() for c in authmatch ]
>                                 companies += [ line.strip().lower() ] # XXX fix this for columnized author list
529c574
<                                     if authors[k] in companies:
---
>                                     if authors[k] and authors[k].lower() in companies:
568c613
<             # authors.sort() 
---
>             authors.sort() 
579,580c624,628
<         title_re = re.compile('(?:\n\s*\n\s*)((.+\n){1,2}(.+\n?))(\s+<?draft-\S+\s*\n)\s*\n')
<         match = title_re.search(self.pages[0])
---
>         match = re.search('(?:\n\s*\n\s*)((.+\n){0,2}(.+\n*))(\s+<?draft-\S+\s*\n)\s*\n', self.pages[0])
>         if not match:
>             match = re.search('(?:\n\s*\n\s*)<?draft-\S+\s*\n*((.+\n){1,3})\s*\n', self.pages[0])
>         if not match:
>             match = re.search('(?i)(.+\n|.+\n.+\n)(\s*status of this memo\s*\n)', self.pages[0])
585,592c633
<             self._title = title
<             return self._title
<         # unusual title extract
<         unusual_title_re = re.compile('(.+\n|.+\n.+\n)(\s*status of this memo\s*\n)', re.I)
<         match = unusual_title_re.search(self.pages[0])
<         if match:
<             title = match.group(1)
<             title = title.strip()
---
>             title = re.sub(' +', ' ', title)
596a638,676
>     # ------------------------------------------------------------------
>     def get_refs(self):
>         refs = []
>         normrefs = []
>         rfcrefs = []
>         refline = None
>         for i in range(len(self.lines)-1, 15, -1):
>             if re.search(r"(?i)^ *[0-9.]+ *(((normative|informative|informational|non-normative) )?references|references\W+(normative|informative))", self.lines[i]):
>                 refline = i
>                 break
>         if refline:
>             for i in range(refline, len(self.lines)):
>                 line = self.lines[i].strip()
>                 ref_match = re.search(r"(?i)^\[[a-z0-9.-]+( [a-z0-9.-]+)?\].+", line)
>                 if ref_match:
>                     para = line
>                     while True:
>                         i += 1
>                         if i >= len(self.lines):
>                             break
>                         line = self.lines[i].strip()
>                         if not line:
>                             break
>                         if para[-1] not in ["-", "/"]:
>                             para += " "
>                         para += line
>                     refs += [ para ]
>                     rfc_match = re.search("(?i)rfc ?\d+", para)
>                     if rfc_match:
>                         rfc = rfc_match.group(0).replace(" ","").lower()
>                         rfcrefs += [ rfc ]
>         normrefs = list(set(normrefs))
>         normrefs.sort()
>         rfcrefs = list(set(rfcrefs))
>         rfcrefs.sort()
>         refs = list(set(refs))
>         refs.sort()
>         return normrefs, rfcrefs, refs
> 
625c705,709
<     filename = os.path.join("/www/tools.ietf.org/id", fn)
---
>     if os.path.exists(fn):
>         filename = fn
>         fn = os.path.basename(fn)
>     else:
>         filename = os.path.join("/www/tools.ietf.org/id", fn)
636a721
>     #_debug("\n".join(draft.lines))
644a730,731
>     normrefs, rfcrefs, refs = draft.get_refs()
>     fields["docrfcrefs"] = ", ".join(rfcrefs)
732,733c819,821
<                 _debug( "** Processing '%s'" % draft)
<                 _printmeta(timestamp, draft)
---
>                 if draft:
>                     _debug( "** Processing '%s'" % draft)
>                     _printmeta(timestamp, draft)

--------------080809090707050005040004--

From esanchez@yaco.es  Mon Mar 21 03:55:12 2011
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-idsubmit-tool@core3.amsl.com
Delivered-To: yaco-idsubmit-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8651C3A6822 for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 21 Mar 2011 03:55:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level: 
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a0AHTlIchh4T for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 21 Mar 2011 03:55:11 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 6552E3A67B7 for <yaco-idsubmit-tool@ietf.org>; Mon, 21 Mar 2011 03:55:09 -0700 (PDT)
Received: by wwa36 with SMTP id 36so4832049wwa.13 for <yaco-idsubmit-tool@ietf.org>; Mon, 21 Mar 2011 03:56:42 -0700 (PDT)
Received: by 10.216.143.7 with SMTP id k7mr3626807wej.95.1300705001973; Mon, 21 Mar 2011 03:56:41 -0700 (PDT)
Received: from [192.168.0.192] ([77.227.215.107]) by mx.google.com with ESMTPS id r57sm2516474wes.25.2011.03.21.03.56.28 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Mar 2011 03:56:33 -0700 (PDT)
Message-ID: <4D872EDD.4090407@yaco.es>
Date: Mon, 21 Mar 2011 11:56:29 +0100
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez_L=F3pez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: [yaco-idsubmit-tool] Beta server stopped
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: Mon, 21 Mar 2011 10:55:12 -0000

    Hi all,

    Latelly we are having some troubles with our KVM server where 
beta.submit.yaco.es is located.

    Right now our infraestructure department is working to stabilize the 
system so the beta server will be down until this afternoon.

    When the server is running again I'll notify it to this list. Every 
issue about the tool thas has been discussed in the list is already 
commited (included the last patch sent by Henrik) so when the server 
comes up it will be updated with all the changes.

    Best,

-- 
Emilio A. Sánchez
esanchez@yaco.es

From esanchez@yaco.es  Mon Mar 21 10:36:22 2011
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-idsubmit-tool@core3.amsl.com
Delivered-To: yaco-idsubmit-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 178B128C16A for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 21 Mar 2011 10:36:22 -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=[AWL=-0.083,  BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fSEtsqJuhWdh for <yaco-idsubmit-tool@core3.amsl.com>; Mon, 21 Mar 2011 10:36:20 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 5BA4028C0DF for <yaco-idsubmit-tool@ietf.org>; Mon, 21 Mar 2011 10:36:20 -0700 (PDT)
Received: by wwa36 with SMTP id 36so5166932wwa.13 for <yaco-idsubmit-tool@ietf.org>; Mon, 21 Mar 2011 10:37:52 -0700 (PDT)
Received: by 10.216.18.194 with SMTP id l44mr5648656wel.87.1300729071828; Mon, 21 Mar 2011 10:37:51 -0700 (PDT)
Received: from [192.168.0.192] ([77.227.215.107]) by mx.google.com with ESMTPS id j49sm2638467wer.38.2011.03.21.10.37.50 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Mar 2011 10:37:50 -0700 (PDT)
Message-ID: <4D878CF0.9080606@yaco.es>
Date: Mon, 21 Mar 2011 18:37:52 +0100
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez_L=F3pez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <4D872EDD.4090407@yaco.es>
In-Reply-To: <4D872EDD.4090407@yaco.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [yaco-idsubmit-tool] Beta server stopped
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: Mon, 21 Mar 2011 17:36:22 -0000

    beta.submit.yaco.es is back online.

    It seems that we have lost (one more time) the test submissions of 
the last week. Sorry for the inconvenience.

    Regards,

El 21/03/11 11:56, "Emilio A. Sánchez López" escribió:
> Hi all,
>
> Latelly we are having some troubles with our KVM server where
> beta.submit.yaco.es is located.
>
> Right now our infraestructure department is working to stabilize the
> system so the beta server will be down until this afternoon.
>
> When the server is running again I'll notify it to this list. Every
> issue about the tool thas has been discussed in the list is already
> commited (included the last patch sent by Henrik) so when the server
> comes up it will be updated with all the changes.
>
> Best,
>


-- 
Emilio A. Sánchez
esanchez@yaco.es
