Re: [I18nrp] Additional input needed for i18nRP BOF

"Eliot Lear (elear)" <elear@cisco.com> Wed, 06 June 2018 06:34 UTC

Return-Path: <elear@cisco.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 58AAA130EB4 for <i18nrp@ietfa.amsl.com>; Tue, 5 Jun 2018 23:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 Tu8oE_qwYkNz for <i18nrp@ietfa.amsl.com>; Tue, 5 Jun 2018 23:34:51 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB8B8130EAC for <i18nrp@ietf.org>; Tue, 5 Jun 2018 23:34:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2658; q=dns/txt; s=iport; t=1528266891; x=1529476491; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=RnJjgUdRNaMDRBT0aTNKaawLQbCCKl7355CowNSVfm0=; b=dFL5WoNW0mrrJUOxbkVxzjLmxsTvBYUoyY/IUduns2Mb3XHH2/HA94Sg VKNFQBun17dnPoH6AeX4Wv7UulRIBb7c0CUXIZE9Stj3aWlJornF4M/9v 6n6B/bCtztN/rE52kjx4QdRrwXFT0dyZcneWZyjPKWVUV7pnpptoY/oIA 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DIAADVfxdb/5NdJa1bGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNDgWEog3iIBI5HIZRSFIFkC4RsAheCDiE0GAECAQEBAQE?= =?us-ascii?q?BAmwdC4UoAQEBAwEjEToQCwIBCBgCAiYCAgIwFRACBBODIoF5CKgoghyEWIN?= =?us-ascii?q?qgWiBC4c3gVQ/gQ8kDIIuLoRAARIBgx8xgiQCmHYJAo5mgT2DeIdtkQECERM?= =?us-ascii?q?BgSQdOGFxcBU7KgGCGIIgF44WAW+OM4I4AQE?=
X-IronPort-AV: E=Sophos;i="5.49,482,1520899200"; d="scan'208";a="403163248"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Jun 2018 06:34:50 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id w566Ynx4008823 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <i18nrp@ietf.org>; Wed, 6 Jun 2018 06:34:50 GMT
Received: from xch-aln-005.cisco.com (173.36.7.15) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 6 Jun 2018 01:34:49 -0500
Received: from xch-aln-005.cisco.com ([173.36.7.15]) by XCH-ALN-005.cisco.com ([173.36.7.15]) with mapi id 15.00.1320.000; Wed, 6 Jun 2018 01:34:49 -0500
From: "Eliot Lear (elear)" <elear@cisco.com>
To: "i18nrp@ietf.org" <i18nrp@ietf.org>
Thread-Topic: Additional input needed for i18nRP BOF
Thread-Index: AQHT/VEuwjdjvec+3keSRINsdtIo36RSxk1i
Date: Wed, 6 Jun 2018 06:34:49 +0000
Message-ID: <C41864BB-59DA-4849-BC77-18654CB4CD60@cisco.com>
References: <f997170c-3062-0241-e58d-7a3415fba983@nostrum.com>
In-Reply-To: <f997170c-3062-0241-e58d-7a3415fba983@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/l3YDigA2WlwgPuBYCmYfTIwxCyY>
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 06:34:54 -0000

I wish email had a “like” button. Good call. 

Eliot

> On Jun 6, 2018, at 6:45 AM, Adam Roach <adam@nostrum.com> wrote:
> 
> On today's BOF approval call, the IESG and IAB had an in-depth discussion of the i18nRP BOF proposal. One of the topics that was most discussed is a concern that the BOF does not have a clear path to success, largely because the proposal has very little discussion of proposed potential outcomes. While we do not expect the proponents to presuppose an outcome, we believe that achieving a positive outcome requires one or more specific proposals to serve as a basis for the conversation.
> 
> At the same time, the volume of traffic on the IETF mailing list on this topic does seem to demonstrate that there is interest in discussing topics related to internationalization. The ART area directors have therefore provisionally approved the BOF, subject to the proponents and/or any other interested parties providing concrete proposals as a basis for discussion.
> 
> Concretely, this means that the secretariat has been requested to schedule a one-hour slot for the Montreal meeting for the proposed BOF. If no concrete proposals for procedural approaches to address the issues described by the BOF proponents are available by Wednesday, June 13th, the secretariat will be requested to remove the BOF from the schedule.
> 
> Although it did not come up during the call, I personally wish to point out that open-ended brainstorming sessions without concrete proposals are typically handled as unofficial side-meetings (either in person or virtually). If the BOF proponents wish to maintain the open-ended brainstorm session described in the current proposal, the side meeting scheduling mechanism remains available; and I would be happy to help out should any difficulties occur in using that mechanism.
> 
> Please send proposals and any other follow-up messages to i18nrp@ietf.org
> 
> /a
>