IETF Logo Mail Archive

Re: GitHub blockage in Spain

MARCELO GABRIEL BAGNULO BRAUN <marcelo@it.uc3m.es> Fri, 01 November 2019 17:36 UTC

Return-Path: <marcelo@it.uc3m.es>
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 99010120806 for <ietf@ietfa.amsl.com>; Fri, 1 Nov 2019 10:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=it.uc3m.es
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 g2gyjodeotsr for <ietf@ietfa.amsl.com>; Fri, 1 Nov 2019 10:36:27 -0700 (PDT)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (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 8AA32120812 for <ietf@ietf.org>; Fri, 1 Nov 2019 10:36:27 -0700 (PDT)
Received: by mail-vs1-xe35.google.com with SMTP id b184so3313426vsc.5 for <ietf@ietf.org>; Fri, 01 Nov 2019 10:36:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=it.uc3m.es; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=PHrf+asyEZZ1UG3isdNOZ/a+lPjTEfU2i5tJMwb4M5o=; b=YPuj5bgMFwkXxanZeofqwyPmheJIv6s1lKRLrhMmhdw8gtdLpog2JHMcuwi7ULHiY4 aY51XZv4XAjc99vMEWNLdrB0e9eUsg12skL9LPRDu9Cd+caYo0we03tf6Ja1Hii0FqdU 955b+xhTvy6u1ElXnMZt8qKHyMPJ/Q2wPbawwCgW9J6YEdiuBI+CDRMQA6sF/eh6PBWk 18emDDnMpi925kOwS3tTqc0bn11q0GMfYdFncgUR4rUD6wDHr4vwdie/Zimk/uQCj7wr Ndy/w2TWtZ334z9VXJvGdEvBX2GOBnv53fA5/RZKWRKngmaMsvHjytpPXp3HEXgkgbJ5 vjzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=PHrf+asyEZZ1UG3isdNOZ/a+lPjTEfU2i5tJMwb4M5o=; b=YWRzuPiM+/x9tWQrVTV6AmNwCGYfUC7WEtj5YLyb68zBWs8sX52ftlJ/xjrdKWz11A QAZgXAme/xli3CnpMxKvtau/6o1ZIZ8blgPu4YANGd8zy8xA6irvsf+bdJUXJen2leco WgiYE+VgXuiHTvTrFszEXKkoB07io6tiQS5n3WheIDhsWUnQibm+SobCryQwhIm/mkwC PJrQJgM9I2lxTuckzrKT24hZh8Rl7UFwgeDS56r5YHBZy7pQi2SD7nb2FmoeuGu5jN2r XJdAsBf1TeM0xUW3KPXfQQZFA6PtUmjrCuh/7+lDMv4yITsm8UoE3CgkxEq9La33k29P Dmog==
X-Gm-Message-State: APjAAAXWT677m96rOwBVMP8saJ0GZMlfh6SkyQDxj6O2F62EV1blNDWV XYKYq4+9ZmtPSHLQtOxYOK6sXNNf0rpFhGI9ondo2LwdIrXwcw==
X-Google-Smtp-Source: APXvYqw+oKKj3Ip8w2jIZpeyhiX1Hph3YT/jkSvezNdmdIePygMQkNENbOm6jkO+TLllJoUf4yzJpELkK/VjIm4WP4A=
X-Received: by 2002:a67:f455:: with SMTP id r21mr6271893vsn.87.1572629786286; Fri, 01 Nov 2019 10:36:26 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <b7aba860-0177-7560-b008-90d43f1fa2d4@bluepopcorn.net>
From: MARCELO GABRIEL BAGNULO BRAUN <marcelo@it.uc3m.es>
Date: Fri, 01 Nov 2019 18:36:15 +0100
Message-ID: <CACn7K3zHQ38LaWNwVQekLd5jVoqAxzJ_AakhMs8c5f5Z7zx8ow@mail.gmail.com>
Subject: Re: GitHub blockage in Spain
To: Jim Fenton <fenton@bluepopcorn.net>
Cc: Robert Raszuk <robert@raszuk.net>, Jared Mauch <jared@puck.nether.net>, IETF <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_ZP62uhkEOkZz8XzfNl9Faw2tBk>
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 17:36:29 -0000

mmm, I am currently in spain and I have been able to access
https://github.com/google/proto-quic without any problem. Is there any
specific URL or repo that you think it is relevant for the IETF and
blocked? I can check it for you if you want.

El vie., 1 nov. 2019 a las 18:21, Jim Fenton
(<fenton@bluepopcorn.net>) escribió:
>
> While I think that blocking something like GitHub is a bad thing to do, I'm not suggesting we step into another's country's politics.
>
> My question is mostly about the practicalities of how attendees will be able to use GitHub if the block is still in place then. We are doing an increasing amount of IETF work in GitHub, and attendees need access to it to do other work as well. If we can negotiate an arrangement that will exempt the IETF network from the block, that would (IMO) be a minimally acceptable solution. Of course, attendees staying offsite would still need to use a VPN or something to access GitHub from their hotel, AirBNB, etc. and that's still a bad situation.
>
> On 11/1/19 10:09 AM, Robert Raszuk wrote:
>
> Jared,
>
> I think Jim's last worry was about IETF network :) The way I read and understand it that having IETF in Madrid indirectly support such Spain gov actions.
>
> I suggest we move it to Barcelona.
>
> Thx,
> R.
>
> On Fri, Nov 1, 2019 at 6:04 PM Jared Mauch <jared@puck.nether.net> wrote:
>>
>>
>>
>> > On Nov 1, 2019, at 1:01 PM, Jim Fenton <fenton@bluepopcorn.net> wrote:
>> >
>> > I'm hearing that Spain is blocking GitHub:
>> >
>> > https://reclaimthenet.org/github-spain-blocked-catalan-protests/
>> >
>> > If that were to continue, how would we handle that for IETF 108 (next
>> > July in Madrid)?
>>
>> Relevance?
>>
>> Often these blocks are either done in local DNS or at the local ISP level.  When IETF rolls in, the network is often not part of this.  You’ve seen this work well in countries where the local blocking might have been an issue, the most prominent of them being IETF in China.
>>
>> I get that some people don’t like GitHub and if you want to ask IETF to run a gitlab instance or similar it would likely mitigate the issue as well.
>>
>> - jared



-- 
MARCELO GABRIEL BAGNULO BRAUN
Universidad Carlos III de Madrid

v2.23.0 | Report a Bug | By Email