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 16:11 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 086BB13313F for <rtcweb@ietfa.amsl.com>; Mon, 11 Sep 2017 09:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 2EAdmYEqGMcU for <rtcweb@ietfa.amsl.com>; Mon, 11 Sep 2017 09:11:52 -0700 (PDT)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (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 C10EA1330DE for <rtcweb@ietf.org>; Mon, 11 Sep 2017 09:11:51 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id f199so43643770wme.0 for <rtcweb@ietf.org>; Mon, 11 Sep 2017 09:11:51 -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=nZmgwW2VntPmZlUS8X5/tLxo7WUlb5CO7Gu+CGTqMbc=; b=jE66ODnR40YXWDn1EDkBoJ2FGBHF4sp/tPdgHSLtVmTggznP7DgHtaeZG2FWPRet5R WveOIz0XC2vJBrj9GxA8Rh6yVku63fGfkdLa0dXxnxhNtKsTdgcOtEF9BQUZ+Wv9+AKC 27jI9Z/m5S2SElbA9WXLS9SHcPCTja36NIl0Ew0g0IfGPhUVXTBAf8en2MM/exIM1diF oAXtZ8M52d6xhSA4wh7s4OiN1P0frofs6c8buL2MQeYiBXePJlVr5pDvofnBeGLgJWJP uPFMBiU+6EVIH4e1mSZT0S1sxvw3nYoiYUuKPHKQOw1PCMa/2Mgl3raHK4DDj4mH/NLN nOrg==
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:content-transfer-encoding; bh=nZmgwW2VntPmZlUS8X5/tLxo7WUlb5CO7Gu+CGTqMbc=; b=PxqyS+VPmJ3NiJNFlz0KPCkgHEmLChHJS3qk9FQcp84sVtlgaxnixIytSQsBkfyI8X gR6p9Fsv2mgioe9FrCeyZeYXjGAXJpywFe2vMrhinAB5yOWpB/MiGXw5OAfjEBHIQljE TX5l438WrWnGrXMYa0mRG1Zu/iqGTNGXOai6/t0kMBTrPGxamkL8Mj9hHYsOk49I3Ls2 PLo2VHkedzCixRUYbb6QsZGDl8RJHNGQy/qhqefH+YL6LCxbQ5qOa3+Wl1gy1DFnxi8n E3SV17bYCqXo4z0dOVzyECkf8iesw9eWnHu5d9qMsgmKA0785sA+bm95gsVzKZRU3eEX Qd0A==
X-Gm-Message-State: AHPjjUhrBeJcSqyzumLbI9TlSrgocxWXWrJ7IFg5mrZlIJw4YVk51eBC AF6L7qUl75iTkRQw7kqh9wcmaqjhAOQVBjQ=
X-Google-Smtp-Source: ADKCNb7E+/tvSrWWVF89MXW/CWR4x6p90p+Nhx3LQ42DndvABERHET2coRo8bWNQWRSRiMHeDh6MJ4ciBgLMuTfaUWY=
X-Received: by 10.80.147.91 with SMTP id n27mr9798700eda.36.1505146310085; Mon, 11 Sep 2017 09:11:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.152.129 with HTTP; Mon, 11 Sep 2017 09:11:29 -0700 (PDT)
In-Reply-To: <7029a788-ee1c-0f42-d037-1bfb80b87b52@gmail.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> <CALiegfmerkkf85H_9AOOJq0_Hd=MDj1v_QguucCv6OdXRFqQkw@mail.gmail.com> <D5DC1C96.726D6%mzanaty@cisco.com> <7029a788-ee1c-0f42-d037-1bfb80b87b52@gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 11 Sep 2017 18:11:29 +0200
Message-ID: <CALiegfk57kkXwShmdzLAkKb=aKwnZHet0LjcLbDGKn5Am6mw9w@mail.gmail.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Cc: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/jAKaeS6-Eo1tYrKDYfSzwitAPD8>
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 16:11:53 -0000

On Mon, Sep 11, 2017 at 6:06 PM, Sergio Garcia Murillo
<sergio.garcia.murillo@gmail.com> wrote:
> Aliases are already restricted in same m-line by the header extension RFC.

I don't mean aliases within the same m= section, but usage of
different "a=extmap:N urn:mid" (different N) in different m= sections.

That's not valid since the receiver needs to use a *single* extmap ID
to look for the packet MID extension value, so it can find the
corresponding m=section it belongs to.

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