IETF Logo Mail Archive

Re: [Wish] IETF LC Review of draft-ietf-wish-whip-09

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Mon, 06 November 2023 10:58 UTC

Return-Path: <sergio.garcia.murillo@gmail.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 2C679C1D470B; Mon, 6 Nov 2023 02:58:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AkfYi8VX87cs; Mon, 6 Nov 2023 02:58:10 -0800 (PST)
Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3088FC18FCA7; Mon, 6 Nov 2023 02:58:10 -0800 (PST)
Received: by mail-ej1-x635.google.com with SMTP id a640c23a62f3a-9c2a0725825so628789066b.2; Mon, 06 Nov 2023 02:58:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699268288; x=1699873088; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=SFC8JPcwRyT+yiqmht50Lm+KMf9EZExJfqdnTQEUOPY=; b=YNYb/9lg7zecBhGKHtuuFPLfJjSAcXUM8sPM0QvMZ7ubeTVMy4qsnGpt5g0q8C3wz6 szNZULWDegocJlfVvjAXN9zhI7FDV/9IeXZrgCicCTKnhY4pZEP/Gv6Y0+OP4pJWEVUO pNDsL5/8AWzXMyHdeliaQ/kbdeYLvoDyANSrWXc1ywwJnhhI5NkT2B7fOlaW2MvwdSEO jRctI25FUqO20pKOg2Q6ewbHPkVptHJ3ooZGCzCjQ/4Yj9Ftf8On/gAAqbtSbYo6y82O uhMklRZ3akhynBo5sZ2DxovSeZpUr/U2CJQO779ajQVURJDEzCGIyw1x6/JFDRBoamki oeXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699268288; x=1699873088; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=SFC8JPcwRyT+yiqmht50Lm+KMf9EZExJfqdnTQEUOPY=; b=QK96MB52LikGR2eXtofaUDorZGDosDz8PeUtUIfFJr4cydyTORSbS/hX93bKT7bR6J bMakzAuzT2fc4bYNUfKHkmQppLPoZIuaGHkEDZHXvYq/O6/kOEcy/szXLdG32vMLqEfL jVDJAl+5FumfpEOPwRuw/yghXx/uBe4AGseJ4S1fLE4KoZElVLZNe3lq9PW9MG67jBuv QlzaBBCmJjdhSIWnR1gsUZ7uP14BSDtE4UGY1MWIPne5q5kpAXrZ1z7P76+6bFdVyzed yRVqZ0/aNef87YA1is4s5aQVU2Jyyvr+E3IQrSWpHPFZQ0dNfzpXkf7rvu4P/nljYZqY Zf4w==
X-Gm-Message-State: AOJu0YyNam1j5myhVlnBuZt0P5h9W73Aw21a+MGkbQJ5mzmChyWBeg9e PGnh+8bYooeZekYYGmG/N5vw/dkst32YYmeyh0E=
X-Google-Smtp-Source: AGHT+IFuXXJ8wCxczw2hQNx3ATorCh4Mz3m7nkHMf4UB0mNkRtXjhNpldzBv3Wz4WklyBrdC3fQQYqL4urjOjVZUlds=
X-Received: by 2002:a17:907:7b87:b0:9bf:80f0:7813 with SMTP id ne7-20020a1709077b8700b009bf80f07813mr13830393ejc.16.1699268288385; Mon, 06 Nov 2023 02:58:08 -0800 (PST)
MIME-Version: 1.0
References: <CAOW+2duMfhVVpLbDsrEPMOSJiBZxWs2do7j_68gjTJecGGMzAw@mail.gmail.com> <CA+ag07aoiDGFobZ6vt8T-vrDwrg3Pj+m_A8R8P0tdkVHhddaHA@mail.gmail.com> <6F036C77-7D85-4CCF-9A38-7D719B183143@pi.pe>
In-Reply-To: <6F036C77-7D85-4CCF-9A38-7D719B183143@pi.pe>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Date: Mon, 06 Nov 2023 11:57:58 +0100
Message-ID: <CA+ag07aEqyi20wpEK8UfLU_rDidugLqx-uzL3nRZte3w9cjTwQ@mail.gmail.com>
To: Tim Panton <tim@pi.pe>
Cc: Bernard Aboba <bernard.aboba@gmail.com>, tsv-art@ietf.org, wish@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b533c0060979ba38"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wish/yJycJop01VTozvjtDbCXTaE1aCc>
Subject: Re: [Wish] IETF LC Review of draft-ietf-wish-whip-09
X-BeenThere: wish@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 06 Nov 2023 10:58:14 -0000

Even the remb draft is expired and archived:
https://datatracker.ietf.org/doc/html/draft-alvestrand-rmcat-remb-03

I am all for having implementers guidelines, but not sure if these are in
the scope of an IETF spec or should be just handle them in hackathons and
such..



On Mon, Nov 6, 2023 at 11:48 AM Tim Panton <tim@pi.pe> wrote:

> I agree that cc is an issue - I don’t think it is possible to specify
> exactly what WHIP _must_ do.
> However I do think there is scope for implementation advice somewhere.
>
> One thing to note is that in most WHIP scenarios REMB will be sufficient
> and it is somewhat documented….
>
> An implementation advisory document might also want to discuss the optimal
> keyframe interval.
>
> Or perhaps this is all out of scope for WHIP/IETF and caveat emptor for
> the implementors...
>
> T.
>
> On 6 Nov 2023, at 10:26, Sergio Garcia Murillo <
> sergio.garcia.murillo@gmail.com> wrote:
>
> Hi Bernard, sorry for the late review
>
> I agree with your feedback regarding the importance of congestion control
> to ensure the best quality of ingest session (probably more important for
> UGC than for professional grade studios though).
>
> I am not sure what we could do in order to improve it, as as you suggest
> it is mostly an implementation issue and not a spec one. The consensus
> until now was not to provide implementation guidelines in the spec itself
> and only clarify potential misuses/confusions that could happen during
> implementation. Moreover, the group is not charter to work on the CC algos
> themselves, so we would have to point to work either on RMCAT or RTCWEB (or
> even MoQ).
>
> To make things more complicated, the defacto implementation (twcc and gcc)
> is not specified at all, so I am concerned that we could even provide any
> actual guidance within the spec.
>
> Any idea about how we could progress this? Maybe it is something we can
> discuss during tomorrow's meeting?
>
> Best regards
> Sergio
>
>
> On Wed, Jul 26, 2023 at 3:33 AM Bernard Aboba <bernard.aboba@gmail.com>
> wrote:
>
>> is here:
>>
>> https://datatracker.ietf.org/doc/review-ietf-wish-whip-09-tsvart-lc-aboba-2023-07-25/
>>
>> Datatracker has been unstable today so no emails appear to have been
>> sent.
>> --
>> Wish mailing list
>> Wish@ietf.org
>> https://www.ietf.org/mailman/listinfo/wish
>>
> --
> Wish mailing list
> Wish@ietf.org
> https://www.ietf.org/mailman/listinfo/wish
>
>
>

v2.23.0 | Report a Bug | By Email