Re: [Mtgvenue] Internet Access during IETF Meetings

Eric Rescorla <ekr@rtfm.com> Wed, 22 November 2023 18:41 UTC

Return-Path: <ekr@rtfm.com>
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 089D8C09D4D2 for <mtgvenue@ietfa.amsl.com>; Wed, 22 Nov 2023 10:41:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20230601.gappssmtp.com
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 OB4FdLUbKKKA for <mtgvenue@ietfa.amsl.com>; Wed, 22 Nov 2023 10:41:19 -0800 (PST)
Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE6E2C151992 for <mtgvenue@ietf.org>; Wed, 22 Nov 2023 10:41:18 -0800 (PST)
Received: by mail-yb1-xb34.google.com with SMTP id 3f1490d57ef6-daf7ed42ea6so113565276.0 for <mtgvenue@ietf.org>; Wed, 22 Nov 2023 10:41:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20230601.gappssmtp.com; s=20230601; t=1700678477; x=1701283277; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=CZlJaOeoRMyzQo3k07cpRaXLcMVgdXR24hKVeiH54ws=; b=izR58+B2NBQnsRj14L4gmc2ilSu9EmpSM11697U6WiW07Oot0hpfQ4oPOCkMU5Mj6L EkBCkYjQl2b5k4SirwKLs3g1ipVojIjavTSdtOqrJPgphh6yPaRy1euRz2OsCH7hTGqH AicQDFc3N2nhk4+ckCSJFdFDcGzpbjFw7xsDpD806hl/M9HultvWm2L86/LQn8ThV2QV lXs4jd1NpsE37j10Ur/BWESq0QqGJ8An297clxhip9WRNrpXoH6ajEUd0mrBRna0PnIi GZfA6TVsAq6jo+683qPFopl8VhdR5GMBqIAKsVsvvGdCgFkYZbBFfbF1tQ+pacJGVOyE NgfA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700678477; x=1701283277; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=CZlJaOeoRMyzQo3k07cpRaXLcMVgdXR24hKVeiH54ws=; b=L6pyCOIT59yRoGhq/l3epl88GLVcUU6aVGJciXF5WPZoi6/jlq31LQ6Vg1vb4iaWrX k5NE2GV8JnhYFOLfUiTvmNnzRxLugycMCUBZ1Zi/mgS2zpUWJzvwoS76xF03Lpe4y+ix 6jQni1jbOeOVJsHgmaWfqDuMq/wrJH4V+XCUpRasppe2J6QzvnXx6nEf1RwPXCPbVhAi 03DZhmi1ngAcalyB011IhSPCOhDpCMTlOQM+kaEucDaO9mDv0nxMy1uRUDsMjLohAiv6 Xj2KzERnQuwtMIuRfk0Utdi5LwQq8doVi+zGHaV5biTa7d5MGi2N195XookoqB8/sAtG wcJQ==
X-Gm-Message-State: AOJu0YxczIlIBDOoG+ZRk0wQjEvj1ExStjBk8ZjQmRT/5uadxG3ii2w2 W9rvEh4MBzsO3jla37dV2E+wGAzjuRUQg03hgEdOI+VBIaFZjlIHsys=
X-Google-Smtp-Source: AGHT+IGTRNbMaalddfeOXBY/Lwl+yx+2agXb0rsJEpwqPVGgoQDZHYfRMaLoY7RTUlC8jGji+WvDssVzniZRJebiYDQ=
X-Received: by 2002:a25:400d:0:b0:d9a:3811:9c57 with SMTP id n13-20020a25400d000000b00d9a38119c57mr2912122yba.43.1700678477489; Wed, 22 Nov 2023 10:41:17 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <ZV5FtC98CgA7HnMs@faui48e.informatik.uni-erlangen.de>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 22 Nov 2023 10:40:40 -0800
Message-ID: <CABcZeBMaCCpHU2xhTOPvK4chE-qc5iVgXFmhDPT6aGoJ-6_VPg@mail.gmail.com>
To: Toerless Eckert <tte@cs.fau.de>
Cc: mtgvenue@ietf.org
Content-Type: multipart/alternative; boundary="000000000000873e3a060ac21012"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/du9sUKVMOGnkuzjStSb7CjSzz7Q>
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:41:23 -0000

On Wed, Nov 22, 2023 at 10:17 AM Toerless Eckert <tte@cs.fau.de> wrote:

> On Wed, Nov 22, 2023 at 09:03:38AM -0800, Eric Rescorla wrote:
> > > How does banning books about slavery and evolution in certain US states
> > > count in on 2 ?
> >
> > Citation needed. Perhaps you're referring to books being taken out of
> > libraries or schools? If so, that's not something I approve of, but it's
> > quite different from what Michael is talking about.
>
> Yes, i was referring to libraries/schools. Sorry if "banning" was not the
> appropriate word to represent that condition.
>
> And... we can play "my censorship is different from your censorship" all
> day long,
> but it will still look hypocritical when one focusses more one another
> countries
> censorship than ones own. Especially where that censorship is supported by
> a majority
> of the public of such countries.
>

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.

-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
>