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 1

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 2 Background TURN Flowdata

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

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

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

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

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

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

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

Backup Slides 10 TURN Flowdata

FLOWDATA format: Request uLTRSVD1 Attribute Type (TBD)Length (4) uDTuJTdLTdDTdJT 11 RSVD2 TURN Flowdata Upstream Delay Tolerance Downstream Delay Tolerance 0 = No information available. 1 = very low 2 = low 3 = medium 4 = high

FLOWDATA format: Response AuLTRSVD1 Attribute Type (TBD)Length (4) AuDTuAJTAdLTAdDTAdJT 12 RSVD2 TURN Flowdata Accommodated Upstream Delay Tolerance Accommodated Downstream Delay Tolerance 0 = No information available. 1 = very low 2 = low 3 = medium 4 = high