[MMUSIC] DECISION (BERLIN-Q1/Q2/Q7): Usage of specific PT value for single codec configuration

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 23 August 2013 10:53 UTC

Return-Path: <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 DC45111E80E7 for <mmusic@ietfa.amsl.com>; Fri, 23 Aug 2013 03:53:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.16
X-Spam-Level:
X-Spam-Status: No, score=-4.16 tagged_above=-999 required=5 tests=[AWL=-1.562, 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 UfGwmNSkYkOm for <mmusic@ietfa.amsl.com>; Fri, 23 Aug 2013 03:53:00 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id A363A21F9C70 for <mmusic@ietf.org>; Fri, 23 Aug 2013 03:52:57 -0700 (PDT)
X-AuditID: c1b4fb38-b7fcf8e0000062b8-6c-52173f078407
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id A6.48.25272.70F37125; Fri, 23 Aug 2013 12:52:56 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.146]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.02.0328.009; Fri, 23 Aug 2013 12:52:55 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: mmusic <mmusic@ietf.org>
Thread-Topic: DECISION (BERLIN-Q1/Q2/Q7): Usage of specific PT value for single codec configuration
Thread-Index: Ac6f7ikjB1DJ6cLXRlGYV8ZqhT4gnQ==
Date: Fri, 23 Aug 2013 10:52:55 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C47766D@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.19]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C47766DESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKLMWRmVeSWpSXmKPExsUyM+JvjS6HvXiQwRpti6nLH7M4MHosWfKT KYAxissmJTUnsyy1SN8ugStjyw6dgiU2Fe2TWxkbGK+bdDFyckgImEjcnfiVBcIWk7hwbz1b FyMXh5DAUUaJJx0dLBDOEkaJX1NnATkcHGwCFhLd/7RBGkQEZCT2btrMDGILCyRI/PhxlhEi nipxum8tO4StJ3GvdR0TiM0ioCpx48kWsGW8Ar4S0/c0g8UZgRZ/P7UGzGYWEJe49WQ+E8RB AhJL9pxnhrBFJV4+/scKYStKtD9tYISoz5c4090LNVNQ4uTMJywTGIVmIRk1C0nZLCRlEHEd iQW7P7FB2NoSyxa+Zoaxzxx4zIQsvoCRfRUjR3FqcVJuupHBJkZg0B/c8ttiB+PlvzaHGKU5 WJTEebfonQkUEkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnVwKgiZR+gdFPyolCgpOG77OW9byWM 5swW3nntytnUYi/BZ1Jaqe/0N65h1XWRXz2F9Vt7kO0vvYWSZ/sZ1/EcnFjytc583YvNlb7T A5gWnGtgC23x0Gac/1TXuVdTb5rASgtrRd3rW9gYDqo2Sqwr1zQ9uWPO10VaHCzZWf+/Rt8M dItySroarMRSnJFoqMVcVJwIANrhiHlIAgAA
Subject: [MMUSIC] DECISION (BERLIN-Q1/Q2/Q7): Usage of specific PT value for single 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: Fri, 23 Aug 2013 10:53:07 -0000

Hi,

One of the open issues related to BUNDLE presented in Berlin (Q1, Q2 and Q7 in my slides) was regarding the usage of any given PT value.

My take of the outcome was that:


-          We agreed that any given PT value can only be used for a single codec configuration (Q1)

-          We agreed that we need some definition text for "codec configuration" (Q2)

-          We agreed that, within a BUNDLE group, any given PT value can be used in multiple m- lines, as long as it is used for a single codec configuration (Q7).

Jonathan Lennox promised to suggest some definition text for "codec configuration", so let's wait for that until we go into those discussions.

But, if you have any issues with the agreements in general, please bring them up :)

Regards,

Christer