Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?

Colin Perkins <csp@csperkins.org> Mon, 03 March 2014 10:20 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 376501A0E3F for <mmusic@ietfa.amsl.com>; Mon, 3 Mar 2014 02:20:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham
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 RPUmNUVOZ3Fa for <mmusic@ietfa.amsl.com>; Mon, 3 Mar 2014 02:20:44 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) by ietfa.amsl.com (Postfix) with ESMTP id B99851A0DF3 for <mmusic@ietf.org>; Mon, 3 Mar 2014 02:20:43 -0800 (PST)
Received: from [31.133.156.67] (port=58834 helo=dhcp-9c43.meeting.ietf.org) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1WKPzC-0002E1-Mz; Mon, 03 Mar 2014 10:20:39 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_2B6F36F9-0E08-4E2B-B047-D8BC75700947"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se>
Date: Mon, 03 Mar 2014 10:20:36 +0000
Message-Id: <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1874)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/rCky2bL6MZ8uFY9T7FY2LcvB3hM
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 03 Mar 2014 10:20:46 -0000

Hi,

I did suggest a definition of “codec configuration” in my message. If that’s not acceptable, then I suggest forbidding payload number reuse across m= lines.

Colin



On 3 Mar 2014, at 10:08, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
> Hi Colin,
>  
> We tried to define “codec configuration”, but we never got text that people could agree to.
>  
> Personally I don’t have any strong opinion which way we go (personally I am also ok forbidding re-usage of the same PT value). I just want to close the issue, and not once again “take it to the list”.
>  
> Regards,
>  
> Christer
>  
> From: Colin Perkins [mailto:csp@csperkins.org] 
> Sent: 03 March 2014 11:34
> To: Christer Holmberg
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
>  
> Christer,
>  
> The bundled m= lines form a single RTP session. That means that they share a single RTP payload number space. The rule therefore has to be that you can only reuse the payload type across bundled m= lines if it refers to the exact same configuration of the exact same codec in all cases, where “exact same configuration” means that the a=fmtp: line and all other SDP attributes that configure the codec and packetisation of the media are identical.
>  
> If that’s not specific enough, then MUST NOT reuse payload types across m= lines in a bundled group is the safe choice. I believe your propose that it’s okay if you can handle the media is too vague, and will cause us problems down the line.
>  
> Colin
>  
>  
>  
>  
> On 2 Mar 2014, at 08:44, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
> Hi,
>  
> One of the open issues we have in BUNDLE, is when it is allowed to use the same PT value within multiple m- lines.
>  
> We tried to come up with different criteria, including a “codec configuration” concept, but we never managed to agree on something.
>  
> So, in London, I intend to suggest that we simply say: if you offer the same PT value within multiple m- line, make sure you can handle the associated media when it arrives – period (keep in mind that you always indicate what you want to RECEIVE – the remote peer can still ask you to SEND using different PT values).
>  
> If you don’t like this, please provide an alternative solution, because I want to close this issue in London. There is no idea to keep “taking the issue back to the list”. We’ve done that for a few meetings already.
>  
> Regards,
>  
> Christer
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>  
>  
> 
> -- 
> Colin Perkins
> http://csperkins.org/
>  
>  
>  



-- 
Colin Perkins
http://csperkins.org/