Thanks Jon, will update draft. -Tiru > -----Original Message----- > From: Joe Touch <touch@xxxxxxxxxxxxxx> > Sent: Wednesday, June 26, 2019 8:55 PM > To: Benjamin Kaduk <kaduk@xxxxxxx> > Cc: Konda, Tirumaleswar Reddy <TirumaleswarReddy_Konda@xxxxxxxxxx>; > Magnus Westerlund <magnus.westerlund@xxxxxxxxxxxx>; tsv-art@xxxxxxxx; > draft-ietf-tram-turnbis.all@xxxxxxxx; ietf@xxxxxxxx; > brandon.williams@xxxxxxxxxx; tram@xxxxxxxx > Subject: Re: [Tsv-art] [tram] Tsvart last call review of draft-ietf-tram-turnbis- > 25 > > > > Minor suggestions: > > > On Jun 26, 2019, at 6:37 AM, Benjamin Kaduk <kaduk@xxxxxxx> wrote: > > > > On Wed, Jun 26, 2019 at 10:32:48AM +0000, Konda, Tirumaleswar Reddy > wrote: > >> As per the suggestion from Magnus, modified text as follows: > >> > >> TCP connection between the TURN client and server can use TCP-AO > >> [RFC5925] but UDP does not provide a similar type of authentication until > UDP supports authentication option. > > (an equivalent? a similar?) and cite draft-ietf-tsvwg-udp-options > > >> If TCP-AO would be used between TURN client and server, it would not > >> change the end-to-end security properties of > > Even if both TCP-AO and UDP authentication were both used between... > > >> the UDP payload being relayed. > >> Therefore applications using TURN will need to secure their application > data end-to-end appropriately, e.g. SRTP for RTP applications. > > Joe
