[AVTCORE] What does "same codec+configuration" mean?

Iñaki Baz Castillo <ibc@aliax.net> Fri, 11 March 2016 20:36 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97D8C12DB59 for <avt@ietfa.amsl.com>; Fri, 11 Mar 2016 12:36:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aliax-net.20150623.gappssmtp.com
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 LITk-n5o8AA2 for <avt@ietfa.amsl.com>; Fri, 11 Mar 2016 12:36:52 -0800 (PST)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96B5E12DB87 for <avt@ietf.org>; Fri, 11 Mar 2016 12:36:31 -0800 (PST)
Received: by mail-yw0-x22c.google.com with SMTP id g127so103924788ywf.2 for <avt@ietf.org>; Fri, 11 Mar 2016 12:36:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aliax-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=e0gK1RD7rCSxf9ole4T9nFRCrzNUCvAy1sBJkipPDKY=; b=RzG1FJu6eWdtxKtDVkV60NYmVAtSKLOxFXDnNfLOAj1EMeqlxjX6IMCDNGHLRTv8KN mOOzqGz8JZKJYARDadv5cTlAr816gUiZNp58XHD1TvJzGzmHlcLjAh8/McubDyNrWv5+ Qyf09ClyjJc02DF+DLe0NX9ceIvny/30PXolrEfIqZN4zBY8hcI9hzgonGY+m4T1uko2 znCWtDJ1l+ShwyjVUP4reV929BsMvlFsnQedEbi2qSgdv6ATLMRKilsmjr5AyVykYO2a 4hMImr7BGpS1IdyV8nVMFlHAuMi2JF6mI+XObZDUfqzbLpvU3k7wCWR+BR81/WKfz5fx RIDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=e0gK1RD7rCSxf9ole4T9nFRCrzNUCvAy1sBJkipPDKY=; b=hiWi+mEHtTEa1lqRuEHDWdgxu0cTT7sxaGBbpEGzmQi1U8JgNVXfSI73+ll5Bgp9lt micCImLiHuv9Nv+pLVek/MX5iUhDx9h6FUdLs2+kxO0EsTr5Y6x76G60384nYf2xemT6 zNFqAVldKZqFyOxj+qNIg3iTu7NeKo+/ncuFgoo0Q301GJP+vDUlyL7xPFXVinHAJGaO Xs7nMDwbgcU/vhosEbh8p69OjmkWEp5MDEwaukUC99aYvQp++XItU3z+cnU8gpzMvlMb EUgNxnnkOPO0p6LGReSpANT0svur+gsSFjnfUi4PLUGK6hf+cbjSrgknHWuJXoa1ZnoL VGmw==
X-Gm-Message-State: AD7BkJKq6TO/4Mqa4RNAI5TODuz9cJVy8SoOVitdzZHKbMJyxsyEgpOup3JbARv5Akeac0sgKJtgNFjhjNe8TQ==
X-Received: by 10.129.75.211 with SMTP id y202mr5885818ywa.299.1457728590891; Fri, 11 Mar 2016 12:36:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.201.132 with HTTP; Fri, 11 Mar 2016 12:36:11 -0800 (PST)
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Fri, 11 Mar 2016 21:36:11 +0100
Message-ID: <CALiegfn2bMHX-yRDrHh0RKx-n4DfnLb1HfEeX18_ZigJGYOsLA@mail.gmail.com>
To: "avt@ietf.org" <avt@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/HmJahmXek-CUeOvy4VoeXZaYWj4>
Subject: [AVTCORE] What does "same codec+configuration" mean?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2016 20:36:55 -0000

Hi,

According to BUNDLE spec, two bundled m= lines can share the same PT
value only if such a PT value points to the same codec name + codec
configuration.

What does "codec + configuration" mean? Some codecs have specific
parameters, some parameters may be optional, and AFAIK there are some
parameters that don't need to be fully negotiated by both endpoints.

May I get some examples and be pointed to the appropriate spec?

Thanks a lot.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>