WebRTC: Trickle RFC

[cappentz]

In 5.2.6 trickle:

An ONVIF compliant signaling server, device and client shall support this command to signal new ICE candidates for the trickleICE procedure as defined in RFC 8840.

Both client and device produce ICE candidates and send them to each other, via the server. Once all ICE candidates have been sent by a peer, it shall send a last trickle notification with an empty ICE candidate content to indicate that all candidates have been sent according to RFC 8838.

Is the RFC 8840 reference correct? The RFC talks about SIP INFO messages?

[cappentz]

In 6.4 ICE candidates
A device shall support generating and receiving host, server reflexive and relay ICE candidates as defined in RFC 8445.
A device shall handle passive ICE TCP candidates as defined in RFC 6544. On reception, it shall generate an active ICE TCP candidate to match and establish a TCP connection to the endpoint announced by the candidate. A device is not required to listen on a TCP endpoint and generate a passive ICE TCP candidate.

RFC 8845 is referenced, not the trickle version RFC 8838.

[jmelancongen]

The RFC 8840 reference seems incorrect, it looks like it should have been 8838 there.

Concerning section 6.4, I think this one is fine, as it talks about the different types of candidates that are to be handled, and those are described in details in RFC 8445 (although, they are transported according to 8838).

I just skimmed the specs though, so I might have missed a key point

[sujithhanwha]

@cappentz , would you be filing a PR for this ?

[cappentz]

Yes, just need to double check some details