1 / 12

TURN extension to convey flow characteristics

This draft discusses the integration of flow characteristics into the TURN protocol, which acts as a relay for data regarding applications such as WebRTC. It addresses the inherent challenges faced during high-traffic scenarios, wherein prioritizing different traffic types becomes crucial. The proposed solution introduces a FLOWDATA attribute within STUN messages that allows clients to request specific flow characteristics, while servers can respond with available capabilities. This approach aims to improve traffic management, support NAT traversal, enhance privacy, and maintain performance across different network conditions.

carver
Télécharger la présentation

TURN extension to convey flow characteristics

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TURN extension to convey flow characteristics draft-wing-tsvwg-turn-flowdata-00 July 2014, IETF 90 Meeting Authors: Dan Wing, Tiru Reddy, Brandon Williams, Ram Ravindranath TURN Flowdata

  2. Background • TURN relays data • Sort of like SOCKS or an application proxy • Applications like WebRTC may use TURN • Privacy • NAT/Firewall traversal • Mobility • IPv6/IPv4 interworking • Enterprise auditing / policy control TURN Flowdata

  3. Background TURN server could be deployed by a third party provider or application service provider TURN Flowdata

  4. Problem Statement • TURN server and its network are impacted by traffic using the TURN server • During high traffic, it is desirable to shed less-important traffic TURN Flowdata

  5. Existing Solutions • DPI by TURN service provider • Encrypted traffic • Cost • DSCP • DSCP values not preserved • OS might not allow setting DSCP TURN Flowdata

  6. TURN Flowdata message flow TURN Client TURN Server Peer Allocate Request/Response Channel Bind request with FLOWDATA attribute flow is prioritized Channel Bind response with FLOWDATA attribute Channel Data Data TURN Flowdata

  7. Flowdata format • Flowdata does not communicate Diffserv code points • Flowdataconveys: • Jitter/loss/delay tolerance (high/med/low) PCP Authentication Requirements

  8. Proposed Solution • Define STUN FLOWDATA attribute • Client sends requested flow characteristics • Server responds with what can be provided PCP Authentication Requirements

  9. draft-wing-tsvwg-turn-flowdata-00 Questions? TURN Flowdata

  10. Backup Slides TURN Flowdata

  11. FLOWDATA format: Request Attribute Type (TBD) Length (4) uDT uLT uJT RSVD1 dDT dLT dJT RSVD2 Upstream Delay Tolerance Downstream Delay Tolerance • 0 = No information available. • 1 = very low • 2 = low • 3 = medium • 4 = high TURN Flowdata

  12. FLOWDATA format: Response Attribute Type (TBD) Length (4) AuDT AuLT uAJT RSVD1 AdDT AdLT AdJT RSVD2 Accommodated Downstream Delay Tolerance Accommodated Upstream Delay Tolerance • 0 = No information available. • 1 = very low • 2 = low • 3 = medium • 4 = high TURN Flowdata

More Related