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

Lorenzo Miniero <lorenzo@meetecho.com> Thu, 09 September 2021 16:52 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 47DF83A1CE0 for <wish@ietfa.amsl.com>; Thu, 9 Sep 2021 09:52:25 -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 6Adle7To4C5R for <wish@ietfa.amsl.com>; Thu, 9 Sep 2021 09:52:20 -0700 (PDT)
Received: from smtpcmd0871.aruba.it (smtpcmd0871.aruba.it [62.149.156.71]) by ietfa.amsl.com (Postfix) with ESMTP id 544383A1CF4 for <wish@ietf.org>; Thu, 9 Sep 2021 09:52:20 -0700 (PDT)
Received: from lminiero ([93.34.34.104]) by Aruba Outgoing Smtp with ESMTPSA id ONHemlQlkKBZzONHemmXKU; Thu, 09 Sep 2021 18:52:18 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aruba.it; s=a1; t=1631206338; bh=07NcCmv+imIxevlKcU3FYDsQh5j4/iUaj9yqOwbYXSk=; h=Date:From:To:Subject:MIME-Version:Content-Type; b=dv2+83TisdrM80hwuvxhhROxFMCFtviwKAadczvUO7LsA+a5I/KlgWFD/jYRoM0XS gJsYrUqRg/hRkTtWLrNkHiHx6pEh+ULGr7WsZR1MbYT6DUYuyBADFWh7Y6qzHoLUJc qibZ4NcCCKuT+kmTR8FCJpJqEe1IKnYTv86yQZBrGno10RmKmH8ye4EKtBKfRJ2Whe MZrQm3ARg2rTy824w0aH4hzMdoGvenvA8lSbpY40vuRGLMQ+gM65Fm424f3rCNwvrk iPBkjJz4ODxGdznmcwfCgRyJrkncpE2fX39GK0eAB9cjdAWhJrRSheqjBBzHzhkxUq I0mg4a5aT8maA==
Date: Thu, 9 Sep 2021 18:52:17 +0200
From: Lorenzo Miniero <lorenzo@meetecho.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: wish@ietf.org
Message-ID: <20210909185217.63e966c2@lminiero>
In-Reply-To: <87wnnpg0un.wl-jch@irif.fr>
References: <874kathgcl.wl-jch@irif.fr> <87wnnpg0un.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: MS4wfNA/05CDFHq5E9dHVuf7WEDtlhHF+JKf5k/YWLhgKEL50fE1GCnYcR7tY0wlDIPQ8pj2W/oV1WTEaoInel6TxXOoCI5eNOHz093aknTqWWzNb9tHuzcz zk1Hsdp4qrGocj9suX66752BQGhyahAlOacN6WWLiI+YbIxGCtzgQCbs
Archived-At: <https://mailarchive.ietf.org/arch/msg/wish/2pEzoZh_5WfVKwEmYFXF0tbgs4o>
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: Thu, 09 Sep 2021 16:52:26 -0000

On Thu, 09 Sep 2021 18:39:12 +0200
Juliusz Chroboczek <jch@irif.fr> wrote:

> >      - what happens if a candidate is followed by random non-JSON
> > garbage? Is that an error?  If so, MUST I return an error or MAY I
> > return an error?  I'm currently just ignoring the garbage.  
> 
> Looking at the draft again, it doesn't look like the candidate is
> JSON, it's just the raw SDP.  Since we're doing bundle, the
> sdpMLineIndex is necessarily 0, so it doesn't need to be sent.
> 
> Is that right?
> 
> -- Juliusz
> 

Sergio pointed this out too in a private conversation, as the format of
the candidates to send in a PATCH was one of the assumptions I made in
my implementation. I chose to serialize them to a JSON object exactly
because of what you said (sdpMLineIndex), but if bundling is indeed
mandated, then it's unneeded and the "raw" candidate is fine. I'll fix
this in both server and client tomorrow.

What still isn't clear is whether or not grouping multiple candidates in
a single PATCH request (e.g., because we collected a few before we got
the answer back) is doable or not, and how they should be formatted in
case.

Lorenzo

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