IETF Logo Mail Archive

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

Paul Wouters <paul@nohats.ca> Thu, 09 April 2020 19:36 UTC

Return-Path: <paul@nohats.ca>
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 900343A0CAB for <hrpc@ietfa.amsl.com>; Thu, 9 Apr 2020 12:36:31 -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, SPF_HELO_NONE=0.001, SPF_NONE=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=nohats.ca
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 Ws4eFnMIZM3M for <hrpc@ietfa.amsl.com>; Thu, 9 Apr 2020 12:36:30 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A976D3A0CA5 for <hrpc@irtf.org>; Thu, 9 Apr 2020 12:36:25 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 48yrx20wW6zFhJ; Thu, 9 Apr 2020 21:36:22 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1586460982; bh=sW43q/C8iKidRPWxUJR7UenGtzfdqQH6etO8h5kZpBY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=TdXK+pS4E7QjPwPgl5y9P9cTxS4qgtf7Sr/e56092jsXJG5p8JjbgblbxODibXNTt ft/C3BS881dkw6Rer84An7PRjNuOA7PwOv1ZF1FlnSy0oNb2Kmz/IMcDW4piZm1JOt IHCyBUAG5JIKJEDJTYrPZyFq4WCrdfTEUPJPmzi0=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id HpKy4kk_Nxgl; Thu, 9 Apr 2020 21:36:20 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 9 Apr 2020 21:36:20 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 59FDD6020CF9; Thu, 9 Apr 2020 15:27:06 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 56B6082C65; Thu, 9 Apr 2020 15:27:06 -0400 (EDT)
Date: Thu, 09 Apr 2020 15:27:06 -0400
From: Paul Wouters <paul@nohats.ca>
To: Niels ten Oever <mail@nielstenoever.net>
cc: hrpc@irtf.org
In-Reply-To: <68b733e9-4053-60d9-b65d-f8dac2712f00@nielstenoever.net>
Message-ID: <alpine.LRH.2.21.2004091526060.21348@bofh.nohats.ca>
References: <de0ba70d-f2e8-93cb-d2a9-ee6b73b67f18@doria.org> <27c5e9d9-7c8a-985e-2fb1-99ccb50af9a7@cs.tcd.ie> <PR1PR07MB4891B933546D7D221A808694F3C00@PR1PR07MB4891.eurprd07.prod.outlook.com> <68b733e9-4053-60d9-b65d-f8dac2712f00@nielstenoever.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/yS5joQZ-JTTKbd_lnq2tIRXZOMc>
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: Thu, 09 Apr 2020 19:36:32 -0000

On Wed, 8 Apr 2020, Niels ten Oever wrote:

> The publication in the RFC-series and the connected exposure to, and interaction with, the technical community in the IRTF and IETF is for me the main reason to work and publish here.

I agree with Niels. Publishing an RFC is needed so that the IETF
community takes human rights considerations more seriously.

Paul

v2.23.0 | Report a Bug | By Email