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

Suhas Nandakumar <suhasietf@gmail.com> Sun, 02 March 2014 10:34 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 D5C611A0C99 for <mmusic@ietfa.amsl.com>; Sun, 2 Mar 2014 02:34:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 aEGD0De1BgLq for <mmusic@ietfa.amsl.com>; Sun, 2 Mar 2014 02:34:09 -0800 (PST)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 3615C1A0C97 for <mmusic@ietf.org>; Sun, 2 Mar 2014 02:34:09 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id a1so1994749wgh.3 for <mmusic@ietf.org>; Sun, 02 Mar 2014 02:34:06 -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=zna7LTgrPE28DsthThCc63lR7QuOUGVWmNWTDryh3MM=; b=M4Kumm3kNBWHEsgtb+ebJ2ekeniRd1KmlXlbtMtaIyca3PaM3j8ExqKZUIHor2kTm9 bR27M0mBd/z8272ypbUDsbiC9E++EyKvRuth/Xu4elaMBoT3/keg5spHpIyEIyynKECk f+werCZ5oYrHM212sc5oHXMp1KVKkRiUpebXVIgwR8KbOl0RLvPqj93TW8YcCZhu8tqK OIwGGxIsizvUXzojpfRSHJ3lbxkfMcnFAcoO2IlsTiYAeJ2gMTbYAXpONvUhhDZ2cf3w OiDYq4ViF+Zd5yKAj/BZZkpzYHI3a+ZtT55F2C5WZAFdCS+KA8FQiPbz3epcsldY56gM s8Uw==
MIME-Version: 1.0
X-Received: by 10.180.149.206 with SMTP id uc14mr10602265wib.44.1393756446119; Sun, 02 Mar 2014 02:34:06 -0800 (PST)
Received: by 10.195.12.134 with HTTP; Sun, 2 Mar 2014 02:34:06 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se>
Date: Sun, 02 Mar 2014 10:34:06 +0000
Message-ID: <CAMRcRGRq5zrZJNBwvPpX-nshqar8vS2u3Kefu91GhoGXTtoJYA@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="001a11c38008dfdd6004f39d3505"
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/b2E1TSAk17R67rQU51ItyOiBdKc
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: Sun, 02 Mar 2014 10:34:12 -0000

+1 on closing this action item

I support either a clearly specified codec configuration definition or
something on the lines above

Cheers
Suhas

On Sunday, March 2, 2014, 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
>