Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt

Barry Leiba <barryleiba@computer.org> Tue, 21 August 2012 19:34 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
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 E22C421F869E for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 12:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.008
X-Spam-Level:
X-Spam-Status: No, score=-103.008 tagged_above=-999 required=5 tests=[AWL=-0.031, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OOVREEZk-Uuj for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 12:34:02 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 16FBE21F86B1 for <ietf@ietf.org>; Tue, 21 Aug 2012 12:34:01 -0700 (PDT)
Received: by lahm15 with SMTP id m15so102827lah.31 for <ietf@ietf.org>; Tue, 21 Aug 2012 12:34:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=2gon2sW1DHJYT6vb/kezoWG+fVMVQm7fUkn6VXRH32Y=; b=a3jKcnTInl6Vvo2SdDXccBGdoh7b/AJlNrejUDmXKou4IWTgMdQkdli9usokJQ4OXu E4qqAd8mWNDgtTMladaAKpnVGTRSPnq23V3nSean2xc+B6L8k2FF03N9uOy78VM4z4iG e3x8rX9xoEMK/U6Myedpm8FKSNrxKRoe9uvottNJG1cawSNwmmEkOhsK85WiG54h5kEb k0l3OCaONBAlr9FNNAn1LB/md51VpRF+EXymY8+KnphPTdo22kf+cQfIMnGQ5AyDfZtP nyRWlvwFir0lSKjmCH8tOsmL+Bmc0/JZ0gZ3K60hU+0mlk77Oor7aINi715jyyVnPKMO IZqQ==
MIME-Version: 1.0
Received: by 10.112.31.197 with SMTP id c5mr8226419lbi.50.1345577641038; Tue, 21 Aug 2012 12:34:01 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.113.196 with HTTP; Tue, 21 Aug 2012 12:34:00 -0700 (PDT)
In-Reply-To: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk>
References: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk>
Date: Tue, 21 Aug 2012 15:34:00 -0400
X-Google-Sender-Auth: fC6c08fRlUOizFoDFlV6OCbLy1U
Message-ID: <CAC4RtVB=N=CP7ManPZ=Hu65QbrX5WXnWRFFDZ-CpOcKQyqRWqg@mail.gmail.com>
Subject: Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
From: Barry Leiba <barryleiba@computer.org>
To: adrian@olddog.co.uk
Content-Type: text/plain; charset="ISO-8859-1"
Cc: draft-leiba-3777upd-eligibility@tools.ietf.org, 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: Tue, 21 Aug 2012 19:34:03 -0000

> I have one discussion point and a number of small nits...

Fine comments, all; thanks for taking the time.

I don't really see the discussion point as needing discussion.  You're
right, and I'll fix that set of stuff in the next version.  I could
say why certain text got in there in the first place (from early
comments and discussion), but it doesn't matter: I agree that it
should be changed.

There are just two points in your comments that I want to pursue:

>       15.2.  People serving in the IETF Secretariat and the RFC Editor
>            may not volunteer to serve as voting members of the
>            nominating committee.
>
> Slight problem with the term "RFC Editor" since this is a single person
> and also a service function. I suspect you mean the latter.

I do, and I actually had the same problem with it when I wrote it as
you do.  So help me, please: How *should* this be put?  I don't like,
"and those employed in the RFC Editor function," and I really can't
think of a concise, clean, accurate way to write it down, though we
all (today) know what it means.  Text, please, someone.

>    o  In bullet 16, to correct an erratum, the last paragraph is
>       replaced by this:
>
>          One possible selection method is described in RFC 3797 [1].
>
> Perfectly correct, but I don't think this document is the place to
> correct random errata.

I was (and am) ambivalent here.  I did not have this in my first
version.  SM did.  When we merged the proposals, I thought it was a
good idea to fix that.  But you're right that it's rather off topic,
and the right place to do that would be 3777bis, which this decidedly
is NOT.

I'm inclined to pull it out (having not checked that with SM yet,
though).  Does anyone (including SM) think it definitely needs to be
in here?

Barry