New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Normative versus Non-Normative References #133

Closed
aboba opened this Issue Jul 15, 2014 · 1 comment

Comments

Projects
None yet
1 participant
@aboba
Copy link
Contributor

aboba commented Jul 15, 2014

All of the references in the document are currently normative. However, looking at the WebRTC 1.0 specification, there are a number of non-normative references that are normative in the ORTC API specification. Is this intentional?

For example, some of the following references might be considered Informative:

Informative references

[RFC3389]
R. Zopf. Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN). September 2002. Proposed Standard. URL: http://www.ietf.org/rfc/rfc3389.txt
[RFC4587]
R. Even. RTP Payload Format for H.261 Video Streams. August 2006. Proposed Standard. URL: http://www.ietf.org/rfc/rfc4587.txt
[RFC5109]
A. Li, Ed.. RTP Payload Format for Generic Forward Error Correction. December 2007. Proposed Standard. URL: http://www.ietf.org/rfc/rfc5109.txt
[RFC5322]
P. Resnick, Ed.. Internet Message Format. October 2008. Draft Standard. URL: http://www.ietf.org/rfc/rfc5322.txt
[RFC5583]
T. Schierl; S. Wenger. Signaling Media Decoding Dependency in the SDP. July 2009. RFC. URL: http://tools.ietf.org/html/rfc5583
[RFC6184]
Y.-K.. Wang; R. Even; T. Kristensen; R. Jesup. RTP Payload Format for H.264 Video. May 2011. RFC. URL: http://tools.ietf.org/html/rfc6184
[RFC6190]
S. Wenger; Y.-K. Wang; T. Schierl; A. Eleftheriadis. RTP Payload Format for Scalable Video Coding. May 2011. RFC. URL: http://tools.ietf.org/html/rfc6190
[RFC6455]
I. Fette; A. Melnikov. The WebSocket Protocol. December 2011. RFC. URL: http://tools.ietf.org/html/rfc6455
[RFC6681]
M. Watson; T. Stockhammer; M. Luby. Raptor Forward Error Correction (FEC) Schemes for FECFRAME. August 2012. Proposed Standard. URL: http://www.ietf.org/rfc/rfc6681.txt
[VP8-RTP]
P. Westin; H. Lundin; M. Glover; J. Uberti; F. Galligan. RTP Payload Format for VP8 Video. 10 February 2014. Internet Draft (work in progress). URL: http://tools.ietf.org/html/draft-ietf-payload-vp8
[WEBRTC10]
Adam Bergkvist; Daniel Burnett; Cullen Jennings; Anant Narayanan. WebRTC 1.0: Real-time Communication Between Browsers. 10 September 2013. W3C Working Draft. URL: http://www.w3.org/TR/webrtc/
[WEBSOCKETS-API]
Ian Hickson. The WebSocket API. 20 September 2012. W3C Candidate Recommendation. URL: http://www.w3.org/TR/websockets/

robin-raymond pushed a commit to robin-raymond/ortc that referenced this issue Jul 16, 2014

Robin Raymond
Added section on WebRTC 1.0 compatibility issues, responding to Issue w…
…3c#66

Added Identity support, as described in Issue w3c#78
Reworked getStats method, as described in Issue w3c#85
Removed ICE restart method described in Issue w3c#93
Addressed CNAME and synchronization context issues described in Issue w3c#94
Fixed WebIDL issues noted in Issue w3c#97
Addressed NITs described in Issue w3c#99
DTLS transport issues fixed as described in Issue w3c#100
ICE transport issues fixed as described in Issue w3c#101
ICE transport controller fixes made as described in Issue w3c#102
Sender and Receiver object fixes made as described in Issue w3c#103
Fixed RTCRtpEncodingParameter default issues described in Issue w3c#104
Fixed 'Big Picture' issues descibed in Issue w3c#105
Fixed RTCRtpParameter default issues described in Issue w3c#106
Added a multi-stream capability, as noted in Issue w3c#108
Removed quality scalability capabilities and parameters, as described in Issue w3c#109
Added scalability examples as requested in Issue w3c#110
Addressed WebRTC 1.0 Data Channel compatibility issue described in Issue w3c#111
Removed header extensions from RTCRtpCodecParameters as described in Issue w3c#113
Addressed RTP/RTCP non-mux issues with IdP as described in Issue w3c#114
Added getParameter methods to RTCRtpSender and RTCRtpReceiver objects, as described in Issue w3c#116
Added layering diagrams as requested in Issue w3c#117
Added a typedef for payload type, as described in Issue w3c#118
Moved onerror from the RTCIceTransport object to the RTCIceListener object as described in Issue w3c#121
Added explanation of Voice Activity Detection (VAD), responding to Issue w3c#129
Clarified the meaning of maxTemporalLayers and maxSpatialLayers, as noted in Issue w3c#130
Added RFC 6051 to the list of header extensions and removed RFC 5450, as noted in Issue w3c#131
Addressed ICE terminology issues, as described in Issue w3c#132
Separated references into Normative and Informative, as noted in Issue w3c#133
@aboba

This comment has been minimized.

Copy link
Contributor

aboba commented Jul 17, 2014

Here is a list of references that are either:

  1. Informative in WebRTC 1.0 API;
  2. Not referenced normatively in any IETF RTCWEB WG work item;
  3. Are no better than OPTIONAL in any IETF RTCWEB WG work items.

Potential Informative references

[APPID](not mentioned in RTP-USAGE)
R. Even; J. Lennox; Q. Wu. The Session Description Protocol (SDP) Application Token Attribute. 11 April 2014. Internet Draft (work in progress). URL: http://tools.ietf.org/html/draft-even-mmusic-application-token

[RFC3389](Not mentioned in AUDIO or RTP-USAGE)
R. Zopf. Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN). September 2002. Proposed Standard. URL: http://www.ietf.org/rfc/rfc3389.txt

[RFC4587](No MTI recommendation in VIDEO)
R. Even. RTP Payload Format for H.261 Video Streams. August 2006. Proposed Standard. URL: http://www.ietf.org/rfc/rfc4587.txt

[RFC5109](No FEC recommendation in RTP-USAGE)
A. Li, Ed.. RTP Payload Format for Generic Forward Error Correction. December 2007. Proposed Standard. URL: http://www.ietf.org/rfc/rfc5109.txt

[RFC5322](Informative in WebRTC 1.0)
P. Resnick, Ed.. Internet Message Format. October 2008. Draft Standard. URL: http://www.ietf.org/rfc/rfc5322.txt

[RFC5583](Not mentioned in RTP-USAGE)
T. Schierl; S. Wenger. Signaling Media Decoding Dependency in the SDP. July 2009. RFC. URL: http://tools.ietf.org/html/rfc5583

[RFC6184](No MTI recommendation in VIDEO)
Y.-K.. Wang; R. Even; T. Kristensen; R. Jesup. RTP Payload Format for H.264 Video. May 2011. RFC. URL: http://tools.ietf.org/html/rfc6184

[RFC6190](No MTI recommendation in VIDEO)
S. Wenger; Y.-K. Wang; T. Schierl; A. Eleftheriadis. RTP Payload Format for Scalable Video Coding. May 2011. RFC. URL: http://tools.ietf.org/html/rfc6190

[RFC6455](Informative in WebRTC 1.0)
I. Fette; A. Melnikov. The WebSocket Protocol. December 2011. RFC. URL: http://tools.ietf.org/html/rfc6455

[RFC6465](OPTIONAL in RTP-USAGE)
E. Ivov; E. Marocco; J. Lennox. A Real-time Protocol (RTP) Header Extension for Mixer-to-Client Audio Level Indication. December 2011. RFC. URL: http://tools.ietf.org/html/rfc6465

[RFC6681](No FEC recommendation in RTP-USAGE)
M. Watson; T. Stockhammer; M. Luby. Raptor Forward Error Correction (FEC) Schemes for FECFRAME. August 2012. Proposed Standard. URL: http://www.ietf.org/rfc/rfc6681.txt

[VP8-RTP](No MTI recommendation in VIDEO)
P. Westin; H. Lundin; M. Glover; J. Uberti; F. Galligan. RTP Payload Format for VP8 Video. 10 February 2014. Internet Draft (work in progress). URL: http://tools.ietf.org/html/draft-ietf-payload-vp8

[WEBSOCKETS-API](Non-normative in WebRTC 1.0)
Ian Hickson. The WebSocket API. 20 September 2012. W3C Candidate Recommendation. URL: http://www.w3.org/TR/websockets/

@aboba aboba closed this Jul 17, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment