Re: [Netrqmts] IETF 105 Minutes

[Michael Richardson <[e-mail]>]

Alessandro Amirante <[e-mail]> 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.

    > At IETF, Meetecho deploys remote participation servers at the meeting
    > venue mainly for two reasons:
    > 1. minimize the delay, which is critical
    > to have remote participants participate to Q&A or give presentations;
    > 2. feed them with audio+video from the meeting rooms via LAN, over a
    > dedicated vLAN, so to not be affected by packet loss and external
    > network conditions.

I can't estimate what about of incremental work this requirement causes
for the NOC over what we do *today*.  I suspect it's non-trivial, but
not complex.

Clearly, if we had a fully NAT44 network that most other meetings have, that
we'd be looking at more effort.  Either bringing in real networking, or
having some cloud component.

This is, I think, an example of synergies that we get from having a real
network.  We are lowering the bar for things like Meetecho, but we might
never consider doing this just for Meetecho.

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