IETF Logo Mail Archive

Re: [Netrqmts] R: Re: IETF 105 Minutes

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 31 July 2019 20:55 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: netrqmts@ietfa.amsl.com
Delivered-To: netrqmts@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34E39120077 for <netrqmts@ietfa.amsl.com>; Wed, 31 Jul 2019 13:55:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 6K-hLQHgFOSC for <netrqmts@ietfa.amsl.com>; Wed, 31 Jul 2019 13:55:14 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9902712006D for <netrqmts@ietf.org>; Wed, 31 Jul 2019 13:55:14 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 9C7A2380BE; Wed, 31 Jul 2019 16:54:46 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D62E5D92; Wed, 31 Jul 2019 16:55:12 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Alessandro Amirante <alex@meetecho.com>, netrqmts@ietf.org
In-Reply-To: <np754afisdg0cv28tlb574hu.1564601354124@email.android.com>
References: <DF3803B7-C05B-4A31-B873-73A86B1416CE@vigilsec.com> <19915.1564514403@localhost> <20190730202439.zl6gjvzasxofvej2@faui48f.informatik.uni-erlangen.de> <27837.1564524525@localhost> <3fbb96e8-9977-39be-cd92-492b819aa1b9@meetecho.com> <13156.1564597945@localhost> <np754afisdg0cv28tlb574hu.1564601354124@email.android.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 31 Jul 2019 16:55:12 -0400
Message-ID: <15599.1564606512@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netrqmts/WwmjK3a2QdUrtpZSkH17pS7mL_o>
Subject: Re: [Netrqmts] R: Re: IETF 105 Minutes
X-BeenThere: netrqmts@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Meeting Network Requirements <netrqmts.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netrqmts>, <mailto:netrqmts-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netrqmts/>
List-Post: <mailto:netrqmts@ietf.org>
List-Help: <mailto:netrqmts-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netrqmts>, <mailto:netrqmts-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jul 2019 20:55:17 -0000

Alessandro Amirante <alex@meetecho.com> wrote:
    >> Alessandro Amirante <alex@meetecho.com> wrote: >> I know that Meetecho
    >> is used at other conferences, and I assume that >> those conferences
    >> do not bring the same kit that IETF brings, so I >> wonder what they
    >> do there, and what problems we are avoiding.
    >> 
    >> > Meetecho is mostly used at other conferences for _streaming_ only,
    >> not > for actual _remote participation_. I.e., no remote audio/video >
    >> injection into the physical room, no virtual queue. RTC servers are
    >> not > deployed on site. A good uplink bandwidth from the conference
    >> venue is > still required.
    >> 
    >> Thanks for this update.  Can you explain the reasons why other
    >> conferences/meetings do not do remote participation?  Is it economic
    >> (too expensive for them), or just logistical (it's unidirectional
    >> slideware really), or it is because they lack a real Internet
    >> connection, and so you can't even consider discussing it.

    > They are conferences: they're not interested in having remote
    > participants contribute with questions or even presentations. My guess
    > is that they want people to show up in person, pay the conference
    > fee...

    > I'd love to push remote participation to other SDOs, though!

Thank you for the reply.
Making our use of Meetecho more similar to other users is probably good for
all of us.  If that means encouraging others to be more like us, then fine :-)

If the networks that we "upgrade" in conference centers make that easier,
that's something... as we would be improving the Internet :-)

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email