Re: [Ietf-languages] Fwd: RE: Re: Fwd: RE: can I share the drafts of ISO 21636

Sebastian Drude <drude@xs4all.nl> Thu, 10 December 2020 21:02 UTC

Return-Path: <drude@xs4all.nl>
X-Original-To: ietf-languages@ietfa.amsl.com
Delivered-To: ietf-languages@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2019A3A1272 for <ietf-languages@ietfa.amsl.com>; Thu, 10 Dec 2020 13:02:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.333
X-Spam-Level:
X-Spam-Status: No, score=-1.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=xs4all.nl
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 y6cXFaKECoGn for <ietf-languages@ietfa.amsl.com>; Thu, 10 Dec 2020 13:02:53 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE2FC3A1268 for <ietf-languages@ietf.org>; Thu, 10 Dec 2020 13:02:52 -0800 (PST)
Received: by mork.alvestrand.no (Postfix) id 2CF7A7C64EA; Thu, 10 Dec 2020 22:02:51 +0100 (CET)
Delivered-To: ietf-languages@alvestrand.no
X-Comment: SPF skipped for whitelisted relay - client-ip=192.0.33.74; helo=pechora4.lax.icann.org; envelope-from=drude@xs4all.nl; receiver=ietf-languages@alvestrand.no
Received: from pechora4.lax.icann.org (pechora4.icann.org [192.0.33.74]) by mork.alvestrand.no (Postfix) with ESMTPS id C0DCC7C4AD4 for <ietf-languages@alvestrand.no>; Thu, 10 Dec 2020 22:02:50 +0100 (CET)
Received: from lb3-smtp-cloud9.xs4all.net (lb3-smtp-cloud9.xs4all.net [194.109.24.30]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by pechora4.lax.icann.org (Postfix) with ESMTPS id 58A6470035C6 for <ietf-languages@iana.org>; Thu, 10 Dec 2020 21:02:48 +0000 (UTC)
Received: from cust-d2ef4cbd ([IPv6:fc0c:c138:75cc:34bc:4631:c48c:494:61cb]) by smtp-cloud9.xs4all.net with ESMTPA id nT4qkytWB6PzInT4wkRPNl; Thu, 10 Dec 2020 22:02:24 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xs4all.nl; s=s2; t=1607634144; bh=3WiVCm+5gTsbUON5BYd03wbtGJBtZdfbDv+wTezONZk=; h=Subject:To:From:Message-ID:Date:MIME-Version:Content-Type:From: Subject; b=h5d8r38CHfPxmHxkqa4JizI6Ltn9yqU9SkeuTgZbLe1b0Y3QIt5dLfdleBv74QOlQ JXHDRGz2WUFf/XZzLTSAaOYgCd34Z6ws1CIyzKK0xKdi1O5YTTh/2aoHbqYs5lHnzv 7oFftgGCqECTdwMVZdH/Kr6lg/rcJjcsegMIDYJj6mtM58qkBSr1/sTG6qwffwcgMh 6lJ3yyYIk0gKfBggIrsso6GLfcVo7Chaz2l9LNi8aDFcV/OMozDk3t9Vz1iXJMmCY4 DWiFqjFZcyHaG3qzklMxpSTfDb1IfBez2lqTPic6kiTRh0rlR3IGgt2kM3A06XgkR2 kLV9d/BNbU+SQ==
To: Peter Constable <pgcon6@msn.com>, IETF Languages Discussion <ietf-languages@iana.org>
References: <VI1PR0502MB37571FFEABA44E8C316DEB48CECC0@VI1PR0502MB3757.eurprd05.prod.outlook.com> <ca663582-aed1-f283-f43c-e0eeb5f56675@xs4all.nl> <MWHPR1301MB211215AE59A482E94E126C3E86CB0@MWHPR1301MB2112.namprd13.prod.outlook.com> <988cfe57-6e4b-d6cc-ac51-46e1502f1aff@xs4all.nl> <MWHPR1301MB211218CA70BD8A943D18B97886CB0@MWHPR1301MB2112.namprd13.prod.outlook.com>
From: Sebastian Drude <drude@xs4all.nl>
Message-ID: <46b60d6b-1bfe-8490-918d-4a7c69e2c3a6@xs4all.nl>
Date: Thu, 10 Dec 2020 18:02:15 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <MWHPR1301MB211218CA70BD8A943D18B97886CB0@MWHPR1301MB2112.namprd13.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------E8A98037F82E21BD9F2BCEE5"
Content-Language: pt-BR
X-CMAE-Envelope: MS4xfDivU/6+sEOm4P+IQn+BTTetdonDUJn6JCSVbbxlvPAlbDM8mZYC9i0sc1Hif1QxYKAO23EAe9lVl5v3/tQiANDgwRLbeBeLGhFYbK9FnYkvA8xFwxjj mXEW58T0EVgyNgookzNVdaoxy1zIjUlGNjD9r/SOahOLaFWS7yzkJ5jhkteT3hTWs1iry6BgkKQ6vpZhcrPn7wlv43+QbrRoZM7YJE/EznX/f6/49A+axeOI ZeIBWmVt8zx7MwcOkmHY5SjA08UHixVXAXbjt/3ENKnVGiRgQP1IgRQeezwCO9VC4VkgJ7jsdw/L+oISGdsjNg==
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2 (pechora4.lax.icann.org [0.0.0.0]); Thu, 10 Dec 2020 21:02:48 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/ESDoLHn5UqEDBkGXok3aJnRECSM>
Subject: Re: [Ietf-languages] Fwd: RE: Re: Fwd: RE: can I share the drafts of ISO 21636
X-BeenThere: ietf-languages@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ietf-languages.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-languages>, <mailto:ietf-languages-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-languages/>
List-Post: <mailto:ietf-languages@ietf.org>
List-Help: <mailto:ietf-languages-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-languages>, <mailto:ietf-languages-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Dec 2020 21:02:56 -0000

Thanks again, Peter.


Yes, in principle that seems feasible (even if one or two other IETF 
members would like to join?).

So let me understand this properly, I (me as a person?) could request 
with ISO (so to Mercè again, is it?) that IETF enters a liaison A with 
TC37/SC2, and Doug (and perhaps someone else) be IETF's representatives 
in this liaison?  (Shouldn't  that be approved somehow within IETF first?)

Hopefully indeed ANSI (which is the responsible member body) would 
approve that if approached by ISO.

I will have to look into the documentation that Mercè sent to understand 
the steps to establish such a liaison.  I'll do so as soon as I find the 
time.


Best,

Sebastian

-- 

Museu P.E. Goeldi, CCH, Linguistica ▪ Av. Perimetral, 1901
Terra Firme, CEP: 66077-530 ▪ Belém do Pará – PA ▪ Brazil
drude@xs4all.nl ▪ +55 (91) 3217 6024 ▪ +55 (91) 983733319
Priv: Tv. Juvenal Cordeiro, 184, Apt 104 ▪ 66070-300 Belém

On 10/12/2020 17:02, Peter Constable wrote:
>
> If Doug Ewell is the only one interested, then you could request that 
> he be recorded as representative for IETF as a category A liaison to 
> TC37/SC2. Given the nature of IETF, I don’t know if there might be 
> complications in getting that approved.
>
> “When an organization applies for a liaison with a technical 
> committee/subcommittee, the office of the
>
> CEO will check with the member body in the country in which the 
> organization is located. If the member
>
> body does not agree that the eligibility criteria have been met, the 
> matter will be referred to the TMB to
>
> define the eligibility.”
>
> Will they just say, “Oh, we already know about IETF; approved”? Or 
> will they say, “Let’s figure out who at IETF to contact to confirm 
> that they desire a liaison relationship and that this person is their 
> representative”?
>
> Peter
>
> *From:* Sebastian Drude <drude@xs4all.nl>
> *Sent:* Thursday, December 10, 2020 6:45 AM
> *To:* Peter Constable <pgcon6@msn.com>; IETF Languages Discussion 
> <ietf-languages@iana.org>
> *Subject:* Re: [Ietf-languages] Fwd: RE: Re: Fwd: RE: can I share the 
> drafts of ISO 21636
>
> Thanks, Peter.
>
> Your help will certainly be useful, much appreciated.
>
> I do not think that the cooperation on TR 21636 and BCP47 necessarily 
> needs to go via participating in ISO TC37/SC2/WG*1*, but those who 
> what to cooperate need a legal way to have access to the TR drafts.
>
> We'll figure that out when it comes to forming a concrete working 
> group on that cooperation.
>
>
> Best wishes from Brazil,
> Sebastian
>
>   
> -- 
>   
> Museu P.E. Goeldi, CCH, Linguistica ▪ Av. Perimetral, 1901
> Terra Firme, CEP: 66077-530 ▪ Belém do Pará – PA ▪ Brazil
> drude@xs4all.nl  <mailto:drude@xs4all.nl>  ▪ +55 (91) 3217 6024 ▪ +55 (91) 983733319
> Priv: Tv. Juvenal Cordeiro, 184, Apt 104 ▪ 66070-300 Belém
>
> On 10/12/2020 03:49, Peter Constable wrote:
>
>     If there are US persons that would like to become active in
>     TC37/SC2/WG2 to participate in work on ISO TR 21636 (currently in
>     development), you can respond to me privately and I can help
>     facilitate that.
>
>     Peter
>
>     *From:* Ietf-languages <ietf-languages-bounces@ietf.org>
>     <mailto:ietf-languages-bounces@ietf.org> *On Behalf Of *Sebastian
>     Drude
>     *Sent:* Wednesday, December 9, 2020 5:07 PM
>     *To:* IETF Languages Discussion <ietf-languages@iana.org>
>     <mailto:ietf-languages@iana.org>
>     *Subject:* [Ietf-languages] Fwd: RE: Re: Fwd: RE: can I share the
>     drafts of ISO 21636
>
>     Dear IETF-Languages group,
>
>
>     just to let you know, I got a response from the responsible ISO
>     secretariat (below).
>
>     I hope that it may be a possibility that those IETF-experts
>     interested in collaborating with us on making ISO TR 21636 and BCP
>     47 interoperable be recognized as experts sent by ANSI (and/or
>     NIST?) to participate in ISO TC 37 / SC 2.  That is how I am
>     participating, as a German DIN delegate expert (via University
>     Frankfurt).
>
>     Perhaps it would be worthwhile to contact the corresponding ANSI
>     people?  I guess you may have better contacts than "info@ansi.org
>     <mailto:info@ansi.org>".
>
>     Or you see other possibilities.
>
>     Best wishes,
>
>     Sebastian
>
>     -------- Forwarded Message --------
>
>     *Subject: *
>
>     	
>
>     RE: Re: [Ietf-languages] Fwd: RE: can I share the drafts of ISO 21636
>
>     *Date: *
>
>     	
>
>     Wed, 9 Dec 2020 08:21:21 +0000
>
>     *From: *
>
>     	
>
>     FERRES Mercè <FERRES@iso.org> <mailto:FERRES@iso.org>
>
>     *To: *
>
>     	
>
>     Drude Sebastian Mr <drude@xs4all.nl> <mailto:drude@xs4all.nl>,
>     Galinski Christian Dr <christian.galinski@chello.at>
>     <mailto:christian.galinski@chello.at>
>
>
>
>     Dear Sebastian,
>
>     Thanks for your request.
>
>     Technical participation in ISO is restricted to the ISO member
>     bodies and liaison organisations.
>
>     The US member body for ISO is ANSI: experts would have to be
>     appointed by ANSI. But I can see we have very many expert from
>     NIST in ISO, so although I do  not know how NIST and ANSI
>     coordinate, it seems possible that the experts come from NIST.
>
>     This is a general ANSI contact, in case it helps:
>     https://www.iso.org/member/2188.html
>     <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iso.org%2Fmember%2F2188.html&data=04%7C01%7C%7C3d285e825ab94935b95708d89d1a280d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637432082957393575%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2BaXbr50qqcOHDLIbutRAgCqzDsIDA3Gq%2FfyGFU4%2FklE%3D&reserved=0>
>
>     Best regards,
>
>     Mercè
>
>     mercè ferrés hernández
>     technical programme manager | standardization department |
>     iso central secretariat
>     <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.iso.org%2Fiso%2Fcontact_iso&data=04%7C01%7C%7C3d285e825ab94935b95708d89d1a280d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637432082957393575%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2MtACHnDdjr9bIrKVHS3V6KqpJAXdOR21WcH4uKOeTQ%3D&reserved=0>
>     | phone: +41 (0)79 222 53 54
>
>     *From:* Sebastian Drude <drude@xs4all.nl> <mailto:drude@xs4all.nl>
>     *Sent:* 2020-12-08 20:57
>     *To:* FERRES Mercè <FERRES@iso.org> <mailto:FERRES@iso.org>;
>     Galinski Christian Dr <christian.galinski@chello.at>
>     <mailto:christian.galinski@chello.at>
>     *Subject:* Fwd: Re: [Ietf-languages] Fwd: RE: can I share the
>     drafts of ISO 21636
>
>     Dear Mercé,
>
>     let me please come back to you with the question of how the
>     Internet Engineering Taskforce on languages can collaborate with
>     ISO TC 37 / SC 2.  The colleagues at the IETF are not convinced
>     that it would be a good move to enter a formal liaison.
>
>     Please see the dialogue below.  Doug has a point there at the end
>     -- it is *both* our interest, also ours at ISO, that the two
>     frameworks are interoperable.
>
>     Besides asking them to join ISO, are there other ways? Can
>     individual members of the IETF be nominated experts by NIST, for
>     instance?  Or can there an official joint working group be
>     established without the IETF entering a liaison?
>
>     Thanks again in advance for your help and for trying to think out
>     of the box.
>
>
>     Best wishes, Sebastian
>
>
>
>             Doug Ewell: I don’t think it would be helpful to establish a liaison with IETF
>
>             proper, that is to say, Area Directors and above. They have little to
>
>             no idea what this group does.
>
>               
>
>             Michael [Everson] and I are IETF Designated Experts for BCP 47. I wonder if SC2
>
>             would consider that.
>
>         SD: although I am not sure what exactly 'consider' means, in this context.
>
>         What would be the goal, that you as individual experts enter into a
>
>         special realtionship with ISO TC37/SC2?
>
>     DE: That's kind of what I meant, I guess. Perhaps other experts
>     from this list could participate as well. The list at large is not
>     really a committee with a fixed membership that could itself
>     constitute a liaison group. And again, IETF leadership would not
>     have any idea where to begin with this project.
>
>         SD: I did not conclude my first experience with getting an institution
>
>         (CLARIN) to be a ISO liaison, so I really do not have much expertise
>
>         here how to proceed.  I will consult with colleagues within ISO.
>
>     DE: That would be helpful.*The proposal has a stated goal of being
>     interoperable with BCP 47, but BCP 47 experts are not allowed to
>     view it or provide constructive feedback that could facilitate
>     that interoperability.  That doesn't feel much like a plan for
>     success.*
>
>
>
>     _______________________________________________
>
>     Ietf-languages mailing list
>
>     Ietf-languages@ietf.org  <mailto:Ietf-languages@ietf.org>
>
>     https://www.ietf.org/mailman/listinfo/ietf-languages  <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fietf-languages&data=04%7C01%7C%7C3d285e825ab94935b95708d89d1a280d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637432082957403569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=AmwudWXSJvAfjc2ByFLyIp2cOTD0KW2nCftt3TI5%2Fvo%3D&reserved=0>
>