
From henrik@levkowetz.com  Tue Apr 26 05:55:04 2011
Return-Path: <henrik@levkowetz.com>
X-Original-To: yaco-idsubmit-tool@ietfa.amsl.com
Delivered-To: yaco-idsubmit-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D36BE075D for <yaco-idsubmit-tool@ietfa.amsl.com>; Tue, 26 Apr 2011 05:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BDqGrNFv9Nft for <yaco-idsubmit-tool@ietfa.amsl.com>; Tue, 26 Apr 2011 05:55:03 -0700 (PDT)
Received: from merlot.tools.ietf.org (unknown [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by ietfa.amsl.com (Postfix) with ESMTP id 88193E0750 for <yaco-idsubmit-tool@ietf.org>; Tue, 26 Apr 2011 05:55:03 -0700 (PDT)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:58495 helo=dyn-fg117.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.75) (envelope-from <henrik@levkowetz.com>) id 1QEhn6-00025V-3m; Tue, 26 Apr 2011 14:54:56 +0200
Message-ID: <4DB6C09D.3060104@levkowetz.com>
Date: Tue, 26 Apr 2011 14:54:53 +0200
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: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
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-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] Fwd: Bug report in new IDST
X-BeenThere: yaco-idsubmit-tool@ietf.org
X-Mailman-Version: 2.1.12
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/options/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, 26 Apr 2011 12:55:04 -0000

Hi Emilio,

Please see below.  The observation is correct, of course -- the tool
needs to allow posting of correctly dated drafts from any timezone.


Best,

	Henrik

-------- Original Message --------
Subject: Bug report in new IDST
Date: Tue, 26 Apr 2011 06:19:49 -0400
From: Matt Larson <mlarson@amsl.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
CC: Glen Barney <glen@amsl.com>

Hi Henrik!

We've received a ticket for the new IDST:

> Hi,
> 
> There's a timezone-related bug in the new I-D submission tool,
> which did not exist in the old version.
> 
> It flags a metatdata error thus:
> 
> "Creation date 2011-04-26
> Creation Date must not be set after submission date"
> 
> I am submitting a draft created a few moments ago, just after
> 17:00 (5 pm.) today April 26th, New Zealand Standard Time.
> 
> Oh look, it's still April 25th in California - you guys are
> sooo backward :-)
> 
> The tool needs to have enough tolerance to deal with submissions
> from the other side of the world, like the previous version did.
> 
> (OK, I know the workaround, but this bug needs to be fixed.)
> 
> -- 
> Regards
> Brian Carpenter

Matt


-------------------------------------------
Matthew Larson, Asst. IT Director
Association Management Solutions
Forum Management, Meeting and Event Planning
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
http://www.amsl.com



From henrik@levkowetz.com  Tue Apr 26 06:01:57 2011
Return-Path: <henrik@levkowetz.com>
X-Original-To: yaco-idsubmit-tool@ietfa.amsl.com
Delivered-To: yaco-idsubmit-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF58E0771 for <yaco-idsubmit-tool@ietfa.amsl.com>; Tue, 26 Apr 2011 06:01:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, NORMAL_HTTP_TO_IP=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DiNNhTFjbAFu for <yaco-idsubmit-tool@ietfa.amsl.com>; Tue, 26 Apr 2011 06:01:56 -0700 (PDT)
Received: from merlot.tools.ietf.org (unknown [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by ietfa.amsl.com (Postfix) with ESMTP id 50C45E0764 for <yaco-idsubmit-tool@ietf.org>; Tue, 26 Apr 2011 06:01:56 -0700 (PDT)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:58528 helo=dyn-fg117.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.75) (envelope-from <henrik@levkowetz.com>) id 1QEhtj-0007UJ-GE; Tue, 26 Apr 2011 15:01:49 +0200
Message-ID: <4DB6C23B.2000008@levkowetz.com>
Date: Tue, 26 Apr 2011 15:01:47 +0200
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: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
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-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] Fwd: RE: [Tools-discuss] Fwd: [vixie@isc.org: googlebot to the rescue]
X-BeenThere: yaco-idsubmit-tool@ietf.org
X-Mailman-Version: 2.1.12
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/options/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, 26 Apr 2011 13:01:57 -0000

Hi Emilio,

Please see below.  The observation is correct -- a http GET should not
have side effects, so we need to make the confirmation link return a
web page with a confirmation button (which will do the appropriate POST
which should make the actual confirmation happen.


Best,

	Henrik

-------- Original Message --------
Subject: RE: [Tools-discuss] Fwd: [vixie@isc.org: googlebot to the rescue]
Date: Mon, 25 Apr 2011 21:56:29 -0700
From: Dan Wing <dwing@cisco.com>
To: 'Henrik Levkowetz' <henrik@levkowetz.com>,        'Mark Nottingham' <mnot@mnot.net>
CC: 'IETF TOOLS discussion' <tools-discuss@ietf.org>

> -----Original Message-----
> From: tools-discuss-bounces@ietf.org [mailto:tools-discuss-
> bounces@ietf.org] On Behalf Of Henrik Levkowetz
> Sent: Saturday, March 26, 2011 2:24 AM
> To: Mark Nottingham
> Cc: IETF TOOLS discussion
> Subject: Re: [Tools-discuss] Fwd: [vixie@isc.org: googlebot to the
> rescue]
> 
> Hi,
> 
> The new draft submission tool doesn't have this problem. 

Just now I used the new submission tool for the first time, and it also
seemed to only need a GET to authorize the actual posting of the I-D.

-d


> I'm about to
> start merging that code to the trunk of the datatracker svn repository
> in something like 10 minutes from now, and do the first deployment
> today.
> 
> 
> Best,
> 
> 	Henrik
> 
> 
> 
> On 2011-03-23 00:25 Mark Nottingham said the following:
> > In case this hasn't been seen -- it needs to be fixed (i.e., a GET
> shouldn't have such side effects).
> >
> > Cheers,
> >
> >
> > Begin forwarded message:
> >
> >> *Resent-From: *ietf-http-wg@w3.org <mailto:ietf-http-wg@w3.org>
> >> *From: *Stephane Bortzmeyer <bortzmeyer@nic.fr
> <mailto:bortzmeyer@nic.fr>>
> >> *Date: *23 March 2011 12:01:23 AM AEDT
> >> *To: *HTTP Working Group <ietf-http-wg@w3.org <mailto:ietf-http-
> wg@w3.org>>
> >> *Subject: **[vixie@isc.org: googlebot to the rescue]*
> >> *organization: *NIC France
> >> *archived-at: *<http://www.w3.org/mid/20110322130123.GB12433@nic.fr>
> >>
> >> The draft management tool apparently can change the state of a draft
> >> in response to a simple GET...
> >>
> >> Nice violation of the HTTP standard :-)
> >>
> >> *From: *Paul Vixie <vixie@isc.org <mailto:vixie@isc.org>>
> >> *Date: *19 March 2011 2:50:30 AM AEDT
> >> *To: *dnsext@ietf.org <mailto:dnsext@ietf.org>
> >> *Subject: **googlebot to the rescue*
> >>
> >>
> >> i think the 0x20 draft was going nowhere in any case so cancelling
> it is fine.
> >>
> >> 148.68.249.66.in-addr.arpa domain name pointer
> >> crawl-66-249-68-148.googlebot.com <http://crawl-66-249-68-
> 148.googlebot.com>.
> >>
> >> crawl-66-249-68-148.googlebot.com <http://crawl-66-249-68-
> 148.googlebot.com> has address 66.249.68.148
> >>
> >> it's interesting that it can be done by a web crawler, though.
> >>
> >> re:
> >>
> >>
> >> *From: *IETF I-D Submission Tool <idsubmission@ietf.org
> <mailto:idsubmission@ietf.org>>
> >> *Date: *18 March 2011 10:36:25 PM AEDT
> >> *To: *ipr@ietf.org <mailto:ipr@ietf.org>, dagon@cc.gatech.edu
> <mailto:dagon@cc.gatech.edu>, vixie@isc.org <mailto:vixie@isc.org>
> >> *Subject: **Submission of draft-vixie-dnsext-dns0x20-00 has been
> Cancelled *
> >>
> >>
> >> This message is to notify you that submission of an Internet-Draft,
> draft-vixie-dnsext-dns0x20-00, has just been cancelled by a user whose
> computer has an IP address of 66.249.68.148.
> >>
> >> The IETF Secretariat.
> >>
> >>
> >>
> >> _______________________________________________
> >> dnsext mailing list
> >> dnsext@ietf.org <mailto:dnsext@ietf.org>
> >> https://www.ietf.org/mailman/listinfo/dnsext
> >>
> >>
> >
> > --
> > Mark Nottingham http://www.mnot.net/
> >
> >
> >
> >
> >
> > _______________________________________________
> > Tools-discuss mailing list
> > Tools-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/tools-discuss
> _______________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss



From esanchez@yaco.es  Tue Apr 26 06:39:37 2011
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-idsubmit-tool@ietfa.amsl.com
Delivered-To: yaco-idsubmit-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4D6EE07A4 for <yaco-idsubmit-tool@ietfa.amsl.com>; Tue, 26 Apr 2011 06:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.816
X-Spam-Level: 
X-Spam-Status: No, score=-1.816 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hSGlhh5vzUuA for <yaco-idsubmit-tool@ietfa.amsl.com>; Tue, 26 Apr 2011 06:39:36 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 27FCEE06BC for <yaco-idsubmit-tool@ietf.org>; Tue, 26 Apr 2011 06:39:35 -0700 (PDT)
Received: by wyb29 with SMTP id 29so534379wyb.31 for <yaco-idsubmit-tool@ietf.org>; Tue, 26 Apr 2011 06:39:35 -0700 (PDT)
Received: by 10.227.200.138 with SMTP id ew10mr798797wbb.21.1303825175055; Tue, 26 Apr 2011 06:39:35 -0700 (PDT)
Received: from [192.168.0.197] ([77.227.215.107]) by mx.google.com with ESMTPS id z13sm3852481wbd.63.2011.04.26.06.39.33 (version=SSLv3 cipher=OTHER); Tue, 26 Apr 2011 06:39:34 -0700 (PDT)
Message-ID: <4DB6CB18.5080903@yaco.es>
Date: Tue, 26 Apr 2011 15:39:36 +0200
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <4DB6C23B.2000008@levkowetz.com>
In-Reply-To: <4DB6C23B.2000008@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [yaco-idsubmit-tool] Fwd: RE: [Tools-discuss] Fwd: [vixie@isc.org: googlebot to the rescue]
X-BeenThere: yaco-idsubmit-tool@ietf.org
X-Mailman-Version: 2.1.12
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/options/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, 26 Apr 2011 13:39:37 -0000

    Hi Henrik,

    I'm going to check all the views. Some of them (like approve or 
confirm view) are used as action in POST forms but if the user makes a 
GET request by hand the view also does the work.

    By the way, it seems that the original problem was that a webcrawler 
was launching actions in the old tool, with the new tool it doesn't 
happen cause the confirmation link is send by mail and contains a 
confirmation code so no webcrawler will follow it.

    But I'm going to do the changes so we respect the HTTP standard :)

El 26/04/11 15:01, Henrik Levkowetz escribió:
> Hi Emilio,
>
> Please see below.  The observation is correct -- a http GET should not
> have side effects, so we need to make the confirmation link return a
> web page with a confirmation button (which will do the appropriate POST
> which should make the actual confirmation happen.
>
>
> Best,
>
> 	Henrik
>
> -------- Original Message --------
> Subject: RE: [Tools-discuss] Fwd: [vixie@isc.org: googlebot to the rescue]
> Date: Mon, 25 Apr 2011 21:56:29 -0700
> From: Dan Wing<dwing@cisco.com>
> To: 'Henrik Levkowetz'<henrik@levkowetz.com>,        'Mark Nottingham'<mnot@mnot.net>
> CC: 'IETF TOOLS discussion'<tools-discuss@ietf.org>
>
>> -----Original Message-----
>> From: tools-discuss-bounces@ietf.org [mailto:tools-discuss-
>> bounces@ietf.org] On Behalf Of Henrik Levkowetz
>> Sent: Saturday, March 26, 2011 2:24 AM
>> To: Mark Nottingham
>> Cc: IETF TOOLS discussion
>> Subject: Re: [Tools-discuss] Fwd: [vixie@isc.org: googlebot to the
>> rescue]
>>
>> Hi,
>>
>> The new draft submission tool doesn't have this problem.
>
> Just now I used the new submission tool for the first time, and it also
> seemed to only need a GET to authorize the actual posting of the I-D.
>
> -d
>
>
>> I'm about to
>> start merging that code to the trunk of the datatracker svn repository
>> in something like 10 minutes from now, and do the first deployment
>> today.
>>
>>
>> Best,
>>
>> 	Henrik
>>
>>
>>
>> On 2011-03-23 00:25 Mark Nottingham said the following:
>>> In case this hasn't been seen -- it needs to be fixed (i.e., a GET
>> shouldn't have such side effects).
>>>
>>> Cheers,
>>>
>>>
>>> Begin forwarded message:
>>>
>>>> *Resent-From: *ietf-http-wg@w3.org<mailto:ietf-http-wg@w3.org>
>>>> *From: *Stephane Bortzmeyer<bortzmeyer@nic.fr
>> <mailto:bortzmeyer@nic.fr>>
>>>> *Date: *23 March 2011 12:01:23 AM AEDT
>>>> *To: *HTTP Working Group<ietf-http-wg@w3.org<mailto:ietf-http-
>> wg@w3.org>>
>>>> *Subject: **[vixie@isc.org: googlebot to the rescue]*
>>>> *organization: *NIC France
>>>> *archived-at: *<http://www.w3.org/mid/20110322130123.GB12433@nic.fr>
>>>>
>>>> The draft management tool apparently can change the state of a draft
>>>> in response to a simple GET...
>>>>
>>>> Nice violation of the HTTP standard :-)
>>>>
>>>> *From: *Paul Vixie<vixie@isc.org<mailto:vixie@isc.org>>
>>>> *Date: *19 March 2011 2:50:30 AM AEDT
>>>> *To: *dnsext@ietf.org<mailto:dnsext@ietf.org>
>>>> *Subject: **googlebot to the rescue*
>>>>
>>>>
>>>> i think the 0x20 draft was going nowhere in any case so cancelling
>> it is fine.
>>>>
>>>> 148.68.249.66.in-addr.arpa domain name pointer
>>>> crawl-66-249-68-148.googlebot.com<http://crawl-66-249-68-
>> 148.googlebot.com>.
>>>>
>>>> crawl-66-249-68-148.googlebot.com<http://crawl-66-249-68-
>> 148.googlebot.com>  has address 66.249.68.148
>>>>
>>>> it's interesting that it can be done by a web crawler, though.
>>>>
>>>> re:
>>>>
>>>>
>>>> *From: *IETF I-D Submission Tool<idsubmission@ietf.org
>> <mailto:idsubmission@ietf.org>>
>>>> *Date: *18 March 2011 10:36:25 PM AEDT
>>>> *To: *ipr@ietf.org<mailto:ipr@ietf.org>, dagon@cc.gatech.edu
>> <mailto:dagon@cc.gatech.edu>, vixie@isc.org<mailto:vixie@isc.org>
>>>> *Subject: **Submission of draft-vixie-dnsext-dns0x20-00 has been
>> Cancelled *
>>>>
>>>>
>>>> This message is to notify you that submission of an Internet-Draft,
>> draft-vixie-dnsext-dns0x20-00, has just been cancelled by a user whose
>> computer has an IP address of 66.249.68.148.
>>>>
>>>> The IETF Secretariat.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> dnsext mailing list
>>>> dnsext@ietf.org<mailto:dnsext@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/dnsext
>>>>
>>>>
>>>
>>> --
>>> Mark Nottingham http://www.mnot.net/
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Tools-discuss mailing list
>>> Tools-discuss@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tools-discuss
>> _______________________________________________
>> Tools-discuss mailing list
>> Tools-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-discuss
>
>
> _______________________________________________
> yaco-idsubmit-tool mailing list
> yaco-idsubmit-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool


From esanchez@yaco.es  Tue Apr 26 07:55:55 2011
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-idsubmit-tool@ietfa.amsl.com
Delivered-To: yaco-idsubmit-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABFF7E077A for <yaco-idsubmit-tool@ietfa.amsl.com>; Tue, 26 Apr 2011 07:55:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.816
X-Spam-Level: 
X-Spam-Status: No, score=-1.816 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y1QXoPZRkuqt for <yaco-idsubmit-tool@ietfa.amsl.com>; Tue, 26 Apr 2011 07:55:50 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 28BD1E0772 for <yaco-idsubmit-tool@ietf.org>; Tue, 26 Apr 2011 07:55:49 -0700 (PDT)
Received: by wyb29 with SMTP id 29so613340wyb.31 for <yaco-idsubmit-tool@ietf.org>; Tue, 26 Apr 2011 07:55:49 -0700 (PDT)
Received: by 10.227.0.152 with SMTP id 24mr872254wbb.126.1303829749047; Tue, 26 Apr 2011 07:55:49 -0700 (PDT)
Received: from [192.168.0.197] ([77.227.215.107]) by mx.google.com with ESMTPS id l24sm3896728wbc.47.2011.04.26.07.55.46 (version=SSLv3 cipher=OTHER); Tue, 26 Apr 2011 07:55:47 -0700 (PDT)
Message-ID: <4DB6DCF6.3060501@yaco.es>
Date: Tue, 26 Apr 2011 16:55:50 +0200
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <4DB6C23B.2000008@levkowetz.com>
In-Reply-To: <4DB6C23B.2000008@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [yaco-idsubmit-tool] Fwd: RE: [Tools-discuss] Fwd: [vixie@isc.org: googlebot to the rescue]
X-BeenThere: yaco-idsubmit-tool@ietf.org
X-Mailman-Version: 2.1.12
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/options/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, 26 Apr 2011 14:55:55 -0000

    Ticket #650 [1] is finished. Now any of the submission tool urls 
must change nothing in response to GET request.

    Best,

[1] http://trac.tools.ietf.org/tools/ietfdb/ticket/650

El 26/04/11 15:01, Henrik Levkowetz escribió:
> Hi Emilio,
>
> Please see below.  The observation is correct -- a http GET should not
> have side effects, so we need to make the confirmation link return a
> web page with a confirmation button (which will do the appropriate POST
> which should make the actual confirmation happen.
>
>
> Best,
>
> 	Henrik
>
> -------- Original Message --------
> Subject: RE: [Tools-discuss] Fwd: [vixie@isc.org: googlebot to the rescue]
> Date: Mon, 25 Apr 2011 21:56:29 -0700
> From: Dan Wing<dwing@cisco.com>
> To: 'Henrik Levkowetz'<henrik@levkowetz.com>,        'Mark Nottingham'<mnot@mnot.net>
> CC: 'IETF TOOLS discussion'<tools-discuss@ietf.org>
>
>> -----Original Message-----
>> From: tools-discuss-bounces@ietf.org [mailto:tools-discuss-
>> bounces@ietf.org] On Behalf Of Henrik Levkowetz
>> Sent: Saturday, March 26, 2011 2:24 AM
>> To: Mark Nottingham
>> Cc: IETF TOOLS discussion
>> Subject: Re: [Tools-discuss] Fwd: [vixie@isc.org: googlebot to the
>> rescue]
>>
>> Hi,
>>
>> The new draft submission tool doesn't have this problem.
>
> Just now I used the new submission tool for the first time, and it also
> seemed to only need a GET to authorize the actual posting of the I-D.
>
> -d
>
>
>> I'm about to
>> start merging that code to the trunk of the datatracker svn repository
>> in something like 10 minutes from now, and do the first deployment
>> today.
>>
>>
>> Best,
>>
>> 	Henrik
>>
>>
>>
>> On 2011-03-23 00:25 Mark Nottingham said the following:
>>> In case this hasn't been seen -- it needs to be fixed (i.e., a GET
>> shouldn't have such side effects).
>>>
>>> Cheers,
>>>
>>>
>>> Begin forwarded message:
>>>
>>>> *Resent-From: *ietf-http-wg@w3.org<mailto:ietf-http-wg@w3.org>
>>>> *From: *Stephane Bortzmeyer<bortzmeyer@nic.fr
>> <mailto:bortzmeyer@nic.fr>>
>>>> *Date: *23 March 2011 12:01:23 AM AEDT
>>>> *To: *HTTP Working Group<ietf-http-wg@w3.org<mailto:ietf-http-
>> wg@w3.org>>
>>>> *Subject: **[vixie@isc.org: googlebot to the rescue]*
>>>> *organization: *NIC France
>>>> *archived-at: *<http://www.w3.org/mid/20110322130123.GB12433@nic.fr>
>>>>
>>>> The draft management tool apparently can change the state of a draft
>>>> in response to a simple GET...
>>>>
>>>> Nice violation of the HTTP standard :-)
>>>>
>>>> *From: *Paul Vixie<vixie@isc.org<mailto:vixie@isc.org>>
>>>> *Date: *19 March 2011 2:50:30 AM AEDT
>>>> *To: *dnsext@ietf.org<mailto:dnsext@ietf.org>
>>>> *Subject: **googlebot to the rescue*
>>>>
>>>>
>>>> i think the 0x20 draft was going nowhere in any case so cancelling
>> it is fine.
>>>>
>>>> 148.68.249.66.in-addr.arpa domain name pointer
>>>> crawl-66-249-68-148.googlebot.com<http://crawl-66-249-68-
>> 148.googlebot.com>.
>>>>
>>>> crawl-66-249-68-148.googlebot.com<http://crawl-66-249-68-
>> 148.googlebot.com>  has address 66.249.68.148
>>>>
>>>> it's interesting that it can be done by a web crawler, though.
>>>>
>>>> re:
>>>>
>>>>
>>>> *From: *IETF I-D Submission Tool<idsubmission@ietf.org
>> <mailto:idsubmission@ietf.org>>
>>>> *Date: *18 March 2011 10:36:25 PM AEDT
>>>> *To: *ipr@ietf.org<mailto:ipr@ietf.org>, dagon@cc.gatech.edu
>> <mailto:dagon@cc.gatech.edu>, vixie@isc.org<mailto:vixie@isc.org>
>>>> *Subject: **Submission of draft-vixie-dnsext-dns0x20-00 has been
>> Cancelled *
>>>>
>>>>
>>>> This message is to notify you that submission of an Internet-Draft,
>> draft-vixie-dnsext-dns0x20-00, has just been cancelled by a user whose
>> computer has an IP address of 66.249.68.148.
>>>>
>>>> The IETF Secretariat.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> dnsext mailing list
>>>> dnsext@ietf.org<mailto:dnsext@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/dnsext
>>>>
>>>>
>>>
>>> --
>>> Mark Nottingham http://www.mnot.net/
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Tools-discuss mailing list
>>> Tools-discuss@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tools-discuss
>> _______________________________________________
>> Tools-discuss mailing list
>> Tools-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-discuss
>
>
> _______________________________________________
> yaco-idsubmit-tool mailing list
> yaco-idsubmit-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool


From esanchez@yaco.es  Tue Apr 26 08:12:33 2011
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-idsubmit-tool@ietfa.amsl.com
Delivered-To: yaco-idsubmit-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA6EEE0757 for <yaco-idsubmit-tool@ietfa.amsl.com>; Tue, 26 Apr 2011 08:12:33 -0700 (PDT)
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=[AWL=0.000,  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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S9NdYEd0nY1Y for <yaco-idsubmit-tool@ietfa.amsl.com>; Tue, 26 Apr 2011 08:12:33 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id C44B2E07DE for <yaco-idsubmit-tool@ietf.org>; Tue, 26 Apr 2011 08:12:26 -0700 (PDT)
Received: by wwa36 with SMTP id 36so536896wwa.13 for <yaco-idsubmit-tool@ietf.org>; Tue, 26 Apr 2011 08:12:26 -0700 (PDT)
Received: by 10.227.130.96 with SMTP id r32mr914852wbs.67.1303830745794; Tue, 26 Apr 2011 08:12:25 -0700 (PDT)
Received: from [192.168.0.197] ([77.227.215.107]) by mx.google.com with ESMTPS id h11sm3905398wbc.60.2011.04.26.08.12.23 (version=SSLv3 cipher=OTHER); Tue, 26 Apr 2011 08:12:24 -0700 (PDT)
Message-ID: <4DB6E0DC.2080801@yaco.es>
Date: Tue, 26 Apr 2011 17:12:28 +0200
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <4DB6C09D.3060104@levkowetz.com>
In-Reply-To: <4DB6C09D.3060104@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [yaco-idsubmit-tool] Fwd: Bug report in new IDST
X-BeenThere: yaco-idsubmit-tool@ietf.org
X-Mailman-Version: 2.1.12
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/options/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, 26 Apr 2011 15:12:33 -0000

    Hi Henrik,

    I have solved it just like the old told does by allowing that the 
creation date is three days after or three days before the current 
submission date.

    See http://trac.tools.ietf.org/tools/ietfdb/ticket/652

    Best,

El 26/04/11 14:54, Henrik Levkowetz escribió:
> Hi Emilio,
>
> Please see below.  The observation is correct, of course -- the tool
> needs to allow posting of correctly dated drafts from any timezone.
>
>
> Best,
>
> 	Henrik
>
> -------- Original Message --------
> Subject: Bug report in new IDST
> Date: Tue, 26 Apr 2011 06:19:49 -0400
> From: Matt Larson<mlarson@amsl.com>
> To: Henrik Levkowetz<henrik@levkowetz.com>
> CC: Glen Barney<glen@amsl.com>
>
> Hi Henrik!
>
> We've received a ticket for the new IDST:
>
>> Hi,
>>
>> There's a timezone-related bug in the new I-D submission tool,
>> which did not exist in the old version.
>>
>> It flags a metatdata error thus:
>>
>> "Creation date 2011-04-26
>> Creation Date must not be set after submission date"
>>
>> I am submitting a draft created a few moments ago, just after
>> 17:00 (5 pm.) today April 26th, New Zealand Standard Time.
>>
>> Oh look, it's still April 25th in California - you guys are
>> sooo backward :-)
>>
>> The tool needs to have enough tolerance to deal with submissions
>> from the other side of the world, like the previous version did.
>>
>> (OK, I know the workaround, but this bug needs to be fixed.)
>>
>> --
>> Regards
>> Brian Carpenter
>
> Matt
>
>
> -------------------------------------------
> Matthew Larson, Asst. IT Director
> Association Management Solutions
> Forum Management, Meeting and Event Planning
> 48377 Fremont Blvd., Suite 117, Fremont, CA  94538
> http://www.amsl.com
>
>
> _______________________________________________
> yaco-idsubmit-tool mailing list
> yaco-idsubmit-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool


From henrik@levkowetz.com  Tue Apr 26 09:46:53 2011
Return-Path: <henrik@levkowetz.com>
X-Original-To: yaco-idsubmit-tool@ietfa.amsl.com
Delivered-To: yaco-idsubmit-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCCE7E0760 for <yaco-idsubmit-tool@ietfa.amsl.com>; Tue, 26 Apr 2011 09:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k1fbP6xHZM2b for <yaco-idsubmit-tool@ietfa.amsl.com>; Tue, 26 Apr 2011 09:46:52 -0700 (PDT)
Received: from merlot.tools.ietf.org (unknown [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by ietfa.amsl.com (Postfix) with ESMTP id 81536E07A2 for <yaco-idsubmit-tool@ietf.org>; Tue, 26 Apr 2011 09:46:52 -0700 (PDT)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:50829 helo=dyn-fg124.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.75) (envelope-from <henrik@levkowetz.com>) id 1QElPM-0000he-Lq; Tue, 26 Apr 2011 18:46:43 +0200
Message-ID: <4DB6F6EF.8010709@levkowetz.com>
Date: Tue, 26 Apr 2011 18:46:39 +0200
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: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
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-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] Fwd: Fwd: New Version Notification for draft-iesg-rfc1150bis-00
X-BeenThere: yaco-idsubmit-tool@ietf.org
X-Mailman-Version: 2.1.12
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/options/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, 26 Apr 2011 16:46:53 -0000

Hi Emilio,

Please see below.

There are two adjustments which are needed for the I-D submission tool.

The first is a tweak to the template for the new version notification
messages; submissions which aren't working group documents or special
submissions should be called 'Individual Submission' rather than the
current 'Independent Submission'.


The second is to take care of documents named 'draft-iesg-*'.  These
are not individual submissions, but IESG submissions, and should be
treated as an exception, saying 'IESG' instead of 'Individual Submission'.

We probably should change the 'WG ID:' string to something more fitting,
too, but that's a minor template tweak.


Best,

	Henrik



-------- Original Message --------
Subject: Fwd: New Version Notification for draft-iesg-rfc1150bis-00
Date: Mon, 25 Apr 2011 09:19:44 -0500
From: Robert Sparks <rjsparks@nostrum.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
CC: Russ Housley <housley@vigilsec.com>

Hi Henrik -

Two things:

1) Can we make the submission tool label these "Individual Submission" and not "Independent Submission" below.
Independent Submission is a term used with the Independent Stream, and this is training people to use it a different way.

2) Can we have it notice draft-iesg- as a special case?

Begin forwarded message:

> From: Russ Housley <housley@vigilsec.com>
> Date: April 22, 2011 2:23:34 PM CDT
> To: IESG <iesg@ietf.org>
> Subject: Fwd: New Version Notification for draft-iesg-rfc1150bis-00 
> 
> 
> 
> Begin forwarded message:
> 
>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>> Date: April 22, 2011 3:20:19 PM EDT
>> To: housley@vigilsec.com
>> Subject: New Version Notification for draft-iesg-rfc1150bis-00 
>> 
>> 
>> A new version of I-D, draft-iesg-rfc1150bis-00.txt has been successfully submitted by Russ Housley and posted to the IETF repository.
>> 
>> Filename:	 draft-iesg-rfc1150bis
>> Revision:	 00
>> Title:		 FYI on FYI: No Additional FYI Notes
>> Creation_date:	 2011-04-22
>> WG ID:		 Independent Submission
>> Number_of_pages: 2
>> 
>> Abstract:
>> The FYIs (For Your Information) sub-series of RFCs was used by the
>> IETF User Services Area, which no longer exists.  The IESG does not
>> intend to make any further additions to the FYI sub-series.
>> 
>> 
>> 
>> The IETF Secretariat.
>> 
>> 
> 


