Re: privacy and IETF meetings in US

Nico Williams <nico@cryptonector.com> Fri, 07 June 2019 19:40 UTC

Return-Path: <nico@cryptonector.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 5C519120129 for <ietf@ietfa.amsl.com>; Fri, 7 Jun 2019 12:40:55 -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 (1024-bit key) header.d=cryptonector.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 DQTE_RDg3Ter for <ietf@ietfa.amsl.com>; Fri, 7 Jun 2019 12:40:53 -0700 (PDT)
Received: from eastern.birch.relay.mailchannels.net (eastern.birch.relay.mailchannels.net [23.83.209.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FD6E12004B for <ietf@ietf.org>; Fri, 7 Jun 2019 12:40:52 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 44224227DB; Fri, 7 Jun 2019 19:40:52 +0000 (UTC)
Received: from pdx1-sub0-mail-a26.g.dreamhost.com (100-96-4-95.trex.outbound.svc.cluster.local [100.96.4.95]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 6A24422656; Fri, 7 Jun 2019 19:40:50 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a26.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.17.2); Fri, 07 Jun 2019 19:40:52 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Obese-Continue: 4c7af7681fef8825_1559936452093_681777937
X-MC-Loop-Signature: 1559936452093:3957888883
X-MC-Ingress-Time: 1559936452092
Received: from pdx1-sub0-mail-a26.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a26.g.dreamhost.com (Postfix) with ESMTP id 288C1825E4; Fri, 7 Jun 2019 12:40:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=IG3RCfACzTgnWm HFtEM3uu14J8c=; b=AXLF66PRq5K8BmzRJfqPKeUf1z9dEsKZsKsxUyD+/1fHPr rQ9mU2UnZtLOoe/J/BHrf5NLH9RybM+frWyCNNF4cLK8havgLW1/Mf0qeiUt6m9l GaYkhuNd+eRQMAK05qfTpcDYTZPBbATxYIzVubbruI4gd7TViZWwAswVfxN+Q=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a26.g.dreamhost.com (Postfix) with ESMTPSA id CEBC2825E8; Fri, 7 Jun 2019 12:40:42 -0700 (PDT)
Date: Fri, 07 Jun 2019 14:40:21 -0500
X-DH-BACKEND: pdx1-sub0-mail-a26
From: Nico Williams <nico@cryptonector.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Paul Wouters <paul@nohats.ca>, ietf@ietf.org
Subject: Re: privacy and IETF meetings in US
Message-ID: <20190607194020.GB2124@localhost>
References: <5B42C40D-50EF-4D56-8661-BFA8FF107426@consulintel.es> <33839E7AE337BD20319D6BF0@PSB> <8989A94D-FDA7-40E3-BE4B-023DA221BD7C@consulintel.es> <5f314b9b-d922-8d47-a913-a7e58aef98ec@gmail.com> <alpine.LRH.2.21.1906071237490.13812@bofh.nohats.ca> <20190607184342.GA2124@localhost> <27405.1559935129@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <27405.1559935129@localhost>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduuddrudegiedgudegudcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucggtfgfnhhsuhgsshgtrhhisggvpdfftffgtefojffquffvnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvuffkfhggtggujggfsehttdertddtredvnecuhfhrohhmpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqnecukfhppedvgedrvdekrddutdekrddukeefnecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopehlohgtrghlhhhoshhtpdhinhgvthepvdegrddvkedruddtkedrudekfedprhgvthhurhhnqdhprghthheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqedpmhgrihhlfhhrohhmpehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmpdhnrhgtphhtthhopehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rqZTTLr9wZ8yYehCqkuHNbRlVR8>
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, 07 Jun 2019 19:40:55 -0000

On Fri, Jun 07, 2019 at 03:18:49PM -0400, Michael Richardson wrote:
> Nico Williams <nico@cryptonector.com> wrote:
> > Then again, I think this new policy is a bit useless.  Finding a visa
> > applicant's social media is relatively simple given their names and
> > pictures (which the consulate already demands and long has, and besides,
> > they have cameras).  And it's not like consular officials can easily
> > find pseudonymous social media if it lacks easily identifiable contents
> > like pictures that can be matched by facial recognition.  Yes, it would
> 
> So, how does one prove one does not have a social media account?

You don't.  You assert you don't have one and good luck.  If they
reject, go create one and seed it with harmless content.

> And, as there are at least 7 people on facebook with the same name as me,
> which one is it?  That's why they want the specific identification.

Yes, but it's usually easy enough to check if any of the 7 are yours.

> How do I prove which one is me?

By showing that you post pictures of yourself?  Get vain.

>     > be a violation to fail to tell them about things they can't find, so the
>     > rule is still invasive, but from a practical point of view, those that
>     > State might exclude aren't going to be disclosing pseudonyms that State
>     > can't doxx on its own.  I.e., this is just more mostly-ineffective
>     > security theater.
> 
> You are right: theatre, but it has a useful chilling effect on speech.

That's not really intended by anyone with half a brain (meaning it might
still be intended!).  You want those who are security risks to speak.

I'm not sure what speech they would object to.  I suspect State is
probably staffed more by Democrats than by Republicans, and they're
bound to have different views as to what's objectionable -- it's almost
certainly a crapshoot.  The UK has used political speech of the sort
that has nothing to do with terrorism to exclude visitors.  So has
Australia.  The speech chilling train has long-ago left the station --
it's affecting more people, but the trend as to speech curbs is global,
and the U.S. is behind that curve.

Really, considering the 38 countries on the visa waiver program, how
many active IETF participants will be affected?  That should inform any
decision to move/cancel the SF meeting.  Future meetings might not be
hosted in the U.S. at all, but again, when other countries start doing
this too (if they haven't already, just without any fancy PRs), then
what?

Nico
--