Re: [Recentattendees] Background on Singapore go/no go for IETF 100

Behcet Sarikaya <sarikaya2012@gmail.com> Tue, 31 January 2017 15:48 UTC

Return-Path: <sarikaya2012@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 5570D12950A for <ietf@ietfa.amsl.com>; Tue, 31 Jan 2017 07:48:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.729
X-Spam-Level:
X-Spam-Status: No, score=-0.729 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 h3jFMBFB7LTT for <ietf@ietfa.amsl.com>; Tue, 31 Jan 2017 07:48:05 -0800 (PST)
Received: from mail-wj0-x241.google.com (mail-wj0-x241.google.com [IPv6:2a00:1450:400c:c01::241]) (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 B190B1294C5 for <ietf@ietf.org>; Tue, 31 Jan 2017 07:48:04 -0800 (PST)
Received: by mail-wj0-x241.google.com with SMTP id le4so1793309wjb.0 for <ietf@ietf.org>; Tue, 31 Jan 2017 07:48:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:cc:content-transfer-encoding; bh=6+7p3ZhvXvl9Fio3fQLsdavHoZIUGzK6iMk9EgJ06Ww=; b=YOqttDJRc36l9OLcX9ZYs6EZlUMPQM/7YmHM4RoQYTgkP6nqY0hh/cgdXEiGCuyQHx nyaTyd7sFioqI6JcEEYgWd1n6gyu3Ya67A31QcSTRqg+AHAaZe2+qiyjYHda/unCr6Tu 44Yb1peixu5i7CvskgtCfCJRorJQf6YRn868Cc2aKlGkMW+B+xMrwTAGzTVDq3We3ZJh TxsM4M40XOxvIVbTOWiJLTGoIr76S5fHhkKc6EeGWpt8SUgotdUZKlhMtovVcEA8EBK2 4165jAubkQI4pNDB2/VI5lvXtE1oe6DrkVi17AZL4Ywtaw9Bc1XZZQz27nz7P6l712RX WYUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:cc:content-transfer-encoding; bh=6+7p3ZhvXvl9Fio3fQLsdavHoZIUGzK6iMk9EgJ06Ww=; b=Iob3qMog6YJZ2TFvbTBzBjCOSVlQl+5Ug+ul0/syBXpZaxcyJ/87lKPMykQ+/eKQ6r nkrD/tpL/hSy/RPfrXni+ldYdXOf9ftrYVcYsZcuOs2rJcLesnPzOGAcNQZ5gpXJiVpt cXob0wCRMIs2/JfIjRU3l6Xajd+6ZNXzGjo6u/qJV4qjEFi+U00KyPwJs3Z0+7Xo9V0p lgYe41cnJQVRzOGlCyFhoeutWn4UmmDwO6tuvzOzD6aYXh7K5mhMfA1yw45m6+fJccHT vFA23m3KpwpcSHZAatth3m/dFYhnr6RRheDNVvIMn/Vf+TU0d6BPypbau4jaUltT5XGY BYIA==
X-Gm-Message-State: AIkVDXJjgzjUY9WBK8g7UBKrsorSWk7sE1xbUFpdQNZP1pULiHyjABfCHxrRFNzN91JAZ4gbPwwz9T4H9cWlqA==
X-Received: by 10.223.138.220 with SMTP id z28mr23968961wrz.26.1485877682867; Tue, 31 Jan 2017 07:48:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.138.146 with HTTP; Tue, 31 Jan 2017 07:48:02 -0800 (PST)
In-Reply-To: <6BC98448-93D1-4584-90FB-8E2DC03A41B5@itron.com>
References: <20160525220818.18333.71186.idtracker@ietfa.amsl.com> <700D9CB7-4EFD-459B-AA12-133A6BB04E90@senki.org> <1C8639E6-1058-4D04-84ED-0C354E6567D1@cisco.com> <9CBABA69-1814-4676-9C69-E129F04AD24C@cisco.com> <5DFDEA43-8156-491D-A300-2BCED1AED1A4@gmail.com> <5747909C.20403@si6networks.com> <955df2106aa2e12cefbd450be022e779.squirrel@www.trepanning.net> <D36D49EE.35116%jefft0@remap.ucla.edu> <CE39F90A45FF0C49A1EA229FC9899B05266663BF@USCLES544.agna.amgreetings.com> <CA+ruDECdMAC2PQqibqQijc-nLHUxOGw0h-ZYyh8FnZZaeZ8sTA@mail.gmail.com> <CA+ruDEBHyzk5cg5Vmq-anKJTxLkZpHrb9APwkfbDGn6FeFzR_w@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B052BD4B85D@USCLES544.agna.amgreetings.com> <6BC98448-93D1-4584-90FB-8E2DC03A41B5@itron.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Tue, 31 Jan 2017 09:48:02 -0600
Message-ID: <CAC8QAcfZBqPUYf6goNpC9MNTgQ97U_UOZ6DOoOPfugz0ApZbpg@mail.gmail.com>
Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF 100
Cc: "Ietf@Ietf. Org" <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ra34JqBVTHh_nm8Gil_U2vIweqI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: sarikaya@ieee.org
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, 31 Jan 2017 15:48:06 -0000

On Tue, Jan 31, 2017 at 2:45 AM, Mani, Mehdi <Mehdi.Mani@itron.com>; wrote:
> Dear all,
>
> As an european holding a french passport with my origin coming from Iran i
> cannot travel to US with this executive order of Mr Trump even if i work for
> an American company.
>
> So i beleive as well that meeting venues should not be any more in US with
> such à discriminatory law.
>

I am concerned on the fact that some people are taking this discussion
to anti-America meeting sites, especially as someone living in the US.
I remind people that just a few years ago, all the meetings were being
held in the US.
US is the home ship for IETF. Yes, I sympatize with those having
issues in entering and hope that somehow those restrictions will go
away.

Actually I propose meeting more often in the US, that will be good for
everybody.

Regards,
Behcet
> Regards
> Mehdi
>
> Sent from my iPhone
>
> On 30 Jan 2017, at 20:58, MH Michael Hammer (5304) <MHammer@ag.com>; wrote:
>
>
>
> James,
>
>
>
> Seeing as the email you chose to quote was a response to my email from May
> 27th, 2016, I’m left trying to decide if you were responding specifically to
> my comments or that earlier thread in general. I still stand by my
> statements even if it means that the ultimate IETF decision is not to hold
> meetings in the USA – I think your prognostication unfortunately was
> correct. I was not being rhetorical in my earlier comments – We, as
> participants engaged in technical efforts across national boundaries need to
> figure out pragmatic ways of ensuring our efforts and activities continue to
> function despite decisions by specific localities.
>
>
>
> Looking forward, it might be reasonable for IETF to include a cancellation
> clause based on the government of the host country engaging in an act like
> the ban (after the contract has been signed.)
>
>
>
> Mike
>
>
>
> From: James Seng [mailto:james.seng@gmail.com]
> Sent: Sunday, January 29, 2017 2:08 PM
> To: MH Michael Hammer (5304)
> Cc: Thompson, Jeff; Dan Harkins; recentattendees@ietf.org; Ietf@Ietf. Org
> Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF 100
>
>
>
> I rescind my previous comment that the scenario I painted is rhetorical.
>
>
>
> None of our US fellow IETFers here have any moral authority to talk about
> "inclusive" ever again.
>
>
>
> -James Seng
>
>
>
> On Sat, May 28, 2016 at 5:44 AM, James Seng <james.seng@gmail.com>; wrote:
>
> Since after 9-11, things have change a lot for United States[1].
>
>
>
> Especially for TSA, I remember going to SFO the first time after 9-11, it
> took me 2 hours just to clear the security and I missed my flight. I also
> remember pre 9-11, I could get into US for less than 15-20mins.
>
>
>
> Now, for my American friends who pay in the price in time, let me tell you
> what we non-American citizen has to do to get into US after 9-11. We have
> been tagged, photographed, fingerprinted, all our 10 fingers every time we
> have to enter US. We have been systematically profiled, often by racial or
> nationality, and some of us have to go through enhanced body-to-body search
> everytime we cross security. I was put in a "Muslim" basket been a Malaysian
> for a while so ... And we have to do it with a smile because if any of us
> pull of a stunt like Aaron Tobey[2], we could be denied our entry and
> possibility forever.
>
>
>
> My wife complains that the over the last decade I have put on a lot of
> weight and asked me to check my photos. Unfortunately, I don't like selfie
> nor do I like to take pictures of myself. But I told her not to worry as TSA
> has a complete profile of me becoming fat over the years.
>
>
>
> Today, we all saw a US President may-to-be calling up to forbid Muslim to
> enter US, to build walls to prevent people from the south, who threaten to
> get even tougher to foreigners.
>
>
>
> So by the same principle that Jeff is advocate, that we hold IETF meeting
> where "law declares some people less valid", I prognosticate we may no
> longer able to hold our meetings in US.
>
>
>
> [1]
> http://www.ibtimes.com/pulse/united-states-after-911-6-things-have-changed-2001-2093156
>
>
>
> [2] http://dailylounge.com/the-daily/entry/how-to-fight-the-tsa
>
>
>
> ps: This is rhetorical to put any doubt in rest. I love US even though
> getting there is still a pain for me.
>
>
>
> -James Seng
>
>
>
>
>
>
>
> On Fri, May 27, 2016 at 9:34 PM, MH Michael Hammer (5304) <MHammer@ag.com>;
> wrote:
>
>
>
>> -----Original Message-----
>> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Thompson, Jeff
>> Sent: Friday, May 27, 2016 3:55 AM
>> To: Dan Harkins
>> Cc: recentattendees@ietf.org; Ietf@Ietf. Org
>> Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF
>> 100
>>
>> On 2016/5/26, 21:11:51, "Recentattendees on behalf of Dan Harkins"
>> <recentattendees-bounces@ietf.org on behalf of dharkins@lounge.org>;
>> wrote:
>>
>> >  I would also like to suggest that the ability of certain members to
>> >bring their family on a vacation that coincides with an IETF should not
>> >be a governing factor in venue selection. Many people like to launder a
>> >business trip into a family vacation (myself
>> >included!) but that's not why the IETF exists and it should have no
>> >bearing on where we meet.
>>
>> So then, the IETF policy would read ³The IETF may hold meetings in
>> countries
>> where the law declares some people less valid. If you are such a person,
>> then
>> the IETF recommends that to avoid trouble with the law you should hide who
>> you are, including not bringing your family.²
>>
>> Is this the organization that the IETF is going to be?
>>
>> - Jeff
>>
>
> Jeff,
>
> Is there any country in the world that meets the standard your comment
> implies should be the IETF policy? Is this a case of perfection being the
> enemy of good? Perhaps it is a case of perfection being the enemy of
> reality. I don't know what IETF policy should be but I do recognize that
> there are very real limitations that constrain choices. I'll also point out
> that the choices made will constrain the choices of participants. I'm not
> advocating for any particular choice by the IETF with regard to meeting
> locations.
>
> Mike
>
>
> _______________________________________________
> Recentattendees mailing list
> Recentattendees@ietf.org
> https://www.ietf.org/mailman/listinfo/recentattendees
>
>
>
>
>
> --
>
> -James Seng
>
>
>
>
>
> --
>
> -James Seng
>
> _______________________________________________
> Recentattendees mailing list
> Recentattendees@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_recentattendees&d=DwICAg&c=pqcuzKEN_84c78MOSc5_fw&r=Epy6n6lZ-_AtB6Unawan0zjIdEv95r_5HxuTpDOXS88&m=YG0d5xRrune4H9v4a848Pf_VWTMitYGP8HqzQqCQN5E&s=IbrWLu7DYbdtAsLRNOqj9FIMn8BuytPgAY3QQ-34hu4&e=