Re: [hrpc] re history lessons

Eliot Lear <lear@cisco.com> Thu, 06 May 2021 09:00 UTC

Return-Path: <lear@cisco.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 F300F3A1912 for <hrpc@ietfa.amsl.com>; Thu, 6 May 2021 02:00:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level:
X-Spam-Status: No, score=-9.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 TU4nFShgkgsm for <hrpc@ietfa.amsl.com>; Thu, 6 May 2021 02:00:12 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BCC93A190D for <hrpc@irtf.org>; Thu, 6 May 2021 02:00:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7321; q=dns/txt; s=iport; t=1620291612; x=1621501212; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=fMxUNgyftYJCZNpJBLacUbsWRwI8/E2/KCXQ4crYA0E=; b=eH0jSVfVjCVXcafN5H8+EhRn1oWHOrpIh3GqqeCpIbNgcF8e2/1//2Qz 9Qon4PrhRFjDuIKAtLmpus8DaIE9h9NwmmoWHc39A32xvWrZAveRIP5PC Q68Kxm6ueCWjeoVXgsVqnPSyp77O3MWNcryMQFwUcB4UMJe18fnBK7vH6 E=;
X-Files: signature.asc : 488
X-IPAS-Result: A0BZAACXr5Ng/xbLJq1aGgEBAQEBAQEBAQEDAQEBARIBAQEBAgIBAQEBgheDIlYBJxIxhESJBIhNJQOKNIoliCYEBwEBAQoDAQEqCgQBAYRQAoIDJjgTAgQBAQEDAgMBAQEBAQUBAQECAQYEcROFUA2GRAEBAQMBI1YFCwsMDCoCAiEcGgYTgnEBglUDDiEPp2Z6gTKBAYNKAYEYgk4NghcKBoE6AYFShTIBhllDgguBFScMEIJfPoIeQgEBhHc2gisEgXhOAYEJMAGBXU4LPpNiihicQluDG4NJgUmSX4VCBSOlJqRPkD6EBwIEBgUCFoFrI4FZMxoIGxVlAYIKAQEBMT4SGQ6OKxaDTopfPwMvOAIGAQkBAQMJjQ8BAQ
IronPort-HdrOrdr: A9a23:cfFNBq+0lLYN6PPAbwJuk+DdI+orL9Y04lQ7vn2ZhyYlEfBw9v rDoB11737JYVoqMk3I3OrhBED/ex7hHO9OjrX5VI3KNGLbUSmTXeRfBODZrQEIdReOlNK1rZ 0QF5SXzLbLfD5HZQGQ2njeL+od
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.82,277,1613433600"; d="asc'?scan'208,217";a="33338908"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 06 May 2021 09:00:10 +0000
Received: from smtpclient.apple ([10.61.144.32]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 146909lF027694 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 6 May 2021 09:00:09 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <180FA715-80A9-4358-8276-BA1CE84BDAB3@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_A9C4AAF1-1C61-44E5-8974-99758F05C3D2"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.80.0.2.43\))
Date: Thu, 06 May 2021 11:00:07 +0200
In-Reply-To: <CAD499e+PHChcFNUWs6gCgCsQZ48q+UiRrnT_NMN4=4Sv--WGqw@mail.gmail.com>
Cc: Colin Perkins <csp@csperkins.org>, Mallory Knodel <mknodel@cdt.org>, Sandra Braman <braman@tamu.edu>, Ted Lemon <mellon@fugue.com>, Hrpc <hrpc@irtf.org>, Gurshabad Grover <gurshabad@cis-india.org>
To: Corinne Cath <corinnecath@gmail.com>
References: <CAB2unbOv2nUym_fjB9f1jtZUP+4dM9e1JHQ3-PutG-UN9UTcRw@mail.gmail.com> <A81BD7F6-22A1-4F27-AA1F-E6BAEFE375DE@fugue.com> <25d1aa9a-b708-d8b3-1a36-b7b5b72b9ca1@cis-india.org> <8782A25C-4970-4C0E-9178-F3BEB99DF05F@csperkins.org> <CAD499e+PHChcFNUWs6gCgCsQZ48q+UiRrnT_NMN4=4Sv--WGqw@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.80.0.2.43)
X-Outbound-SMTP-Client: 10.61.144.32, [10.61.144.32]
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/xsjQfZHfznOzgR3wEUOPqwAB9_M>
Subject: Re: [hrpc] re history lessons
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, 06 May 2021 09:00:17 -0000

Hi Corinne,

First and foremost, best wishes on your defense!


> On 6 May 2021, at 09:07, Corinne Cath <corinnecath@gmail.com> wrote:
> 
> Hiya,
> 
> I think part of the question is also whether the inclusion of a human rights section in RFCs is the only way to judge the effects of the HRPC group.

Yes.

> 
> In my PhD, I track the ways in which having these discussions in the IETF/IRTF has changed the sensibilities of engineers in terms of what type of "social" concerns they consider to be relevant to their work.
> 
> This is much harder to measure quantitatively, as it speaks to change in naturalized ways of seeing the world, but in addition to doing ethnographic work like I did, I think it might also be interesting to do further analysis of mailinglists as Colin suggests.


I would add one other aspect, and this is entirely subjective, anecdotal, and I could be entirely wrong, but… my feel is that the participant mix at the IETF has changed dramatically over the last twenty years, with less of a focus on L3 technologies, and more of a focus on transport and security.  People have argued that the neck of the hourglass is now HTTP and not IP.  With the advent of LetsEncrypt and with centralization of services, this has permitted something of a focus on HR at those layers where it simply wasn’t previously practicable.

Another possibility to consider is that there may have been a bit of a Gartner hyper effect in play, where you get that initial zing of interest a’la Edward Snowden, then a lull, and then slow but steady adoption of more mature principles.  And some of that is well above us and well into the application layer (a’la https://www.washingtonpost.com/technology/2021/05/05/apple-airtags-stalking/ <https://www.washingtonpost.com/technology/2021/05/05/apple-airtags-stalking/>).  One wonders what the IETF could ever do about such a thing.  But certainly there are things within our control, and the application of RFC 8280 over time will be worth studying.

Eliot