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 20810 - SDP inadequately defined
Summary: SDP inadequately defined
Status: RESOLVED WONTFIX
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Web RTC Working Group
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-29 18:11 UTC by Matthew Kaufman
Modified: 2014-10-28 18:41 UTC (History)
2 users (show)

See Also:

Attachments

Description Matthew Kaufman 2013-01-29 18:11:25 UTC 
In the WebRTC draft, Section 4.7.2.1, the RTCSessionDescription interface is described as having an ‘sdp’ parameter.  The normative reference for this is RFC 3264.  RFC 3264 does not provide enough information for an implementer to successfully implement the SDP necessary to implement the complete set of features described in the document.  RFC 3264 also references an old version of the SDP RFC (RFC 2327), which contains numerous errors, misses key features and would introduce interoperability problems if it were implemented (see Section 10 of RFC 4566 for a list of problems).
Comment 1 Harald Alvestrand 2013-01-30 12:30:13 UTC 
The normative reference should be to the JSEP draft.
Comment 2 Matthew Kaufman 2013-01-30 16:19:51 UTC 
The JSEP draft, at present, is 1) not an Internet RFC and 2) does not provide sufficient specification of the SDP in order to produce an interoperable implementation, so this should stay open until both are resolved.
Comment 3 Harald Alvestrand 2014-10-28 18:41:13 UTC 
Closing as "this is the IETF's problem".

Note: There is no requirement that Candidate Recommendations' normative references have to be published as RFCs.