Re: Concerns about Singapore and other places

Phillip Hallam-Baker <phill@hallambaker.com> Tue, 12 April 2016 17:17 UTC

Return-Path: <hallam@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 F2BDF12EA94 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:17:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level:
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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 i5gL_WcSX-eD for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:17:31 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 4FB8C12EA6F for <ietf@ietf.org>; Tue, 12 Apr 2016 10:17:30 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id g184so34818344lfb.3 for <ietf@ietf.org>; Tue, 12 Apr 2016 10:17:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=WXd1CwSv7EU8ROdvsqqVgvKCX1t9GycPhxeZ2+ESQ+0=; b=je9X03Ic+38SHVrN/VJg6heZFq3pp3W2BPD+cKZqiCt0w3gBIQXPd7qiyoi66QOMdm OQlOssLyG7jlRwHlxeAWNSVAy1xQU9GxlmDtfUcpyw+zeFNcNZ8xSNpYczDbpA9nQNF5 +/ER0FQRt1yTIeDlCR5Ojjup9IY5529m5zA79P+uluCO1VeaKg9AL6904t+g4lh+a/7k mzwwbaZt//QaRLKIeAZmNbxiH/GLIkb+4VOSpFzP82r4igMuU9BYpdj0S97Jt+DzQDXq udafUKycUju5sYrup26GtNxbOqLAEvrnwtYNv6baWhGN7pZDVKKu8sQfpZsvGs4fUTkT Q5mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=WXd1CwSv7EU8ROdvsqqVgvKCX1t9GycPhxeZ2+ESQ+0=; b=BKELimZl4L8D5IWbnqT2Emyf0wCuXvi9XgvZdgBWzcWPJEStrNj5w0C89fuJsWnm0+ ImwTZSh/NgdXknGWAD9GST8G8krnzkervRobK3pqbQ51mzhMqMYqxrCndAZZJe6Jk+Bk y4uGZ4ivc74SV8Q7h8SUY8agDVZ4tSN8H3R2EzxfwoR8oH5xfuxo7ejjigkBc+ZzK2eV edPV4eaKLbYHiW2NHFLwArILtoQ200WX+nGZtwLnpvjKRtvcacSvwRXiERexPg7IxqKc fPeMzxPWVSr7/Be6ADM777PR/78UKfrtu57K8D1IB/OyVeuhkgXpp2MTp+2inuDUyjRe dnqg==
X-Gm-Message-State: AOPr4FUWYeeho1xyjEjXlh4KqV55dVEO6mTtSd4Mm93uvitwxHkLLMcl+8o7UJd1SMWbW/2zUr+NqpTPvYRNWA==
MIME-Version: 1.0
X-Received: by 10.25.208.144 with SMTP id h138mr1531518lfg.48.1460481448479; Tue, 12 Apr 2016 10:17:28 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.151.67 with HTTP; Tue, 12 Apr 2016 10:17:28 -0700 (PDT)
In-Reply-To: <CAPt1N1nLWrVqGpPh+h=Ano6PJyw2ZRaroiAMgG4RDKTFV7rkpA@mail.gmail.com>
References: <alpine.OSX.2.01.1604100736080.45987@rabdullah.local> <20160410181958.58762.qmail@ary.lan> <CAMm+LwgE_oOJSCjgsMGTSMDV2-LsUzw1zW3-+N_VCtE14m26BA@mail.gmail.com> <CAPt1N1nLWrVqGpPh+h=Ano6PJyw2ZRaroiAMgG4RDKTFV7rkpA@mail.gmail.com>
Date: Tue, 12 Apr 2016 14:17:28 -0300
X-Google-Sender-Auth: eScI4ms-VB9GSC6ejPes_kG69ic
Message-ID: <CAMm+Lwi=9ghLfQb-RKLr4ZZCjiLmhgBervZ3svytAe-DEY2=7w@mail.gmail.com>
Subject: Re: Concerns about Singapore and other places
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/-FilI7GBKp-uggONOZAJ1kihFGk>
Cc: John Levine <johnl@taugh.com>, IETF Discussion Mailing 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: Tue, 12 Apr 2016 17:17:36 -0000

That is the parental filter, if you don't opt out, you get pestered by
continuous messages asking you if you want to like it was an O/S
upgrade.

The child porn filtering is separate and I suspect is using the type
of BGP and IP intercept techniques that are commonly used to shut down
a large range of Internet crimes in pretty much every jurisdiction,
the US included.



On Tue, Apr 12, 2016 at 1:52 PM, Ted Lemon <mellon@fugue.com> wrote:
> The UK filter is an "opt out" filter, and I assume that we (the IETF) opted
> out.   Even the "opt out" blocking is voluntary at present--an ISP is not
> required by law to have a filter, but in practice the big ones do.
>
> On Tue, Apr 12, 2016 at 12:24 PM, Phillip Hallam-Baker
> <phill@hallambaker.com> wrote:
>>
>> On Sun, Apr 10, 2016 at 3:19 PM, John Levine <johnl@taugh.com> wrote:
>> >>The IETF has a meeting network requirements document that specifies a
>> >>number of parameters which includes no blocking.
>> >
>> > In London in 2014, do you know whether we were behind the national
>> > child porn filters?
>> >
>> > R's,
>> > John
>>
>> I am not sure that they actually filter.
>>
>> I think it rather more likely that if you were to surf to
>> kiddieporn.com from the Hilton Metropole, that you would find Mr Plod
>> knocking on your hotel room door 15 minutes later. That being the
>> driving time from New Scotland Yard.
>>
>