IETF Logo Mail Archive

Re: [Ltru] Resolving issues

Chris Newman <Chris.Newman@Sun.COM> Tue, 10 July 2007 06:02 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 1I88nh-0004oY-UI; Tue, 10 Jul 2007 02:02:17 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1I88ng-0004oS-8i for ltru-confirm+ok@megatron.ietf.org; Tue, 10 Jul 2007 02:02:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I88nf-0004oK-Uo for ltru@ietf.org; Tue, 10 Jul 2007 02:02:15 -0400
Received: from brmea-mail-1.sun.com ([192.18.98.31]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I88nX-0000Zf-Pg for ltru@ietf.org; Tue, 10 Jul 2007 02:02:15 -0400
Received: from fe-amer-03.sun.com ([192.18.108.177]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l6A627p7021388 for <ltru@ietf.org>; Tue, 10 Jul 2007 06:02:07 GMT
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JKY00A018HPFP00@mail-amer.sun.com> (original mail from Chris.Newman@Sun.COM) for ltru@ietf.org; Tue, 10 Jul 2007 00:02:07 -0600 (MDT)
Received: from [10.0.1.21] (216-165-236-126.championbroadband.com [216.165.236.126]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JKY00DT88RFKZ10@mail-amer.sun.com>; Tue, 10 Jul 2007 00:02:06 -0600 (MDT)
Date: Mon, 09 Jul 2007 23:02:23 -0700
From: Chris Newman <Chris.Newman@Sun.COM>
Subject: Re: [Ltru] Resolving issues
In-reply-to: <30b660a20707011732n6bca450aj187400d05d3ba46c@mail.gmail.com>
To: Mark Davis <mark.davis@icu-project.org>, Martin Duerst <duerst@it.aoyama.ac.jp>
Message-id: <3A5A0E7C33578AA7170CB186@[10.0.1.21]>
MIME-version: 1.0
X-Mailer: Mulberry/3.1.6 (Mac OS X)
Content-type: text/plain; format="flowed"; charset="us-ascii"
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <30b660a20706291506jd82e202s8bbc931de10e24b3@mail.gmail.com> <6.0.0.20.2.20070701105325.0ac7b750@localhost> <30b660a20707011732n6bca450aj187400d05d3ba46c@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
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>
Errors-To: ltru-bounces@ietf.org

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



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

v2.14.0 | Report a Bug | By Email