Re: [secdir] timing of reviews

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 24 May 2013 16:17 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15E8C21F8EBD for <secdir@ietfa.amsl.com>; Fri, 24 May 2013 09:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.605
X-Spam-Level:
X-Spam-Status: No, score=-102.605 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IcajQQKCnkFg for <secdir@ietfa.amsl.com>; Fri, 24 May 2013 09:17:49 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5716721F85EF for <secdir@ietf.org>; Fri, 24 May 2013 09:17:49 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-173.dsl.dynamic.sonic.net [50.1.98.173]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r4OGGNla061041 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 May 2013 09:16:24 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <D8F42545-7218-468D-AB6B-9D7116F35DA6@piuha.net>
Date: Fri, 24 May 2013 09:16:24 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA8C7C71-B6C5-4196-B587-5CA1FE40D82D@vpnc.org>
References: <5E0AD376-F965-40AE-82E4-667D16E8313A@piuha.net> <519F2EBD.1030408@cs.tcd.ie> <20895.23252.179339.686278@fireball.kivinen.iki.fi> <519F5D63.4000206@cs.tcd.ie> <519F7486.9030002@gmail.com> <67FEC0F2-9C17-4CCA-B41C-85FCB40E59E7@vpnc.org> <D8F42545-7218-468D-AB6B-9D7116F35DA6@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1503)
Cc: "secdir@ietf.org" <secdir@ietf.org>
Subject: Re: [secdir] timing of reviews
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 16:17:50 -0000

On May 24, 2013, at 8:59 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

> I feel bad about getting you guys all disagree with each other :-)

If WG co-chairs always agreed, you would only need one chair per WG. :-)

> But back to substance. There are obvious situations where WGLC is done on a document that is far from ready. It comes as a surprise, or the WG chairs are doing it on purpose to solicit reviews that do not appear to be forthcoming otherwise. While early help with half-finished documents can be useful, I don't think we should waste secdir, Gen-ART, etc. reviewer's time on it at that point. When we talked about this in the IESG, it was brought up that the WG chairs should be involved in the decision to call for review. I agree with that. There are details to think about, however. Perhaps we can request review only for docs that the chairs believe are well baked, and use the old process for others, for instance.

Maybe. But I also think that if the WG chair knows that the WG is going to get all their out-of-area reviews when they press the "WG LC" button, they might do a "pre-LC" call for more reviewers. This is a topic that Yaron and I are actively working on in our less-than-active WG.

A possibility for what you want is a new state or sub-state of "outside reviews requested" that the WG chair can put in the tracker. I bet this means that most chairs will forget to do this and Tero won't hear about most documents until they are in IETF LC, so I'm hesitant to propose this.

--Paul Hoffman