Re: [Mtgvenue] Issue #21: unfiltered should be mandatory (was: Re: issue #3: Too many mandatory)

"Tobias Gondrom" <tobias.gondrom@gondrom.org> Tue, 18 April 2017 22:54 UTC

Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 335731314DC for <mtgvenue@ietfa.amsl.com>; Tue, 18 Apr 2017 15:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=tobias.gondrom@gondrom.org header.d=gondrom.org
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 rPt7Y8z_duVs for <mtgvenue@ietfa.amsl.com>; Tue, 18 Apr 2017 15:54:51 -0700 (PDT)
Received: from gondrom.org (www.gondrom.org [5.35.241.16]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D6661314E1 for <mtgvenue@ietf.org>; Tue, 18 Apr 2017 15:54:51 -0700 (PDT)
Received: from seraph (x5ce4409f.dyn.telefonica.de [92.228.64.159]) by gondrom.org (Postfix) with ESMTPSA id 77257649EA; Wed, 19 Apr 2017 00:54:49 +0200 (CEST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gondrom.org; b=VNE3+uRMi3LeeQXXM27Ciw3z9NX1VOXBD6FJhiCFam+4xmPWT2Y6FNAj8vTvVrexZHBG1T+8Kvqq0FSbF1Q9SziDflV9w59L99fvSG4ENcXGI3lF/vUleikwMPzAtfRs4TmicoT1R+OSC4ae5wyYBQ0gA0iBdvEUl4gz2yxYzl8=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language;
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
To: 'Ted Hardie' <ted.ietf@gmail.com>, 'Yoav Nir' <ynir.ietf@gmail.com>
Cc: mtgvenue@ietf.org, 'Alissa Cooper' <alissa@cooperw.in>, 'Eliot Lear' <lear@cisco.com>
References: <37de22dc-04a4-f868-698e-cf03cd791957@cisco.com> <5CF8C201-00C4-4E07-BAB6-8CC5A30B54F5@cooperw.in> <7aba8a44-f1b8-b368-2b9a-91ad4bccfbcc@cisco.com> <D6DA3121-3365-4409-9DF1-8B761608DA11@gmail.com> <CA+9kkMDa4rQfwW=-M4nEgd2GPSmB_2NbT0owZA7yhHdU3AuS7A@mail.gmail.com>
In-Reply-To: <CA+9kkMDa4rQfwW=-M4nEgd2GPSmB_2NbT0owZA7yhHdU3AuS7A@mail.gmail.com>
Date: Tue, 18 Apr 2017 23:54:43 +0100
Message-ID: <022001d2b896$c6d552c0$547ff840$@gondrom.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0221_01D2B89F.289CA0F0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQIXiKhTaJZ9Fq0WEpsD2z3WJKMYxgGIcOz0AjYfvj4BoCAIagIXu1YuoQZmE9A=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/sDuD_7dYeyz1rhhwxl0-nZ9ZkFY>
Subject: Re: [Mtgvenue] Issue #21: unfiltered should be mandatory (was: Re: issue #3: Too many mandatory)
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 22:54:54 -0000

<IAOC hat=”off”>

 

I agree with Ted. 

I see unfiltered Internet as a strong requirement. But I don’t think this should to be mandatory. 

Statements like “unfiltered and unmodified *by the venue's own actions* would be something we could enforce in a contract stage, unless there are state level obligations to the venue that we can not overcome. Also I would note that filtering may happen in very different levels and amounts. 

 

In light of the discussion we had in Chicago, I would like to remind that we should be very conservative with the use of mandatory for requirements, but rather use “strong/ high priority requirement” or other determinations. 

 

I would see this as a very strong requirement and for the IAOC to continue to use strong incentives to ascertain that the venue has unfiltered Internet access, but I don’t think that this must be mandatory. IMHO so far the track record of the IAOC for selecting unfiltered locations is reasonably good. So I hope we can continue in that mode and rather strengthen this criteria if at some point the community feels that the criteria is not strong enough enforced by the IAOC in the selection process. 

 

Just my 2cents. 

 

Tobias

 

 

From: Mtgvenue [mailto:mtgvenue-bounces@ietf.org] On Behalf Of Ted Hardie
Sent: Tuesday, April 18, 2017 8:58 PM
To: Yoav Nir <ynir.ietf@gmail.com>
Cc: mtgvenue@ietf.org; Alissa Cooper <alissa@cooperw.in>; Eliot Lear <lear@cisco.com>
Subject: Re: [Mtgvenue] Issue #21: unfiltered should be mandatory (was: Re: issue #3: Too many mandatory)

 

On Tue, Apr 18, 2017 at 7:54 AM, Yoav Nir <ynir.ietf@gmail.com <mailto:ynir.ietf@gmail.com> > wrote:

Both of those points assume we need some kind of Internet access that others people on business travel don’t.

 

I think this varies a good bit.  Some of our communication back to our companies is bog standard business traveler stuff; some of our communications among ourselves or our devices is not.  A network that allows WebRTC media and data channels to flow without TURN servers is better for our remote participants, for example, and that may be a consideration for the typical business traveler.  We also have IETF network users who are more likely to engage in direct network management (or management of network devices) than would be common.  A tight firewall will hinder their ability to do that, and result in them spending time on fiddling with that rather than contributing.

I agree that  "unfiltered and unmodified" may be difficult to assure when nation states may change their laws, but I think it is reasonable for us to require that this be unfiltered and unmodified *by the venue's own actions*.  The larger question of what to do when meeting in a place all of whose facilities are required to implement such filtering likely belongs in a different requirement.

Just my two cents,

Ted