Re: [Ltru] Resolving issues

"Mark Davis" <mark.davis@icu-project.org> Tue, 10 July 2007 14:38 UTC

Return-path: <ltru-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8GrS-0000l4-Va; Tue, 10 Jul 2007 10:38:42 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1I8GrR-0000kw-Jk for ltru-confirm+ok@megatron.ietf.org; Tue, 10 Jul 2007 10:38:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8GrR-0000ko-AI for ltru@ietf.org; Tue, 10 Jul 2007 10:38:41 -0400
Received: from nz-out-0506.google.com ([64.233.162.226]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8GrR-0006WO-0E for ltru@ietf.org; Tue, 10 Jul 2007 10:38:41 -0400
Received: by nz-out-0506.google.com with SMTP id n1so1000942nzf for <ltru@ietf.org>; Tue, 10 Jul 2007 07:38:40 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=o/jwbzQGTVatn95J9bGWs8YLGOWtMM+yEwgcRQthvDaNSV67sxa0goqrKRZ9t7T/sVQUhe8xa0ePPpuehlDp7IaikdD75peR+KZRobov188iOcxyt71HKQTnqqd/Yy6UPJSVjS53X1q6nt4Gw3MftXmd6CLTu9NR2HfXT7qh3Bo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=X6Vhg8dMoRa3d1k/H/pW7flfSyl/16xOqtnyOBIraxV5LTvAMcU/mZ4yrJoIQTQYYjNEqv2/tHedQMCaYT/eFIfByu1+SpuKwHt21ZqU+cvdGjG9hx8gksQTD64yre8xVYPHGgvOn6h0kp7STHOvJV6Iysy0Mb8TJ0wqVe4iaeM=
Received: by 10.114.77.1 with SMTP id z1mr4251291waa.1184078320183; Tue, 10 Jul 2007 07:38:40 -0700 (PDT)
Received: by 10.114.196.12 with HTTP; Tue, 10 Jul 2007 07:38:40 -0700 (PDT)
Message-ID: <30b660a20707100738o14d49d5era58bd9d2e9ef7376@mail.gmail.com>
Date: Tue, 10 Jul 2007 07:38:40 -0700
From: Mark Davis <mark.davis@icu-project.org>
To: Chris Newman <Chris.Newman@sun.com>
Subject: Re: [Ltru] Resolving issues
In-Reply-To: <3A5A0E7C33578AA7170CB186@10.0.1.21>
MIME-Version: 1.0
References: <30b660a20706291506jd82e202s8bbc931de10e24b3@mail.gmail.com> <6.0.0.20.2.20070701105325.0ac7b750@localhost> <30b660a20707011732n6bca450aj187400d05d3ba46c@mail.gmail.com> <3A5A0E7C33578AA7170CB186@10.0.1.21>
X-Google-Sender-Auth: 77bba359697b76e8
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: LTRU Working Group <ltru@ietf.org>
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1176201306=="
Errors-To: ltru-bounces@ietf.org

I was actually just quoting Martin in my message. The language Addison and I
originally suggested was:

The IESG will solicit nominees for the position (upon adoption of this
document or upon a vacancy) and then solicit feedback on the nominees'
qualifications.

Qualified candidates should be familiar with BCP 47 and its requirements; be
willing to fairly, responsively, and judiciously administer the registration
process; and be suitably informed about the issues of language
identification so that they can draw upon and assess the claim and
contributions of language experts and subtag requesters.

Mark

On 7/9/07, Chris Newman <Chris.Newman@sun.com> wrote:
>
> Mark Davis wrote on 7/1/07 17:32 -0700:
> > I think one big issue that isn't dealt with here is that the appointment
> > is for an infinite term. I think it would be much better to have a
> > limited term (e.g. two years), with a possibility for renewal.
> > This gives a good chance for reviewing from both sides (both the
> > reviewer as well as the IESG).
>
> Having to review _every_ expert reviewer every two years would be a
> significant
> time commitment for the IESG (there are a _lot_ of expert reviewers --
> 100+).
> I'd rather apply the "if it's not broken, don't fix it" principle to
> expert
> reviewers as that's more scalable.  If the community has problems with an
> expert reviewer, please express those concerns directly to the expert
> reviewer
> and if that doesn't satisfy, contact an appropriate area director or the
> IESG.
>
>                 - Chris
>
>


-- 
Mark
_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru