Re: [hrpc] Possible options for a HRPC research publication

Mark Perkins <marknoumea@yahoo.com> Wed, 08 April 2020 09:08 UTC

Return-Path: <marknoumea@yahoo.com>
X-Original-To: hrpc@ietfa.amsl.com
Delivered-To: hrpc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 117FD3A0ECD for <hrpc@ietfa.amsl.com>; Wed, 8 Apr 2020 02:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 9oUre6D6SOHc for <hrpc@ietfa.amsl.com>; Wed, 8 Apr 2020 02:08:03 -0700 (PDT)
Received: from sonic314-15.consmr.mail.bf2.yahoo.com (sonic314-15.consmr.mail.bf2.yahoo.com [74.6.132.125]) (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 B15933A0F04 for <hrpc@irtf.org>; Wed, 8 Apr 2020 02:08:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1586336882; bh=8kdQadotnNH6QeK7zpHHyrCtB+3N9c2IfWwUq07lS6k=; h=Subject:To:References:From:Date:In-Reply-To:From:Subject; b=g/C99KB7Ok0XilNCnSaw3l0lNB4K7+ouweZYBQ1eX6cHez+j05gKMmsqzGAgzFOIpy3CU+7SSy+sWRY6gEnS3nzmsfzSgsY9tscQhu6HFOGuAyizVekvdOulhV1w5HYXqQmsxIWiO2Bhu+oh+BY6H7Gn3m60zdl29i8ZFzQ22pAvDY0xMIYzp8eY5N2dK8QyRdStRDTjMFcGve/15c7+/MZI68XdEYhX0KwAeaDHOO/ronX94RepCW/mzorzv3Sfq7LuGUTqZM8ZIjdK9OSc/84tVkPW4sZG+UAFYVDVnrds0Hw6d2nK4iZ055qR9iiXcsdFl8wBQVMEcY2lTA5xtQ==
X-YMail-OSG: wDUsghcVM1koNr4E.C9SMN77HsXGd9VhHBqA9aWAHvF9wk5Mack38jeMcUCG_UF GgsYWlSd8CHyGjfedjMQPHks6dYyak0JQvOxDpGmURdb6np9Je1M_iouSQLDMo1OvgndjTJe5MoV WwXL14mvy1v2n8chikmGM_M8M70iaeXiw9twSa0OAmu9WtHbgBDpTSCCEed1DJ3HQ_TqLS3W09Td BnIhW.2FOBK4YNqGQvSSY08IgBFma7IOod_Zw8bIW11C0VDhaeG.Qgm9TFBKhr7iLVKCShp95Mv2 .4ac4Kt5BA5rogp2d9khb51m9o.Gxi5.R82MqrA21dkVL0Hd2pGGvjryr49E6GywpKzRmzLWSNKs _z4DEKWcdwXVwCIuYi7yy4gBsqWy58V2zjF9NxJNx0mwyKc5S01nsDgJqyWNUXmTU1qRNu73S.J4 7.qjHa9vCnbn4u9fQTwc0D4tfzHwzttkF7hHZsC4naZ.17tD80axRlNfnkM_tL1Fo4EIa84RwHZW CrM6Z44CmLN3c6zj.9beE977G4ZYYuVLhKT1ix9EPGNjYpOSJ8n6sQhjER9W1Jt7iihDHDrJQZ0M fmQ4JOtKA_xzQOzfYlDeplDGGzaQta3kw6wqliCj.p3Gnf95kSK9sBRsgjPIs7FzDOA7UNRM05yL qo97AVA1TTLU.6XzuRNCP9Hbl6Wue9DoHLRP7ECpWs5frHDmsMacEpGYZRMsA4fPPnxOZDk3eR_B 2YRFv24T8GA.lT1c9iQ3e1k.bccxf6.yzaJFdpiHbQSxZ7K18DpfWJQr8b2zN6PnvUeaS9JhammL tMwfQmaV_gTW1RLAK26yG924wcVM8kwnoqbDziXhWR8H1OJcn5u_KDIwZo5qL_OMdcWaTEA4YaNt msjOMRHqvXhAoz4cGfkfn6EB5UEZI5rrb4VwSsgKwsyL0FgFxacfKi4AIWx6v.sRe0WKpPHsBLlc yrMNNfr49OAKiwWIt4NyaF2ixtoAU.ZDMssBDzOJsAV3Eec1ssTg.TV4GpSp2aVoK8_iBNahBrsX 5vIW9_1drt3G3BdHAjuKGTzk.wLUwbrnXW1F3ANDQIoqzE8TRWjKt.NwShdU031H2j2v3C7EVC1Y a6aHMolj0Tiv.3nq56lyiZV.6.ZTT_wczR0X9qPWkcQCVNUg1fsuCKFXHr0II0R4uoL2vQI6qsad 2MIC9wPQprxciyjTXrejQhOhjLD0Locv6MbzS2USdH88aiCdnxIigLI_ud3nLZs2vXjcn.oKEQVw I.ajkuslnWydcV8bDQQaZwijTeq3raM8zQxsPmOSk.PIEv0BaNFc8D.ouEemDqxymfcEDRZKwr_G yy.LvYEleqqceab29Rs6tvLCUSjMebUzoV1mNgnIofAVg9jxVklTMITBJDF9O2iAdWsO1olfWJN9 172nlzwYSVF9tnM4AnzkvQuAyYwD56q6VQpgHBENo.kiZg5D9gaQBR1zt
Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.bf2.yahoo.com with HTTP; Wed, 8 Apr 2020 09:08:02 +0000
Received: by smtp427.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID c1e8fbdfecb92234ebe9974b62f331c8; Wed, 08 Apr 2020 09:07:57 +0000 (UTC)
To: hrpc@irtf.org
References: <de0ba70d-f2e8-93cb-d2a9-ee6b73b67f18@doria.org>
From: Mark Perkins <marknoumea@yahoo.com>
Message-ID: <27f4afd3-f146-b3b4-cfa1-2270e3388c4c@yahoo.com>
Date: Wed, 08 Apr 2020 20:07:52 +1100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <de0ba70d-f2e8-93cb-d2a9-ee6b73b67f18@doria.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: fr
X-Antivirus: Avast (VPS 200407-0, 07/04/2020), Outbound message
X-Antivirus-Status: Clean
X-Mailer: WebService/1.1.15620 hermes Apache-HttpAsyncClient/4.1.4 (Java/11.0.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/2NiEryOJ_lYYPxOhXjaOFpipJeA>
Subject: Re: [hrpc] Possible options for a HRPC research publication
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: hrpc discussion list <hrpc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hrpc>, <mailto:hrpc-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hrpc/>
List-Post: <mailto:hrpc@irtf.org>
List-Help: <mailto:hrpc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hrpc>, <mailto:hrpc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2020 09:08:11 -0000

Hi Avri

If something is published as via a 'non RFC track', eg via wiki + epub 
format, this would not preclude publishing a later edition via the  the 
'RFC track'? If so, then I propose starting with

1 - Take the draft-politics as the seed and build the edition around the
various aspects of that discussion and the issues it raises.

and see how it goes. If this goes well, we could go onto your 2nd option.

However, I would not want to preclude things published via 'non RFC 
track' from being later developed into something published via RFC 
track; but more to get things moving, ensure all the discussion and 
refinement is not lost down an email black hole, and hopefully move 
things forward on the RG internet drafts side

Regards

Mark P.

Le 08/04/2020 à 14:24, avri@doria.org a écrit :
> Hi,
>
> **
>
> *Recently it has felt to me as though the HRPC RG was spinning its
> wheels. Our documents aren't moving along the path to RFC very easily
> and except for interesting presentations at meetings, well worth while
> in themselves, we have not been making great progress with our research.*
>
> *
>
> Part of this comes from a disagreement about the use of RFC publishing.
> While I know it is not a requirement for the IRTF, I strongly believe
> that research published as a RG RFC should have RG agreement for
> publication. This does not mean that there must be agreement on all the
> ideas and statements in the doc, but on the finished product. This was
> the process we followed with RFC 8280 and I believe it works. A bit
> cumbersome and slow at times, but it led to what I believe was a better
> document.
>
>
> Not everyone, including my co-chair, agrees with this approach. To many,
> the RFC series is the publication method used by the IRTF and not
> everything needs to be a rough consensus document. In addition to
> individual submissions, IRTF submissions are not bound by IETF rules.
> They rightly ask why HRPC should be so strict when there is no
> requirement to be. This question in one way or another has been asked by
> several people in the RG over the last few years. The recent difficulty
> has also been named as a reason for why researchers have seemed a bit
> less willing to work on documents lately; what is the point if they
> won't get published.
>
>
> I can see this point of view, and yet, I still find myself unable to
> support sending a RG document to the IRSG  that the RG does not think is
> ready for publication. Of course individual submissions would be a
> different matter as those do not need to be shepherded by the RG chair
> in the same way.
>
>
> Mallory and I have been discussing this impasse on and off for the last
> two years. The last time we talked we both felt, I believe, that it was
> time to try something different to break the impasse.  I made a
> suggestion for working with two tracks, one the RFC track where RG
> internet drafts need RG support for publication as RFCs, and the other,
> the production of a yearly publication that is an edited volume that
> does not require RG approval. Mallory suggested that I bring this to the
> RG for discussion.
>
>
> What I am suggesting for the non RFC track is that we pick a topic per
> year and publish a collection of research, essays, and commentary on
> that topic. How we would publish this remains to be discovered; could be
> anything from a wiki site to an ebook or even finding a journal to do a
> special release, if such a thing is possible. Mallory and I would act as
> lead editors, but we would need to enlist help from members of the RG in
> terms of putting such an effort together, as it does take work and
> contributions.
>
>
> In terms of topics for a first year, I have thought of two, but am not
> wed to either of them at all. We would need to find a subject that
> members of the RG, and hopefully others, would be willing to contribute
> their writing to.
>
>
> 1 - Take the draft-politics as the seed and build the edition around the
> various aspects of that discussion and the issues it raises.
>
>
> 2 - Take the HRPC core question on “whether standards and protocols can
> enable, strengthen or threaten human rights” and explore the various
> viewpoints on that question, including the pros, the cons and anything
> in between.
>
>
> This topic is on our upcoming meeting agenda, and I hope to gather some
> viewpoints that will guide how we can move forward, or not as the case
> may be, with the idea. Also interested in opinions on the list.
>
> Thanks
>
> avri
>
>
> *
>
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc

-- 
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus