[hrpc] Moving forward on draft-irtf-political

Eliot Lear <lear@cisco.com> Tue, 24 September 2019 10:49 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 3064C12018B for <hrpc@ietfa.amsl.com>; Tue, 24 Sep 2019 03:49:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 LkYABiakdgL1 for <hrpc@ietfa.amsl.com>; Tue, 24 Sep 2019 03:49:21 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B89F12010E for <hrpc@irtf.org>; Tue, 24 Sep 2019 03:49:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8662; q=dns/txt; s=iport; t=1569322160; x=1570531760; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=RiUEsHp0eUss1pS9fh6WWZ0uDGsSikhZZQkUlD3I4Bs=; b=KMwLWeUo2ft3FMZTeb0+e+RZkYAcAhAYiRPbn52F3LqkzpkQtIWzRhLk A6Wbhs6/3tHVnZzxIiq6KMr0iFqPeURR9cYZdEvnRgOgNuBynMIz1RfRf yHH8O6i17zDQq5xJ7oYrHpisLi5VXoU09NN/CrVAYzjSPBX5bbYbf/kTB c=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ALAAAr9Ild/xbLJq1kGgEBAQEBAgEBAQEMAgEBAQGBVQMBAQEBCwGBboFvMiqEIoh8h3oliWeJMIYLgXsCBwEBAQkDAQEvAQGEPwKDQzYHDgIDCQEBBAEBAQIBBQRthTmFSgEBAgIBI08HBQsjKgICITYGE4MiAYFqAw4PrE9zgTKFTIJIDYIbEIE0AYFQilCBf4E4DBOBToNWggMLgycygiYElgKIIY4oQYIsA4IrgROIFYUzhAEbgjaHS4N+hnqELJg1i2mDEQIEBgUCFYFZBisqgS4zGggbFWUBgkE+EhAUkBU+AzCKX4JUAQE
X-IronPort-AV: E=Sophos;i="5.64,543,1559520000"; d="asc'?scan'208,217";a="17217148"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 24 Sep 2019 10:49:16 +0000
Received: from [10.61.212.69] ([10.61.212.69]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x8OAnFv9024596 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 24 Sep 2019 10:49:16 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <01F67955-FA6C-4191-9D5D-A9E1AB61703C@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_54BB54F9-0E23-4090-B1D6-15E619F4AB7D"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 24 Sep 2019 12:49:15 +0200
In-Reply-To: <CAD499eJdLWK0dU-GGRy=_F=xACDP_EdOac2488_b6H4QBF_Raw@mail.gmail.com>
Cc: Hrpc <hrpc@irtf.org>, Niels ten Oever <mail@nielstenoever.net>
To: Corinne Cath <corinnecath@gmail.com>
References: <156882005427.4606.6393818361687491816@ietfa.amsl.com> <a5361cda-994c-27ad-adf7-0aa06d61a8a2@nielstenoever.net> <20190920183918.d7mpxb4jyulfqqwj@anvilwalrusden.com> <CABcZeBPK8h8Bn-vhr6vq9_K9jUAE-ry5iZhLLiwjd15gpEuwHQ@mail.gmail.com> <28d4faab-cb89-34bd-d8bc-525aab96ab66@nielstenoever.net> <CABcZeBPCEiAxksRz6HnErN=eJDho+WYGg28No1YzOZEL1GjYMA@mail.gmail.com> <793367e8-7151-354e-04ca-b472760c6af7@nielstenoever.net> <CABcZeBMT8JC_EQ0zd7nhjnTvPJY0szw+7kY8y=siD32f9vdT7Q@mail.gmail.com> <CAD499eJdLWK0dU-GGRy=_F=xACDP_EdOac2488_b6H4QBF_Raw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Outbound-SMTP-Client: 10.61.212.69, [10.61.212.69]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/UtLwf5N_eYM487QYUmjEah-0ylI>
Subject: [hrpc] Moving forward on draft-irtf-political
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, 24 Sep 2019 10:49:24 -0000

Corinne,

Thanks.  Please see below.

> On 23 Sep 2019, at 20:47, Corinne Cath <corinnecath@gmail.com> wrote:
> 
> Hi,
> 
> I think Stephane Couture made an important point: it is important to locate consensus on the politics of protocols in its respective academic disciplines and literatures, and have the document reflect that nuance.

Agree.

> 
> Furthermore, having followed this discussion for a while now (about a year or four) I feel part of the continued disagreement seems to stem from the fact that people have very different understandings of the word "political" and "politics”.

Although, at least for me, characterizing that as disagreement is overstating the case,  I agree that providing clarity on the terms and the bounding of their meaning would put any thesis and argumentation on better footing.

> For some it refers to the subtle ways by which protocol design is influenced by the values/interests/power dynamics between various folks present in the IETF and to others it refers to capital R or D conversations among politicians happening outside of the IETF, and yet to others its definition lies somewhere in the middle of these two.

Again, some precision is called for.  I think you are talking about the politics of development of standards versus the political ramifications of the results.  This relationship could be explored.  For instance, I think those who participated in webrtc would have found that development process somewhat political, in terms of finding a way forward; but I would be hard pressed to find political ramifications from the results, in as much as broader society is impacted (again, my imagination may be limited).  On the other hand, I could imagine the reverse, where the IETF standardized something with little if any controversy that turned out to have profound political ramifications.

Asking Avri and you now with your co-chair hats, I think it would be helpful to pause for a moment and just reflect on the issues the have been raised with regard to this work and how to structure discussion going forward.

For instance: is there agreement on the research question in the document?  If not, what is the point of considering anything else?  Has that question already been addressed elsewhere?  If not, great.  If so, what is the contribution this work is intended to provide?

As you ponder this, it may be that there are multiple points of view to be heard.  As an RG we have the possibility to publish differing perspectives, and this has happened in the past, most notably in the Routing RG when it was active.

Regards,

Eliot