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

Emil Ivov <emcho@jitsi.org> Thu, 20 June 2013 11:33 UTC

Return-Path: <emil@sip-communicator.org>
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 9501C21F9BD9 for <mmusic@ietfa.amsl.com>; Thu, 20 Jun 2013 04:33:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
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 BnlNylMnD86h for <mmusic@ietfa.amsl.com>; Thu, 20 Jun 2013 04:33:13 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 833DA21F9BDB for <mmusic@ietf.org>; Thu, 20 Jun 2013 04:33:13 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id z11so6118wgg.5 for <mmusic@ietf.org>; Thu, 20 Jun 2013 04:33:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=xuQ4MQa+T/h0MLeSZa38JnzSCEanSfD62zjS8YOlnYU=; b=QVFsAODe/PDcWigvPUI1a8JRkFQVxVhHuE7G5llSo0PFmML8Qkv+re37swYMXqH3v4 IxPZd5RwCxHWCRsl3jdKhHv12nPKDFcLrGg7QEyeSrZkfUSQcGaxANmEvZnAb2hSxsRR gIxdhVt1zllNz02SpbDwJyf7QmZMekmRQ/DptJUqj+5LGShpAk5TxGJHUO/JPZz5Urtg IGmjjdPwb7HcqySgPFeondRMLfYJT93eZ0m8j3B1bgQg9Gix0/ZpZUB07oMI9Krkz9sq Yhtjf8LVYRNnGFulZ1g8Dx/xor+PfPYNbS3sb+LoXmEUZL06ZxYios0RpgACAMhVzpho F3zQ==
X-Received: by 10.180.102.37 with SMTP id fl5mr14106200wib.52.1371727992640; Thu, 20 Jun 2013 04:33:12 -0700 (PDT)
Received: from camionet.local (shm67-5-88-165-90-188.fbx.proxad.net. [88.165.90.188]) by mx.google.com with ESMTPSA id f8sm15173508wiv.0.2013.06.20.04.33.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Jun 2013 04:33:11 -0700 (PDT)
Message-ID: <51C2E875.6020000@jitsi.org>
Date: Thu, 20 Jun 2013 13:33:09 +0200
From: Emil Ivov <emcho@jitsi.org>
Organization: Jitsi
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
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> <51C203EF.4090404@alvestrand.no> <51C205AA.6000308@jitsi.org> <7594FB04B1934943A5C02806D1A2204B1C3B1A65@ESESSMB209.ericsson.se> <CAPvvaaKGmynXn36+xegxTcD+6qH3RkkDSTYnPaUTqf_rb2VKkg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C3B1E9E@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C3B1E9E@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQk228iS1xVPOSwQlKDa3DXNitRgQGbo066V4mm5RXflYix6OkhMRWcQkEeUnjGMaFmGnj3v
Cc: mmusic <mmusic@ietf.org>
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 11:33:14 -0000

Hey Christer,

On 20.06.13, 10:52, Christer Holmberg wrote:
> Hi,
>
>>>> Well same question then: what would be the downside of only
>>>> allowing that once support for a non-PT demuxing mechanism has > > been confirmed?
>>>
>>> It for sure seems like a feasible solution, in my opinion.
>>>
>>> But, again, at this point I'd like to figure out whether we are going to
>>> specify A rule in BUNDLE to begin with, or whether we trust the
>>> applications to do the right thing :)
>>
>> I was suggesting (here  http://www.ietf.org/mail-archive/web/mmusic/current/msg11569.html ) that we adopt PT demuxing and make it the default
>> and MTI mechanism. Others would of course also be allowed to override it if supported by both sides. This way SIP UAs wouldn't need  to implement
>> five demuxing techniques to maximize their chances of successfully negotiating bundle from the first o/a.
>> Is there any downside to this?
>
> That could be done for RTP, yes.
>
> Keep in mind, though, that the text in BUNDLE is generic. You could also have multiple m= lines for some other transport protocol, and I don't think we want to start specifying solutions for all of them.

Well we'd certainly need RTP demuxing to be discussed somewhere. Given 
that 3264 takes RTP rather "personally", I don't think it would be a bad 
idea to do the same in BUNDLE and at least define one default mechanism 
there.

I agree that BUNDLE is not the right place to define demuxing procedures 
for any possible transport. (One of the main issues being that all 
possible transports have yet to be specified.)

Emil

-- 
https://jitsi.org