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

Joerg Ott <ott@in.tum.de> Fri, 16 June 2023 11:54 UTC

Return-Path: <ott@in.tum.de>
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 66D95C151076 for <mmusic@ietfa.amsl.com>; Fri, 16 Jun 2023 04:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.997
X-Spam-Level:
X-Spam-Status: No, score=-6.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=in.tum.de
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 rmfZKA7oKSzy for <mmusic@ietfa.amsl.com>; Fri, 16 Jun 2023 04:54:34 -0700 (PDT)
Received: from mailout1.rbg.tum.de (mailout1.rbg.tum.de [IPv6:2a09:80c0::201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 7EBC1C151B27 for <mmusic@ietf.org>; Fri, 16 Jun 2023 04:54:33 -0700 (PDT)
Received: from mailrelay1.rbg.tum.de (mailrelay1.in.tum.de [131.159.254.14]) by mailout1.rbg.tum.de (Postfix) with ESMTPS id 01E9FA6; Fri, 16 Jun 2023 13:54:25 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=in.tum.de; s=20220209; t=1686916465; bh=J03meIqCi4Fg9wHz2Ch25U6k7gd1k1I59D2skTw87cY=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=pZiz85fRxj19Q7vGMnxySs9CqwhLfs0EocdKcvlUoliDIowo6v+ZzSdCIzCQgZLjB 0ZlaXfvx6Gq6CAGOq3la/yfi7nF16rdN/F4TsUgAVQbqYCv4WOI2+MI3AnsQggV6mA DQLefb6fTJfowXS4Tl8UEqXyesceeujqZLl0ogyGBJeHTinH1lTnZPD0dEgPCddVUV oYGCnN0Ek9LxbcU+sMP5DZmkUkuP8YEtqDmTDsOx1TjkUHz3NsM/uoGAgQo9U5mU6N AU6dIBVeY6/UU4E225AmAGcu9fHE7llijK53l43wbMGrY1cKiw/dR0iAkcJWbcl/V1 g9mSvjgG0C4pg==
Received: by mailrelay1.rbg.tum.de (Postfix, from userid 112) id F05F01DC; Fri, 16 Jun 2023 13:54:24 +0200 (CEST)
Received: from mailrelay1.rbg.tum.de (localhost [127.0.0.1]) by mailrelay1.rbg.tum.de (Postfix) with ESMTP id 9DA491DB; Fri, 16 Jun 2023 13:54:24 +0200 (CEST)
Received: from mail.in.tum.de (vmrbg426.in.tum.de [131.159.0.73]) by mailrelay1.rbg.tum.de (Postfix) with ESMTPS id 96CBC1DA; Fri, 16 Jun 2023 13:54:24 +0200 (CEST)
Received: by mail.in.tum.de (Postfix, from userid 112) id 8ED184A034A; Fri, 16 Jun 2023 13:54:24 +0200 (CEST)
Received: (Authenticated sender: ott) by mail.in.tum.de (Postfix) with ESMTPSA id C650F4A02E6; Fri, 16 Jun 2023 13:54:23 +0200 (CEST) (Extended-Queue-bit xtech_bv@fff.in.tum.de)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Joerg Ott <ott@in.tum.de>
Mime-Version: 1.0 (1.0)
Date: Fri, 16 Jun 2023 13:54:12 +0200
Message-Id: <A10783AD-D45C-4542-A334-63EBBE34EAFD@in.tum.de>
References: <HE1PR07MB4441E284AC9058185C6E28A39358A@HE1PR07MB4441.eurprd07.prod.outlook.com>
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, jonathan@vidyo.com, jo@acm.org, ts@thomas-schierl.de, superuser@gmail.com, Francesca Palombini <francesca.palombini@ericsson.com>, Bo Burman <bo.burman@ericsson.com>, fandreas@cisco.com, phancke@microsoft.com, mmusic@ietf.org
In-Reply-To: <HE1PR07MB4441E284AC9058185C6E28A39358A@HE1PR07MB4441.eurprd07.prod.outlook.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: iPad Mail (20F66)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MrasBjEKJWe3iioAZDGny0P_TTo>
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, 16 Jun 2023 11:54:39 -0000

Not sure what the semantics would be. Ultimately, the grouping framework should not try to prescribe the semantics of its interpretation, and one could possibly create a use case where the same ssrc-id might appear multiple times. For the present ones, it doesn’t seem to maske sense.

Not sure that any action is needed.

Jörg

Sent from my iPad

> On 16. Jun 2023, at 09:18, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
> 
> Why would someone use something like a=ssrc-group:FID 1234 1234? And, even if 
> someone does, what error would it cause?
> 
> Also, we don't have similar text for e.g., the SDP group attribute.
> 
> Regards,
> 
> Christer
> 
> 
> -----Original Message-----
> From: mmusic <mmusic-bounces@ietf.org> On Behalf Of RFC Errata System
> Sent: Thursday, 15 June 2023 21.37
> To: jonathan@vidyo.com; jo@acm.org; ts@thomas-schierl.de; superuser@gmail.com; 
> Francesca Palombini <francesca.palombini@ericsson.com>; Bo Burman 
> <bo.burman@ericsson.com>; fandreas@cisco.com
> Cc: phancke@microsoft.com; mmusic@ietf.org; rfc-editor@rfc-editor.org
> Subject: [MMUSIC] [Technical Errata Reported] RFC5576 (7544)
> 
> The following errata report has been submitted for RFC5576, "Source-Specific 
> Media Attributes in the Session Description Protocol (SDP)".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7544
> 
> --------------------------------------
> Type: Technical
> Reported by: Philipp Hancke <phancke@microsoft.com>
> 
> Section: 4.2
> 
> Original Text
> -------------
> Every <ssrc-id> listed in an "ssrc-group" attribute MUST be defined by a 
> corresponding "ssrc:" line in the same media description
> 
> Corrected Text
> --------------
> Every <ssrc-id> listed in an "ssrc-group" attribute MUST be defined by a 
> corresponding "ssrc:" line in the same media description and MUST appear only 
> once in this ssrc-group
> 
> Notes
> -----
> The goal is to clarify that something like
>  a=ssrc-group:FID 1234 1234
> is not valid. While this is demuxable (in the BUNDLE sense) it would require 
> chaining of ssrc-demuxing and payload type demuxing which is a lot of 
> complexity.
> The uniqueness is already implied by the following sentence (emphasis is 
> mine):
>   The SDP media attribute "ssrc-group" expresses a relationship among 
> *several* sources of an RTP session earlier in the section.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please use 
> "Reply All" to discuss whether it should be verified or rejected. When a 
> decision is reached, the verifying party can log in to change the status and 
> edit the report, if necessary.
> 
> --------------------------------------
> RFC5576 (draft-ietf-mmusic-sdp-source-attributes-02)
> --------------------------------------
> Title               : Source-Specific Media Attributes in the Session 
> Description Protocol (SDP)
> Publication Date    : June 2009
> Author(s)           : J. Lennox, J. Ott, T. Schierl
> Category            : PROPOSED STANDARD
> Source              : Multiparty Multimedia Session Control RAI
> Area                : Real-time Applications and Infrastructure
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic