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

Iñaki Baz Castillo <ibc@aliax.net> Thu, 24 March 2016 15:41 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 69C4112DB31 for <avt@ietfa.amsl.com>; Thu, 24 Mar 2016 08:41:56 -0700 (PDT)
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 Gk_MboMM8MUF for <avt@ietfa.amsl.com>; Thu, 24 Mar 2016 08:41:54 -0700 (PDT)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 B284812DC3E for <avt@ietf.org>; Thu, 24 Mar 2016 08:27:50 -0700 (PDT)
Received: by mail-yw0-x22b.google.com with SMTP id h65so63594751ywe.0 for <avt@ietf.org>; Thu, 24 Mar 2016 08:27:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aliax-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=72lIytpBX7ETsLncZ5aa1vbQlpRF3GtUHc3Ib5yU2Fs=; b=zBYfxQzpaSi1MTHbTEkJfqQkQQ0rOK4TghzjHiHDUto8s8kgHEp3GyRzabx1gyzOmK aBcL9aV1xEc3jXlsv5lCNKd6cTSAdjDUqjKDjgaV+sa3ETePT+4UlgEMxX2rIaCkiyTE k21bmgWgYBfn39tApfnCRsvcPyf5Suh73JTGtl5/4bVwgA5cDDrezlTPq5IrBVjwMRAB jwKYOVVmKudh5W/eVIIPuKuWpQ6geK5haswTBInBzKgB6T7MpfY21wpu6nB1xAx31nv0 96UZP8/W+eJT9qD6oRTlk0yqT6KEJrSQ8QvScu9+6moEhfZcsyjW7dHC8wuRZfzvD/5Q VCVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=72lIytpBX7ETsLncZ5aa1vbQlpRF3GtUHc3Ib5yU2Fs=; b=mG2bOTN7ifU7yNqlPgjKZN4/Y9zDNZRD/AxSG7g96uobj3PlvBrByJA5lSbBokkwG2 8c+Zpmprc/SZ5ViB6kG9Effk+sdS9czE/Edmx1ts4O6DaD4WaIR5t0lQwUzJhc4P02EY ELITnb8Tc4lCkrkDGp4lZszKPH2oxlS36yYy7G+9/Uv0n6BU6nDo4F03ZcNYKCjqqzG7 PlaTTnWuyhSJpUIfXWVq7ubL8IUVUWzGJFSvd3w5VucB8JFXGR7DvSVUtgrxfrQiTM3K u09dtRelbKkE4z/IjX4Si3Mp36WwM9BnXWBoggACKrDmKCKlVb44ZuDWE3Cv1+5YUsyO 0t8g==
X-Gm-Message-State: AD7BkJIqbkFEHLtcWcz6M2FlZySSEgEVbUu5eJiA95UFwL8tOIJhkM3rnuUFdOp/cMnIKCKxGr24RETBTL1FIA==
X-Received: by 10.13.215.149 with SMTP id z143mr4527051ywd.278.1458833269898; Thu, 24 Mar 2016 08:27:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.201.132 with HTTP; Thu, 24 Mar 2016 08:27:30 -0700 (PDT)
In-Reply-To: <CALiegf=tzUZQUApL7MiLHA0vLcD+RsGHz61NMACL_Obv0NE3cA@mail.gmail.com>
References: <CALiegfn2bMHX-yRDrHh0RKx-n4DfnLb1HfEeX18_ZigJGYOsLA@mail.gmail.com> <56F15CDC.202@ericsson.com> <CALiegf=tzUZQUApL7MiLHA0vLcD+RsGHz61NMACL_Obv0NE3cA@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Thu, 24 Mar 2016 16:27:30 +0100
Message-ID: <CALiegfnb87+xw5uxr1TOYeiVvPwFThAnuuDuLVddbLa6sTu-_Q@mail.gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/42sfIRYv5-fe3q1jOXX9s2FcdUE>
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [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: Thu, 24 Mar 2016 15:41:56 -0000

2016-03-23 13:46 GMT+01:00 Iñaki Baz Castillo <ibc@aliax.net>et>:
> 4) H264 in Firefox:
>
>   a=rtpmap:126 H264/90000
>   a=fmtp:126 profile-level-id=42e01f;level-asymmetry-allowed=1;packetization-mode=1
>
>   a=rtpmap:97 H264/90000
>   a=fmtp:97 profile-level-id=42e01f;level-asymmetry-allowed=1
>
> Since Firefox offers two H264 codecs I must assume they are, indeed,
> different codecs. So it seems that "packetization-mode=1" make them
> different (which also means that its default value is not 1). Right?


I've clarified this:

https://tools.ietf.org/html/rfc6184#section-6

  6.2.  Single NAL Unit Mode

   This mode is in use when the value of the OPTIONAL packetization-mode
   media type parameter is equal to 0 or the packetization-mode is not
   present.  All receivers MUST support this mode.





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