Re: Issue 64: Section 2.5.1 Fingerprint attribute

I agree. The JS app shouldn't need to deal with the fingerprint as an
ArrayBuffer, it is largely an opaque blob. As such, keeping it in a format
that can be easily serialized makes sense to me.


On Tue, Apr 22, 2014 at 10:14 AM, Robin Raymond <robin@hookflash.com> wrote:

>
> I think the algorithm should be a DOMString based on section 8 of rfc 4572
> IANA registry.
>
> As for the value, I think it might be easiest if we simply made it a hex
> string for easy string validation. Then the silly debate is always
> lowercase vs uppercase and I think there's been a general move towards
> lowercase for hash strings used for verification but I don't know if we
> should mandate lower, especially consider RFC 4572 uses uppercase which is
> against the current trend. I don't have a strong opinion here and a binary
> array would solve upper vs lower issue because binary would be the "raw"
> hash value. But then most people would need to write a binary to string
> conversion routine anyway to send the information to a remote party over
> the wire.
>
> -Robin
>
>
>   Justin Uberti <juberti@google.com>
>  April 18, 2014 at 4:50 PM
> That mostly LGTM. Is |value| expected to be hex or binary?
>
>
>
>   Bernard Aboba <Bernard.Aboba@microsoft.com>
>  April 18, 2014 at 4:07 PM
> How about this:
>
> dictionary RTCDtlsParameters {
> RTCDtlsRole role = "auto";
> sequence<RTCDtlsFingerprint> fingerprint;
> };
>
>
> dictionary RTCDtlsFingerprint {
> RTCDtlsCertificateHashAlgorithm algorithm;
> ArrayBuffer value;
> };
>
>
> enum RTCDtlsCertificateHashAlgorithm {
> "sha-1",
> "sha-224",
> "sha-256",
> "sha-384",
> "sha-512"
> };
>
> ________________________________________
> From: Bernard Aboba [Bernard.Aboba@microsoft.com]
> Sent: Wednesday, April 16, 2014 11:02 AM
> To: public-ortc@w3.org
> Subject: Issue 64: Section 2.5.1 Fingerprint attribute
>
> The current editor's draft has a typo in the description of the
> fingerprint attribute in Section 2.5.1:
>
> fingerprint of type sequence<DOMString>
> 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."
>
>   Bernard Aboba <Bernard.Aboba@microsoft.com>
>  April 16, 2014 at 2:02 PM
> The current editor's draft has a typo in the description of the
> fingerprint attribute in Section 2.5.1:
>
> fingerprint of type sequence<DOMString>
> 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."
>
>