IETF Logo Mail Archive

Re: [rtcweb] Does RID require the same ext id for all the m= sections?

Iñaki Baz Castillo <ibc@aliax.net> Mon, 11 September 2017 13:52 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F07F133097 for <rtcweb@ietfa.amsl.com>; Mon, 11 Sep 2017 06:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] 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 FPtbgYGQLHcO for <rtcweb@ietfa.amsl.com>; Mon, 11 Sep 2017 06:52:44 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 E4A78133091 for <rtcweb@ietf.org>; Mon, 11 Sep 2017 06:52:43 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id 189so8663085wmh.1 for <rtcweb@ietf.org>; Mon, 11 Sep 2017 06:52:43 -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; bh=/SnnGL+e4JplcFvg/VXuFl5b/xhgBiYyIGBjU5G96os=; b=rWRQ0QZYg9CMcnk2dTswxJ1Cv2Aq4H+0bXZwGs4wlhHCDbk5hljbWksNXifeGuDmnJ X0CcSm/vScGP79nn5cefNbK38u1QYB3aAxshbDJCgKRVoOlnV79/OKZEz16FAeoH7V/d mhbodrHSGOzpqEwsPRtbdB+UYaLBGC0JrPhKjY90rnvR5X27NjjMpGyycY6edEchYD22 1RpswC7p2SCOs+BLQA7D9WbrrYS8sOmfiR5+s0Bl3tFiaPNBZ6CyH4eY/OsxyXMWs5hF OMZzcELCXSPEi4I7TZtaNXGS0fF6L9xx+0vb0dEwRq8GP6LL3PCZ35psiFceeC44besn rReQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=/SnnGL+e4JplcFvg/VXuFl5b/xhgBiYyIGBjU5G96os=; b=Ldm+La6SCm2JdtDcUaPf+gWFzifKlAGyk137k6i/oEwDh96xxMkInOV7zdh18KDL9u qTFhsFz5/q8PvrZGeUqNpVDK5xKQsLt0wpTX+oAmuC/B/JqshOH5wjTnOL01D/F1tSvA pWYCp1tgf5Mj42IJ6yuGl5+LA06oJzk6ujqQBtdYw4D1G/rordpzOJkm2HGrWMGZpSww 82kJrbvjsVEkEdMXykehwcycSFvzWRFP9ZYfdAsr6lrn6NBgCnCrHlXF2LlXo+W9XyMz O4DPCmPiS0oi/ONadXuzX2imBOFgAlnHVSEtgoVqbkqYeKCs9+GjaQPFSLBASw8uZgRy OcoQ==
X-Gm-Message-State: AHPjjUjtm5S6TNxqCQiKCePGkWBoQTI6eRFcytWvf1cSkQHxv2H5CSyk h+q71lEWExjs9k3k3L0ZNv7qQIReZcaG
X-Google-Smtp-Source: ADKCNb4RbkW2G0EhxqYLO9IiQ1Mz8n67GAYK9ABIAYxg+0ZLcee+N+uhR+roIwMMre/gAZFTcM6NzZH1KGDYVKodPu0=
X-Received: by 10.80.149.87 with SMTP id v23mr9658802eda.284.1505137962364; Mon, 11 Sep 2017 06:52:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.152.129 with HTTP; Mon, 11 Sep 2017 06:52:41 -0700 (PDT)
Received: by 10.80.152.129 with HTTP; Mon, 11 Sep 2017 06:52:41 -0700 (PDT)
In-Reply-To: <881A3BC9-C9ED-4E1E-ACFE-C887333BB672@cisco.com>
References: <CALiegfnGvkdrhG_hPKGuGuhZCbcL9mUoauheBA3bc15s_G7ihg@mail.gmail.com> <EB2B7F8E-2847-4C8F-8DF4-5BAEE3C1DEE6@cisco.com> <CALiegf=6xRCXAx71XiErwqzwdVBVbFmzhvtaKS77v88Oh569TQ@mail.gmail.com> <881A3BC9-C9ED-4E1E-ACFE-C887333BB672@cisco.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 11 Sep 2017 15:52:41 +0200
Message-ID: <CALiegfmerkkf85H_9AOOJq0_Hd=MDj1v_QguucCv6OdXRFqQkw@mail.gmail.com>
To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
Cc: rtcweb@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c1997e895c6c30558ea3d90"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/IQelJlAVHXsDfj2oMdcVDDmZlyY>
Subject: Re: [rtcweb] Does RID require the same ext id for all the m= sections?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 13:52:50 -0000

Ok, but that is not valid for MID, as the reveiver transport is supposed to
check the MID value using a single extmap ID, right?

El 11 sept. 2017 3:34 p. m., "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
escribió:

> See bundle section 13.
>
> https://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-
> negotiation-38#section-13
>
> The same ID must always map to the same URN. Different IDs can map to the
> same URN as aliases. (The latter is not stated but implied.)
>
> Mo
>
> On Sep 11, 2017, at 8:49 AM, Iñaki Baz Castillo <ibc@aliax.net> wrote:
>
> On Sun, Sep 10, 2017 at 8:22 PM, Mo Zanaty (mzanaty) <mzanaty@cisco.com>
> wrote:
>
> All extmap IDs must be consistent in all bundled m= sections, just like
> PTs.
>
>
> Thanks.
>
> However, what does "consistent" mean? I assume/expect that the extmap
> ID (for example a=extmap:4) cannot exist in two different m= sections
> pointing to different extension URLs, right?
>
> But, and given that you told about PTs, it's perfectly valid that two
> different PTs point to the same codec+condiguration within the same m=
> section or in different m= sections.
>
> So, could a m=audio section have an "a=extmap:4 urn:foo" line while a
> m=video section has "a=extmap:8 urn:foo"? or should both use extmap ID
> 4?
>
> For example, the extmap ID for MID must be *UNIQUE* across all the
> m=sections. Does the same constrain exist for the extmap ID for RID?
>
>
>
> --
> Iñaki Baz Castillo
> <ibc@aliax.net>
>

v2.23.0 | Report a Bug | By Email