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

[Mészáros Mihály <[e-mail]>]

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