IETF Logo Mail Archive

Re: [tram] stun-origin status==? Is it dead?

Alan Johnston <alan.b.johnston@gmail.com> Wed, 18 January 2017 13:39 UTC

Return-Path: <alan.b.johnston@gmail.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD55D1296D3 for <tram@ietfa.amsl.com>; Wed, 18 Jan 2017 05:39:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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] 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 ov-CMeJ15RX7 for <tram@ietfa.amsl.com>; Wed, 18 Jan 2017 05:39:55 -0800 (PST)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 A7B811296D2 for <tram@ietf.org>; Wed, 18 Jan 2017 05:39:54 -0800 (PST)
Received: by mail-wm0-x22b.google.com with SMTP id r144so25535312wme.1 for <tram@ietf.org>; Wed, 18 Jan 2017 05:39:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YhRLh/f+hrmCX5wxKu/215IpBf7FU/NHYCLC33rGBDk=; b=HaEvxUIdken7nAnAuUkyUgM98Ry2I7X55ukHbIvNiA4eslmKqnp5Zzn2yiJ2D1MwLi B6HdUCb5W1YhCnIkM21WRKzlQDbKhQVX38QZWbs2rSMxpaVjP7tL7D1j7lKVoWUvxJ2B w4PZ/W2X/6DzN3jmytmRl8xbBoDhelUSgjsjTnM1vaNBuBWGEFKgINKglErHeO/4v6xx n0NahEigD1yrRDguKt6bd+p5JJS1V+5TjSAJ+nIVOVjZWoHUXBSprVRxXZz9GRM44/eN 465rO4F1fXk1vWkLckMt2jsuBATaMAYf47eucx1In2b3I7g9ZFepSDNcHRJMRNunqDdp R3fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YhRLh/f+hrmCX5wxKu/215IpBf7FU/NHYCLC33rGBDk=; b=r9jDdgr6s/H+FMfLWpzKLrgzCPZSnRhNvDyCbdQTDlNIJc3QzPRRpulXSOUmejuc2l 0Pgc2cFEMCB+gB6HtC1AIqMjdIzcIGcU5V2TQOIXrrM/15uEOH+U9Pmlu5zMsD2GGG+I 93WS3tl9f+kauD3AmeXP9xt9cixWhvWiojb2m0Xd6oSzz7v0z/sy058QzYzIGsuBpAPn NCClQoCtlBwDW/PkXdqhrWVMni62tep2Xn/oczT1ghdRq5npcDkhrR3c4E7abJHXgAK5 9gycB/NDBEAzTKXiuYtDQ3SpKQtUqlSlQbc43TawfSXFQuGDY9s0z+ObATDb3Rxs2Jcx VEyQ==
X-Gm-Message-State: AIkVDXLLqZgBNdD9bSTAA+/JyfZtt61aYiF3aoxtvkvo+vAV6117aNxWTTsWtwVPWIAhin3soTjbzgGv0jt5wA==
X-Received: by 10.28.11.135 with SMTP id 129mr15567815wml.111.1484746793091; Wed, 18 Jan 2017 05:39:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.171.8 with HTTP; Wed, 18 Jan 2017 05:39:52 -0800 (PST)
In-Reply-To: <d11e7647-2c3b-f9bd-1228-ac5532835b8b@niif.hu>
References: <d11e7647-2c3b-f9bd-1228-ac5532835b8b@niif.hu>
From: Alan Johnston <alan.b.johnston@gmail.com>
Date: Wed, 18 Jan 2017 05:39:52 -0800
Message-ID: <CAKhHsXGBXHO0pmtt9M_y96_2LPvwD=ASm84C2pXQNmzdy6qf4A@mail.gmail.com>
To: Mészáros Mihály <misi@niif.hu>
Content-Type: multipart/alternative; boundary="001a1144514e2f063305465e8d5d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/rKb19tMU71Wn4BootKOOtIi0z54>
Cc: hcornflower@appear.in, deadbeef@webrtc.org, Oleg Moskalenko <mom040267@gmail.com>, juberti@webrtc.org, "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] stun-origin status==? Is it dead?
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 18 Jan 2017 13:39:57 -0000

Hi Misi,

Yes, it is dead.  While the mechanism is convenient, it leaks too much
meta-data so the working group abandoned the effort.

- Alan -

On Wed, Jan 18, 2017 at 3:45 AM, Mészáros Mihály <misi@niif.hu> wrote:

> Hi,
>
> I am planning to build a multi realm TURN service that would use multi
> realm feature in coturn.
>
> But I sadly realized that there was some for me not very clear IETF
> concerns and somehow writing draft-ietf-tram-stun-origin has been stopped..
>
> I am wondering what is the WG position about this draft status and future?
>
> I need this multi domain to avoid server duplication:
>
>    - I need to use multi realm to reuse TURN servers and separate user
>    credential domains, to avoid TURN server duplication for every realm in
>    every region.
>    - If this origin way could not be fixed then then I don't see any way
>    to make a multi realm TURN service.
>    (coTURN name is based on this feature AFAIK.)
>    - If we don't send any information from client side that could be use
>    on coTURN side to identify user credential realm than coTRUN multidomain
>    feature could not be used at all.. :(
>
> I am wondering if you know what was the main concern about in IESG/IETF
> tram?
>
> And if this is final or not? Could it be somehow work it out?
>
> Why is it a show stopper concern?
>
> Is it possible to make any workaround to make it possible to send any
> realm related info to to turn server ?
>
> I read the connected tram list mails and the ballot
> <https://datatracker.ietf.org/doc/draft-ietf-tram-stun-origin/ballot/>,
> but still not clear for me the main concern, and the actual status.
>
> (The hardest concern was I think Stephen Farrell concerns, but I feel it
> could be addressed.)
>
> Unfortunately I saw all WebRTC browsers stopped implementing it.
>
>    - https://bugzilla.mozilla.org/show_bug.cgi?id=1123722
>    - https://bugs.chromium.org/p/webrtc/issues/detail?id=4091#c10
>
> All in all I would like to know the reasons behind Justin statement:
>
> This feature is dead. We should plan to remove the code when convenient.
>
> I would like to turn it back if possible and find a way to make multi
> realm TURN work.
>
> Any comments would be highly appreciated!
>
> Thanks,
> Misi
>
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
>
>

v2.23.0 | Report a Bug | By Email