MIME-Version: 1.0
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: =?UTF-8?B?TcOpc3rDoXJvcyBNaWjDoWx5?= <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?
Precedence: list

--001a1144514e2f063305465e8d5d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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=C3=A9sz=C3=A1ros Mih=C3=A1ly <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 i=
n
>    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 multidoma=
in
>    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=3D1123722
>    - https://bugs.chromium.org/p/webrtc/issues/detail?id=3D4091#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
>
>

--001a1144514e2f063305465e8d5d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Misi,<div><br></div><div>Yes, it is dead.=C2=A0 While t=
he mechanism is convenient, it leaks too much meta-data so the working grou=
p abandoned the effort.</div><div><br></div><div>- Alan -</div></div><div c=
lass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Jan 18, 2017 at=
 3:45 AM, M=C3=A9sz=C3=A1ros Mih=C3=A1ly <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:misi@niif.hu" target=3D"_blank">misi@niif.hu</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
 =20

   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <p>Hi,</p>
    <p>I am planning to build a multi realm TURN service that would use
      multi realm feature in coturn.<br>
    </p>
    <p>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.. <br>
    </p>
    <p>I am wondering what is the WG position about this draft status
      and future?</p>
    <p>I need this multi domain to avoid server duplication:<br>
    </p>
    <ul>
      <li>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.</li>
      <li>If this origin way could not be fixed then then I don&#39;t see
        any way to make a multi realm TURN service. <br>
        (coTURN name is based on this feature AFAIK.)<br>
      </li>
      <li>If we don&#39;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.. :(
      </li>
    </ul>
    <p>I am wondering if you know what was the main concern about in
      IESG/IETF tram? <br>
    </p>
    <p>And if this is final or not? Could it be somehow work it out?<br>
    </p>
    <p>Why is it a show stopper concern? <br>
    </p>
    <p>Is it possible to make any workaround to make it possible to send
      any realm related info to to turn server ?<br>
    </p>
    <p>I read the connected tram list mails and the <a href=3D"https://data=
tracker.ietf.org/doc/draft-ietf-tram-stun-origin/ballot/" target=3D"_blank"=
>ballot</a>,
      but still not clear for me the main concern, and the actual
      status.</p>
    <p>(The hardest concern was I think Stephen Farrell concerns, but I
      feel it could be addressed.)<br>
    </p>
    <p>Unfortunately I saw all WebRTC browsers stopped implementing it.<br>
    </p>
    <ul>
      <li><a class=3D"m_-6070672403353451083moz-txt-link-freetext" href=3D"=
https://bugzilla.mozilla.org/show_bug.cgi?id=3D1123722" target=3D"_blank">h=
ttps://bugzilla.mozilla.org/<wbr>show_bug.cgi?id=3D1123722</a></li>
      <li><a class=3D"m_-6070672403353451083moz-txt-link-freetext" href=3D"=
https://bugs.chromium.org/p/webrtc/issues/detail?id=3D4091#c10" target=3D"_=
blank">https://bugs.chromium.org/p/<wbr>webrtc/issues/detail?id=3D4091#<wbr=
>c10</a></li>
    </ul>
    <p>All in all I would like to know the reasons behind Justin
      statement:<br>
    </p>
    <pre class=3D"m_-6070672403353451083issue_text">This feature is dead. W=
e should plan to remove the code when convenient.</pre>
    I would like to turn it back if possible and find a way to make
    multi realm TURN work.<br>
    <br>
    Any comments would be highly appreciated!<br>
    <br>
    Thanks,<br>
    Misi<br>
  </div>

<br>______________________________<wbr>_________________<br>
tram mailing list<br>
<a href=3D"mailto:tram@ietf.org">tram@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tram" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/tram</a><br>
<br></blockquote></div><br></div>

--001a1144514e2f063305465e8d5d--