[AVTCORE] BUNDLE: a single stream with multiple MIDs?

Jonathan Lennox <jonathan@vidyo.com> Thu, 07 July 2016 22:36 UTC

Return-Path: <prvs=1996aa63cb=jonathan@vidyo.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E436F12D5C9; Thu, 7 Jul 2016 15:36:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.831
X-Spam-Level:
X-Spam-Status: No, score=-1.831 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=0.77, 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 gWLQoPTDa-bt; Thu, 7 Jul 2016 15:36:42 -0700 (PDT)
Received: from mx0a-00198e01.pphosted.com (mx0a-00198e01.pphosted.com [67.231.149.202]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60367127071; Thu, 7 Jul 2016 15:36:42 -0700 (PDT)
Received: from pps.filterd (m0073109.ppops.net [127.0.0.1]) by mx0a-00198e01.pphosted.com (8.15.0.59/8.15.0.59) with SMTP id u67MaOTq005126; Thu, 7 Jul 2016 18:36:42 -0400
Received: from mail.vidyo.com ([162.209.16.214]) by mx0a-00198e01.pphosted.com with ESMTP id 241vjvr43g-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 07 Jul 2016 18:36:42 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Thu, 7 Jul 2016 17:36:41 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: IETF AVTCore WG <avt@ietf.org>, mmusic <mmusic@ietf.org>
Thread-Topic: BUNDLE: a single stream with multiple MIDs?
Thread-Index: AQHR2KAHze27W5Jfo0ybRgYSx8aBWQ==
Date: Thu, 07 Jul 2016 22:36:40 +0000
Message-ID: <6C642BD1-679B-4CCA-9148-DD4A7ACB48A4@vidyo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [160.79.219.114]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1194365E18A71641BBCC242A8BF1DA5C@vidyo.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.96, 1.0.3, 0.0.0000 definitions=2016-07-07_12:2016-07-07,2016-07-07,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1603290000 definitions=main-1607070214
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/oxcrZzCs29Y-8c_IwvlLNnlUH4U>
Subject: [AVTCORE] BUNDLE: a single stream with multiple MIDs?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2016 22:36:44 -0000

Hi, all —

(This was an issue I raised in AVTCORE in Buenos Aires — I promised to send e-mail to the list but hadn’t remembered to get around to it until now.)

When finishing up the CLUE RTP mapping draft, I realized that one of CLUE’s RTP requirements didn’t actually end up getting satisfied by BUNDLE (which is the solution CLUE converged on).  This isn’t a CLUE-specific issue, so I’m raising it here.

The issue is whether we want to support a use case, in BUNDLE, where a single RTP stream corresponds to more than media description (and thus has more than one MID value)?

The use case is where one m-line has a semantic of “always view this person” (my boss, say, or my customer); and another m-line has a semantic of “the current loudest speaker”. (In CLUE, these would be a single content capture in the former case, and a switched capture for the latter.)  Whenever the boss *is* the current loudest speaker, the same content would be sent for both m-lines.

A naive implementation would simply duplicate all the packets for the two m-lines, with different MID values, but this has two problems.  First off all, it obviously wastes bandwidth.  Potentially more seriously, it precludes any RTP middlebox topology which doesn’t rewrite SSRC values, since the same content (arriving with a single SSRC value at the middlebox) would need to be sent with two different SSRC values down from the middlebox.  If PERC goes with its current consensus of no SSRC rewriting, this will particularly be a problem for PERC.

I certainly don’t think this is something that should block BUNDLE’s completion, but I think it could be a pretty easy extension.  

(My initial design proposal was to allow multiple SDES values of the same type, and multiple SDES header extensions items of the same type, to be sent simultaneously in RTP — protocol-syntactically this is trivial, you’d just need to negotiate that you support it.  But I’m not wedded to this solution.)

What do people think — is this worth working on?  Is there interest in discussing it in Berlin, and if so, in what venue?