Re: [I18nrp] Additional input needed for i18nRP BOF

Adam Roach <adam@nostrum.com> Wed, 06 June 2018 22:11 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: i18nrp@ietfa.amsl.com
Delivered-To: i18nrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73F9A130DE8 for <i18nrp@ietfa.amsl.com>; Wed, 6 Jun 2018 15:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
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 eTdByMYWdTdq for <i18nrp@ietfa.amsl.com>; Wed, 6 Jun 2018 15:11:21 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90199130DE5 for <i18nrp@ietf.org>; Wed, 6 Jun 2018 15:11:20 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w56MBJfb044951 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 6 Jun 2018 17:11:20 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Peter Saint-Andre <stpeter@mozilla.com>, John C Klensin <john-ietf@jck.com>, i18nrp@ietf.org
References: <f997170c-3062-0241-e58d-7a3415fba983@nostrum.com> <CE6F76BB323F1555D6B217A5@PSB> <9ecf8b7a-d086-1c56-03fb-6773aed332c6@nostrum.com> <4DA478C4C99396556E1B3EF1@PSB> <a31e91ff-c78c-6a7c-fe8c-70b9563312f7@nostrum.com> <8774afa2-4d3f-bc08-69af-f88e229f547a@mozilla.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <07356789-b93f-b1a2-21d6-bef704b7c0b0@nostrum.com>
Date: Wed, 6 Jun 2018 17:11:13 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <8774afa2-4d3f-bc08-69af-f88e229f547a@mozilla.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/U6xqzD_Ua8broB0slNb5mX_ECTM>
Subject: Re: [I18nrp] Additional input needed for i18nRP BOF
X-BeenThere: i18nrp@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Internationalization Review Procedures <i18nrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18nrp/>
List-Post: <mailto:i18nrp@ietf.org>
List-Help: <mailto:i18nrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2018 22:11:25 -0000

On 6/6/18 4:19 PM, Peter Saint-Andre wrote:
> On 6/6/18 3:06 PM, Adam Roach wrote:
>> I trust that you will attempt to
>> provide these additional details?
> Adam, what are the IESG's requirements and expectations regarding
> creation of a new directorate? Is it expected, for instance, that a
> charter of some kind will need to be provided and approved? Guidance
> would be helpful.

With the caveat that I may have overlooked some bit of formal process...

In the general case, the creation of a new directorate simply requires 
convincing an area director that such directorate would serve a useful 
purpose. While directorates don't have charters per se, as a practical 
matter, they need to have a reasonably complete description of their 
purpose and role.

I'll note that directorates have a broad range of formality and document 
coverage associated with them: on one end, SECDIR and GENART have active 
secretaries who assign every document during IETF last call to a 
volunteer from a large pool of specialists (SECDIR) or generalists 
(GENART). On the other end, the SDPDIR has a relatively small pool of 
self-directed experts that authors, chairs and area directors can reach 
out to for advice and review. The SDPDIR does not proactively review 
documents.

In the specific case of establishing an i18n review directorate: based 
on the comments made so far, I think we would want a carefully defined 
process (possibly documented in an RFC, but perhaps just part of the 
directorate description) that described what role the directorate would 
play in the development and publication of specifications.

We would also need a plausible group of volunteers to execute that 
process. For example, if the proposed process were to review every 
document, in the style of SECDIR and GENART, I'd want to see a group of 
i18n expert volunteers (or volunteers who are willing and able to 
educate themselves into being experts) of roughly the same size as those 
directorates. For reference, the SECDIR has 64 members, and GENART has 
27. By contrast, if the role were to provide feedback only as requested, 
it could be similar in size to the SDPDIR, which has seven members.

In practice, I suspect the process the interested parties might 
reasonably settle upon would be somewhere in between, with someone 
(possibly a rotating duty) providing light triage on documents during 
IETF last call for the purposes of identifying which have an 
intersection with i18n, and a pool of dedicated reviewers to whom 
documents that do are assigned. The number of people such activity would 
require to succeed is, of course, a judgement call, but based on the 
size and function of existing directorates, I think we can safely say 
that it is significantly more than seven, and somewhat less than 27.

/a