Re: Fwd: New Version Notification for draft-kucherawy-rfc7437bis-03.txt

John C Klensin <john-ietf@jck.com> Thu, 19 February 2015 13:21 UTC

Return-Path: <john-ietf@jck.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 E0B401A9070 for <ietf@ietfa.amsl.com>; Thu, 19 Feb 2015 05:21:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 g9ajUPKPli1g for <ietf@ietfa.amsl.com>; Thu, 19 Feb 2015 05:21:24 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 310DE1A906F for <ietf@ietf.org>; Thu, 19 Feb 2015 05:21:24 -0800 (PST)
Received: from [198.252.137.35] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1YOR2g-0007MM-Q2; Thu, 19 Feb 2015 08:21:22 -0500
Date: Thu, 19 Feb 2015 08:21:17 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, ietf <ietf@ietf.org>
Subject: Re: Fwd: New Version Notification for draft-kucherawy-rfc7437bis-03.txt
Message-ID: <50A1D255974CEC3D77FC80EE@JcK-HP8200.jck.com>
In-Reply-To: <CAL0qLwZJNa+hajdk7XdKpWDau4CW8qxYZCGbbDFnYTiinS5oPw@mail.gmail.com>
References: <20150219050040.15019.44954.idtracker@ietfa.amsl.com> <CAL0qLwZJNa+hajdk7XdKpWDau4CW8qxYZCGbbDFnYTiinS5oPw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/SNyG0abO1XHzUHrhjrsY6GKph7U>
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: Thu, 19 Feb 2015 13:21:26 -0000


--On Thursday, February 19, 2015 00:04 -0500 "Murray S.
Kucherawy" <superuser@gmail.com> wrote:

>...
> 3) Added a section talking about evolving the qualification
> requirements the next time we revise this document, on the
> presumption that we can't come to consensus right now on an
> acceptable revision.  If in fact we can come to consensus on
> some, I can throw this out and make those changes.

Murray,

I might be the only one (and this is more or less a call for
others concerned to speak up), but I do not consider deferring
the qualification issues until the "next time" acceptable,
especially given how infrequently we are willing to
significantly revisit BCP 10 and the supposed emphasis on
diversity, expanding IETF participation, and enabling remote
participation.  I believe "qualification requirements" issue is
actually two topics with the second being more important than
the first:

(1) The actual qualifications for serving on the Nomcom (see
Sam's note and my follow-up).

(2) The linkages of various other procedural qualifications to
Nomcom eligibility.

At least the latter is, IMO, a fairness issue.

      john