This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20813 - Protocol security not defined
Summary: Protocol security not defined
Status: RESOLVED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Web RTC Working Group
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-29 18:15 UTC by Matthew Kaufman
Modified: 2014-10-28 18:44 UTC (History)
2 users (show)

See Also:

Attachments

Description Matthew Kaufman 2013-01-29 18:15:52 UTC 
The WebRTC draft does not provide, or reference, an explanation of how media is secured.  DTLS-SRTP is mentioned once, two lines above the change log without citation. References to 'SDP' are also inadequate to explain how to secure media using the API.
Comment 1 Harald Alvestrand 2014-10-28 18:44:28 UTC 
Closing as "this is the IETF's problem".

We do have a normative dependency on rtcweb-security-arch.