Re: Drafts getting bounced with little explanation

"Adrian Farrel" <adrian@olddog.co.uk> Sat, 10 July 2004 07:03 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26353 for <wgchairs-archive@lists.ietf.org>; Sat, 10 Jul 2004 03:03:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BjBrE-0007Yp-Gn; Sat, 10 Jul 2004 03:01:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BjBnK-0006xe-6W for wgchairs@megatron.ietf.org; Sat, 10 Jul 2004 02:57:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26151 for <wgchairs@ietf.org>; Sat, 10 Jul 2004 02:57:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BjBnH-0001WN-Og for wgchairs@ietf.org; Sat, 10 Jul 2004 02:57:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BjBmG-0001Ba-00 for wgchairs@ietf.org; Sat, 10 Jul 2004 02:56:04 -0400
Received: from relay2.mail.uk.clara.net ([80.168.70.142]) by ietf-mx with esmtp (Exim 4.12) id 1BjBlC-0000eJ-00 for wgchairs@ietf.org; Sat, 10 Jul 2004 02:54:59 -0400
Received: from du-069-0044.access.clara.net ([217.158.132.44] helo=Puppy) by relay2.mail.uk.clara.net with smtp (Exim 4.34) id 1BjBlB-000F4R-Ce; Sat, 10 Jul 2004 07:54:58 +0100
Message-ID: <006901c4664a$d11342d0$2c849ed9@Puppy>
From: Adrian Farrel <adrian@olddog.co.uk>
To: wgchairs@ietf.org
References: <p06110412bd131e03cf36@[10.71.10.67]><Pine.LNX.4.56.0407081558060.12199@internaut.com><40EE5709.6050205@erg.abdn.ac.uk><20040709114432.2a786753@chardonnay><099b01c465bc$b2312a00$0202a8c0@aceeinspiron> <20040709161200.723a7619@chardonnay>
Date: Sat, 10 Jul 2004 01:34:36 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,DATE_IN_PAST_06_12 autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: Re: Drafts getting bounced with little explanation
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
Sender: wgchairs-bounces@ietf.org
Errors-To: wgchairs-bounces@ietf.org
Content-Transfer-Encoding: 7bit

I *THINK* the issue is that you have to pick up the patched IPR boilerplate *AND* place it
as the first paragraph in the "Status of this Memo" section.

Of course, this neither conforms to 3667/8 nor to the email that we are supposed to
follow.

I have had several email exchanges asking (pleading) to be told what is wrong, and have
had no better answer than "you are not conformant". Several authors in my WG are
scrambling to meet the deadlines and are going frantic.

Can anyone give a good reason why it is not possible to point out how a draft is failing?
Are we playing class-room cricket? Are we trying to slow down the IETF process?

Adrian


----- Original Message ----- 
From: "Henrik Levkowetz" <henrik@levkowetz.com>
To: "Acee Lindem" <acee@redback.com>
Cc: <wgchairs@ietf.org>
Sent: Friday, July 09, 2004 3:12 PM
Subject: Re: Drafts getting bounced with little explanation


> Hi Acee,
>
>     This one passes, for instance:
>
> http://ietf.levkowetz.com/drafts/eap/rfc2284bis/draft-ietf-eap-rfc2284bis-10.e.txt
>
> For more information from the idnits tool, you can run it with
> the --verbose option.
>
> Henrik
>
> On Friday,  9 Jul 2004, Acee Lindem wrote:
> > Hi Henrik,
> > Can you (or somebody) point me to a draft that passes all the
> > nits? I tried a draft that "thought" conformed to 3667/3668 yet
> > the tools says I'm using RFC 2026 boilerplate.
> > Thanks,
> > Acee
> >
> > ----- Original Message ----- 
> > From: "Henrik Levkowetz" <henrik@levkowetz.com>
> > Cc: <wgchairs@ietf.org>
> > Sent: Friday, July 09, 2004 5:44 AM
> > Subject: Re: Drafts getting bounced with little explanation
> >
> >
> > >
> > > I've also run into one instance of a draft returned without explanatory
> > > details, and it's quite frustrating.
> > >
> > > One possible help in finding out what the trouble is with a particular
> > > document could be to use the idnits tool I've written
> > >  ( http://ietf.levkowetz.com/tools/idnits ) - that should report any
> > > ID-checklist violation that doesn't require human judgement.
> > >
> > > But it would be nicer and easier if the secretariat would just indicate
> > > why it is bouncing a document...
> > >
> > > Henrik
> > >
> > >
> > > On Friday,  9 Jul 2004, Gorry Fairhurst wrote:
> > > > This is frustrating, and I note that the ones that are not bounced do
> > > > not have consistent heading and ordering either.... :-)
> > > >
> > > > Waiting 1-2 days to receive this confusing message is certainly not
> > > > encouraging to new authors/editors.
> > > >
> > > > Gorry Fairhurst
> > > >
> > > > Bernard Aboba wrote:
> > > >
> > > > > Yes.  I had to compare my (bounced) draft to the ones that were getting
> > > > > through and then submit new boilerplate.   I still don't know what exactly
> > > > > was wrong, but they did get through after I copied successful boilerplate.
> > > > >
> > > > > On Thu, 8 Jul 2004, Paul Hoffman / VPNC wrote:
> > > > >
> > > > >
> > > > >>Just a heads-up: drafts that are not in perfect format are being
> > > > >>bounced with the message:
> > > > >>
> > > > >>According to the new procedure your I-D has to include some statements.
> > > > >>Please check the
> > > > >>http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg00244.html
> > > > >>for more details.
> > > > >>
> > > > >>The two rejections that I have seen did not say what was missing.
> > > > >>
> > > > >>--Paul Hoffman, Director
> > > > >>--VPN Consortium
> > > > >>
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
>
>
>