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

avri@doria.org Fri, 10 April 2020 17:19 UTC

Return-Path: <avri@doria.org>
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 2F03C3A0A45 for <hrpc@ietfa.amsl.com>; Fri, 10 Apr 2020 10:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.398, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 xjRkmtiK5d2V for <hrpc@ietfa.amsl.com>; Fri, 10 Apr 2020 10:19:36 -0700 (PDT)
Received: from smtprelay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CDCE3A0A44 for <hrpc@irtf.org>; Fri, 10 Apr 2020 10:19:36 -0700 (PDT)
Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay06.hostedemail.com (Postfix) with ESMTP id C352018225E09; Fri, 10 Apr 2020 17:19:34 +0000 (UTC)
X-Session-Marker: 6176726940646F7269612E6F7267
X-Spam-Summary: 50, 0, 0, , d41d8cd98f00b204, avri@doria.org, , RULES_HIT:1:2:41:152:355:379:599:800:854:960:967:973:988:989:1260:1261:1263:1277:1311:1313:1314:1345:1359:1437:1513:1515:1516:1518:1521:1593:1594:1605:1730:1747:1777:1792:1963:2110:2198:2199:2393:2525:2553:2566:2682:2685:2691:2693:2741:2743:2859:2906:2911:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3865:3866:3867:3868:3870:3871:3872:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4050:4184:4250:4362:4425:5007:6117:6119:7652:7875:7901:7903:7974:9010:9025:9036:10004:11232:11658:11855:11914:12043:12297:12324:12663:12740:12895:13019:13161:13229:14877:21060:21063:21080:21324:21325:21433:21451:21627:21740:21790:21796:21881:21972:21987:30036:30041:30045:30054:30062:30070:30080:30090:30091, 0, RBL:none, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:, MSBL:0, DNSBL:none, Custom_rules:0:0:0, LFtime:1, LUA_SUMMARY:none
X-HE-Tag: dolls81_195b6735e4e53
X-Filterd-Recvd-Size: 10445
Received: from [192.168.0.32] (ip68-9-182-8.ri.ri.cox.net [68.9.182.8]) (Authenticated sender: avri@doria.org) by omf12.hostedemail.com (Postfix) with ESMTPA; Fri, 10 Apr 2020 17:19:34 +0000 (UTC)
To: Colin Perkins <csp@csperkins.org>
Cc: hrpc@irtf.org
References: <de0ba70d-f2e8-93cb-d2a9-ee6b73b67f18@doria.org> <27c5e9d9-7c8a-985e-2fb1-99ccb50af9a7@cs.tcd.ie> <3A5AEC71-74DB-4FDF-B849-F2343959C903@csperkins.org>
From: avri@doria.org
Autocrypt: addr=avri@doria.org; prefer-encrypt=mutual; keydata= mQENBFJXhnsBCADCE9YSMulYfOUptnfTF1uwP2BRzUq87CAUacN6N5H5k8lNffqEXmgI+QWC njF7OwJ71rQLVYV3sIlpCQU9UyQfLHZDZoqV1d+aAJhgmmG6XtSReUi4jgAvsLzj+HkJSSqU 4voepwXs5k2DgRONAXojxvV5rFExDNqz4fn1zj2jf0SMTbCBkhHw1HQ6WXqW5T73LNbEUVys yEJBb+3+ITCVPTeVm7P/dXIEnsIsRVW8yeYoo1+E+jbPJ0OqHXtrWTdqqlU1CUHBgGWEFIIM qT//XVO0Kck8qyir7wqXb37fhSAkw32ZAKrd2NFrq71qk9Yj+SLtgxxqjGVLcbh3WVfRABEB AAG0G2F2cmkgZG9yaWEgPGF2cmlAZG9yaWEub3JnPokBPAQTAQgAJgIbLwcLCQgHAwIBBhUI AgkKCwQWAgMBAh4BAheAAhkBBQJZvm+gAAoJENWp6aLJ/w+n0uQIAKc9Cb5C7NLtjvu2JvcQ Y8QLiubHVvYHAcTsP2J/JRviFIGeZY7uShuhf6VDI8wYXqAjhLfPGv6KvudwOs1dZ4VvzmUt 4yLWPGMEz7T7cQItc/jcYxJYdtI9g0OfYXQMV4TIIQB2KC40bnLjkd3d5EF+2cQIpivE3RED xQ5DZcsbi5q4E4t0z4Zzg5iskwR58cNnlvbVr+5qlVu1KiDYAMCR+ij4AJtzwpRTkH1l6hrv zOmgsdqqPIzSHWdcZPxWsSOm53sFDE54qABhL6+4fbPzRDZnvObnTP6bukPzX5vzYFGXIcQw RqgGOHi83Wf6dPum6K9YmCzxbdgwRsQGEda5AQ0EUleGewEIAL2hntjt90xA4j9yeFvFMAmE qG/rIj0w3XfV3bQsDBUUdH4rVl3SSPp7rBNhe7drGN+SgQP2lJ6hcikRxfZEj9DnT0/9ERrM MqO7SYUTB6Tx8vIoqmy/T4nqHpVlnCTyixxJDaohUHtTkN3BEie//PlMnIC2tXt9JRMXSTAq 3lrUp2mRzDXBWZLhPVUqx6Uo3MMH1magq888piNJAQdf/P+vSuayjVwPyuG6HEEdG+5Q006Q eZQKfAZinaq3ICEyimWZbLWZRC5bw26PZOKxICUKNA1hAaIhw4OKrGsKRCTOj4cN5T6rr/wj zrwwsxypxUiEac/7bVwgEv5O/+TipAkAEQEAAYkCPgQYAQIACQIbLgUCWb5voAEpwF0gBBkB AgAGBQJSV4Z7AAoJEOo+L8tCe36HTvYH/RXrGi8imCvHou7US+pua51wTQrWghz6nEaavtFR +k5wHrf7WdjxEdDaJnb0YZki5IiEyqhHEq9Tb0JMCye4rzgWpvd1Z8JJ2FXmY8EjuRZg1sP3 3bvxm1hM7qsPCTWXzn1eHY3i5zAdtEEk0h+isLmEuuFWhGNwzyb0BC/h84YHylqv7/bMrHUz CtkUKdO2Vx0W8e/EWUDfLJnHtvTFTT1E/koOnWErJfmKhq2G6rMv13XsU7vr9AWZ6vDA3z2o sCHWkA2gkhU7TwHqPkY9HPoekUXlR/n11jBS9Jwx4Dnsyd7pqaRHxoyRqfEWTi8JF+N+XzC3 buf3G3buW3BDmNcJENWp6aLJ/w+n+8wH/0dSUDcbks95ftWatIWFXdtofOTexLvj13dH9BWa Sy7OQDKa1N838tTsRVLOMpF3AmbkqNWDqdF37HcWST9aO/Pi8vSFGtIbVHD74aFUG3PlNOBs lZea+G2UUV2WSXZPiTci8IL2mF8hrt92LcE/4AaaXh35d8ngpjx3CqIkFoMUHVEA1iye5YL+ GjqFR3R2AMLhwK/Nu9uw+cSJQqeZpzkGulPd4Gccxj8YMLQIiZwMTPIReWgSETohRmzyS04Z 6yQ42xcvoUbQ6lLXW0fjNNTBcD93hnlOk1xf+d9tx3fvigMrkxbVGNx/Ob92oRGwz63nnnPg DoZoktZXmyHIh2E=
Message-ID: <d275d504-90c1-da25-68bf-1371eafee83c@doria.org>
Date: Fri, 10 Apr 2020 13:19:33 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <3A5AEC71-74DB-4FDF-B849-F2343959C903@csperkins.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
X-Antivirus: Avast (VPS 200409-0, 04/09/2020), Outbound message
X-Antivirus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/Ja5_YjJiITEiiFPhrEAUQLihw28>
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: Fri, 10 Apr 2020 17:19:38 -0000

Hi,

Thanks for this.

Am trying to be flexible on RFCs and trying to be creative.

Basically will be willing to pass anything to the IRSG for review that
the RG agrees is ready to passed on. Will ask the question of the RG
after every drop of a ID that the authors feel might be ready.

Time will tell if anything comes of what may turn out to be workable
idea. I appreciate the offer of support if/when we figure out that we
want to do something beyond RFCs.

Thanks

avri



On 08-Apr-20 06:06, Colin Perkins wrote:
> Hi,
>
> There’s a lot of flexibility in how RGs can operate, and publishing
> RFCs is only one option.
>
> For RFCs, consensus documents are certainly important, and are a
> common way for groups to operate, but consensus is certainly not a
> requirement. Provided that it’s clear why a document is being
> published, and whose opinion it represents, a document that
> articulates a non-consensus view can be valuable. It might even be
> more valuable if published alongside a critique or discussion of the
> counterpoint view. The IRTF can be reasonably creative in what RFCs it
> publishes. 
>
> Outside of RFCs, IRTF groups have certainly held workshops in the
> past, and I'd encourage such activities. The RAIM workshop
> <https://irtf.org/raim-2015> was a good example of this, and the IAB
> workshops <https://www.iab.org/activities/workshops/> are perhaps
> another example that might be relevant. Such workshops often publish a
> workshop report as an RFC, but we could also work with an appropriate
> academic publisher to publish archival proceedings, or simply host
> position papers on the website as we did with RAIM. More formal
> workshops associated with academic conferences work for some research
> groups. Perhaps working with a journal might work for HRPC? 
>
> Also, we can certainly be more creative in hosting research group
> content on irtf.org <http://irtf.org>, where it makes sense to do so.
> If HRPC wants to host a curated set of resources, essays, commentary,
> etc., then we can discuss how to do that.
>
> Think what makes sense to advance the research of the group, and we’ll
> try to figure out how to support it.
>
> Cheers,
> Colin
>
>
>
>
>> On 8 Apr 2020, at 10:21, Stephen Farrell <stephen.farrell@cs.tcd.ie
>> <mailto:stephen.farrell@cs.tcd.ie>> wrote:
>>
>>
>> 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 <mailto: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
>>>
>>>
>>> *
>> <0x5AB2FAF17B172BEA.asc>
>
> -- 
> Colin Perkins
> https://csperkins.org/
>
>
>
>