Re: GitHub blockage in Spain

John C Klensin <john-ietf@jck.com> Fri, 01 November 2019 23:36 UTC

Return-Path: <john-ietf@jck.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 C29DD120090 for <ietf@ietfa.amsl.com>; Fri, 1 Nov 2019 16:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 PfpVKbJezCRU for <ietf@ietfa.amsl.com>; Fri, 1 Nov 2019 16:36:47 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 841D7120074 for <ietf@ietf.org>; Fri, 1 Nov 2019 16:36:47 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1iQgTG-0007LN-7V; Fri, 01 Nov 2019 19:36:46 -0400
Date: Fri, 01 Nov 2019 19:36:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
Subject: Re: GitHub blockage in Spain
Message-ID: <260F2B44165234CE288A1A5D@PSB>
In-Reply-To: <53b3a510-6a1d-83ce-ebb9-995d8ae562c3@gmail.com>
References: <e587b025-dad9-1cc1-45b1-f82c584d7f21@bluepopcorn.net> <2E1AD01E-3621-446B-BA53-D1BAAB3E9EDD@puck.nether.net> <CAOj+MMGARt6jHNBZuJSLBuS8k_51QwhtFFSxuOO+bNeg6BSdSw@mail.gmail.com> <b7aba860-0177-7560-b008-90d43f1fa2d4@bluepopcorn.net> <BE0C8D10-8AFF-4E46-86A3-663BD3915B07@telefonica.com> <71788D2A-E586-41A1-82C1-89838C2FE9BB@tzi.org> <005BC04B-E91C-4BA4-866C-83C5D043E99E@consulintel.es> <53b3a510-6a1d-83ce-ebb9-995d8ae562c3@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GxfALncgj4MbnQDC9bu671bk_kg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <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, 01 Nov 2019 23:36:50 -0000


--On Saturday, November 2, 2019 08:02 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> IMHO we should not discuss here any aspect except the narrow
> technical one whether a successful IETF meeting in Madrid in
> July 2020 is possible. In fact it seems to be the
> responsibility of IASA, and the meeting planners in
> particular, to check this and let us know if there are any
> risks.
> 
> I certainly don't want to enter into political debates here,
> on matters where most of us are ill-informed and not
> personally affected.

Brian,

While I almost entirely agree, I note that we've had discussions
on this list about IETF participants being harassed or arrested
because of personal behavior or various "preferences" (aspects
of their lives that may not be discretionary choices, and hence
not preferences in the usual sense at all).  If there were
significant risk of IETF participants being harassed or arrested
because of their views on the relationship between Catalonia and
the rest of Spain (I note Jordi's description used the terms
"criminal activities" and "trying to break Spain and circumvent
our laws" ... and, before this turns into precisely the debate
you want to avoid, also note that I said "rest of Spain").

I also agree with Diego, and presumably you, that this list is
not a good place for discussions of "politics, fake news, and
deliberate exaggerations" and not just because most of us are
ill-informed.

I wouldn't expect us to avoid holding a meeting in California
because some of our participants might believe the state should
be divided in two or to avoid a meeting in Montreal because
there are people there and further to the north and east who
believe Quebec should withdraw from Canada.  And, of course, the
US and Scotland were, historically, both involved in rather
nasty wars over who has the right to secede from a country and
under what terms (including whether such beliefs or actions
taken to support them were appropriately classified as criminal
acts).  One might draw some analogies to the former Soviet Union
as well.  There are obviously differences among those examples
and between them and the Spanish case.  Your last paragraph
clearly would apply to debates about those situations or the
distinctions on this list.

At the same time, it is not clear to me whether the meeting
planners consider it part of their mandate to evaluate the
relevant tensions and any possible resulting interference with
the ability to hold a successful meeting and for any active IETF
participant to attend without having significant concerns about
what they would define as mistreatment (remember that we have
set interesting precedents about meeting in the US that might or
might not be relevant).  It would be useful to get a statement
from them --sooner rather than later-- about where they think
their responsibilities begin and end.   If they end before they
would get to evaluations of local tensions (including whatever
might be classified as criminal by relevant authorities) and
whether they might pose a threat to however we (and affected
participants) might define as a successful meeting, then I think
that boundary, and who or what does have responsibility for
those discussions, are probably an appropriate topic for this
list.  So is who is accountable to the community for whatever
decisions are made and how they are accountable.

Obviously not an easy line, or set of lines, to draw.  But
dismissing the need to do so by making inflammatory statements
(such as a few in this thread.. but nothing in your note) is
probably not a helpful way forward.

best,
   john