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

farzaneh badii <farzaneh.badii@gmail.com> Wed, 08 April 2020 16:45 UTC

Return-Path: <farzaneh.badii@gmail.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 2AA093A0F53 for <hrpc@ietfa.amsl.com>; Wed, 8 Apr 2020 09:45:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=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=gmail.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 zWVGPzb_3Q_f for <hrpc@ietfa.amsl.com>; Wed, 8 Apr 2020 09:45:56 -0700 (PDT)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 04A573A0F4A for <hrpc@irtf.org>; Wed, 8 Apr 2020 09:45:56 -0700 (PDT)
Received: by mail-qt1-x834.google.com with SMTP id m33so367789qtb.3 for <hrpc@irtf.org>; Wed, 08 Apr 2020 09:45:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gZujmSH/whgjmGYynB15jnA5E6ElIVMcavR1LActc9o=; b=k+vH4Pt2LfTcIIiIca+aAF97AgMgHB+fPtSX6T2sXCs/88c0n1UcLPaAOR1UErxNYh 6U3+t4ToLKW0xJwCvQLluwQv4CTLmd7YnG9Pe5ETOVrnNCzTCAUYsYczv8bwUmSUA9Rs rtcx9jkVcFzUEvzf1cNJxitPv9gwJwEILV4NfDoE+ZIJDb45d5Ru3XgYKGVF1j8E6VRz aWTKFvgf3PivRuIZhzbq1pn3iyY9rXMgYi7jfBvft/msKHbh2YJ6lwtHzQXSvgpaz5GX Dm98iExWtyfIJjiLibaB0Ejjtv3dLulai/VX6Vjof93ZnT13sWXbPon+E3dra6ZxMxkW oG/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gZujmSH/whgjmGYynB15jnA5E6ElIVMcavR1LActc9o=; b=M/DOHEyx27347/m6zyRne4SGL0b8/BzsWqlQezuEsureINZAaO9ePNsFLIgtqOSBJA jDGZ8JV6As9R1O5+/C2uJfKHBYGcRS+GveneYFCpg41m/rrRcckEF8LKYyY3wuzR5WQ8 FaTjNFdNH950u/d2OsrpefXrYXQdvNZCNT+Ozzb5y9YByfISoIAk5S7uNMLwdbPGdO9B 8efD7DmLULitw+5sAEm5jBSJx2pgKYHhstcXzTUizcFKGN8udpov3asM2x7zMeSIid0G iWgm1HPHIpj8M0ra9r3c6vlNpuSxigk/CcZ7WBFv8G2ISW+QqCR9riTNnNNViv3l3I/I 5O4Q==
X-Gm-Message-State: AGi0PuYPuGDPKngthzmvQgbutKHT25kqqqpWLu4YTrKYfSQz4cW9SruH fS/X9ReJpHok/GZQ9qf6bo4A8Bwuo8IMZzs9GGY=
X-Google-Smtp-Source: APiQypKbwD4TsQvPU4a1B/uvywR20mP6JsAajyHqKsySccc22fex+DnHMYw13jcABJdiQDr6z3Vim/XXiF100Fgt/lg=
X-Received: by 2002:ac8:4e33:: with SMTP id d19mr8192661qtw.20.1586364354633; Wed, 08 Apr 2020 09:45:54 -0700 (PDT)
MIME-Version: 1.0
References: <de0ba70d-f2e8-93cb-d2a9-ee6b73b67f18@doria.org>
In-Reply-To: <de0ba70d-f2e8-93cb-d2a9-ee6b73b67f18@doria.org>
From: farzaneh badii <farzaneh.badii@gmail.com>
Date: Wed, 08 Apr 2020 12:45:43 -0400
Message-ID: <CAN1qJvA+LySB+fLea5W21LUwQCUCCSp3N=TMKCVNZxy7u=Lk7A@mail.gmail.com>
To: avri@doria.org
Cc: hrpc@irtf.org
Content-Type: multipart/alternative; boundary="000000000000d7d07105a2ca3b59"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/N_b6lf2OjdD8yPCLvPmDDeIugxk>
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 16:45:58 -0000

Excellent approach Avri. I think this approach could potentially reduce the
risk of the politicization of the RFC process, gives us an alternative to
discuss the topics freely without having to be concerned about reaching an
agreement or not. The approach also prevents us from diverting from RFCs
consensus based processes.

On Tue, Apr 7, 2020 at 11:25 PM <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
>
-- 
Farzaneh