Re: Purpose of IESG Review

John Leslie <john@jlc.net> Thu, 11 April 2013 22:08 UTC

Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C54A221F86F7 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 15:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.199
X-Spam-Level:
X-Spam-Status: No, score=-107.199 tagged_above=-999 required=5 tests=[AWL=-0.599, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 xLreQ3u0oW0s for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 15:08:01 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id A182D21F85DA for <ietf@ietf.org>; Thu, 11 Apr 2013 15:08:01 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id B5E5B33C26; Thu, 11 Apr 2013 18:08:01 -0400 (EDT)
Date: Thu, 11 Apr 2013 18:08:01 -0400
From: John Leslie <john@jlc.net>
To: l.wood@surrey.ac.uk
Subject: Re: Purpose of IESG Review
Message-ID: <20130411220801.GI71270@verdi>
References: <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org> <290E20B455C66743BE178C5C84F12408223F494E5A@EXMB01CMS.surrey.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E5A@EXMB01CMS.surrey.ac.uk>
User-Agent: Mutt/1.4.1i
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 11 Apr 2013 22:08:03 -0000

l.wood@surrey.ac.uk <l.wood@surrey.ac.uk> wrote:
> 
> +1 to Joe's comment.
> 
> Example: the existence of the extensibility bit in multipath tcp,
> which i understand came out of a review by the iesg member responsible
> for security.

   I assume you're talking RFC 6824. I recommend reading the Narrative
Minutes of September 13th:

http://www.ietf.org/iesg/minutes/2012/narrative-minutes-2012-09-13.html

There were DISCUSSes from Stephen Farrell (Security), Barry Leiba
(Applications), Robert Sparks (RAI), and Sean Turner (Security).
Stephen Farrell did complain about a negotiation scheme that only allowed
seven security algorithms; and asked "how you could practically extend
this design for stronger cryptographic security".

> In that context, that would be outside the scope of any security
> review,

   Hardly! Those are exactly what I would hope for in a Security review.

> and the comments weren't raised in a personal capacity years earlier
> on the relevant mailing list.

   I'm not going to research that; but it seems hardly relevant...

> Sure, getting past iesg only cost multipath tcp a bit.

   (which, BTW, I strongly endorse!)

> But iesg members exceeding their bounds as reviewers and leaving a
> personal mark seems commonplace.

   Perception is easily mistaken for reality. :^(

   But if you look at the datatracker history:

http://datatracker.ietf.org/doc/draft-ietf-mptcp-multiaddressed/history/

you'll see that all four DISCUSSes were cleared by October 22.

   Considering that this document started life in June of 2010, and
was a major enhancement of TCP, 40 days doesn't seem excessive, IMHO.

> iesg members are there for expertise in their area and to provide that
> expertise in focused reviews,

   Note that there's really a lot of overlap between areas: so "focused"
may not be the right criterion.

> not to block until a protocol is redesigned to suit their personal
> tastes.

   I am told this used to happen. I have not experienced it in the five
years I have been scribing.

====

   I really don't know how to change the perception -- but I strongly
recommend referring to the Narrative Minutes. Hopefully that history
will be preserved "forever".

--
John Leslie <john@jlc.net>