Re: [MMUSIC] BUNDLE TEXT: De-mux procedures (June 19th)

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 20 June 2013 05:11 UTC

Return-Path: <prvs=88837ccfb6=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 3430F21F9E04 for <mmusic@ietfa.amsl.com>; Wed, 19 Jun 2013 22:11:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.857
X-Spam-Level:
X-Spam-Status: No, score=-5.857 tagged_above=-999 required=5 tests=[AWL=0.392, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZ6ZovaGUDMp for <mmusic@ietfa.amsl.com>; Wed, 19 Jun 2013 22:11:34 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 7DDFD21F9DFA for <mmusic@ietf.org>; Wed, 19 Jun 2013 22:11:33 -0700 (PDT)
X-AuditID: c1b4fb30-b7f9e6d000002643-a9-51c28f047f2a
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 32.F8.09795.40F82C15; Thu, 20 Jun 2013 07:11:32 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.6]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.02.0328.009; Thu, 20 Jun 2013 07:11:32 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] BUNDLE TEXT: De-mux procedures (June 19th)
Thread-Index: Ac5s4y9zPDdk8vnuSOSyMPT24r/CS///6fSA///dtTCAACcFAIAADdaA///cleCAAC1bgIAAPlNg///oowD//9xlEP//0iKA//97moD//jZq4A==
Date: Thu, 20 Jun 2013 05:11:32 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3B1A7F@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C3AFDB7@ESESSMB209.ericsson.se>, <51C1A4A3.6070105@alvestrand.no>, <7594FB04B1934943A5C02806D1A2204B1C3AFEA1@ESESSMB209.ericsson.se>, <51C1A89A.9020603@alvestrand.no>, <BLU169-W56DEA51EC84C8180A7DCD5938D0@phx.gbl>, <7594FB04B1934943A5C02806D1A2204B1C3B0B60@ESESSMB209.ericsson.se>, <BLU169-W1288AEADA7A090C209F376C938D0@phx.gbl> <7594FB04B1934943A5C02806D1A2204B1C3B0EF1@ESESSMB209.ericsson.se> <51C1DD3A.8030705@alvestrand.no> <7594FB04B1934943A5C02806D1A2204B1C3B1392@ESESSMB209.ericsson.se> <51C1E5D5.9020009@jitsi.org> <51C207F1.1010102@alum.mit.edu>
In-Reply-To: <51C207F1.1010102@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrGLMWRmVeSWpSXmKPExsUyM+JvrS5L/6FAg94tWhZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxW2TlFhSFpyZnqdvl8CdcXDeMqaCO4IVJ+cuYmtg/MrbxcjJISFg ItF0dg0bhC0mceHeeiCbi0NI4DCjxPcZj6GcRYwSdw+1MXYxcnCwCVhIdP/TBmkQEfCVePb4 NlizsICDxL3fsxgh4o4SzUveskDYdRL9M3eA2SwCqhIN8zexg9i8QL37Wx8zQ8x/wyKxefJC sCJOAR2JRY8Pgg1lBLro+6k1TCA2s4C4xK0n85kgLhWQWLLnPDOELSrx8vE/VpDbJAQUJZb3 y0GU60gs2P2JDcLWlli28DUzxF5BiZMzn7BMYBSdhWTqLCQts5C0zELSsoCRZRUje25iZk56 ufkmRmA0HNzy22AH46b7YocYpTlYlMR5P53aFSgkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDE0Rw STUwHlyQe6ur8FJ+1/Ka5UYv7rIuN5+m9/WYRfj9rSzf33vlzPld8da7IzK+S2aJ9O35r1X1 Yy1vTijrDZaTalGdtbrEpuf64ilx5o/XHtq+Wsf16d+rkdqfbwrVs7KfqJrzZVkLO3fqcvWT Vv2Lt7Bff6t9OL/llKP9z2caz6dyHEtkFXsnkqv7UomlOCPRUIu5qDgRADGqUVZZAgAA
Subject: Re: [MMUSIC] BUNDLE TEXT: De-mux procedures (June 19th)
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, 20 Jun 2013 05:11:40 -0000

Hi,

>> *IF* you have a way to find the right m= line, couldn't PT X have 
>> different codec configurations in different m= lines?
>
> Yes, I think so.

RTP seems to forbid it, though.

>> Let's assume that it could ... but then how would you know that your 
>> peer also supports the same demuxing technique as yourself?
>
> Muxing/demuxing (in the sense of associating to a particular m-line) MUST be consistent on both ends. (The sender knows which m-line he associates a packet with, and expects that the receiver will make the same association.)
>
> There must be enough signaling to get the two sides in sync about this.

When it comes to PT values, each endpoint decides which PT values it wants to other endpoint to send.

So, even if Alice uses the same PT value in multiple "m=" lines, and have some way to find the "m=" line when media is received, Bob can still assign unique PT values in each "m=" line.

I don't think there is a requirement to have symmetric PT values in both directions, eventhough I know implementations often do that.


>> In SIP for example, when constructing a first offer, you may want to 
>> map both Opus and VP8 to 96, then add SSRCs for demuxing. This means 
>> that you expect your peer to support SSRC demuxing and you can't 
>> expect that unless we mandate it.
>
> In this case there will be two m-lines, one audio and one video, each using PT 96. And the offer specifies a specific ssrc for each m-line.
>
> If the answerer does't understand or support muxing by ssrc it will then note that if it accepted both m-lines it would not be able to associate packets with m-lines. So it then has two choices in constructing its answer:
>
> - reject the bundle, but accept both m-lines
> - accept the bundle, but reject one of the m-lines.

Again, my understanding is that the Offerer indicates which PT values it wants to RECEIVE. So, it it assigns the same PT value to both audio and video, it will receive the same PT value in the media packets.

But, the Answerer can indicate different PT values for audio and video in the SDP Answer, and it will receive different PT values in the media packets.

Regards,

Christer