[MMUSIC] Simulcast: Inclusion of the same SCID in multiple Simulcast streams
Magnus Westerlund <magnus.westerlund@ericsson.com> Tue, 01 November 2016 09:46 UTC
Return-Path: <magnus.westerlund@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 9AFAC1294F3; Tue, 1 Nov 2016 02:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 J_rAy9yeHJp9; Tue, 1 Nov 2016 02:46:15 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E46D1294C7; Tue, 1 Nov 2016 02:46:14 -0700 (PDT)
X-AuditID: c1b4fb25-93fff70000001e3e-36-58186464b6de
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by (Symantec Mail Security) with SMTP id AD.02.07742.56468185; Tue, 1 Nov 2016 10:46:13 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.26) with Microsoft SMTP Server id 14.3.319.2; Tue, 1 Nov 2016 10:46:12 +0100
To: "mmusic (E-mail)" <mmusic@ietf.org>, "draft-ietf-mmusic-sdp-simulcast@ietf.org" <draft-ietf-mmusic-sdp-simulcast@ietf.org>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <5bc8bd40-7c70-f1f0-a209-1ef09c93165f@ericsson.com>
Date: Tue, 01 Nov 2016 10:46:10 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupmluLIzCtJLcpLzFFi42KZGbFdQjc1RSLC4PonBYvns16wWExd/pjF gcljyZKfTAGMUVw2Kak5mWWpRfp2CVwZJ04sZC14LF9xb+IKxgbGW5JdjJwcEgImEk8nzWfu YuTiEBJYxyjR8usGK4SzjFHi7LfvjCCOiEATo8TkjcuYQFrYBCwkbv5oZAOxhQV8JH5u/AUW 5xWwlzg27SALiM0ioCJx+8YBsLioQIzE9WeP2CBqBCVOznwCVMPBwQxU/2BrGUiYWUBeonnr bGYQW0hAW6KhqYN1AiPvLCQdsxA6ZiHpWMDIvIpRtDi1OCk33chYL7UoM7m4OD9PLy+1ZBMj MIgObvmtuoPx8hvHQ4wCHIxKPLwFMeIRQqyJZcWVuYcYJTiYlUR4y5MkIoR4UxIrq1KL8uOL SnNSiw8xSnOwKInzmq28Hy4kkJ5YkpqdmlqQWgSTZeLglGpgdC3wqIt6HaZ/R+J2zc5g0zcn 5n96oLjWXNnDLXgW25ue6YopQi4Ox+q4uzaVK8st/XLt0LnVxhcD187+LRQrtP+pSOyu81fC fu28vnlbS1np8zmfaj/5pMvN57p5XP7kivMSaYfX7d/TI26exx62I+Cv0/z2bftuZ5sum7Hh nV/CuWnTbm80vaDEUpyRaKjFXFScCACkuzYUHgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ranGof7L1daWuJIoWe_EVfcV44Y>
Subject: [MMUSIC] Simulcast: Inclusion of the same SCID in multiple Simulcast streams
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 01 Nov 2016 09:46:16 -0000
WG, During the reviews of the edits yesterday I did find one more issue that should be resolved to avoid interoperability issues. There is currently no text making it explicit if it is allowed to have the same simulcast format (and thus SCID) appear in multiple simulcast streams. I believe that unless we either explicit allow this or explicitly disallow it implementations will make different interpretations and thus we end up with interoperability issues. So the reason Bo and I didn't conclude yesterday that this is a bad idea and we should just explicitly disallow it because it would simplify things are two reasons. The first is that as we have attempted to create the best possibilities for future extensions, e.g. for multicast or at least spread one media source over multiple RTP sessions. Thus, forbidding things can cause issues for the ones defining such extensions, unless we see it necessary to ensure the base mechanism working. Secondly, there are actually usage benefits for allowing a format to be included in multiple simulcast streams. A not unusual way to consider simulcast streams is that they fulfill a purpose in the application. For example one simulcast is the video suitable to present the current speaker in a better fidelity version with higher resolution. One may also have a simulcast stream suitable for the recent speakers that is an intermediate format between high resolution and low resolution thumbnails. In such a case the simulcast stream for the high resolution could include a least preferred simulcast format (SCID=Y) of a rather low resolution version (for being the high resolution) as the last fallback for this streams purpose. At the same time the intermediate simulcast stream could include the same format SCID=Y as suitable format for this medium resolution usage, possible with a much higher preference as it would provide good quality for this streams purpose. So by including the same format in two streams, in situation where the media sender becomes resource restrained, for example in bandwidth, the media source sender could make the decision that the best way of providing both the high and intermediate simulcast streams are to select to send a single RTP stream according to SCID=Y that matches both. If one would not allow an SCID to be in multiple simulcast streams, then the likely result in the above case is that one have to turn of the high resolution simulcast stream due to insufficient resources. This may or may not mean that the application logic chooses to use the intermediate stream as stand in for the high, given that the stream fits the restriction of any of the high resolution simulcast stream's formats. So, this example is not particular convincing in regards to why one should allow this, as the application logic and with some care when negotiating the simulcast formats for the different streams still can allow a simulcast using middlebox to utilize the simulcast stream as stand in for another simulcast stream if that one is not available. So, I currently don't have any better example of why one would allow it, but I think it is important that the WG gets to think about this. So please consider if you have usage that would benefit from allowing multiple simulcast streams to include the same format (with the same SCID)? If no good usage arises then I suggest we explicitly disallow it. Please provide your feedback by the end of the IETF meeting (18th of November). Cheers Magnus Westerlund ---------------------------------------------------------------------- Services, Media and Network features, Ericsson Research EAB/TXM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ----------------------------------------------------------------------
- [MMUSIC] Simulcast: Inclusion of the same SCID in… Magnus Westerlund
- Re: [MMUSIC] Simulcast: Inclusion of the same SCI… Adam Roach
- Re: [MMUSIC] Simulcast: Inclusion of the same SCI… Magnus Westerlund
- Re: [MMUSIC] Simulcast: Inclusion of the same SCI… Roni Even
- Re: [MMUSIC] Simulcast: Inclusion of the same SCI… Roni Even
- Re: [MMUSIC] Simulcast: Inclusion of the same SCI… Magnus Westerlund
- Re: [MMUSIC] Simulcast: Inclusion of the same SCI… Adam Roach