IETF Logo Mail Archive

Re: Updating BCP 10 -- NomCom ELEGIBILITY

Ted Lemon <Ted.Lemon@nominum.com> Wed, 11 February 2015 22:42 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 287311A0390 for <ietf@ietfa.amsl.com>; Wed, 11 Feb 2015 14:42:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UQ10FQj1C6AE for <ietf@ietfa.amsl.com>; Wed, 11 Feb 2015 14:42:11 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47B851A0104 for <ietf@ietf.org>; Wed, 11 Feb 2015 14:42:11 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 2D81EDA01C6 for <ietf@ietf.org>; Wed, 11 Feb 2015 22:42:11 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id EC91853E084; Wed, 11 Feb 2015 14:42:10 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 11 Feb 2015 14:42:10 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <28490.1423687732@sandelman.ca>
Date: Wed, 11 Feb 2015 17:42:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <1B8FA895-997E-452D-A180-F758CBAA3CDA@nominum.com>
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <9772.1420830216@sandelman.ca> <CAL0qLwZatYW2e4Wk6GXB2U26fsCn8BV2qt-07kHBugiq34zrcQ@mail.gmail.com> <54DBB40D.9030801@gmail.com> <28490.1423687732@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/OVxiuIw1M3I3lZIIuZ9uTFlxnew>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2015 22:42:13 -0000

On Feb 11, 2015, at 3:48 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
>  2) be the document uploader (pressed submit) on a document that
>     was scheduled into a WG session.
> 
> So anyone can upload at any time.  If the WG takes your document on,
> then the datatracker clearly knows this, so that part is easy to check.
> If you draft-author- is scheduled, this will require some additional
> datatracker effort for the WG chairs to indicate that your document goes into
> the agenda... but, I we wanted to be able to track which documents were
> discussed into which WG anyway for all sorts of reasons, so I think that his
> work will already happen.

I worry that this criterion will result in people being even more aggressive about scheduling talks on documents that were never discussed on the mailing list.

v2.23.0 | Report a Bug | By Email