[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Do drafts need to pass IDnits to be posted?
Hi Loa,
I also verify that drafts pass ID-nits before submitting them to
the IESG. The rejections came on drafts that are still a
work-in-progress in the WG.
Regards,
Brian
Loa Andersson wrote:
Brian, all,
I'm not the process expert, but there are two documents that
controls how IDs are formatted.
http://www.ietf.org/ietf/1id-guidelines.html among other things
contains *rules* that needs to be followed for publication.
http://www.ietf.org/ID-Checklist.html
contains the nits, that needs to be sorted out before sending the
document to IESG.
The current practice I used for a couple of years is to actually sort
out the nits before sending the ID to working group last call.
/Loa
Brian Haberman wrote:
I have wondered the same thing over the past few months. The only ID
nits rule that I am aware of is for advancing the draft to the IESG.
But I have been snagged at least twice in the past 3 months by the ID
nits check on drafts that are still be worked in my WG.
Regards,
Brian
Alexey Melnikov wrote:
Have I missed a change in rules requiring that all drafts need to
pass IDnits (as opposed to just have a correct boilerplate)?
------------------------------------------------------------------------
Subject:
Re: Manual Post Requested for draft-ietf-lemonade-imap-notify
From:
"IETF Drafts Team" <internet-drafts at ietf.org>
Date:
Mon, 23 Jun 2008 13:59:57 -0700 (PDT)
To:
alexey.melnikov at isode.com
To:
alexey.melnikov at isode.com
CC:
From wgchairs-bounces at ietf.org Thu Jun 26 06:54:45 2008
Return-Path: <wgchairs-bounces at ietf.org>
X-Original-To: wgchairs-archive at optimus.ietf.org
Delivered-To: ietfarch-wgchairs-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id C04613A6ACE;
Thu, 26 Jun 2008 06:54:45 -0700 (PDT)
X-Original-To: wgchairs at core3.amsl.com
Delivered-To: wgchairs at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 0C44F3A6ACE
for <wgchairs at core3.amsl.com>; Thu, 26 Jun 2008 06:54:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.932
X-Spam-Level:
X-Spam-Status: No, score=-2.932 tagged_above=-999 required=5
tests=[AWL=-0.333, BAYES_00=-2.599]
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 u6R+d8v2aLTE for <wgchairs at core3.amsl.com>;
Thu, 26 Jun 2008 06:54:44 -0700 (PDT)
Received: from jhuapl.edu (pilot.jhuapl.edu [128.244.198.200])
by core3.amsl.com (Postfix) with ESMTP id DE6633A6990
for <wgchairs at ietf.org>; Thu, 26 Jun 2008 06:54:43 -0700 (PDT)
Received: from ([128.244.206.192])
by pilot.jhuapl.edu with ESMTP id 5502123.100376255;
Thu, 26 Jun 2008 09:54:31 -0400
Message-ID: <48639F97.6000508 at innovationslab.net>
Date: Thu, 26 Jun 2008 09:54:31 -0400
From: Brian Haberman <brian at innovationslab.net>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Loa Andersson <loa at pi.nu>
Subject: Re: Do drafts need to pass IDnits to be posted?
References: <48639373.7030803 at isode.com> <4863969D.2010708 at innovationslab.net>
<48639DF8.50507 at pi.nu>
In-Reply-To: <48639DF8.50507 at pi.nu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Working Group Chairs <wgchairs at ietf.org>
X-BeenThere: wgchairs at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>,
<mailto:wgchairs-request at ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/wgchairs>
List-Post: <mailto:wgchairs at ietf.org>
List-Help: <mailto:wgchairs-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>,
<mailto:wgchairs-request at ietf.org?subject=subscribe>
Sender: wgchairs-bounces at ietf.org
Errors-To: wgchairs-bounces at ietf.org
Hi Loa,
I also verify that drafts pass ID-nits before submitting them to
the IESG. The rejections came on drafts that are still a
work-in-progress in the WG.
Regards,
Brian
Loa Andersson wrote:
Brian, all,
I'm not the process expert, but there are two documents that
controls how IDs are formatted.
http://www.ietf.org/ietf/1id-guidelines.html among other things
contains *rules* that needs to be followed for publication.
http://www.ietf.org/ID-Checklist.html
contains the nits, that needs to be sorted out before sending the
document to IESG.
The current practice I used for a couple of years is to actually sort
out the nits before sending the ID to working group last call.
/Loa
Brian Haberman wrote:
I have wondered the same thing over the past few months. The only ID
nits rule that I am aware of is for advancing the draft to the IESG.
But I have been snagged at least twice in the past 3 months by the ID
nits check on drafts that are still be worked in my WG.
Regards,
Brian
Alexey Melnikov wrote:
Have I missed a change in rules requiring that all drafts need to
pass IDnits (as opposed to just have a correct boilerplate)?
------------------------------------------------------------------------
Subject:
Re: Manual Post Requested for draft-ietf-lemonade-imap-notify
From:
"IETF Drafts Team" <internet-drafts at ietf.org>
Date:
Mon, 23 Jun 2008 13:59:57 -0700 (PDT)
To:
alexey.melnikov at isode.com
To:
alexey.melnikov at isode.com
CC:
curtis.kcurtis.king at isode.com, arnt at oryx.com, gparsons at nortel.com,
eburger at standardstrack.com
Hi All,
Unfortunately this draft has an error of being over 15 pages long and
not
having a table of contents. Please add a table of contents and I
will be
happy to post this draft.
Thank you,
IETF Secretariat
On Sat, June 21, 2008 9:51 am, IETF I-D Submission Tool wrote:
Manual Posting Requested for following Internet-Draft:
I-D Submission Tool URL:
https://datatracker.ietf.org/idst/status.cgi?submission_id=7434
Filename: draft-ietf-lemonade-imap-notify
Version: 06
Staging URL:
http://www3.ietf.org/proceedings/staging/draft-ietf-lemonade-imap-notify-06.txt
Title: The IMAP NOTIFY Extension
Creation_date: 2008-06-21
WG ID: lemonade
Number_of_pages: 22
Abstract:
This document defines an IMAP extension which allows a client to
request specific kinds of unsolicited notifications for specified
mailboxes, such as messages being added to or deleted from
mailboxes.
[[Add Updates: RFC-CONTEXT to the headers]]
Submitter: Alexey Melnikov (Alexey.Melnikov at isode.com)
Author(s):
Curtis King, Curtis.King at isode.com
Alexey Melnikov, Alexey.Melnikov at isode.com
Arnt Gulbrandsen, arnt at oryx.com
Comment:
IDnits shouldn't care about page length, this issue is not essential
for
drafts and can easily be fixed by the RFC editor.
ing at isode.com, arnt at oryx.com, gparsons at nortel.com,
eburger at standardstrack.com
Hi All,
Unfortunately this draft has an error of being over 15 pages long and
not
having a table of contents. Please add a table of contents and I
will be
happy to post this draft.
Thank you,
IETF Secretariat
On Sat, June 21, 2008 9:51 am, IETF I-D Submission Tool wrote:
Manual Posting Requested for following Internet-Draft:
I-D Submission Tool URL:
https://datatracker.ietf.org/idst/status.cgi?submission_id=7434
Filename: draft-ietf-lemonade-imap-notify
Version: 06
Staging URL:
http://www3.ietf.org/proceedings/staging/draft-ietf-lemonade-imap-notify-06.txt
Title: The IMAP NOTIFY Extension
Creation_date: 2008-06-21
WG ID: lemonade
Number_of_pages: 22
Abstract:
This document defines an IMAP extension which allows a client to
request specific kinds of unsolicited notifications for specified
mailboxes, such as messages being added to or deleted from
mailboxes.
[[Add Updates: RFC-CONTEXT to the headers]]
Submitter: Alexey Melnikov (Alexey.Melnikov at isode.com)
Author(s):
Curtis King, Curtis.King at isode.com
Alexey Melnikov, Alexey.Melnikov at isode.com
Arnt Gulbrandsen, arnt at oryx.com
Comment:
IDnits shouldn't care about page length, this issue is not essential
for
drafts and can easily be fixed by the RFC editor.