W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2021

[webrtc-pc] what error is thrown for an SDP without a a=fingerprint attribute (#2672)

From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
Date: Fri, 27 Aug 2021 06:19:55 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-980914024-1630045193-sysbot+gh@w3.org>
fippo has just created a new issue for https://github.com/w3c/webrtc-pc:

== what error is thrown for an SDP without a a=fingerprint attribute ==
Writing a test about rejecting SDES I found that browsers differ in the type of error they reject the following with:
```
const sdp = `v=0
o=- 0 3 IN IP4 127.0.0.1
s=-
t=0 0
m=video 9 UDP/TLS/RTP/SAVPF 100
c=IN IP4 0.0.0.0
a=rtcp-mux
a=sendonly
a=mid:video
a=rtpmap:100 VP8/90000
a=fmtp:100 max-fr=30;max-fs=3600
a=crypto:0 AES_CM_128_HMAC_SHA1_80 inline:2nra27hTUb9ilyn2rEkBEQN9WOFts26F/jvofasw
a=ice-ufrag:ETEn
a=ice-pwd:OtSK0WpNtpUjkY4+86js7Z/l
`;

promise_test(async t => {
  const pc = new RTCPeerConnection();
  t.add_cleanup(() => pc.close());

  
  return promise_rejects_dom(t, 'SomeError',
    pc.setRemoteDescription({type: 'offer', sdp}));
}, 'rejects a remote offer that only includes SDES and no DTLS');
```
Chrome rejects with `InvalidAccessError`
Firefox with `OperationError`
This suggests they run into different branches of step 4
https://w3c.github.io/webrtc-pc/#set-description
either
```
6. If the content of description is invalid, then reject p with a newly created
  InvalidAccessError and abort these steps.
7. For all other errors, reject p with a newly created OperationError.
```
Which one is correct?

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2672 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 27 August 2021 06:19:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 27 August 2021 06:19:58 UTC