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

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 21 August 2012 19:58 UTC

Return-Path: <adrian@olddog.co.uk>
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 4435821F865C for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 12:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level:
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599]
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 cR2e3YkK0msG for <ietf@ietfa.amsl.com>; Tue, 21 Aug 2012 12:58:34 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 698C521F85A4 for <ietf@ietf.org>; Tue, 21 Aug 2012 12:58:34 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7LJwS7k012993; Tue, 21 Aug 2012 20:58:29 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7LJwR6u012975 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 21 Aug 2012 20:58:28 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Donald Eastlake' <d3e3e3@gmail.com>, 'Barry Leiba' <barryleiba@computer.org>
References: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk> <CAC4RtVB=N=CP7ManPZ=Hu65QbrX5WXnWRFFDZ-CpOcKQyqRWqg@mail.gmail.com> <CAF4+nEF96=yCWp7e7AUJ3iBn=gyaX8d9DxsLGL7=N00Ha8cUFw@mail.gmail.com>
In-Reply-To: <CAF4+nEF96=yCWp7e7AUJ3iBn=gyaX8d9DxsLGL7=N00Ha8cUFw@mail.gmail.com>
Subject: RE: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
Date: Tue, 21 Aug 2012 20:58:26 +0100
Message-ID: <142e01cd7fd7$54725e50$fd571af0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKeymM+EHr04TPM6WVIrAnLSY7g2QJcPtJAAZ1bDpGVokzpIA==
Content-Language: en-gb
Cc: draft-leiba-3777upd-eligibility@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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:58:35 -0000

How about asking Heather for the appropriate term?
Seems easier than guessing :-)

A

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: 21 August 2012 20:45
> To: Barry Leiba
> Cc: adrian@olddog.co.uk; draft-leiba-3777upd-eligibility@tools.ietf.org;
> ietf@ietf.org
> Subject: Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
> 
> On Tue, Aug 21, 2012 at 3:34 PM, Barry Leiba <barryleiba@computer.org> wrote:
> >> I have one discussion point and a number of small nits...
> >
> > ...
> >
> > 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.
> 
> In particular, I believe the there are Editorial Boards that the
> various fragments of the RFC Editor appoint and consult which should
> not be excluded.
> 
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
> 
> >>    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