Re: [I18nrp] Additional input needed for i18nRP BOF

[Peter Saint-Andre <[e-mail]>]

On 6/6/18 2:29 PM, Brian E Carpenter wrote:
> On 07/06/2018 06:23, Adam Roach wrote:
>> On 6/6/18 8:58 AM, John C Klensin wrote:
>>> I had hoped to see an open discussion in the weeks between now
>>> and the start of the IETF meeting but, while I have some ideas,
>>> the absence of specific proposals in the BOF proposal was
>>> deliberate.
>>
>>
>> I'd like to add two points of clarification, to make sure we're not 
>> talking past each other.
>>
>>  1. This is not a request to revise the BOF request itself. We are
>>     looking for concrete process proposals within the next week on this
>>     mailing list.
> 
> Isn't there one fairly straightforward proposal already implied in
> the mail threads? Something like:
> 
> * Before the following IETF, the IESG (via a suitable AD) should
> create an I18N Directorate which should perform I18N reviews
> on all drafts during IETF Last Call, and provide advice and
> assistance to draft authors and WGs earlier in the process when
> possible.

Concisely described; thanks!

I believe it would also be helpful to:

* Publish an RFC on "Internationalization Considerations for Internet
Protocols" (similar to RFC 3552 on security and RFC 6973 on privacy)
offering guidance for developing internationalization considerations for
inclusion in protocol specifications, with the goal of making designers
and implementers of Internet protocols aware of design choices related
to internationalization.

Such a document would gather, in one place, many of the lessons we have
learned over the last ~20 years from IETF work on UTF-8, IDNA[2008],
Stringprep, EAI, PRECIS, Net-Unicode, et al. Writing down this tribal
wisdom will help the proposed I18n Directorate complete its reviews,
train and mentor new participants, and educate outside experts in
particular scripts or languages regarding the challenges and constraints
of applying internationalization techniques to Internet protocols such
as the DNS, HTTP, and email.

Peter