[rtcweb] JSEP fingerprint hash requirements

[Kevin Dempsey <[e-mail]>]

The JSEP draft says that the fingerprint is REQUIRED to use sha-256 and
additional fingerprints using 'stronger' hashes can be included. However,
RFC 4572 says that the fingerprint hash must match the certificate's
signature algorithm. Recent chrome canary builds have stopped using sha-256
and use sha-1 as that matches their certificate's signature algorithm.

So:
1) does the fingerprinh hash need to match the certificate
2) do webrtc compatible endpoints need to handle hashes 'weaker' than
sha-256
3) are there any rules for handling multiple fingerprints?

Regards,
Kevin