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

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 03 March 2014 11:13 UTC

Return-Path: <christer.holmberg@ericsson.com>
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 B09F61A0DE4 for <mmusic@ietfa.amsl.com>; Mon, 3 Mar 2014 03:13:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Level:
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 TFpLi--gxLxY for <mmusic@ietfa.amsl.com>; Mon, 3 Mar 2014 03:13:54 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 3DEDC1A0CC6 for <mmusic@ietf.org>; Mon, 3 Mar 2014 03:13:53 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-46-531463ed961c
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 76.93.10875.DE364135; Mon, 3 Mar 2014 12:13:49 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 12:13:48 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
Thread-Index: Ac818yLx23ucJzjaSbubJw5GhjG+ygAyCDEAAAM6QvD///NSAP//7o6ggAAV3AD//+xLsIAAGcSA///u21AAAkQTAP//7vZw///sHgD//8c0cA==
Date: Mon, 03 Mar 2014 11:13:48 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C5E62@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se> <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5BBF@ESESSMB209.ericsson.se> <D1A5B4EB-45E0-4BFA-BB93-96119F1B8152@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5CCE@ESESSMB209.ericsson.se> <FF73D8EC-D4EB-4E53-8D05-63D4624F4B01@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5DDF@ESESSMB209.ericsson.se> <331AFD56-7C29-4BB3-9B63-00D1E9317F9C@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5E15@ESESSMB209.ericsson.se> <A140A09A-20C9-4294-82F7-487606F98C68@csperkins.org>
In-Reply-To: <A140A09A-20C9-4294-82F7-487606F98C68@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C5E62ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsUyM+Jvje7bZJFggy2nRC2WvzzBaDF1+WMW ByaPaffvs3ksWfKTKYApissmJTUnsyy1SN8ugSvj99PfrAXbDSuunTjD0sC4TbuLkYNDQsBE omN3TBcjJ5ApJnHh3no2EFtI4BCjRFN3ShcjF5C9mFHi78YFrCD1bAIWEt3/tEFqRARUJXYc /8cIEmYWUJe4ujgIpFxYoIVRovXMAXYQR0SglVFiSv8RJpAiEYE6iZ2TIkB6WQRUJLrON7OD 2LwCvhLT195khtj1mlWiu6uVFSTBKeAo0finGewgRqDjvp9awwRiMwuIS9x6Mp8J4mgBiSV7 zjND2KISLx//Y4WwlSQW3f4MVZ8v8XnxTFaIZYISJ2c+YZnAKDoLyahZSMpmISmDiOtILNj9 iQ3C1pZYtvA1M4x95sBjJmTxBYzsqxjZcxMzc9LLDTcxAiPq4JbfujsYT50TOcQozcGiJM77 4a1zkJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbG7nb94JlB+1d3mmZO67HW7mAwTUmVCGW8 vMf6wNuEhu5gVumoST2lxwqiunjmnBCqusQuviDkZehy38DpPa8PnRcLcKsJ0FdY9Dz6jJmH zecVth25R659sXa8oaI0Ne/sgi9RH3V7NWezmjDtuLCvbJ2qddLa6w+ZWaczR4oF8ry/7xpY m6LEUpyRaKjFXFScCAAXfHo3dgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ZmoLKuHFUKTkc8AN9urbvJV1qj8
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 11:13:55 -0000

Hi,
Assume you have two video m- lines.
On both m- lines, you indicate that you can receive a codec using PT value Y.
Then, you receive a video media packet, with PT value Y, and SSRC value 1234567. How do you know which of the two m- lines this media packet is associated with?
We've discussed this multiple times before. If payload types numbers are unique across m= lines, then obviously you can use them to identify the m= line. If you reuse payload type values across m= lines, then you need some other way of identifying m= lines, if you care about doing so. Signalled SSRC values are one approach, something like AppID might be another.

...which takes us back to what I said in the beginning: when you send your initial offer, and assign the PT values you want to receive, you don't know whether the remote peer supports AppID, or whatever other mechanism that could be used.

Regards,

Christer