Re: [103attendees] A/V in Bangkok

Brian E Carpenter <> Fri, 09 November 2018 22:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9A17C12D4E7 for <>; Fri, 9 Nov 2018 14:56:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DGQQj8DLKxiI for <>; Fri, 9 Nov 2018 14:56:02 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 98F73128A5C for <>; Fri, 9 Nov 2018 14:56:02 -0800 (PST)
Received: by with SMTP id 70so1452400pgh.8 for <>; Fri, 09 Nov 2018 14:56:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=L9J/8kApff7SMEybv5gBSl0EGIi2PpTVybGpLzhH2+g=; b=nBoZUiuhilpjjwX0fLzhq5cQuXEPCmrCAj5B07oS6VhYIzn1sMuB0nBD15AZqWK8T/ Zm/OiiqqvraCoWbYJ6Nr3uv0Wy1rJAwmitCFEWK21WjmZzRaDaIjTIhlDdNDTHd3Pi0u P/q57pECpFAPaxNTE78dl1uy2MgQmzMPEnF3Lwc6Yhm8eoiD9i0TRGaFsBokbCzp3sRi XelGCA3MOKStoixfWYaTdYS4PGz4kavafp74cYrSHtlblQSWTqTDlOHciemu6gh9Mlox WFKnFX3kcv8w7Q0pFkHzOQ4UhF665OGUbyd3zd//HYomIjRWPA5O9McqRgHxbcJHHR67 o2Rg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=L9J/8kApff7SMEybv5gBSl0EGIi2PpTVybGpLzhH2+g=; b=mAocpvYu2dPZ1/ZCsySzjmJnoEV8xHYztMT6gdp1DqHzOm/l/kXr0kxOpw+Gbj0vWu BjQvwASZAP/pzt40y5thyKczHtbkO5095st9wgTwrv9sfo7gHViFZrML2NXazsQOVTfL SvYDjugt3KgsIU/SYR2XomOBbfDluRXOTr634GddOQj24fQvPANpfU7kES6OEFmXCAJk kI3QkuFoUc5gC/8HrY/+nlY22flqxW1fKW+cB/thNLU6EMym5DjLQqQxPpynNdf8uwMh eiyLH9tysvfzUV1c/1Y9X2vSHeEKj2SNMJ82V+FBycF05ZnqMA3zF5QIm9KyCMZmTR84 tTOA==
X-Gm-Message-State: AGRZ1gJe6jHyH/vMCLA3TshnlHg29CUQ9XhGy/Wt91fwe00yBLivunfn UGiSZz02xh7CS98Ggafmxwg6tOkm
X-Google-Smtp-Source: AJdET5cwFUnyY2Fmjzupr5jiN8uomUPDSA8e8IDaon2sb5Yk/dw4RRAGqc6zIteCytjS1tr/b3aw9Q==
X-Received: by 2002:a63:b105:: with SMTP id r5mr9227783pgf.442.1541804161689; Fri, 09 Nov 2018 14:56:01 -0800 (PST)
Received: from [] ([]) by with ESMTPSA id s8-v6sm7687947pgi.44.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Nov 2018 14:56:00 -0800 (PST)
To: John C Klensin <>, Ted Lemon <>
Cc: Carsten Bormann <>,
References: <> <> <E1443D6EC0DFCDCC464FD64C@PSB> <> <F07FBEC3D5CD39652FE90A78@PSB>
From: Brian E Carpenter <>
Message-ID: <>
Date: Sat, 10 Nov 2018 11:55:55 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <F07FBEC3D5CD39652FE90A78@PSB>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [103attendees] A/V in Bangkok
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list of IETF 103 attendees that have opted in on this list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 09 Nov 2018 22:56:05 -0000

On 2018-11-10 09:29, John C Klensin wrote:
> --On Friday, November 9, 2018 15:06 -0500 Ted Lemon
> <> wrote:
>> There were a lot of cases, particularly early on, when remote
>> presenters' audio clipped badly, making it painful to sit in
>> the room.   That seemed to improve over the course of the
>> week, but the gain on remote presenters in every single remote
>> presentation I heard was still too high, again making it
>> painful to sit in the room.
>> Quite a few times when someone wanted to comment remotely they
>> couldn't, because their microphone wasn't working.   This
>> wasn't necessarily meetecho's fault in a direct way, but we
>> have to figure out how to get this right if we're serious
>> about remote participation.
> Ted, 
> Very helpful.  Thanks.  Wrt the remote presenters and borrowing
> from some earlier comments from one of the Meetech team, is
> there any way to differentiate how many of those problems with
> remote presenters of whom Meetecho was notified well in advance
> and with whom they have an opportunity to test and debug (as
> they have been requesting for several years)

At least in my case, I'd done the test, discovered that my browser
(Waterfox) couldn't use any of the STUN/ICE options, and switched
to a browser (Firefox) that passed the tests. But when I came to
put my hand up in a WG, the floor control for some reason failed
to enable me, so I couldn't speak. Fortunately there was an active
jabber scribe in that session who read out my comments.

(Before anyone points out that Waterfox and Firefox are virtually
identical: yes, I know, and all the relevant config options were
set identically. But something was different. Just one of RTCweb's
little mysteries.)

I wonder if it would be possible to setup a dummy WG session during
the last few days before each IETF, where anybody could do a test,
with some non-meetecho person acting as chair, and meetecho
watching as they do for real sessions.

> and those who
> simply used the remote queue facilities as if they were just
> making a comment?

afaik, the meetecho test is supposed to validate both that mode and
presenter mode. But the devil is in the details.


> thanks,
>    john