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 15: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 0ED55132F49 for <rtcweb@ietfa.amsl.com>; Mon, 11 Sep 2017 08:52:35 -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 TNsBNRNGVtGh for <rtcweb@ietfa.amsl.com>; Mon, 11 Sep 2017 08:52:33 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 667CA1321DF for <rtcweb@ietf.org>; Mon, 11 Sep 2017 08:52:33 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id i189so43177326wmf.1 for <rtcweb@ietf.org>; Mon, 11 Sep 2017 08:52:33 -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=Zemo/tYw6zAvgRbv0P5ZRvMI/gQQD3NYVsmjc/IAhDA=; b=htK6FNdTSJesu26Qh9sRLj8RF/AsczuABctkGurEAUzEjRWBs21oKlrrJNYHcpYM9O ZfXMwQELXV+gI5Be2qzeenFevuv/yuKUxWw10AeDuazM/kDZ7gkOdOtLqJWjJWgq8mUw Wde4pJBud7RyNn4sYlU5hAjnHNl4Cq9GcIb2tv8/pVFxes83hxYN+m8nWOXVlRJ9Pkz/ 08O/dDD3SLunzZwtfoluVKXFpPrmY4JNd7GZajViEM7FxFVn+DAeknLhMLweVhuYZxqY vzxa4HwdKPC4oVyxSRMgHxpaNfxrPvWTPirwaI/NdiXd2ABjat1VfBsux3jU0AIqu1NF l15A==
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=Zemo/tYw6zAvgRbv0P5ZRvMI/gQQD3NYVsmjc/IAhDA=; b=FCDmIGR2SZJXuPmYHEcwiGRYjluhgDFdfEyzGbCvwSkOPo6a98zkVWG0lsA90tn9ld ehTZAImc2vopX+3mfm6pVzkHr9oNeSoKy/deURb31S5sRBvpY6pkU9YhiebMv4bEfPD2 /fXXfTlCREK0b8AmF4oyPdD8QFey+72t+U16x3Lgl0fwb2wRvZuWgjlFcFIiKJp/1sM6 kbhLsTOe7whfUjwLh9/74pKUnTSo6SPLLPrrlvgQ1JnR6ZnZ0LNREHpysSStKS9bepEs 9DTfW8AxTXSrWyqCDe8Hnxf6N4/EVmXcIq+J8si8nBcC+QMAEb1/my0epYoHsYWLoc25 aKEQ==
X-Gm-Message-State: AHPjjUhev3nIOsPPi0QE7YtSLrNthtItO9zCPDirm8kzLCQNOjmBHyUp orYs4oY3mU4WLCWuLkW+AA+GORQDMikNbfY=
X-Google-Smtp-Source: ADKCNb7mHce2tLuZ3mulQCtilDpFWaJWeM6NtEF7yVsgbAufFWruX96bZsV5o3jUY+d4fsr++Y+np0f3Q+U7Xgv+YvI=
X-Received: by 10.80.179.199 with SMTP id t7mr9879763edd.19.1505145151848; Mon, 11 Sep 2017 08:52:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.152.129 with HTTP; Mon, 11 Sep 2017 08:52:11 -0700 (PDT)
In-Reply-To: <D5DC1C96.726D6%mzanaty@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> <CALiegfmerkkf85H_9AOOJq0_Hd=MDj1v_QguucCv6OdXRFqQkw@mail.gmail.com> <D5DC1C96.726D6%mzanaty@cisco.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 11 Sep 2017 17:52:11 +0200
Message-ID: <CALiegfkB-DF2njWYzJYg455GddByLK8dQJq21wp+JEWSaJC=sQ@mail.gmail.com>
To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
Cc: "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/l5J1LX0MTr8wtNtHib3O4V9p198>
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 15:52:35 -0000

On Mon, Sep 11, 2017 at 5:02 PM, Mo Zanaty (mzanaty) <mzanaty@cisco.com> wrote:
> Bundle defines MID, and section 13 restricts all extmap IDs (including MID,
> RID, etc.) to be consistent across all bundled m= sections, just like PTs. I
> see no restriction against aliases, nor any reason to impose one.

The RTP MID extension value is used (should be used when someone
implements it) to lookup the associated m=section, so the extmap ID
MUST be unique across all the m=sections in the SDP. Otherwise the
lookup operation would be impossible.

This has been discussed in this mailing list not so long ago.


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

v2.23.0 | Report a Bug | By Email