Re: [MMUSIC] RFC 5576 is da answah

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 22 November 2012 09:31 UTC

Return-Path: <christer.holmberg@ericsson.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 2509821F8839 for <mmusic@ietfa.amsl.com>; Thu, 22 Nov 2012 01:31:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.704
X-Spam-Level:
X-Spam-Status: No, score=-5.704 tagged_above=-999 required=5 tests=[AWL=-0.056, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fjftgSNdAFHM for <mmusic@ietfa.amsl.com>; Thu, 22 Nov 2012 01:31:35 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id BA88321F883A for <mmusic@ietf.org>; Thu, 22 Nov 2012 01:31:34 -0800 (PST)
X-AuditID: c1b4fb30-b7f936d0000018b3-4d-50adf0f5726e
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 15.6D.06323.5F0FDA05; Thu, 22 Nov 2012 10:31:33 +0100 (CET)
Received: from ESESSHC020.ericsson.se (153.88.183.78) by esessmw0237.eemea.ericsson.se (153.88.115.90) with Microsoft SMTP Server (TLS) id 8.3.279.1; Thu, 22 Nov 2012 10:31:32 +0100
Received: from ESESSMB209.ericsson.se ([169.254.9.119]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.02.0318.001; Thu, 22 Nov 2012 10:31:32 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] RFC 5576 is da answah
Thread-Index: AQHNx4I7LDBSKk491E6gDy7Y6A3iQpf1l09w
Date: Thu, 22 Nov 2012 09:31:31 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B0420E9@ESESSMB209.ericsson.se>
References: <BLU002-W21780C8EDF047E1811F270D93540@phx.gbl>
In-Reply-To: <BLU002-W21780C8EDF047E1811F270D93540@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B0420E9ESESSMB209ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyM+Jvje7XD2sDDK6+k7fYv+Qys8XU5Y9Z HJg8HvecYfNYsuQnUwBTFJdNSmpOZllqkb5dAlfGnlOfmAuanCruN35hbmBcZ9XFyMkhIWAi cfrcBSYIW0ziwr31bCC2kMBJRonZ7VFdjFxA9k5GibXHF7FAJJYwSixcqdvFyMHBJmAh0f1P GyQsIhAiMWfFXrA5wgLaEjO+fmMFKRER0JE4My0XosRI4teMo8wgYRYBVYmtjSkgYV4Bb4lV 046yQwy3kvh2/C0ziM0pYC2xsucvI4jNCHTZ91NrwKYzC4hL3HoyH+piAYkle84zQ9iiEi8f /2OFsBUldp5tZ4aoz5eYf+MKG8QuQYmTM59APaIt0bJ4AvsERrFZSMbOQtIyC0kLRFxHYsHu T2wQtrbEsoWvmWHsMwceMyGLL2BkX8XInpuYmZNebr6JERhlB7f8NtjBuOm+2CFGaQ4WJXFe PdX9/kIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoY2RbV/doZK/dKI2NXnub/RWIi+zrnVpxc kruV/fqVbSVVe15l8C//zyQVHjI/d39LfYbW9CXZU1e7GiUIifWmMD68lrIohYn3/IPPfe2F 3VZp7RlM8gGS8y228yeLZ83ea7a0fdJfvwuqpfUTfhdP+jLltGx7xuXEPQxOhw7wx3IVdmpY C99UYinOSDTUYi4qTgQAHit6UIACAAA=
Subject: Re: [MMUSIC] RFC 5576 is da answah
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 22 Nov 2012 09:31:37 -0000

Hi,

>From Section 8:
>
>   When used with the SDP Offer/Answer Model [RFC3264], SDP source-
>   specific attributes describe only the sources that each party is
>   willing to send (whether it is sending RTP data or RTCP report
>   blocks).  No mechanism is provided by which an answer can accept or
>   reject individual sources within a media stream; if the set of
>   sources in a media stream is unacceptable, the answerer's only option
>   is to reject the media stream or the entire multimedia session.
>
> [BA] The advice above appears to only apply to an answerer that supports RFC 5576.  If it doesn't support RFC 5576, then it
> will presumably ignore the a=ssrc lines, but may not reject the media stream (by setting the port to zero) or the entire session.
> In this case, it may not be clear to the Offerer whether in fact it can send all the declared ssrc's or not.  Contrast this with the
> CLUE approach in which receiver gets to indicate what media captures it would like to receive.

In CLUE we have a requirement to be able to communicate with "non-CLUE" and "single stream" devices, so also there we may have to deal with the case where an endpoint doesn't support CLUE and/or RFC 5576.

Also keep in mind that, eventhough max-ssrc allows you to specify the number of streams, it is currently not a mechanism to indicate WHICH streams are accepted/rejected.

Regards,

Christer