Re: IAOC requesting input on (potential) meeting cities

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 11 April 2017 11:11 UTC

Return-Path: <prvs=1274da9a4c=jordi.palet@consulintel.es>
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 7EC5B1275AB for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 04:11:46 -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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 3jkh6Cb5zdWR for <ietf@ietfa.amsl.com>; Tue, 11 Apr 2017 04:11:44 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 037A6127869 for <ietf@ietf.org>; Tue, 11 Apr 2017 04:11:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1491909102; x=1492513902; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=DTy3YKkrP6capTMY8hanBo2PJ cE+yqkmmzGa1vtQtjw=; b=Rc26aSafYTFfC5Zju6GzOVvJSPjK+JjeXZB+59LfA 5rCP5aMfELUDb97MQTLnr9U1Sl2UvikqyrJwshhWRsA7YYyJmixNIwXIO+krHgFP FwAwxb9a7BQCyUz+Zdu2WNmD0xnVyLQpoYRMIC6W3ahzfv/yvdTwxOpzIFebTc6t Dk=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=cQEMfNUsFzrwHAUm+6LgrXlmzIMs2yaFrDVU488E2G42O6FfFIERvI9KsBJK kZg0E25IJmsxSLRwMPT1vxKZYOMXsKUIO+kbAxyxZyHuXdbMw3NdIVdA8 e1Fy2MYnhJN5WyUiJLOPWcQosd+R9mjyddVrly7tpUCyDEBcTDCNs8=;
X-MDAV-Processed: mail.consulintel.es, Tue, 11 Apr 2017 13:11:42 +0200
X-Spam-Processed: mail.consulintel.es, Tue, 11 Apr 2017 13:11:41 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005406170.msg for <ietf@ietf.org>; Tue, 11 Apr 2017 13:11:41 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170411:md50005406170::m9L8mJG6l5YcjY8H:0000F8f/
X-Return-Path: prvs=1274da9a4c=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.20.0.170309
Date: Tue, 11 Apr 2017 13:11:34 +0200
Subject: Re: IAOC requesting input on (potential) meeting cities
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF Discussion <ietf@ietf.org>, <iaoc@ietf.org>
Message-ID: <22EB34C2-CF25-4E18-8185-47F27363A6AD@consulintel.es>
Thread-Topic: IAOC requesting input on (potential) meeting cities
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com> <20170404221042.GC4004@localhost> <7E834C8D-FCFB-48C4-925A-73B5FDEC60FD@consulintel.es>
In-Reply-To: <7E834C8D-FCFB-48C4-925A-73B5FDEC60FD@consulintel.es>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jVzR4ZtBLCaZu9nexVPCpiVUeUA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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, 11 Apr 2017 11:11:46 -0000

Can we get an answer from the IAOC to the questions below?

If we cancel San Francisco, how much that is going to cost to the IETF for each of two planned meetings?

Can we cancel the actual hotel contract considering the new US situation? If not, has this been considered for new contracts to avoid this problem?

Otherwise there is any reason that can justify the lack of transparency in this?

Regards,
Jordi
 

-----Mensaje original-----
De: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Fecha: miércoles, 5 de abril de 2017, 10:26
Para: <iaoc@ietf.org>
Asunto: Re: IAOC requesting input on (potential) meeting cities

    One important question here, same as we had in the case of Singapore.
    
    If we cancel San Francisco, how much that is going to cost to the IETF for each of two planned meetings?
    
    Furthermore, can the IAOC respond to this:
    
    Can we cancel the actual hotel contract considering the new US situation? If not, has this been considered for new contracts to avoid this problem?
    
    I think the relevant information in the contract need to be disclosed and have it now on the table, otherwise we will be wasting the time discussing possibilities that are actually impossible to assume for the IETF …
    
    My general position is:
    1) I will prefer not cancelling already planned meetings.
    2) I will prefer not “blocking” any regions or countries from future meetings, including US.
    3) However, for already contracted meetings, if this is going to cost IETF thousands of dollars, we can’t afford that.
    4) We must work with authorities to avoid people being banned for attending the meetings.
    
    Maybe I’ve missed responses to some of my answers already, in any case, can the IAOC provide urgently those with a complete summary of the situation?
    
    Regards,
    Jordi
     
    
    -----Mensaje original-----
    De: Eliot Lear <lear@cisco.com>
    Responder a: <lear@cisco.com>
    Fecha: miércoles, 5 de abril de 2017, 6:39
    Para: Nico Williams <nico@cryptonector.com>om>, Yoav Nir <ynir.ietf@gmail.com>
    CC: IETF <ietf@ietf.org>rg>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>es>, Jared Mauch <jared@puck.nether.net>
    Asunto: Re: IAOC requesting input on (potential) meeting cities
    
        Nico,
        
        On 4/5/17 12:10 AM, Nico Williams wrote:
        > I do suspect that the U.S. will be a more difficult location for more
        > attendees than other locations.  Certainly the news we all see is not
        > encouraging as to hosting IETF meetings in the U.S.  This I don't deny.
        > Though it's also possible that this is becoming a self-reinforcing meme
        > and that we're just not seeing incidents in other countries in the news.
        > In any case, the U.S. certainly does not have a monopoly on the border
        > harasment business.
        
        Certainly people have had trouble getting into other countries, most
        notably Canada where an IAB member was refused entry.  But this isn't
        just news.  It is a series of declarations by the U.S. government of
        their intentions, and the IAOC has to plan ahead.  That's why Jared's
        request for data is simply not tenable *at this stage*.  If it turns out
        that things aren't so bad, the IAOC can react accordingly.  However, as
        I wrote in my original email, there is now good reason to believe that
        things will get worse, due to the European Parliament’s decision to
        require visas from U.S. citizens.
        
        > Some people may wish to boycott the U.S. by refusing to host events
        > there.  There is some precedent for such a boycott.  For example, some
        > time back an obscure agency of the Texas state government decided to
        > guard its surplus budget by policing public drunkenness at hotel bars,
        > which led to a number of conferences pulling out of Texas, and the
        > ensuing bad PR led the legislature to rein in said agency.
        >
        > However, at the scale of a state/province the politics of boycotts is
        > generally not partisan, but at a national/global scale it tends to be
        > rankly partisan, and boycotts may not be productive and may be divisive,
        > and should be approached with care.  Here "care" means: get some
        > evidence of negative impact on participation.  
        
        We ALREADY have evidence, as some people couldn't make Chicago, and said
        so on this very list (and, by the way, were shamefully attacked and
        dismissed (no, it certainly wasn't you)).  What we don't have is an
        understanding of the order of magnitude of the impact, and that is going
        to be very hard to gather in so  fluid a situation with so long a
        lookahead.  The point, by the way, as I see it, is not to punish the
        U.S. but to hold a successful meeting (that is what the mtgvenue draft
        states as well).
        
        > Reducing frequency of
        > U.S. meetings is not a boycott, and is something the IETF has been doing
        > for a long time anyways.  Further reducing that frequency in the short
        > term would be perfectly fine, though it would also reduce opportunities
        > for gather the stats we really need to make a sound, non-partisan
        > decision to boycott if the stats warrant it.
        >
        
        Turn this around: suppose we do keep the meeting in San Francisco, for
        instance, and some number of people cannot get there for whatever
        reason, or cannot otherwise function on an equal footing.  Would the
        IAOC then be attacked for having ignored the vast number of warnings
        that have been signaled?
        
        Eliot
        
        
    
    
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.