Subject: Re: [tram] ALPN identifiers for STUN and TURN

From: "Tirumaleswar Reddy (tireddy)" <[email-masked]>
Date: Wed, 6 Aug 2014 14:57:19 +0000

Protocols like peer to peer streaming protocol (PPSP) are also using TURN to upload/download content (or chunks) from remote peers.  The TURN APLN identifier would be useful for coarse-grain policy enforcement on firewall to ensure that only the Enterprise TURN server is selected by the clients for various applications and the TURN servers provided by application server and access network are not used. If additional information is also conveyed like WebRTC, PPSP etc. it could help firewalls to enforce granular policies. 

-Tiru

> -----Original Message-----
> From: tram [mailto:[email-masked]] On Behalf Of Martin Thomson
> Sent: Tuesday, August 05, 2014 12:06 AM
> To: Prashanth Patil (praspati)
> Cc: [email-masked]; Justin Uberti
> Subject: Re: [tram] ALPN identifiers for STUN and TURN
> 
> On 4 August 2014 05:43, Prashanth Patil (praspati) <[email-masked]>
> wrote:
> > Right, the intent was that it could be useful for a firewall to
> > identify a (D)TLS flow as TURN traffic, especially when sent over 443.
> 
> 
> Note however that this is nearly information-free.  A TURN binding can be
> used for literally anything.
> 
> _______________________________________________
> tram mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/tram