Problems with Security Descriptions in RTCWEB Architecture
draft-wing-rtcweb-sdes-problems-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dan Wing | ||
| Last updated | 2013-06-21 (Latest revision 2012-12-18) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document analyzes the problems of deploying Security Descriptions on the RTCWEB architecture. This document contributes to the discussion and analysis of Security Descriptions, and is not intended to become an RFC.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)