IETF Logo Mail Archive

Re: [Perc] Drop support for E2E RTP header extensions

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Sat, 13 May 2017 15:46 UTC

Return-Path: <sergio.garcia.murillo@gmail.com>
X-Original-To: perc@ietfa.amsl.com
Delivered-To: perc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB590129BF9 for <perc@ietfa.amsl.com>; Sat, 13 May 2017 08:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 AeIPbhmIN1l4 for <perc@ietfa.amsl.com>; Sat, 13 May 2017 08:46:15 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (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 7D9FD129B19 for <perc@ietf.org>; Sat, 13 May 2017 08:43:56 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id v15so7563345wmv.1 for <perc@ietf.org>; Sat, 13 May 2017 08:43:56 -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-transfer-encoding; bh=uTDeWj6oedNFhN2RFtRk7XXdL4vrwtTXf7ZMoUgHFhM=; b=cce2Us8M2SAbxAUFbEbuismuPZ2YX9Nuy0VVm2Z+CsFdnjYLKQa7Wqt6KS5ZnaaqNB nzPGAjMA2M5MPUWJxSosRhhRppXcGd9gbBBVE+JxcG6XLtEf9yZ0VulQOdSKG3J8bYJ5 BWL2gyqCSJ3rrKhINHGpneW0ipCoOG7DfgksepdbAUa7kwaMpJV0m+HaDkp+6sBCXamg BfqQ2+EJsElJMI2ImVv9k3BRPDN2C6hkwsxbxrxLLymCxkZjicSlziQJSSFQQthpo8Zq kQKdg3W4295lQjIJVnDivNaQYyixMjniKhkW+psgv2QVOZxEACXIwHZ9hjsO6/ofQdwz 9QiQ==
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-transfer-encoding; bh=uTDeWj6oedNFhN2RFtRk7XXdL4vrwtTXf7ZMoUgHFhM=; b=GljKk9D5nr2HMid4XdOFTeJ+eId8gIX0Zy9TcSSSib2sjRwLAhboMPzguJ0aZ1CC0v TYMDPKx9wOHM9CMEwyEAgeIOokqiuFq043UCY5xl89BN1DkK9kDeI9I3vkWFQjJz6xQy azsDvxSNQkijVyM4PfAMon8qGh/EZw/3ZBJ2ADUFGFKS3VYD7LmqwV2i5XjnH3tVVEIg CWot4ZDycI5EZtcMsMS8gkA9H8N0f1+GbwNF2oqqoaklKqGrc/ZkXDwO8hFtXeGwsvr6 SxC5TOLnvJZt6djv4/ecqJv8q/xdIbaK4Y/rklzBWv1JwWftnF2c7YtgincKGKDAGHFw ou4A==
X-Gm-Message-State: AODbwcA2HUW39bnmjWMt6PBSfLj4kQr/27y8OFNpGg769IJGCst/Cl3U g9ZWL5tQriMuSWzKMmk=
X-Received: by 10.28.8.17 with SMTP id 17mr1449755wmi.61.1494690234842; Sat, 13 May 2017 08:43:54 -0700 (PDT)
Received: from [192.168.0.196] ([193.125.63.82]) by smtp.googlemail.com with ESMTPSA id 188sm5615425wmf.29.2017.05.13.08.43.53 for <perc@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 13 May 2017 08:43:53 -0700 (PDT)
To: perc@ietf.org
References: <49c7de34-8bc6-bb7d-4524-0af26089eecb@gmail.com> <1CF6F66C-939F-484D-8C53-46ACB8CA69BE@vidyo.com> <27ca2993-5c66-8388-7187-b47ed8ae1340@gmail.com> <CAL02cgRDaz7BT+GzxWJ0cM7rebhd2cu2WbPy+Mwjkk0wJK=6mw@mail.gmail.com> <aef9a32f-f761-c9e8-de99-57c4acfd5088@gmail.com> <8FD07F5D-CD52-445B-AF75-BA1696F3A151@mozilla.com> <aff1a9bf-7dcb-71e6-3d01-afe5cac87ca5@gmail.com> <E234DDC1-9AB5-4C64-91C0-A8FCB58DA351@iii.ca> <8ddbf495-ac23-8529-aa0b-a233a0b336c0@gmail.com> <74BE8407-9AC0-45D3-9476-5C109A7B7A3C@iii.ca> <286A6294-EC1E-49D3-88BB-023178DB07BD@packetizer.com> <2810AD6C-0F45-41CC-BC6F-4303B5649CB0@iii.ca>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Message-ID: <6afb5b1b-6603-58ad-be4d-9119f32596d0@gmail.com>
Date: Sat, 13 May 2017 17:43:55 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <2810AD6C-0F45-41CC-BC6F-4303B5649CB0@iii.ca>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/perc/6BNtl5lSnXj0px_OsWx2GIxo4a4>
Subject: Re: [Perc] Drop support for E2E RTP header extensions
X-BeenThere: perc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Privacy Enhanced RTP Conferencing <perc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perc>, <mailto:perc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perc/>
List-Post: <mailto:perc@ietf.org>
List-Help: <mailto:perc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perc>, <mailto:perc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 May 2017 15:46:17 -0000

On 13/05/2017 16:33, Cullen Jennings wrote:
>
>> On May 12, 2017, at 12:10 AM, Paul E. Jones <paulej@packetizer.com> wrote:
>>
>> I don't see how we can support any E2E extension given the offerer specifies the ID mapping. Multiple endpoints in a conference might indicate any number of didn't ID values for the same extension.
>>
> Just so we are all clear on how this would work ... sorry for the repetition ....
>
> If Alice's UA offers urn:ietf:params:rtp-hdrext:encrypt with and ID of 1 and the conferences wants to use 22 because that is what other endpoints are using, the conference server simply rejects that in the answer then does and reoffers that with an ID of 22.
>
> This of course does not take care of Sergio request that the conference bridge would like to tell ALice's UA if this should be protected E2E or not. I'll send a separate email on that.

But as there is no way to know if any extension is E2E and HBH, the MD 
will have to reject all extensions always, and re offer them with the 
common ids. Also, for the same reason, if we want to avoid sending 
unknown extensions to all the peers, the MD will have to disable any 
extension not available to all the peers on the conference, and do it 
dynamically. That means, each time a participant joins which does not 
support an extension for the common set, it will have to re-offer to all 
other participants to remove it

Best regards
Sergio

v2.23.0 | Report a Bug | By Email