[opsarea-chairs] FW: Help........

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 18 August 2011 15:34 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: opsarea-chairs@ietfa.amsl.com
Delivered-To: opsarea-chairs@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id EDF4021F8BCB for <opsarea-chairs@ietfa.amsl.com>; Thu, 18 Aug 2011 08:34:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.434
X-Spam-Status: No, score=-103.434 tagged_above=-999 required=5 tests=[AWL=0.165, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id mGffdN31B9Y6 for <opsarea-chairs@ietfa.amsl.com>; Thu, 18 Aug 2011 08:34:28 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com []) by ietfa.amsl.com (Postfix) with ESMTP id 31EE321F8BF9 for <opsarea-chairs@ietf.org>; Thu, 18 Aug 2011 08:34:28 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.68,245,1312171200"; d="scan'208";a="262972097"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([]) by de307622-de-outbound.net.avaya.com with ESMTP; 18 Aug 2011 11:35:21 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([]) by co300216-co-erhwest-out.avaya.com with ESMTP; 18 Aug 2011 11:31:41 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 18 Aug 2011 17:35:19 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040385FF10@307622ANEX5.global.avaya.com>
Thread-Topic: Help........
Thread-Index: AcxdvFCCefPWJpQ2SH2/dKYhsYl7FwAAAkGg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <opsarea-chairs@ietf.org>
Subject: [opsarea-chairs] FW: Help........
X-BeenThere: opsarea-chairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Archived discussions of OPS Area WG Chairs and ADs <opsarea-chairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsarea-chairs>, <mailto:opsarea-chairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsarea-chairs>
List-Post: <mailto:opsarea-chairs@ietf.org>
List-Help: <mailto:opsarea-chairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsarea-chairs>, <mailto:opsarea-chairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2011 15:34:29 -0000

opsarea-chairs@ietf.org, please!

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com] 
Sent: Thursday, August 18, 2011 6:33 PM
To: Tim Chown
Cc: ops-chairs@ietf.org
Subject: Re: Help........

On Aug 17, 2011, at 6:46 AM, Tim Chown wrote:

> I thought the submission tool now refused to post if there were nits

That would be nice if true. That said, if a draft is posted in June and
I send it to Ron in September, its references may have been updated in
the meantime if nothing else. 

> At least, I recall having this happen to me before the Quebec
> Tim
> On 13 Aug 2011, at 03:49, Joel Jaeggli wrote:
>> if the nit checker produces anything other than warnings it should be
summarily rejected unless it arrives with an explination of why it
doesn't pass the nit checker.
>> e.g. that's evidence of a lack of even rudimentary supervision.
>> joel
>> On Aug 12, 2011, at 10:55 AM, Ronald Bonica wrote:
>>> Folks,
>>> Most of you already do these things, so please don't be offended by
the following reminder.
>>> Before a WG chair sends a document to the IESG for publication, the
chair should:
>>> - Make sure that at least a few experts have carefully reviewed the
>>> - Read the draft
>>> - If the chair's evaluation of the draft is different than the
experts', resolve the difference
>>> - Run the ID nit checker (http://tools.ietf.org/tools/idnits/)
>>> - If any problems are found, ask the author fix them
>>> Lately, a few drafts with glaring errors have reached the IESG. We
can prevent this with a little up-front effort.
>>>                                               Ron