Re: Concerns about Singapore

<chopps@chopps.org> Mon, 11 April 2016 01:16 UTC

Return-Path: <chopps@chopps.org>
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 8C1D012DC94 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 18:16:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level:
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 5T11dzHE0keN for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 18:16:57 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 81C3F12DC64 for <ietf@ietf.org>; Sun, 10 Apr 2016 18:16:57 -0700 (PDT)
Received: from tops.chopps.org (24-247-68-31.dhcp.trcy.mi.charter.com [24.247.68.31]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 7811061176; Mon, 11 Apr 2016 01:16:56 +0000 (UTC)
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com>
User-agent: mu4e 0.9.16; emacs 24.5.1
From: <chopps@chopps.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Concerns about Singapore
In-reply-to: <570AB3AF.2050401@gmail.com>
Date: Sun, 10 Apr 2016 21:16:55 -0400
Message-ID: <87twj99c6w.fsf@tops.chopps.org>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/wN1HXfVWmPNk32XbEU34hjdZB8I>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 11 Apr 2016 01:16:58 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> writes:

> On 11/04/2016 02:48, Michael StJohns wrote:
>> On 4/10/2016 10:45 AM, Randy Bush wrote:
>>>>> it was clean unfettered Internet.  some local folk stuck their necks out
>>>>> very far to accomplish this.  it was definitely different than one got
>>>>> outside of the ietf meeting network.  this has been a condition placed
>>>>> on hosts and beijing was no exception.
>>>> This surprises me - "this has been a condition placed on hosts...".
>
> In the case of Beijing it was very clear from the earliest discussions,
> going back to 2005 and before, to my personal knowledge.
>
> ...
>>
>> I repeat - "where" have the local hosts/laws specified conditions that resulted in the IETF network content access being
>> markedly different than that accessible to the random local citizen?
>
> Why is that relevant? The criterion is: can the IETF do its work properly?
> Of which a sub-criterion is: will there be clean unfettered Internet at
> the meeting site?

It's certainly relevant to me, b/c I don't personally think that IETF
meetings should be held in oppressive and censoring countries. I don't
know how to articulate this well -- others are better at it -- but I
certainly would like to skip any meetings that I feel violate IETFs
value of openness so that I can at least vote with my feet and my
dollars.

Thanks,
Chris.

>
> How RFC 4084 applies in the local coffee shops is another matter.
>
>    Brian