Justin Uberti
Justin Uberti
are you thinking the candidates would be IPs or FQDN? If IP, how would certificate verification be handled?
TURN-TLS is well defined by RFC 5766, so we can set that aside. Here, we can either try to focus on: 1) ICE-TLS using FQDN candidates 2) ICE-TCP but with...
I was on a walk today and realized I've been thinking about this the wrong way. The issue is that we don't have a hostname to verify the cert. but...
Good suggestion. Just comes down to whether we want to put a SAN or a fingerprint in the a=candidate line. Or we could support both 😀
@pthatcherg also has https://datatracker.ietf.org/doc/html/draft-thatcher-p2p-quic-00 for sending RTP over QUIC, although it doesn't touch on how to verify certificates. I think the best path forward is to revive @martinthomson's draft as...
@Sean-Der I think Chrome will validate certs for TURN/TLS? Is that not what you were seeing? @martinthomson I agree the value of verification is less clear here than in TURN/TLS,...
Correct. Client would only verify the hostname if we used the SAN approach.
The 32 GB includes the Llama 3 finetune. With the quantization described in #8 you should be able to run on a consumer GPU.
I think this is due an incompatibility with `streaming=True`, where the length of the epoch is not known in advance.