Re: [hrpc] I-D Action: draft-irtf-hrpc-political-04.txt

Ted Lemon <mellon@fugue.com> Tue, 17 September 2019 16:52 UTC

Return-Path: <mellon@fugue.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 D15F3120108 for <hrpc@ietfa.amsl.com>; Tue, 17 Sep 2019 09:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.898
X-Spam-Level:
X-Spam-Status: No, score=-0.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, GB_AFFORDABLE=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 Mk2Ln7tdwWmm for <hrpc@ietfa.amsl.com>; Tue, 17 Sep 2019 09:52:06 -0700 (PDT)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (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 A3943120112 for <hrpc@irtf.org>; Tue, 17 Sep 2019 09:52:06 -0700 (PDT)
Received: by mail-qt1-x833.google.com with SMTP id u40so5216129qth.11 for <hrpc@irtf.org>; Tue, 17 Sep 2019 09:52:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=NJPqln1Fv7MyYMfZ0FWlZ+SDnRat6ER6Ft+2OceHDQY=; b=NN20LGFXnWPPprMMTSCGwEDS+7DVfBZE43qvzGzMSxoH3F56S3JSyefPx+WoTCsE7x OL3m3bWDghCIG/SReC0kotyeKqGs15PrKwYavx2QJBjAqRLzIUh8eUBtOfPLnGz2UrGe cDJ4EHegL1ai0DkQ33ZEBuitYs588wavr53aRRMEiRXWTv93L+OB3pPRM1BA4/BWX7hm XMqf2CmB8DPbMUlwiaRW5gJAvaYP0fVmwQK7bAUFP2VojjivmlYAt6U/0+v8Y6Zcr+8Q t1yLbRV1Lzzbj+6Phg+0atpiMQNgYhCQ1XZ4JRuJqVSqvJqYcHOrZRJ4USbtgesYsFbU P7uA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=NJPqln1Fv7MyYMfZ0FWlZ+SDnRat6ER6Ft+2OceHDQY=; b=cKvJTZiqfaPqbdHA2m5dZgsEwE/I1G35jn55zLtTrkZ44eoo524iTkVRgLwgNQ3f8r ftcwaCuHaYgIQVOcKRJ6pbpeFPAGX1mj5E8BCcwhH/ilR9fQLLmEsnIW2DjZmwcWlzqW zy2Gf+m1B8BLMzdlt/PgKyl+q6ldTfCqF+4gl963M36A0B1llsuuGbnYXCLBOZEZoH8J 07FfYDuB1bZZcYfINEcFocHiAAdp5IY0xUkxyzhl/AtlP0/dvpeqFCTO862vtrDSsoYE sApLt7cjYfRQw+AmSbkK6BhZ+Hvz2pxYDWLSucfHWxgFU2C8g2KzYXCfCLxtnIG6tNVC oTbg==
X-Gm-Message-State: APjAAAU9qKAAUWTadXb9/y410bJs8EmyT8+GJkIa64ODr1SxKvFo1mhC vU1I+CvuqqtUi4UWCUVeYQLzUw==
X-Google-Smtp-Source: APXvYqxXG6UIOmllkL/aYp83GAEKHfqf+mt9oNERZ7/SaL/dY/k5kEoKHPNZPtM7lk5XpsOvLmXTtQ==
X-Received: by 2002:ac8:5216:: with SMTP id r22mr4695301qtn.281.1568739125585; Tue, 17 Sep 2019 09:52:05 -0700 (PDT)
Received: from [10.0.10.46] (c-73-186-137-119.hsd1.ma.comcast.net. [73.186.137.119]) by smtp.gmail.com with ESMTPSA id b26sm1450932qkl.43.2019.09.17.09.52.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Sep 2019 09:52:05 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <9EA8EA59-2A05-4D91-AECE-1D42F004530B@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7585A159-34D0-495A-B985-AA3F2AA9A9A1"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3578.1\))
Date: Tue, 17 Sep 2019 12:52:03 -0400
In-Reply-To: <alpine.LRH.2.21.1909171059280.22011@bofh.nohats.ca>
Cc: Niels ten Oever <mail@nielstenoever.net>, hrpc@irtf.org
To: Paul Wouters <paul@nohats.ca>
References: <156862506643.28251.9847319195246702362@ietfa.amsl.com> <2927d15d-30a2-189b-7a68-dfb11f5f5be0@nielstenoever.net> <980ffdbd-79fa-96ca-541c-09107b550531@doria.org> <5FEE04EF-307F-4A11-9ED4-E9B7394527AC@cisco.com> <35d4da40-fd0b-2ee9-3cc1-0c250ae1e93a@doria.org> <2CAFB54D-8435-45D5-8996-DEE6175B48A3@fugue.com> <d98e744e-11ee-09b9-0d38-4f5150692ff0@nielstenoever.net> <B4E48D50-5A76-4056-BBE4-39FBDB4EA155@fugue.com> <21470bee-2db1-0571-dea1-00832e01fa8f@nielstenoever.net> <CE7F61F5-B11C-4DE7-853B-3CA1AA0F3167@fugue.com> <alpine.LRH.2.21.1909171059280.22011@bofh.nohats.ca>
X-Mailer: Apple Mail (2.3578.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/W7aN6P1bdxEBOLpUjBz8xUL-ERc>
Subject: Re: [hrpc] I-D Action: draft-irtf-hrpc-political-04.txt
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "mail@nielstenoever.net" <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: Tue, 17 Sep 2019 16:52:09 -0000

On Sep 17, 2019, at 11:45 AM, Paul Wouters <paul@nohats.ca> wrote:
>> What is the good outcome here?
> 
> "This document aims to bring about a better understanding on the political nature of standards and protocols.”


To whom?

>> Is it being heard, or is it being influential?
> 
> It is a bit early to say that, as the document is still in the draft
> stage. The question to ask is more "can this document in the current
> form, positvely influence or shape future IETF developments". I think
> the answer is yes. If you have suggestions of making this document
> even better, I'd love to hear those specific suggestions.

That’s the question I was asking.  Sorry for being unclear.

> I would love to have this document as a reference for document authors
> to think about their specific IETF work impacts the global internet, and
> via the internet, society. That is, this document would be a great
> starting point for a document author to consider if their document needs
> a Human Rights Consideration section. Writing such a section has as goal
> to confirm (or perhaps improve) the protocol described causes no
> unintentional harm to society.

This was my understanding as well.  I think it’s currently not going to succeed at meeting that need.

> Yet, some remote communities
> that relied on proxy/caching servers to be able to have affordable
> internet are now seeing a prohibitively expensive internet bill since
> nothing can be cached anymore. Worse, some hacked up solutions now to
> run the browser remotely in the cloud and only show a graphical output,
> which can be strongly compressed and sometimes even largely cached,
> to the client. This is resulting in a significantly reduced security
> for those users, the equivalent of giving companies or nation states
> administrative access to your personal laptop or mobile phone which
> full surveilance powers. The opposite of what TLS was supposed to
> accomplish.

These are great examples.  I wonder if this document as it is at present could have helped to avoid this problem.  I think the answer is no.  It would be fantastic if this document could be written in such a way that it could help to avoid problems of this type.

The bottom line is that I agree completely with all the aspirations that you have stated.  I just don’t see how this document helps to bring us closer to achieving them.

The canonical answer to that is “send text.”  However, when I have commented in the past, my comments have seemed not to be heard.  If I were to send text, it would almost be a complete rewrite.  I’m certainly not willing to undertake that sort of effort without some notion that it would be useful.