IETF Logo Mail Archive

Re: Off-topic: making WebRTC work in practice (Re: a brief pondering)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 01 April 2020 15:13 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A9373A1088 for <ietf@ietfa.amsl.com>; Wed, 1 Apr 2020 08:13:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 6MAUy524Xtzi for <ietf@ietfa.amsl.com>; Wed, 1 Apr 2020 08:12:57 -0700 (PDT)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE4A33A0FAD for <IETF@ietf.org>; Wed, 1 Apr 2020 08:12:56 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id t17so26186306ljc.12 for <IETF@ietf.org>; Wed, 01 Apr 2020 08:12:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/BmuvyaAm60bN2fRH++/+n4KnMqETZbaiJTKfkzTtTQ=; b=AZeZft1n++BKIES3LTdgv4qxZneqHSZY/bWuRqjibUoHIDtnWDnkctgzpmW/miILez sbyIYitdLuEITv2lfPtf8Naz5uxLpeS7E7kanBl+cPgj7reaWBLQjCo50YuKlHBhBDqK Pd0AOQnnlBDBdNBlzEUxN94SCxo/UEq8h+Xy7hGVb/bQIofwp6gmiSHgUx8jqoLLNj6+ JQv5lx6Ca8vbHmYw/hTLzv9Wx0YauIYRSBhCvlwvGVK0gfzWcOfRN+4kbHg9nobqxOYS 9ZVxfQx/x6sTMSRKQS2l2icsB+J5sy3wvDokfd5Dl1c3C8Rlbp7DapLncN+39KvHVYWr MLQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/BmuvyaAm60bN2fRH++/+n4KnMqETZbaiJTKfkzTtTQ=; b=hWx3xN3cyabtRkrPSiFFwBGPaW2t0MGvHzqS78X6gcvObU3Z++UNBdBjUDXjYUPVo5 i773wRw8ZxuiHNydyRF/KQECFcN3rxBXEkPi7fE5zHoiVCdy4gdv0CuqZ0r+HXddiTXW oAjvbBn7mzm0bZ9skwVRzg41Ecr9VewL07yMtD0fLJtEs15VR901+Ao2YjBBj34iYBFz xuPv1XjcNq67toZz5pcv1TvrYbIdzFFruMOk5NqTVP2BDsu6xLwDGRAaqLElyzgbgmdu D6+bl/ROLM75z3FemNAbAWA0YtELQ9AjpI9vGbNq0FApIZj8Vph9XZW9MlgLNWVMSIBS A2sw==
X-Gm-Message-State: AGi0PubA8+blRMedv6VrcpVFQei+W6pve4gMa3alQ5F7M48TZyPBaXAL LEADoR5CuTEMX8PeXR2Rg9YBDMEPWeXsAAzLN00huQ==
X-Google-Smtp-Source: APiQypJrUXWSAJr9R3VCPsGKC/7yD5FSqPLmCFA6Yk3S8HFgZ7rjW68phQWdtiYzmcGJsWC+0eNE6uwk04sAPUDY+YU=
X-Received: by 2002:a05:651c:23b:: with SMTP id z27mr5472201ljn.125.1585753974841; Wed, 01 Apr 2020 08:12:54 -0700 (PDT)
MIME-Version: 1.0
References: <fd6b7ee2-cdbe-14a1-0087-ce61282b22f6@lear.ch> <29D0DCA7-1D72-428F-A6DD-05511D90C039@cable.comcast.com> <31A798F0-9DE0-4231-A768-76BA9A1A2180@tzi.org> <E1FD746D-0BCD-4ECC-BB9B-75DFA05AA9DC@tzi.org>
In-Reply-To: <E1FD746D-0BCD-4ECC-BB9B-75DFA05AA9DC@tzi.org>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 01 Apr 2020 10:12:27 -0500
Message-ID: <CAKKJt-cXczqjErrj3+8if+K3LsCLLLWY=qiHatOks3u7SwatxA@mail.gmail.com>
Subject: Re: Off-topic: making WebRTC work in practice (Re: a brief pondering)
To: Carsten Bormann <cabo@tzi.org>
Cc: ietf <IETF@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005f23b105a23c1e15"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tzSHSyjPTgZKh40nDQk57AJMCD4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2020 15:13:02 -0000

Hi, Carsten,

On Wed, Apr 1, 2020 at 6:54 AM Carsten Bormann <cabo@tzi.org> wrote:

> In the university, a lot of WebRTC is using Jitsi as a tool.
> This works mostly well, with occasional surprises.
> What we could use now is a better way to diagnose these surprises.
> This requires WebRTC knowledge that our IT people don’t have.
> A WebRTC troubleshooting guide that I could point them to would be most
> helpful.
> (Debugging and fixing Jitsi so it works reliably with both Firefox and
> Chrome would also help.)
>

Just so I understand, are you talking about

   - something that needs to happen in RTCWeb, or
   - something that needs to happen in network operations, or
   - something that needs to happen in the Jitsi implementation itself?

If the answer is two or more of these, that's also good to know.

Best,

Spencer


> Grüße, Carsten
>
>
> > On 2020-03-22, at 06:45, Carsten Bormann <cabo@tzi.org> wrote:
> >
> > On 2020-03-21, at 16:54, Livingood, Jason <Jason_Livingood@comcast.com>
> wrote:
> >>
> >> what can this community (and similar/adjacent ones) do productively
> together to help
> >
> > The one thing that would be most useful for me right now would be a
> document with operational considerations for keeping WebRTC running (e.g.,
> How not to mess it up with your firewall).
> >
> > Grüße, Carsten
> >
>
>

v2.23.0 | Report a Bug | By Email