Re: Concerns about Singapore

Robert Withers <robert.w.withers@gmail.com> Sun, 10 April 2016 23:15 UTC

Return-Path: <robert.w.withers@gmail.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 D50E712D195 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 16:15:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 A-IMb98-x5QY for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 16:15:17 -0700 (PDT)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (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 47B3E12D185 for <ietf@ietf.org>; Sun, 10 Apr 2016 16:15:17 -0700 (PDT)
Received: by mail-qg0-x22c.google.com with SMTP id c6so131518641qga.1 for <ietf@ietf.org>; Sun, 10 Apr 2016 16:15:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=8046h3ihm6q1i+q1hHrKk7e0AIPRmu57kb75zFru/qU=; b=J4of56Cz010pCxQOIe5VZodsObfedUyPYKqYzTLcU22jvIEqC1NLIhM1cp6AYKdF7F lV6rGTfITKo1IH0VCPh7fxzJxwUA1Ef970LlB7yFH+ltzyLfmS/iGLhL36WeMi8P8EOk vXVS962bTBRVyksEi/YQ2zgROBJ22dMdr3UkuI7I+EmL3YPTXagtdRseg6AGKi/JLE/a HynMtV/MMISOJ52HCGI7OyCEcEAt/JSsZUNzKKqyU3XtbfDSB0AvtQ8ekowCXzHOmsW8 ihvEIurl8BjE/N/kAfyZCM1NjF1Xl2yJQAxDgZVLVqcI39RcMxx+iSOebfrG1fzSOEfQ 0dag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=8046h3ihm6q1i+q1hHrKk7e0AIPRmu57kb75zFru/qU=; b=cMwILgqIxVHUMau63Rv8EQxYMtADSkdvPObW4S9IaYom48fIdw0h3Rvqt705zi5mk8 5EZyO140Os0AcOnFbLvdM03vruWXAWGHmOI06dpFTY9WmyL9A9g8R1DuNwCvphHlr3Xx hlpCZ6y3Z+AJXYz38j5vW7Y6brE0MS6Yv1Cs2a/H3iBLfwMbgv26l3QYg9TckRiyN0s8 /YJSXCS2QN1nLuO55Ya5NHu5mMjw8yaSl5UjFPr4tR5dlB5OYmM+plBvnbqB0ByepjP7 qkDVDh8Ook/fjdpXDHS44MJlVRRkRbYHqr6+sDjnOqjPs9GDeZV7OnncCIrxUqrmYqIV NHtA==
X-Gm-Message-State: AD7BkJJBtvpC9x3BB+RumriTm9xy0JseVOPQ5YKl9X03eO+PDLX83HZqRfX16TaU7DqdwA==
X-Received: by 10.140.194.67 with SMTP id p64mr27162607qha.19.1460330116439; Sun, 10 Apr 2016 16:15:16 -0700 (PDT)
Received: from [192.168.2.3] (cpe-107-15-45-203.nc.res.rr.com. [107.15.45.203]) by smtp.gmail.com with ESMTPSA id j185sm2079291qke.40.2016.04.10.16.15.14 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Sun, 10 Apr 2016 16:15:14 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Re: Concerns about Singapore
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (13E238)
From: Robert Withers <robert.w.withers@gmail.com>
In-Reply-To: <8295F54A-0A2B-4D89-9433-519F14F63C65@puck.nether.net>
Date: Sun, 10 Apr 2016 19:15:13 -0400
Content-Transfer-Encoding: quoted-printable
Received: from [192.168.2.3] (cpe-107-15-45-203.nc.res.rr.com. [107.15.45.203]) by smtp.gmail.com with ESMTPSA id m188sm13200240ywe.46.2016.04.10.13.45.01 for <jared@puck.nether.net> (version=TLSv1/SSLv3 cipher=OTHER); Sun, 10 Apr 2016 13:45:01 -0700 (PDT)
Message-Id: <FFA9507A-A1A6-42D9-8047-ADE81B6044EC@gmail.com>
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> <7060475F-E348-4BF0-B515-BB47143A2C24@puck.nether.net> <570A9A5F.6020906@gmail.com> <8295F54A-0A2B-4D89-9433-519F14F63C65@puck.nether.net>
To: ietf@ietf.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/iCjfEvU8cjR658i0ciMlxqE_JnU>
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: Sun, 10 Apr 2016 23:15:19 -0000

Resending to the list...and an extra thought...

If censorship rights are managed in more granularity than nationally, perhaps the neighborhood or subdivision level, it allows variance and differentiation, including mixed access within an urban setting. The nation must be the union and membership in associations may carry censorship requirements limiting one's access by agreement. This sort of approach may be welcomed by those regimes with real concerns regarding 'westernization' of their media. Countries may well allow international conference attendees free access while simultaneously protecting their children from wanting to serve the local warlord rather than sticking to the local Civil Defense Unit. I believe the idea has merit, perhaps reducing slaughter.

From the perspective of those exercising active decision, it would be termed the right to forget, another right to be sure. It's a form of BDS, yes? Quite effective.

Well I think it would be wonderful if network protocols supported filtering in both senses: filter reception from certain senders & filter transmission to certain recipients. I'm thinking of some sort of intersection of sender/receiver permission volumes specified with N dimensional Voronoi tessellations in negotiated session state at the routers, managed with multicast hashes in the traffic headers. One will literally never be in contact with said troublesome traffic and both foreign and domestic users would have that censoring/forgetting guarantee. 

best,
robert

> On Apr 10, 2016, at 16:28, Jared Mauch <jared@puck.nether.net> wrote:
> 
> Countries do their own censorship, or have rights for their citizens eg: regional/ national right to be forgotten. 
> 
> If you need some articles on these topics, let me know. 
> 
> Jared Mauch
> 
>> On Apr 10, 2016, at 2:24 PM, Robert Withers <robert.w.withers@gmail.com> wrote:
>> 
>> Pardon me, do I understanding you to say that it is a basic right for a local region to censor content? As you put it: "local censorship laws and other rights", So to establish specific censorships in local areas, this is a fundamental right of that neighborhood?  That is a very shiny idea, very Millenarianly said.
>> 
>> Robert
>> 
>>> On 04/10/2016 01:53 PM, Jared Mauch wrote:
>>> I would suggest European networks have quite different content than elsewhere as a result of local censorship laws and other rights afforded to people in the region.
>>> 
>>> Jared Mauch
>>> 
>>>> On Apr 10, 2016, at 10:48 AM, Michael StJohns <mstjohns@comcast.net> 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...".
>>>>> it was even in the hour of embarrassing babble fred used to prevent
>>>>> people from talking about real problems at the bof
>>>>> 
>>>>>> Could you enlighten us as to which [and I'll try to be precise here]
>>>>>> other IETFs had a condition where the content accessible by the IETF
>>>>>> network was markedly different from the content of say the network at
>>>>>> a local Starbuck's equivalent wifi hot spot just down the street from
>>>>>> the IETF and where that was mandated by the hosts and/or local laws?
>>>>>> I mean besides Beijing?  Key words "markedly different" and "content
>>>>>> accessible".
>>>>> we don't specify it's 'different'.  among other silly distractions, it
>>>>> would require a 'different from precisely what and in what ways?'
>>>>> 
>>>>> we simply specifiy open and unfettered
>>>> 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?
>>>> 
>>>> 
>>>>> rndy
>> 
>> -- 
>> Robert
>> .  ..   ...    ^,^
>