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

Cullen Jennings <fluffy@iii.ca> Sat, 13 May 2017 14:35 UTC

Return-Path: <fluffy@iii.ca>
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 8AA8F129566 for <perc@ietfa.amsl.com>; Sat, 13 May 2017 07:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.301
X-Spam-Level:
X-Spam-Status: No, score=-3.301 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 zXRqwxFA4fzQ for <perc@ietfa.amsl.com>; Sat, 13 May 2017 07:35:36 -0700 (PDT)
Received: from smtp109.iad3a.emailsrvr.com (smtp109.iad3a.emailsrvr.com [173.203.187.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EEFC129B9C for <perc@ietf.org>; Sat, 13 May 2017 07:33:40 -0700 (PDT)
Received: from smtp14.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp14.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 18C1D25170; Sat, 13 May 2017 10:33:37 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp14.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id BDB5825153; Sat, 13 May 2017 10:33:36 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.67] (S01065475d0f7dcd1.cg.shawcable.net [70.75.17.123]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Sat, 13 May 2017 10:33:37 -0400
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <286A6294-EC1E-49D3-88BB-023178DB07BD@packetizer.com>
Date: Sat, 13 May 2017 08:33:35 -0600
Cc: perc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2810AD6C-0F45-41CC-BC6F-4303B5649CB0@iii.ca>
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>
To: Paul Jones <paulej@packetizer.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/perc/NjL-NXFOV50bI3b9527GQ4grIRM>
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 14:35:38 -0000


> 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.