Re: [MMUSIC] [Technical Errata Reported] RFC5576 (7544)

Philipp Hancke <philipp.hancke@googlemail.com> Fri, 23 June 2023 11:28 UTC

Return-Path: <philipp.hancke@googlemail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33305C1595FD for <mmusic@ietfa.amsl.com>; Fri, 23 Jun 2023 04:28:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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=googlemail.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 hyRRW2ob0c1c for <mmusic@ietfa.amsl.com>; Fri, 23 Jun 2023 04:28:31 -0700 (PDT)
Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) (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 06F10C151710 for <mmusic@ietf.org>; Fri, 23 Jun 2023 04:28:30 -0700 (PDT)
Received: by mail-wm1-x335.google.com with SMTP id 5b1f17b1804b1-3f8fe9dc27aso5914485e9.3 for <mmusic@ietf.org>; Fri, 23 Jun 2023 04:28:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20221208; t=1687519709; x=1690111709; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=EAyD6v7UbBDaM/R7mJWaKU7EH9SMDnorAJvBx4Sew1g=; b=k3ibTmrXPfB9jsJSAkNoXuwLrpynzaGP9cNrEtDrIxA8+XvRBBEZhbSXgJxSZViY3u ifRKSIgNxDoKF7P0n73icbNFSH0rmlH6vFu62/Xgv0tsoutW0kPH9BWVlje6aIiPBx/Q rWq3VZlUhRnTuxmhZrzUtqKDAbML0MKfDQ3A4YfjTK0y921mTi6Jisc8mmLE1iH7I57m 9gpVKsXj5k2qbxdgp8W88+oBWNxJckorsxEhApegDL/k47FxD+mHP6OQwf0FIJEi/vSe Oh/AMuaK5hisfHYNoG5fXyWP2ofjRIqK/ytgW5ealDnmegPPwcE0neeC9GFp4zUafN34 MVdQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687519709; x=1690111709; h=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=EAyD6v7UbBDaM/R7mJWaKU7EH9SMDnorAJvBx4Sew1g=; b=PBE8wVfUsRunm7hJ7E+OaSwIHD9J/7IdwoIxGl01RrUeFurZ40dTMZYlGVEvin5GVQ bEffFV0ZYZ1qYgzGZlNMhibXYLHAG19D6S7iuQFTqC4ywh5FReYXKqMxjMLk5U+0rgFj hCuXJ97xzVH6HZNvXsMc0EwyJva6rakqJYnriIqsTjr6s7Qx1buhUarivszwkUMNjYb/ IPKVnexbYUtMGrJ33Usi2/B+3gQadq9qlr9Gyy7qy0WWXdg9BEGJXV48lJ5YVFzd8WDA 1gH0xgECCR8gTW1TxH3CI2Wkt9S3Kv1qv6CVm0Xr4Qlr50mnPSoiu0syumIkk0/lDokc tr9A==
X-Gm-Message-State: AC+VfDyQV8AeS/dNtyoCXHtnTX4va7eev04IqA30s43nyclBLlXQH4j1 OxE4UmjT/OkiriGBnnBXWeTsgy/b5bktGmcG3620EMh3
X-Google-Smtp-Source: ACHHUZ4GVn+KEkHi/ol2lqsf9bTFtQgOld/EpSI71m3t5svbC2kIteA2vLW3JTfk3uKV12HqVWh/JAHh2wQToB5dqvY=
X-Received: by 2002:a05:600c:a389:b0:3f8:fed0:1c52 with SMTP id hn9-20020a05600ca38900b003f8fed01c52mr13591681wmb.2.1687519709210; Fri, 23 Jun 2023 04:28:29 -0700 (PDT)
MIME-Version: 1.0
References: <6d597607-fb07-a637-d6c3-a6084186e4e0@alvestrand.no> <2015efd9-78f5-4fc7-f889-fa44f95fdfa9@alvestrand.no>
In-Reply-To: <2015efd9-78f5-4fc7-f889-fa44f95fdfa9@alvestrand.no>
From: Philipp Hancke <philipp.hancke@googlemail.com>
Date: Fri, 23 Jun 2023 13:28:18 +0200
Message-ID: <CADxkKiLZG2ipczF+vzv_DXfjLf6pYdFqM76HfoBefQt2ewQPXA@mail.gmail.com>
To: mmusic@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d1afad05feca4c09"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3wSclgvFke-qLIGqhMrHBwG9_iQ>
Subject: Re: [MMUSIC] [Technical Errata Reported] RFC5576 (7544)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jun 2023 11:28:35 -0000

>
> On 6/20/23 11:43, Christer Holmberg wrote:
>
> I am not sure I understand your comment, nor the comment from Philipp.
> They seem to be related to some implementation, because I have no idea
> what you refer to when you say "members", "set", "count" and "field"
> :)
>
> Are there implementations that add multiple instance of the same
> ssrc-id value to the sscr-group attribute?
>
> There was one implementation that crashed when someone sent it an
> ssrc-group
> with multiple occurences of the same SSRC, yes. Whether this was an attack
> or a mistake, I don't know.
>
> It would be nice to know WHY it was sent. Perhaps they think it is a valid
> case, which may also have to be dealt with.
>
> I came up with the idea of trying "what happens if" while debugging
unrelated SRTP issues where "is this trying to send RTX on the wrong SSRC"
was the hypothesis.

I do not think it is being used in production, in particular since for FID
https://www.rfc-editor.org/rfc/rfc4588#section-4
already says
   two different SSRC values MUST be used for the original stream and the
retransmission stream
I don't see the same explicit text in RFC 5956 (for FEC-FR) sadly.
cheers

Philipp
(with better quoting hopefully)