IETF Logo Mail Archive

Re: [tram] Path Forward for STUN ORIGIN - refer policy

Martin Thomson <martin.thomson@gmail.com> Thu, 27 August 2015 18:52 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19D781A0276 for <tram@ietfa.amsl.com>; Thu, 27 Aug 2015 11:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 W0tAOy16gDZa for <tram@ietfa.amsl.com>; Thu, 27 Aug 2015 11:52:02 -0700 (PDT)
Received: from mail-yk0-x232.google.com (mail-yk0-x232.google.com [IPv6:2607:f8b0:4002:c07::232]) (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 9D2141A00E4 for <tram@ietf.org>; Thu, 27 Aug 2015 11:52:02 -0700 (PDT)
Received: by ykbi184 with SMTP id i184so30088540ykb.2 for <tram@ietf.org>; Thu, 27 Aug 2015 11:52:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=EIoFwZENqHzmGx973G6MV3ip2b6iqOngrxGg5pws1to=; b=qPPwYmd7E6CVAYBMnljYscxl6dxMfw09sB/clX6rR1mqqCw88Xnel7CBTyQAfnTS1S CIcUECbceS32AzP2TI2MT5rMwaxsvpHGjIOOI3fGgxaGZdACJDZM/PCaGmW3UmuWUEYB uh/+4Q3P10mI88axbzhIXOxBirC5sh+y/ZdmJELJjK4/4YhbRQBp+Etcnn+oVo0sTbIu DtEaz9pPHo2sqF4lieEVN0Vy5FBGGOpmW1FbxMkcRNb1Q8m4c3iMmonVDiu3lQUy7djP m5x3pPYDVY9xnfzetp3bd0mt2+MlrMScJHS2S/NTth5qrYuri5iLzayV9jFpRGIK34xl Ud5Q==
MIME-Version: 1.0
X-Received: by 10.170.57.202 with SMTP id 193mr4750828ykz.118.1440701521983; Thu, 27 Aug 2015 11:52:01 -0700 (PDT)
Received: by 10.129.133.130 with HTTP; Thu, 27 Aug 2015 11:52:01 -0700 (PDT)
In-Reply-To: <86104CAD-44A6-4C33-BA62-DF15AEE844B5@iii.ca>
References: <CAKhHsXGwB1vovKQYaGnoZ1MuzREbDA8cTp4sCePNc6=saKN5BA@mail.gmail.com> <CABkgnnVef2voSb1i_uKZPjSimYw7Zxooh5wZh=ZmnuLeFj0Hrw@mail.gmail.com> <86104CAD-44A6-4C33-BA62-DF15AEE844B5@iii.ca>
Date: Thu, 27 Aug 2015 11:52:01 -0700
Message-ID: <CABkgnnUkJCyHsYr+tFLsaaRw1vq8-0wFgzjZ8_3F=F0C+zhP+g@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/tram/nszRbZ1Enc_CMIRcAq0buEnSnaE>
Cc: Alan Johnston <alan.b.johnston@gmail.com>, "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] Path Forward for STUN ORIGIN - refer policy
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Aug 2015 18:52:04 -0000

On 27 August 2015 at 06:41, Cullen Jennings <fluffy@iii.ca> wrote:
> The solution you are proposing puts the control of if the information is shared in the hands of the website. I'm pretty sure man websites will choose "yep, share the origin". The privacy issue raised was more about if the protecting the interests of the user of the browser and not so concerned with what the website wanted.

I think that you are mischaracterizing it.  I'm asking sites that want
to share this information to go out of their way to do so.  Just not a
lot out of their way - which isn't that hard in practice.

I don't want this to be exposed by default, if that wasn't already clear.

Also, I didn't think of it before, but the proposal that Alan made
doesn't work if you are authenticating the TURN server.

v2.23.0 | Report a Bug | By Email