Hi Hannes,
Please see inline
-Original Message-
From: Hannes Tschofenig [mailto:hannes.tschofe...@gmx.net]
Sent: Friday, August 22, 2014 2:06 PM
To: Tirumaleswar Reddy (tireddy); oauth@ietf.org
Cc: draft-ietf-tram-turn-third-party-au...@tools.ietf.org;
In case the UMA model of establishing and conducting loosely coupled AS-RS
relationships is of interest, you can find more information here:
http://tools.ietf.org/html/draft-hardjono-oauth-umacore-10 (for the AS's
protection API, the OAuth token securing that API, and the declaration of AS
Hi Tiru,
~snip~
* The Design
I would have used OAuth as is (or maybe selected a specific grant type) to
obtain an access token. Then, I would have defined how the access token is
carried in the TURN protocol. This is a bit similar what we have already done
with the OAuth SASL draft where we
Hi all,
Simon asked us (Derek and myself) to do a quick review of this document
developed within another working group that happens to use OAuth.
* Background
TURN is a special tunnelling gateway (very much like an IPsec gateway
would be) but designed specifically to relay voice/video traffic.
Hi Hannes,
Thanks for the review. Please see inline
-Original Message-
From: Hannes Tschofenig [mailto:hannes.tschofe...@gmx.net]
Sent: Friday, August 22, 2014 12:21 AM
To: oauth@ietf.org
Cc: draft-ietf-tram-turn-third-party-au...@tools.ietf.org;
gonzalo.camari...@ericsson.com
