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

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Mon, 11 September 2017 16:06 UTC

Return-Path: <sergio.garcia.murillo@gmail.com>
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 65BCF133139 for <rtcweb@ietfa.amsl.com>; Mon, 11 Sep 2017 09:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 P1Vk2XVn8erz for <rtcweb@ietfa.amsl.com>; Mon, 11 Sep 2017 09:06:23 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 75710132D79 for <rtcweb@ietf.org>; Mon, 11 Sep 2017 09:06:23 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id i189so43497311wmf.1 for <rtcweb@ietf.org>; Mon, 11 Sep 2017 09:06:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=ZxgRoRsXwmhWXyjCmpDQfGjoKA13VDrdoCl5eMNP06g=; b=e+foxNou11sJcoogu5BeNpKfqkC6pB9XZtUW7RVSZMw5dgZlg7hEKO5VjYMq063dgd ND2HfBNlYPeLqh8g1tw/zXVdDZsIslI4J+QZLHw/6Cf1lWRh4Hy+oedQmpOhZfQIMqvo 28BolCGdhVHHtmM/NhMmr0DDnSrc4gRN7oj4rcgQq+W9N46ycSLeeKvqsaAAusxDrQcn xEFvLUvNcH3tdOvh+oNkvj27D9TVnEsJdr6VosTQ145VHoJEwe69J35xHjfausMGaSUs yBEVgT7AvAbQbmkkpC/lj+FOGzgiKxngnzCv+/ADhbnbLESsaHeA1MzsxdYRNMrpg6+j vYPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=ZxgRoRsXwmhWXyjCmpDQfGjoKA13VDrdoCl5eMNP06g=; b=S7ivhvGQQgPN2jp5VC6mPzLGzWvmmiMirbCXlDesmamAvE9rb4VYDvxAYK9e/JNXr6 QCM8VLgGgONSVm5ll/ebHvOxrwmbrcKS4T6vKobyQ1YWmZqGysSNJNsdPOzE4JyilRK0 Wqc1Nq+j795t4j8GrOI/m9H85GHeY0Bm+K/aIyyJNbOH8KxIJn2rNbcg9NtTV+H7kgzN gMP7ihHuRffC3UBigRtu2SjeUwlbROUXo1Kww2BO9oEco7bBkd5qCTWdWJRGRGisMCta x4upXfgsBjExQABv5mm1z2fmf7fGs6ZNLPh7VDEwJMpbkIGb49o9Qgj84ai/Vj97assI 80iQ==
X-Gm-Message-State: AHPjjUim7OCqzsUWO/f7Eo4Yz1Q77Rx/vrC1qLqiuOgBZ1qoTWvNXr7J nR5viyHSAqgmWMCsqyc=
X-Google-Smtp-Source: ADKCNb44iZuYXswyxm4cuYyhRi6ZntC8gXfOC4RuhjdEE9TIyQIebMgb7QL8pAvMxrTf/x7+pRkaGg==
X-Received: by 10.80.240.67 with SMTP id u3mr5344994edl.35.1505145981594; Mon, 11 Sep 2017 09:06:21 -0700 (PDT)
Received: from [192.168.1.48] (128.red-79-147-157.dynamicip.rima-tde.net. [79.147.157.128]) by smtp.googlemail.com with ESMTPSA id o49sm2225979edo.69.2017.09.11.09.06.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Sep 2017 09:06:20 -0700 (PDT)
To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>, Iñaki Baz Castillo <ibc@aliax.net>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Message-ID: <7029a788-ee1c-0f42-d037-1bfb80b87b52@gmail.com>
Date: Mon, 11 Sep 2017 18:06:18 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <D5DC1C96.726D6%mzanaty@cisco.com>
Content-Type: multipart/alternative; boundary="------------4D7CF5D83FF7B8EC6143BCD0"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/nEqTOhCkZqpSMQORcLj63O13N3w>
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:06:34 -0000

Aliases are already restricted in same m-line by the header extension RFC.

Best regard
Sergio
On 11/09/2017 17:02, Mo Zanaty (mzanaty) 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.
>
> Mo
>
> From: Iñaki Baz Castillo <ibc@aliax.net <mailto:ibc@aliax.net>>
> Date: Monday, September 11, 2017 at 9:52 AM
> To: mzanaty <mzanaty@cisco.com <mailto:mzanaty@cisco.com>>
> Cc: "rtcweb@ietf.org <mailto:rtcweb@ietf.org>" <rtcweb@ietf.org 
> <mailto:rtcweb@ietf.org>>
> Subject: Re: [rtcweb] Does RID require the same ext id for all the m= 
> sections?
>
> 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 
> <mailto:mzanaty@cisco.com>> escribió:
>
>     See bundle section 13.
>
>     https://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation-38#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
>     <mailto:ibc@aliax.net>> wrote:
>
>     On Sun, Sep 10, 2017 at 8:22 PM, Mo Zanaty (mzanaty)
>     <mzanaty@cisco.com <mailto: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 <mailto:ibc@aliax.net>>
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb