Re: [hrpc] Possible options for a HRPC research publication
Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 08 April 2020 09:21 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
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 59F8D3A0F0D for <hrpc@ietfa.amsl.com>; Wed, 8 Apr 2020 02:21:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key) header.d=cs.tcd.ie
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 qCda0HZ_zcJh for <hrpc@ietfa.amsl.com>; Wed, 8 Apr 2020 02:21:45 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DD123A0C96 for <hrpc@irtf.org>; Wed, 8 Apr 2020 02:21:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 61B51BE47; Wed, 8 Apr 2020 10:21:43 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bSvSomUaPsn2; Wed, 8 Apr 2020 10:21:41 +0100 (IST)
Received: from [10.244.2.119] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 12ED0BE20; Wed, 8 Apr 2020 10:21:41 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1586337701; bh=xkHbkSxN4w1cp0agPAp7QrbkPk7J5pRh2ZXkJYBZdLc=; h=Subject:To:References:From:Date:In-Reply-To:From; b=x3NReAcZp5ecJHgvycjHQvc/hwm+hd/0rwf4xImKk1wxZzaK0WM5dkhxIabagvf2R 2FDJDv1I9gQUi7hY7n4BED2cTptf8zpeUbywvmG1yiikwjHQYONuefUrCyJ4RnrOdW eWHV0DrRQbYtNkbiZiKRYqJrDGamH3etm57ibazU=
To: avri@doria.org, hrpc@irtf.org
References: <de0ba70d-f2e8-93cb-d2a9-ee6b73b67f18@doria.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Autocrypt: addr=stephen.farrell@cs.tcd.ie; prefer-encrypt=mutual; keydata= mQINBFo9UDIBEADUH4ZPcUnX5WWRWO4kEkHea5Y5eEvZjSwe/YA+G0nrTuOU9nemCP5PMvmh 5Cg8gBTyWyN4Z2+O25p9Tja5zUb+vPMWYvOtokRrp46yhFZOmiS5b6kTq0IqYzsEv5HI58S+ QtaFq978CRa4xH9Gi9u4yzUmT03QNIGDXE37honcAM4MOEtEgvw4fVhVWJuyy3w//0F2tzKr EMjmL5VGuD/Q9+G/7abuXiYNNd9ZFjv4625AUWwy+pAh4EKzS1FE7BOZp9daMu9MUQmDqtZU bUv0Q+DnQAB/4tNncejJPz0p2z3MWCp5iSwHiQvytYgatMp34a50l6CWqa13n6vY8VcPlIqO Vz+7L+WiVfxLbeVqBwV+4uL9to9zLF9IyUvl94lCxpscR2kgRgpM6A5LylRDkR6E0oudFnJg b097ZaNyuY1ETghVB5Uir1GCYChs8NUNumTHXiOkuzk+Gs4DAHx/a78YxBolKHi+esLH8r2k 4LyM2lp5FmBKjG7cGcpBGmWavACYEa7rwAadg4uBx9SHMV5i33vDXQUZcmW0vslQ2Is02NMK 7uB7E7HlVE1IM1zNkVTYYGkKreU8DVQu8qNOtPVE/CdaCJ/pbXoYeHz2B1Nvbl9tlyWxn5Xi HzFPJleXc0ksb9SkJokAfwTSZzTxeQPER8la5lsEEPbU/cDTcwARAQABtDJTdGVwaGVuIEZh cnJlbGwgKDIwMTcpIDxzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllPokCQAQTAQgAKgIbAwUJ CZQmAAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAUCWj6jdwIZAQAKCRBasvrxexcr6o7QD/9m x9DPJetmW794RXmNTrbTJ44zc/tJbcLdRBh0KBn9OW/EaAqjDmgNJeCMyJTKr1ywaps8HGUN hLEVkc14NUpgi4/Zkrbi3DmTp25OHj6wXBS5qVMyVynTMEIjOfeFFyxG+48od+Xn7qg6LT7G rHeNf+z/r0v9+8eZ1Ip63kshQDGhhpmRMKu4Ws9ZvTW2ACXkkTFaSGYJj3yIP4R6IgwBYGMz DXFX6nS4LA1s3pcPNxOgrvCyb60AiJZTLcOk/rRrpZtXB1XQc23ZZmrlTkl2HaThL6w3YKdi Ti1NbuMeOxZqtXcUshII45sANm4HuWNTiRh93Bn5bN6ddjgsaXEZBKUBuUaPBl7gQiQJcAlS 3MmGgVS4ZoX8+VaPGpXdQVFyBMRFlOKOC5XJESt7wY0RE2C8PFm+5eywSO/P1fkl9whkMgml 3OEuIQiP2ehRt/HVLMHkoM9CPQ7t6UwdrXrvX+vBZykav8x9U9M6KTgfsXytxUl6Vx5lPMLi 2/Jrsz6Mzh/IVZa3xjhq1OLFSI/tT2ji4FkJDQbO+yYUDhcuqfakDmtWLMxecZsY6O58A/95 8Qni6Xeq+Nh7zJ7wNcQOMoDGj+24di2TX1cKLzdDMWFaWzlNP5dB5VMwS9Wqj1Z6TzKjGjru q8soqohwb2CK9B3wzFg0Bs1iBI+2RuFnxLkCDQRaPVAyARAA+g3R0HzGr/Dl34Y07XqGqzq5 SU0nXIu9u8Ynsxj7gR5qb3HgUWYEWrHW2jHOByXnvkffucf5yzwrsvw8Q8iI8CFHiTYHPpey 4yPVn6R0w/FOMcY70eTIu/k6EEFDlDbs09DtKcrsT9bmN0XoRxITlXwWTufYqUnmS+YkAuk+ TLCtUin7OdaS2uU6Ata3PLQSeM2ZsUQMmYmHPwB9rmf+q2I005AJ9Q1SPQ2KNg/8xOGxo13S VuaSqYRQdpV93RuCOzg4vuXtR+gP0KQrus/P2ZCEPvU9cXF/2MIhXgOz207lv3iE2zGyNXld /n8spvWk+0bH5Zqd9Wcba/rGcBhmX9NKKDARZqjkv/zVEP1X97w1HsNYeUFNcg2lk9zQKb4v l1jx/Uz8ukzH2QNhU4R39dbF/4AwWuSVkGW6bTxHJqGs6YimbfdQqxTzmqFwz3JP0OtXX5q/ 6D4pHwcmJwEiDNzsBLl6skPSQ0Xyq3pua/qAP8MVm+YxCxJQITqZ8qjDLzoe7s9X6FLLC/DA L9kxl5saVSfDbuI3usH/emdtn0NA9/M7nfgih92zD92sl1yQXHT6BDa8xW1j+RU4P+E0wyd7 zgB2UeYgrp2IIcfG+xX2uFG5MJQ/nYfBoiALb0+dQHNHDtFnNGY3Oe8z1M9c5aDG3/s29QbJ +w7hEKKo9YMAEQEAAYkCJQQYAQgADwUCWj1QMgIbDAUJCZQmAAAKCRBasvrxexcr6qwvD/9b Rek3kfN8Q+jGrKl8qwY8HC5s4mhdDJZI/JP2FImf5J2+d5/e8UJ4fcsT79E0/FqX3Z9wZr6h sofPqLh1/YzDsYkZDHTYSGrlWGP/I5kXwUmFnBZHzM3WGrL3S7ZmCYMdudhykxXXjq7M6Do1 oxM8JofrXGtwBTLv5wfvvygJouVCVe87Ge7mCeY5vey1eUi4zSSF1zPpR6gg64w2g4TXM5qt SwkZVOv1g475LsGlYWRuJV8TA67yp1zJI7HkNqCo8KyHX0DPOh9c+Sd9ZX4aqKfqH9HIpnCL AYEgj7vofeix7gM3kQQmwynqq32bQGQBrKJEYp2vfeO30VsVx4dzuuiC5lyjUccVmw5D72J0 FlGrfEm0kw6D1qwyBg0SAMqamKN6XDdjhNAtXIaoA2UMZK/vZGGUKbqTgDdk0fnzOyb2zvXK CiPFKqIPAqKaDHg0JHdGI3KpQdRNLLzgx083EqEc6IAwWA6jSz+6lZDV6XDgF0lYqAYIkg3+ 6OUXUv6plMlwSHquiOc/MQXHfgUP5//Ra5JuiuyCj954FD+MBKIj8eWROfnzyEnBplVHGSDI ZLzL3pvV14dcsoajdeIH45i8DxnVm64BvEFHtLNlnliMrLOrk4shfmWyUqNlzilXN2BTFVFH 4MrnagFdcFnWYp1JPh96ZKjiqBwMv/H0kw==
Message-ID: <27c5e9d9-7c8a-985e-2fb1-99ccb50af9a7@cs.tcd.ie>
Date: Wed, 08 Apr 2020 10:21:40 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <de0ba70d-f2e8-93cb-d2a9-ee6b73b67f18@doria.org>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="foeKVuhPSPCAQggKQKc2GzFO1X55zX1fu"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/hTWUucvpWwH_QzeNz6RtQtni-8E>
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:21:47 -0000
Hiya, I like the idea of trying an "annual" (or "occasional") publication of people's works-in-progress. Sounds a bit like the proceedings of a workshop maybe? But however it's cast, I'd say, yes do try it. One other point, maybe a nit: for me, the RG can be happy that a document is ready for publication even if there is not consensus on all of the content of the document. I think HRPC could do more to publish documents in that kind of state via inclusion of some well-written caveats/disclaimers. Cheers, S. On 08/04/2020 04:24, avri@doria.org wrote: > 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 >
- [hrpc] Possible options for a HRPC research publi… avri
- Re: [hrpc] Possible options for a HRPC research p… Mark Perkins
- Re: [hrpc] Possible options for a HRPC research p… Stephen Farrell
- Re: [hrpc] Possible options for a HRPC research p… Colin Perkins
- Re: [hrpc] Possible options for a HRPC research p… Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)
- Re: [hrpc] Possible options for a HRPC research p… Niels ten Oever
- Re: [hrpc] Possible options for a HRPC research p… farzaneh badii
- Re: [hrpc] Possible options for a HRPC research p… Mallory Knodel
- Re: [hrpc] Possible options for a HRPC research p… Paul Wouters
- Re: [hrpc] Possible options for a HRPC research p… farzaneh badii
- Re: [hrpc] Possible options for a HRPC research p… Niels ten Oever
- Re: [hrpc] Possible options for a HRPC research p… Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)
- Re: [hrpc] Possible options for a HRPC research p… Stephen Farrell
- Re: [hrpc] Possible options for a HRPC research p… Mallory Knodel
- Re: [hrpc] Possible options for a HRPC research p… avri
- Re: [hrpc] Possible options for a HRPC research p… avri
- Re: [hrpc] Possible options for a HRPC research p… avri
- Re: [hrpc] Possible options for a HRPC research p… farzaneh badii
- Re: [hrpc] Possible options for a HRPC research p… Stéphane Couture
- Re: [hrpc] Possible options for a HRPC research p… Mallory Knodel
- Re: [hrpc] Possible options for a HRPC research p… Stephane Bortzmeyer
- Re: [hrpc] Possible options for a HRPC research p… Stephane Bortzmeyer
- Re: [hrpc] Possible options for a HRPC research p… Colin Perkins
- [hrpc] The relevance of RFCs // was: Possible opt… Niels ten Oever
- Re: [hrpc] The relevance of RFCs // was: Possible… Paul Wouters