|
|
|
|
|
by still_grokking
1130 days ago
|
|
Oh, that's cool! :-D It implements the missing parts on top of WebTransport. I was especially sad that WT doesn't do client authentication. You can't send credentials with a CONNECT request. But this thingy adds exactly this. Great! Also having some standardized way to open QUIC Streams through NAT sounds nice. (Even I think the proper fix for this issues would just be IPv6.) Frankly it's very early days. It's not implemented, and not even considered currently. > It is not a W3C Standard nor is it on the W3C Standards Track. But as I'm currently into implementing a WebTransport lib maybe I should try to add the features form this draft. Would be funny to have a P2P ready WT lib. Only that NAT traversal part I would leave out for now, I guess, as I'm not sold on the idea that this complexity is strictly needed. NAT just needs to die finally… |
|