Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - A new take.
Suhas Nandakumar <suhasietf@gmail.com> Mon, 03 March 2014 14:01 UTC
Return-Path: <suhasietf@gmail.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 955191A0112 for <mmusic@ietfa.amsl.com>; Mon, 3 Mar 2014 06:01:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.799
X-Spam-Level:
X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, J_CHICKENPOX_15=0.6, SPF_PASS=-0.001] autolearn=no
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 ZvnZgveMjyLy for <mmusic@ietfa.amsl.com>; Mon, 3 Mar 2014 06:01:00 -0800 (PST)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 634441A0117 for <mmusic@ietf.org>; Mon, 3 Mar 2014 06:00:57 -0800 (PST)
Received: by mail-we0-f180.google.com with SMTP id p61so2058325wes.39 for <mmusic@ietf.org>; Mon, 03 Mar 2014 06:00:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LhUTyzWVkM74bHxdL+Rndqe9mgb2gdh2+2/2RJpxGsY=; b=fngUeuEZKVtS869O5ibtxTZvkV4gHkYYPE6I25D//wKcBtcSNE+AioliJnpAZl2kR5 qUggXRXSEkQu3eLa4U7llLIe42jqYa54vl8qO+EuxwmnUjkfjoauxNmGuTzmNC/TdNQk bgx/wr5UcT/frp2q7ir+K6Tgz4Kx+BfLD05F9WN2wkID6bFqLkRkx5wSDvXZEmxvS7a0 FnT93zxkRrc/GnsEO4rSIWGZXPcAd0JmSfSn60xqJjfYis224u9TZISyPFsJ18qCDyJd +QVBlEtjr260jNnViGuqOn8BxruvnG7ejYxW2ym9bV5+iH2+GeufcK2DCINE3fd9tV2i i1pw==
MIME-Version: 1.0
X-Received: by 10.195.13.17 with SMTP id eu17mr18285708wjd.24.1393855254123; Mon, 03 Mar 2014 06:00:54 -0800 (PST)
Received: by 10.195.12.134 with HTTP; Mon, 3 Mar 2014 06:00:54 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C6336@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C6336@ESESSMB209.ericsson.se>
Date: Mon, 03 Mar 2014 14:00:54 +0000
Message-ID: <CAMRcRGRu_BHBvNH8D+CgeEj9RUXiw-0fHj2UuGqhT7HUG=pJxw@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="047d7bd91a7a4a5a1004f3b437e5"
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/El7p8nW5yr_t91NZrltcxDSsr5A
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? - A new take.
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 14:01:02 -0000
Hello Christer A small twist on your proposal I think the recommendation in the BUNDLE document should say 2 points 1. Reuse of PT is allowed only in the cases where the end-point is able to uniquely map the incoming RTP Streams to its corresponding m=line. The specific mechanisms to do so are out of the scope of this document . Informally, SSRC, AppID or similar stream correlators can be used. Also using the same PT across multiple m=lines implies the same underlying codec configuration. 2. Otherwise, reuse of PT across multiple m=lines MUST NOT be performed while multiplexing. We can add example for either if needed Any thoughts Thanks Suhas On Mon, Mar 3, 2014 at 1:17 PM, Christer Holmberg < christer.holmberg@ericsson.com> wrote: > Hi, > > > > Based on the discussions, we basically have two alternatives: > > > > *Alternative 1*: Forbid the usage of the same PT value within multiple m- > lines. > > > > *Alternative 2*: Allow usage of the same PT value within multiple m- > lines, and if the answer does not support whatever extensions that are > needed for the offerer to distinguish the media, the offer needs to handle > that, e.g. by sending a new offer with unique PT values. > > > > IF we choose Alternative 2, we still need to decide whether we let the > offerer decide when it's "appropriate" when to use the same PT value, or > whether we need to specify some rules (as suggested by Colin). My personal > proposal is still to let the offerer decide, and not specify any rules. > > > > Regards, > > > > Christer > > > > > > > > > > > > > > > > > > _______________________________________________ > mmusic mailing list > mmusic@ietf.org > https://www.ietf.org/mailman/listinfo/mmusic > >
- [MMUSIC] IETF#89: BUNDLE: Q9: What are the criter… Christer Holmberg
- Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the cr… Suhas Nandakumar
- Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the cr… Christer Holmberg
- Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the cr… Suhas Nandakumar
- Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the cr… Christer Holmberg