Skip to content
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

Section 2.5.1 Fingerprint attribute #64

aboba opened this issue Apr 16, 2014 · 4 comments

Section 2.5.1 Fingerprint attribute #64

aboba opened this issue Apr 16, 2014 · 4 comments


Copy link

aboba commented Apr 16, 2014

The current editor's draft has a typo in the description of the fingerprint attribute in Section 2.5.1:

fingerprint of type sequence
attribute" defined in [RFC4572].

This should probably say:
"The fingerprint attribute is a sequence of DOMStrings, each containing a hash-function algorithm and fingerprint, in the syntax defined in [RFC4572] Section 5."

Copy link

juberti commented Apr 17, 2014

Should this not be a structured object with .algorithm and .value members?

Copy link

Agree with Justin. I'd rather not use DOMString either. ArrayBuffer seems most appropriate for binary data. Producing strings from those is pretty straightforward.

Copy link
Contributor Author

aboba commented Apr 29, 2014

How about this?

dictionary RTCDtlsParameters {
RTCDtlsRole role = "auto";
sequence fingerprint;
dictionary RTCDtlsFingerprint {
DOMString algorithm;
DOMString value;

Dictionary RTCDtlsFingerprint Members

algorithm of type DOMString
One of the the hash function algorithms defined in the 'Hash function Textual Names' registry, initially specified in [RFC4572] Section 8.

value of type DOMString
The value of the certificate fingerprint, expressed utilizing the syntax of 'fingerprint' in [RFC4572] Section 5.

Copy link

robin-raymond pushed a commit to robin-raymond/ortc that referenced this issue Apr 29, 2014
- Support for contributing sources removed (re-classified as a 1.2 feature), as described in w3c#27
- Cleanup of DataChannel construction, as described in w3c#60
- Separate proposal on simulcast/layering, as described in w3c#61
- Separate proposal on quality, as described in w3c#62
- Fix for TCP candidate type, as described in w3c#63
- Fix to the fingerprint attribute, as described in w3c#64
- Fix to RTCRtpFeatures, as described in w3c#65
- Support for retrieval of remote certificates, as described in w3c#67
- Support for ICE error handling, described in w3c#68
- Support for Data Channel send rate control, as described in w3c#69
- Support for capabilities and settings, as described in w3c#70
- Removal of duplicate RTCRtpListener functionality, as described in w3c#71
- ICE gathering state added, as described in w3c#72
- Removed ICE role from the ICE transport constructor, as described in w3c#73
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

4 participants