IETF Logo Mail Archive

Re: [hrpc] Ten years after Snowden (2013 - 2023), is IETF keeping its promises?

Abdussalam Baryun <abdussalambaryun@gmail.com> Fri, 06 January 2023 07:50 UTC

Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC92C14CF16 for <ietf@ietfa.amsl.com>; Thu, 5 Jan 2023 23:50:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZytuzXo3OIn2 for <ietf@ietfa.amsl.com>; Thu, 5 Jan 2023 23:50:20 -0800 (PST)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 837BEC14CE36 for <ietf@ietf.org>; Thu, 5 Jan 2023 23:50:20 -0800 (PST)
Received: by mail-lj1-x22f.google.com with SMTP id bx6so741963ljb.3 for <ietf@ietf.org>; Thu, 05 Jan 2023 23:50:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Y1lZhrqkwaeQiu4V2zpPdNXJUZibtryJmw3K0kbGBGQ=; b=l81qx1UES0Iulp8ay/CoEKXl8SkLMk90doSCS1ktrrBb9MoY5uOEiqwLyLTuUYTyfw K8fkb+i0ppt5/2jV1+xXAMA3BTQgGk6xU5kekBubmIsQAexbvvK4icx5s5WBAVu48rn4 isWa95ZrbETxoKlZhH2rZtRSahDdcrpF4OPtguGoJPFKATp7Kkn/awWcqdfmfJjO05GY 9I8cnHKjHfKxC4qwZXcuHF1in83fpLg9bd5LZdrhBHG28HwxCk1nAyWQ1Nn1tjFAgFF7 dX6k0pwoLK6548ZxyZWi9F41YmPC7cSWryfiJwP69MSE1QoFl9GF3TF5qReziu0rzr1l rl0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Y1lZhrqkwaeQiu4V2zpPdNXJUZibtryJmw3K0kbGBGQ=; b=o9JcHXr8StvT8EJuFo9DjJfSjDMidkICksfFJAomcYh9Zr/HcZq4SGRGUDlwmcQ8O7 FvEmCLBiO8Xzxr5K0t6FS0e3f1Tx5y3+crNHjtW9bp8phTypryXfam5JFSGqRz2r+mSz GQWJhSUP0X4jwqDidkhGvipomfzRKjaOhh2ebc6uBF/5cSUglgjfqNBZADl25C1wRfZ1 wGSJL6Ryt43Ab3SZuC4msVBfs4fm5N0+bqEx8LUMyP5i2RK3b2BHyY4NJ4lvPkkQ63Z3 Nik560nh8h5Bk0kDQzEtOonD4K0LU4aLcs9ewq3nx8IviIGM9QMBxNgV+7V1bdPYxObW 2omQ==
X-Gm-Message-State: AFqh2krM8LgSpgI2be4e2dblcDg+YSIkq10N4JZjWvNtOxiP85CF0vFi eyzCrM9GqR/2KY/wPxZ4oREtWVGVbmsb+mJ+RYxLPilR
X-Google-Smtp-Source: AMrXdXtM5JvbBAIwX9+WDPseS5h3spby8C6ZPZYLNJCi7d5EvwcjBDm35SkUIuKHQLqU2lbvX+QG/TpruPiH/hFo/4E=
X-Received: by 2002:a2e:8742:0:b0:27f:da32:be4f with SMTP id q2-20020a2e8742000000b0027fda32be4fmr1641754ljj.256.1672991418731; Thu, 05 Jan 2023 23:50:18 -0800 (PST)
MIME-Version: 1.0
References: <HE1PR0701MB305098F652DBC34E3C40810B89F49@HE1PR0701MB3050.eurprd07.prod.outlook.com> <CAA93jw4Y7x4mE+Fkz5EyckMXhUozurCzEz=BRRJ0gnr2NYvpfA@mail.gmail.com> <CANYRo8ijKTLD7z-eaK3u805+G+CRRGZS25dUYf6x-D7PQd-xvA@mail.gmail.com>
In-Reply-To: <CANYRo8ijKTLD7z-eaK3u805+G+CRRGZS25dUYf6x-D7PQd-xvA@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Fri, 06 Jan 2023 09:50:59 +0200
Message-ID: <CADnDZ8_zCm5aiBvu8W4erGwv2hSSCp3=T0Bhtq4bLm9wxaBSDw@mail.gmail.com>
Subject: Re: [hrpc] Ten years after Snowden (2013 - 2023), is IETF keeping its promises?
To: Adrian Gropper <agropper@healthurl.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "hrpc@irtf.org" <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="00000000000039d1e505f193abdf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P4jYyz0WKBt4-raXyD8TWelWkB8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jan 2023 07:50:21 -0000

Hi Adrian,


On Wed, Jan 4, 2023 at 1:10 AM Adrian Gropper <agropper@healthurl.com>
wrote:

> It's thrilling to see a thread about protocols in the HRPC context.
>
> Structural changes are needed to IETF protocols to promote human rights
> considerations. Some of these, like this thread, look like privacy. Others,
> like the GNAP discussions (
> https://mailarchive.ietf.org/arch/msg/hrpc/FW78YvFerkFHsrYDFcSWp-SYNqI/),
> are about human rights impact of forced association.
>
> HRPC needs exactly this kind of discussion instead of distracting changes
> to the charter in the direction of policy.
>

I agree with you, the HRPC should not be directed into policy. It was a
proposal/opinion and still has no consensus.

>
> I hope HRPC and related groups review our 5-year history as evidence
> before we suggest changes to the charter.
>

I agree, there are many problems in the tech_protocol side before
human_policy so we need to research the protocol before policy. The
questions in first message of this thread may open many important ideas,
points and tasks for the HRPC RG. All IETF WGs should take human rights
considerations and look into HRPC outcomes.

Best regards
AB

>
>
>

v2.23.0 | Report a Bug | By Email