IETF Logo Mail Archive

Re: [Wish] Implementation report for draft-ietf-wish-whip-00

Lorenzo Miniero <lorenzo@meetecho.com> Fri, 10 September 2021 13:39 UTC

Return-Path: <lorenzo@meetecho.com>
X-Original-To: wish@ietfa.amsl.com
Delivered-To: wish@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 540803A0AB4 for <wish@ietfa.amsl.com>; Fri, 10 Sep 2021 06:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level:
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-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=aruba.it
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 ioFhjeRxWN7i for <wish@ietfa.amsl.com>; Fri, 10 Sep 2021 06:39:21 -0700 (PDT)
Received: from smtpcmd14161.aruba.it (smtpcmd14161.aruba.it [62.149.156.161]) by ietfa.amsl.com (Postfix) with ESMTP id 87E293A0A88 for <wish@ietf.org>; Fri, 10 Sep 2021 06:39:20 -0700 (PDT)
Received: from lminiero ([2.232.93.8]) by Aruba Outgoing Smtp with ESMTPSA id OgkQmrf1srIRlOgkQmfv1O; Fri, 10 Sep 2021 15:39:19 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aruba.it; s=a1; t=1631281159; bh=vXpEWJxAdUliO/AWyJlDJ8p557f5ZIFE18B9qRO2dx0=; h=Date:From:To:Subject:MIME-Version:Content-Type; b=F90SMRLTySktDhAVuGzmuBM6DFAuhtdEvQ5W2s+u3gzLciYz05Ret/TIR0QYEJ6lE xWJxSQgHLcMDZR7Bf2cvBTqX0QRZr0ucBbn+76NjDWM1W7xxMPNKpGLkfKber9JqZX Wa7droafS9gFYtwscJ7VPRHeyNXhwueNMovHGHtOlOO/3xVVe1GCwvUcjML24H/eIf MIDllus3rYCraYJdPZAh+amxMgzYExXfovg7d07fD1Lt9QsD12LPACtosfA2UYexMW Giw7sQOebDkwAC8oKALWy9xg/RdoBkbkKkleyVHoE5/BZWyQsc0XooEp0ccVJfROnN kYfGY1JL9wPhw==
Date: Fri, 10 Sep 2021 15:39:18 +0200
From: Lorenzo Miniero <lorenzo@meetecho.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: wish@ietf.org
Message-ID: <20210910153918.4a626d78@lminiero>
In-Reply-To: <878s04blj6.wl-jch@irif.fr>
References: <874kathgcl.wl-jch@irif.fr> <87wnnpg0un.wl-jch@irif.fr> <20210909185217.63e966c2@lminiero> <87czpgby87.wl-jch@irif.fr> <20210910110922.3e9afce0@lminiero> <878s04blj6.wl-jch@irif.fr>
Organization: Meetecho
X-Mailer: Claws Mail 3.18.0 (GTK+ 2.24.33; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfHU14HMxBO6wSj6fXvBsZ5sauX0UddSsu+NYOG3Wl+YNdwNrOI93mAs/qI+vMk2q1Kva9ptm3Z8AM0Xn6UiHzP4oVBZvf8hq7N3Va8OTIdtjIb2i90wS sN3sQUIkL7ke+eK9o+v2T+A0DK+tgmfn1xTF+wtqYUt3r8Hwk9kr0b/t
Archived-At: <https://mailarchive.ietf.org/arch/msg/wish/b7UXAVBVKtcMGScKgoqVAJvmlDM>
Subject: Re: [Wish] Implementation report for draft-ietf-wish-whip-00
X-BeenThere: wish@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: WebRTC Ingest Signaling over HTTPS <wish.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wish>, <mailto:wish-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wish/>
List-Post: <mailto:wish@ietf.org>
List-Help: <mailto:wish-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wish>, <mailto:wish-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Sep 2021 13:39:26 -0000

On Fri, 10 Sep 2021 15:35:57 +0200
Juliusz Chroboczek <jch@irif.fr> wrote:

> > Yes, I checked RFC 8840 (my fault for missing it initially) and
> > ice-ugrag, ice-pwd and the "fake" m-line are all required. I'm
> > updating the code of both client and server right now to adhere to
> > the spec.  
> 
> I can easily parse this information in Galene, but won't that preclude
> writing WHIP clients in Javascript?  Neither the m-line nor the
> ice-pwd are readily available in the onicecandidate callback, so I
> don't see how a Javascript client could possibly avoid parsing the
> local description in order to get that information.
> 
> -- Juliusz


That is a bit awkward, yes. That's indeed how I've implemented it in my
client as well, as I'm not aware of a (simpler) way to retrieve the
information from GStreamer's webrtcbin either.

Lorenzo

-- 
I'm getting older but, unlike whisky, I'm not getting any better
https://twitter.com/elminiero

v2.8.7 | Report a Bug | By Email