Re: Do drafts need to pass IDnits to be posted?

[Alexey Melnikov <alexey.melnikov at isode.com>]

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/ietf/1id-guidelines.html> says:

  If the Internet-Draft is longer than about 15 pages, please include, 
on the second page, a table of contents to make the document easier to 
reference.

This doesn't sound normative.

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