Re: Last Call: <draft-nottingham-safe-hint-05.txt> (The "safe" HTTP Preference) to Proposed Standard

S Moonesamy <sm+ietf@elandsys.com> Sat, 25 October 2014 01:14 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 610031A6FBA for <ietf@ietfa.amsl.com>; Fri, 24 Oct 2014 18:14:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level:
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=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 kPlGUaObYlSW for <ietf@ietfa.amsl.com>; Fri, 24 Oct 2014 18:14:58 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 159781A6F7F for <ietf@ietf.org>; Fri, 24 Oct 2014 18:14:58 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.154.196]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s9P1EcSO026186 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Oct 2014 18:14:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1414199690; x=1414286090; bh=C0fIiInDoHAHTI5Vi9MB00yJMcv3tLMxE9lUG1GJZqE=; h=Date:To:From:Subject:In-Reply-To:References; b=EW1sZpZieeYIQg11g9tpTRW5uIwSURSzJF4ncR235OwJXaaXhS8KHPi+PM3YqAHjP JN1z3OpgJF3BvbdaDGkd02tTwpJEU6EKGRXJjN6jEzhQP/GpLd9zxIPfOojS3Gzbhf eg8pk2l52BuX67nps8396Mq2AHCWXKvRRz272E/I=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1414199690; x=1414286090; i=@elandsys.com; bh=C0fIiInDoHAHTI5Vi9MB00yJMcv3tLMxE9lUG1GJZqE=; h=Date:To:From:Subject:In-Reply-To:References; b=NZq2UjL+hHMbC/p6Q6D49OYIejgyMaRwBjSgLV9ggQnLd9BjVt2MC2QBID6LC6Wsd 0gCy18Q+fBpHiozz01gLqHNGQnt6rpADBcY+PmXA3TaFvSO9yvzfuH/5h+5clsRZ1V O3ZjzCXx8WIuAfHvC88PZct/U9e5MT5jaJpx9/s4=
Message-Id: <6.2.5.6.2.20141024152342.0c0b8978@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 24 Oct 2014 18:12:52 -0700
To: Yoav Nir <ynir.ietf@gmail.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-nottingham-safe-hint-05.txt> (The "safe" HTTP Preference) to Proposed Standard
In-Reply-To: <87A3AD2B-5747-46EB-A165-50D35A29DBA7@gmail.com>
References: <20141023140635.10188.qmail@ary.lan> <87A3AD2B-5747-46EB-A165-50D35A29DBA7@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SCp_g2WMH6O-q5c3TE7pST2Ff90
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 25 Oct 2014 01:15:00 -0000

Hi Yoav,
At 12:49 24-10-2014, Yoav Nir wrote:
>Stephen Farrell has made some interesting points 
>about what "safe" might mean in other cultures. 
>I think the failure is much closer to home, so 
>let's assume for the sake of argument that 
>everyone affected is mainstream American 
>(although neither Stephen nor I are Americans). 
>So obviously anyone would consider porn to be 
>"unsafe", because we don't want the children to 
>see it and we don't want it at work. A rabbit 
>teaching the alphabet to kids OTOH is "safe" 
>([1]). But those are the easy types of content. 
>What about political content? What about 
>political content that is non-mainstream? Even 
>inflammatory? Is it safe? For whom?  A signal is 
>useless if there is no agreed-upon semantic to 
>it. Yet the draft punts on attaching such a semantic.

I think that Stephen and you raised good 
points.  I was testing some stuff recently and I 
noticed that Google did not serve the same 
content.  There are other sites which do not 
allow me to view some content because of my 
location.  In the first case it is for regulatory 
reasons whereas in the second case it is for 
commercial reasons.  When it comes to porn it is 
viewed in a country as a matter of free speech 
(see Free Speech Coalition).  The good part about 
Mark's proposal is that it is closer to the 
user.  Obviously, it is far from perfect (re. safe hint).

What about political content which is deemed 
illegal?   Some governments might block the 
content.  Some governments use other means to 
tackle that.  Would the IETF standardize 
that?  There have been proposals about interception; they did not go far.

>Section 3 mentions YouTube. That is actually a 
>perfect example of what I mean. Sites like 
>YouTube, deviantArt, Flickr, and Wattpad, even 
>Wikipedia provide user-generated content.How are 
>they to decide what is and isn't "safe"? They have several choices:

Some of the sites mentioned above monetize 
user-generated content.  There is a commercial 
incentive for them to figure out the semantics of 
"safe".  I doubt that Wikipedia would die anytime 
soon (see http://en.wikipedia.org/wiki/Wikipedia:SOPA_initiative ).

The question I would ask is whether Mark's 
proposal puts the user at risk.  I don't see an 
increase in risk.  The proposal does not attempt 
to touch encryption stuff.  It might help to 
reduce the pressure to standardize state interception services.

Regards,
S. Moonesamy