Re: [MMUSIC] DECISION: Usage of same PT value in multiple m- lines for SAME codec configuration

"Roni Even" <ron.even.tlv@gmail.com> Sat, 29 June 2013 10:50 UTC

Return-Path: <ron.even.tlv@gmail.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 4888321F9F21 for <mmusic@ietfa.amsl.com>; Sat, 29 Jun 2013 03:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[AWL=1.100, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 oBEA39j72Kt9 for <mmusic@ietfa.amsl.com>; Sat, 29 Jun 2013 03:50:24 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) by ietfa.amsl.com (Postfix) with ESMTP id D050821F9930 for <mmusic@ietf.org>; Sat, 29 Jun 2013 03:50:20 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id k10so1601837wiv.11 for <mmusic@ietf.org>; Sat, 29 Jun 2013 03:50:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=Pa6Yi+GoTY/FLta0S0ZNUURtxuSZgNrRKuDJ3cAeMOM=; b=lCbl/YPPfA1x47DhXvOg0LC/dLq5WjoEuXhfOToJ5eCNh8ym20qHB4xnow99XD18OF Z00NtqOmj1Kc0zWEZEjREuPF/8sIV8MIpqpFCY32oBwDagy4/PMCNFNy+X9qI91uAvtm 0v64o0/oIjRmji6TEJArwYztAIy8bOmoU9KAUJ7XGp8DmBfSqQpajzGMQKP/oFqYxxin VBAEUhlloro307/vs6EoVf+c5RhEpgW/Xq2BsLhkO3xd2jiDWgnkShn79iUS1picW2sO Og8bx6p+wkZ1vOTij1YXE75aBpUsh3dGH6B2OEkO8nWiV5oOhJBv7JCGj/2AgYRqwbBY +4NQ==
X-Received: by 10.180.21.147 with SMTP id v19mr5854102wie.25.1372503019593; Sat, 29 Jun 2013 03:50:19 -0700 (PDT)
Received: from RoniE ([109.67.165.48]) by mx.google.com with ESMTPSA id fb2sm3232753wic.4.2013.06.29.03.50.17 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 29 Jun 2013 03:50:19 -0700 (PDT)
From: Roni Even <ron.even.tlv@gmail.com>
To: 'Christer Holmberg' <christer.holmberg@ericsson.com>, mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C3BE558@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C3BE558@ESESSMB209.ericsson.se>
Date: Sat, 29 Jun 2013 13:48:52 +0300
Message-ID: <043b01ce74b6$4059cd20$c10d6760$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_043C_01CE74CF.65A7A160"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHh/gpGsmWjhOKpyEWXgP0lggNVQZklb1Bg
Content-Language: en-us
Subject: Re: [MMUSIC] DECISION: Usage of same PT value in multiple m- lines for SAME codec configuration
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: Sat, 29 Jun 2013 10:50:25 -0000

Hi,

Jonathan Lennox, Qin and I submitted a draft about mapping the PT from the
SDP m-line to the application semantics.

It allows for having the same PT numbers in different m-lines since each
m-line will have different application IDs that can be used to map to an
SSRC using RTCP SDES or RTP header extension.

Roni

 

From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of
Christer Holmberg
Sent: 28 June, 2013 2:25 PM
To: mmusic@ietf.org
Subject: [MMUSIC] DECISION: Usage of same PT value in multiple m- lines for
SAME codec configuration

 

Hi,

 

In Q1, I asked whether we can agree that a PT value can only be used for a
single codec configuration. Eventhough the question is still open, the
feedback received so far seem to indicate that people agree to that.

 

We have also discussed whether it should, within a BUNDLE group, be allowed
to use the same PT value in multiple m- lines - if used for the same codec
configuration. I will now put forward a question on that :)

 

 

Q7: Within a BUNDLE group, do we allow the usage of the same PT value in
multiple RTP m- lines, for the SAME codec configuration?

 

Note: This of course prevents the mapping to m- line purely based on PT, and
based on the outcome of that discussion we may have to add restrictions on
when the same PT value can be used etc. But, this question is whether we
generally want to allow the usage of the same PT value in multiple m- lines
:)

 

Regards,

 

Christer