Re: [hrpc] Censorship

S Moonesamy <sm+ietf@elandsys.com> Mon, 14 March 2022 09:58 UTC

Return-Path: <sm@elandsys.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 9A6BB3A02F9 for <hrpc@ietfa.amsl.com>; Mon, 14 Mar 2022 02:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.576
X-Spam-Level:
X-Spam-Status: No, score=0.576 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FAKE_REPLY_B=2.282, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 iqBwSIqiGOW1 for <hrpc@ietfa.amsl.com>; Mon, 14 Mar 2022 02:58:23 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 108883A00E3 for <hrpc@irtf.org>; Mon, 14 Mar 2022 02:58:23 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.138.166]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id 22E9vniG024179 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Mar 2022 02:58:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1647251898; x=1647338298; i=@elandsys.com; bh=t4s1xyIhIEWQH25BuWA/t8M9b1eGzxlzsaJAV10k9rI=; h=Date:To:From:Subject:Cc; b=1/CyALblhZUATfSujuTgtH8O+TT8b/6svl6a62mhdM8vNgr/piqpmfjtkNRuW83pE Z9fJu6wGNmMBJgJp3WULMZ7/C72eSwhVkdPINtrox0C5oGTZywpOOBol75vcibpeW7 TY/lxI0qcTtYUnBgWG/E7rNs9AxNK/CmjtYElRj8=
Message-Id: <6.2.5.6.2.20220314013727.07d5c430@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 14 Mar 2022 02:55:41 -0700
To: Mallory Knodel <mknodel@cdt.org>, hrpc@irtf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Bill Woodcock <woody@pch.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/R_WyVr0S6gKrsuv7E9evMylBorE>
Subject: Re: [hrpc] Censorship
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: Mon, 14 Mar 2022 09:58:28 -0000

Hi Mallory,

>As for my view, I'm with Stephen in that I don't think it's a
>particularly effective approach that the PCH letter takes and yet the
>political risks are tremendous. If we are to build the capacity in
>internet governance spaces like the IRTF/IETF-- and I would argue that
>is a far better goal than a new IG body-- it had better be on rock solid
>ground in terms of understanding efficacy and tradeoffs.

One of the questions which Bill raised was whether it was appropriate 
to do nothing in response to the recent events.  There is anecdotal 
evidence that some "digital" certificates were revoked.  I doubt that 
it has anything to do with protocol considerations or either of the 
two statements.

There was agenda item nearly a decade ago [1].  There hasn't been 
much open discussion on those topics in response to the recent 
events.  This could mean two things:

   (i) There isn't the capacity in those spaces; or

   (ii) People in those spaces are not interested in those topics.

Regards,
S. Moonesamy

1. https://documents-dds-ny.un.org/doc/UNDOC/LTD/G12/147/10/PDF/G1214710.pdf