Re: [Mtgvenue] Internet Access during IETF Meetings

Toerless Eckert <tte@cs.fau.de> Wed, 22 November 2023 18:56 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 468ADC151545 for <mtgvenue@ietfa.amsl.com>; Wed, 22 Nov 2023 10:56:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QN-jAz9XD0Ej for <mtgvenue@ietfa.amsl.com>; Wed, 22 Nov 2023 10:56:36 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0EDCC151542 for <mtgvenue@ietf.org>; Wed, 22 Nov 2023 10:56:35 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4Sb9St2vpHznkW8; Wed, 22 Nov 2023 19:56:30 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4Sb9St1vggzkm40; Wed, 22 Nov 2023 19:56:30 +0100 (CET)
Date: Wed, 22 Nov 2023 19:56:30 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Eric Rescorla <ekr@rtfm.com>
Cc: mtgvenue@ietf.org
Message-ID: <ZV5O3lQBfsYFHx2E@faui48e.informatik.uni-erlangen.de>
References: <107966AA-6B01-4BCA-AD98-0C43CBF14FBB@ietf.org> <6atbump76t6eluoekue4cyc5prbqw65fvzk3lrbrnintku2dyt@enpmvgesajfz> <247351.1700663586@dyas> <ZV4bl09iH_9WOSKy@faui48e.informatik.uni-erlangen.de> <CABcZeBNPczZoFyVV_TnuNbPAdDicdg-RRYFmg-q3KYC4QatA1g@mail.gmail.com> <ZV5FtC98CgA7HnMs@faui48e.informatik.uni-erlangen.de> <CABcZeBMaCCpHU2xhTOPvK4chE-qc5iVgXFmhDPT6aGoJ-6_VPg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CABcZeBMaCCpHU2xhTOPvK4chE-qc5iVgXFmhDPT6aGoJ-6_VPg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/NZkw3pmUWCW8ifppB0DhL_6FkbA>
Subject: Re: [Mtgvenue] Internet Access during IETF Meetings
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "List for email discussion of the IETF 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: Wed, 22 Nov 2023 18:56:41 -0000

On Wed, Nov 22, 2023 at 10:40:40AM -0800, Eric Rescorla wrote:
> 
> Huh? The question at hand isn't whether censorship is better or worse
> in some absolute sense but whether the filtering in question "materially
> impacts" > the Internet use of IETF participants, and filtering in schools and
> libraries does not.

Sure, but we need to be very careful to closely evaluate only that impact and not
get into making moral judegments about othrer countries policies, which is where
i felt Michaels comment was heading.

I for once have been to enough places with so crappy Internet that it easily doubles as
no Internet at all - without firewalls.  If i would have had wanted to do hackathon
with my lab at home remotely, i would have been on the other end of the spectrum
of how much Internet i needed during IETF. So lets at least make sure we do a
good analysis of how much and what type of Internet use is required for people to
come in person.

Cheers
    Toerless

> -Ekr
> 
> On the "how many no shows would we have":
> > Lets also remember that because of political issues in the USA such as the
> > entity list,
> > likely a relevant number of participants choose to participate only
> > remotely. And we did
> > not even ask or try to vet such a factor for participants not willing/able
> > to come. So
> > if we are trying to figure out what amount of attendees would have to not
> > show up
> > because of some other factors such as Internet blocking, we should at
> > least ask ourselves
> > if it is appropriate for the IETF to take one factor into account, and the
> > other not.
> >
> > Cheers
> >     Toerless
> >
> > > sEkr
> > >
> > >
> > > >
> > > > Aka: Yes, your two points sound obvious from 50,000 feet, but i think
> > such
> > > > arguments go nowhere else but put us into a corner of hypocrites.
> > > >
> > > > My main concern going to Thailand again is btw.: that we again will
> > not see
> > > > the ocean from the conference location. Even crappy old San Francisco
> > had
> > > > that
> > > > to offer. Not to speak of Singapore. And in Berlin the river was around
> > > > the corner
> > > > with a lovely mooring location for river boats ... *sob* (water
> > addict...
> > > > ;-).
> > > >
> > > > > I have experience with using git+ssh://github.com access within one
> > > > country
> > > > > containing a national firewall.  It was interesting: the first
> > kilobyte
> > > > or
> > > > > two was fine, but then bandwidth declined to bytes/minute.  That's
> > not
> > > > > compatible with doing IETF work.
> > > >
> > > > Sounds like a firewall i have experienced too. One may note that the
> > degree
> > > > by which you can get through the firewall also depends on who you are
> > and
> > > > what request for policies you put in. Thats why i previously asked if
> > we
> > > > want to make our judegements against what a typical residential access
> > > > would
> > > > be or against the policies we likely could get when preparing
> > accordingly.
> > > >
> > > > >     > PS: I also have the impression that some of this work is being
> > > > inspired
> > > > >     > by people who are complaining about a site selection result
> > without
> > > > >     > having properly understood RFC 8718.  It might help (though
> > colour
> > > > me
> > > > >     > sceptical) to remind such people what the actual text says
> > about
> > > > what
> > > > >     > is and is not actually mandatory.
> > > > >
> > > > > I think that the LLC has struggled with finding a way to communicate
> > to
> > > > the
> > > > > community what kind of tradeoffs they are making.   For instance,
> > there
> > > > was a
> > > > > fair bit of noise from a few people about the lateness in announcing
> > > > > Brisbane.  That it significantly affected flight prices.  (I'm not
> > > > convinced
> > > > > that is real; but I live in a market with poor competition, so I
> > accept
> > > > the
> > > > > premise).  Had the LLC communicated that the location was "east
> > coast of
> > > > Australia"
> > > > > [with some subject to change], maybe people would have reacted
> > > > differently.
> > > > > In particular, some people might have said, "too rich for me", and
> > then
> > > > > decided to plan for San Francisco/Prague or Vancouver.
> > > >
> > > > I am always cautious to make strong judgement calls because i do not
> > have
> > > > a good
> > > > understanding of the actual amount of work that went into all of this.
> > And
> > > > whenever
> > > > i had a chance to ask in person, i was most often surprise how much
> > more
> > > > it was
> > > > than i thought.
> > > >
> > > > Cheers
> > > >     Toerless
> > > >
> > > > >
> > > > >
> > > > > --
> > > > > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> > > > >  -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > > _______________________________________________
> > > > > Mtgvenue mailing list
> > > > > Mtgvenue@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/mtgvenue
> > > >
> > > >
> > > > --
> > > > ---
> > > > tte@cs.fau.de
> > > >
> > > > _______________________________________________
> > > > Mtgvenue mailing list
> > > > Mtgvenue@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/mtgvenue
> > > >
> >
> > --
> > ---
> > tte@cs.fau.de
> >

-- 
---
tte@cs.fau.de