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 14:11 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 DCF43132C32 for <rtcweb@ietfa.amsl.com>; Mon, 11 Sep 2017 07:11:18 -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 uugZ-LSke9Ej for <rtcweb@ietfa.amsl.com>; Mon, 11 Sep 2017 07:11:16 -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 B1F0213302A for <rtcweb@ietf.org>; Mon, 11 Sep 2017 07:11:15 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id i189so40775631wmf.1 for <rtcweb@ietf.org>; Mon, 11 Sep 2017 07:11:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=G8nmkqVJLr4v5yXFjanqprGFO3DbAJ3XJ6tL245B/34=; b=CT9Gm7IWYuOoUpBPIvQ/gK3E/Il5phVv6JI/avpflHJgrizekAK1DxiYUfWOcVXX+g ggeqdtVhbpa8cERudSz468RG8Ns/VGad5D554GRKs0lHKzcYOtCXO7FGhSENTOx3W45T Zf4jCpL8hu8AZmCfwPO2wocGakGzYrgK5BQOjvYDnAd4ORb6e3EMPAgM5w0VsTh4sVfV Z9TiJUybF7OTj7LaKzYDjhXi8Z6liug6ee702Gcrgi2rzlnViwMSOgLNxFw4oDSLN0fw HJAW014wsziAq3XtTwkp2t0M/Ezfdo1F6NoFaESgq8heleeNVgHAs4xiXByKzdzDmjWh ZIPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=G8nmkqVJLr4v5yXFjanqprGFO3DbAJ3XJ6tL245B/34=; b=Yhz/r3qClQVKOUdS/7zPAVfthhAuClmcdPHb5u9dV6+tiECMC/eHMRb64LZC4ALvqS sjggYXzv8K1LtysFjSoja1SsL9zQBAzKErhXJ5BbBn2rATtDiChdKZZcWvM5Txu8ZY8A TiLu+30ERlsTq3/a3rqaCb8xMQATOks1HQp6YIs9lXOV77gf4LlJrXq0yuseDYBjsQFc /zTY+68cW/yq5YYDdFOMUfju6zYqoybCYOuBVoG33T98U5wgcUI7PArFp1lwsLXy10e3 YQ3buTsM1dzVRAYpKSSuYJL7PMIaQGHIQF9iACzaHwPmmvyBXM//+/iyLzMVLYAIlzfo 6LHw==
X-Gm-Message-State: AHPjjUhAb//AdRNJngxmjc3cBFpqxfBN6+zVIavrmA9HZ3AqbE6cOSpU NpfF1yLLYOn24I3BIJjpKw4Z3c22
X-Google-Smtp-Source: AOwi7QBOGydVgSIvow3FnTIr8U9eST2CztH/6KteQ6Ku0MwBftWSKEQ5a1koxXfNYUT5eFzJMi3v4Q==
X-Received: by 10.28.74.211 with SMTP id n80mr3265346wmi.94.1505139073961; Mon, 11 Sep 2017 07:11:13 -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 n3sm7781128wrg.38.2017.09.11.07.11.13 for <rtcweb@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Sep 2017 07:11:13 -0700 (PDT)
To: 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>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Message-ID: <a494c448-afa5-4b9d-da8a-64619451d806@gmail.com>
Date: Mon, 11 Sep 2017 16:11:11 +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: <881A3BC9-C9ED-4E1E-ACFE-C887333BB672@cisco.com>
Content-Type: multipart/alternative; boundary="------------7476D84B62FADC950E5E0343"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/df6t-v0746PnGnzfzksd3YXN6vI>
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 14:11:19 -0000

But according to RFC 5285:

    An extension URI with the same attributes MUST NOT appear more than
    once applying to the same stream, i.e., at session level or in the
    declarations for a single stream at media level.


And

    In addition, as noted above,
    the IDs used MUST be unique for each stream type for a given media,
    or for the session for session-level declarations.


So it is not possible to have same URN with exact parameters with 
different IDs for same "stream" (whatever "stream" is meant to be 
nowadays), and I would (at least) assume that each URN cannot appear 
more than once in each m-line with same parameters.

Also, IMHO, bundle should be updated to make this requirement session 
level, as it is done with the ID uniqueness.

Best regards
Sergio
On 11/09/2017 15:34, Mo Zanaty (mzanaty) wrote:
> 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 
> <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