Metadata discovery for third party authorized TURN session
draft-reddy-tram-token-metadata-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2016-03-19 (latest revision 2015-09-16) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-reddy-tram-token-metadata-01.txt
Abstract
The operator of the TURN server might want to have fine grained control on the clients usage of the server resources for providing features such as limiting the bandwidth usage, number of allocations and so on. This document proposes a generic mechanism for the operator to introspect the access token to retrieve any policy restrictions imposed by the authorization server on the TURN server resources assigned to the client.
Authors
Reddy K
(tireddy@cisco.com)
Suhas Nandakumar
(snandaku@cisco.com)
Dan Wing
(dwing@cisco.com)
Brandon Williams
(brandon.williams@akamai.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)