Juliusz Chroboczek
Juliusz Chroboczek
No, the provided trace only contains Update TLVs with the new encoding. The new encoding is also allowed in Request TLVs, but they are NOT RECOMMENDED by the RFC, and...
This issue is about the case when `ICETransportPolicy`=`ICETransportPolicyRelay`. There can be no server-refexive candidates in that case, so it's safe to skip the initial delay. The general case is interesting...
> Only thing I would like to note is that most torrent clients out there have an issue where they leak the permanent SLAAC address. That's quite easy to avoid,...
> I understand that it's difficult to rollback the entire commit, but is is practical to submit a PR to undo actual functionality changes I believe that the proper way...
@AlexVulaj, the problem is that since 666c197 is so large and undocumented, it is impossible to review. If you want us to trust gorilla/websocket again, you need to revert 666c197,...
@AlexVulaj This is not a mere desire. There is simply no way to review that commit, and hence there is no way to convince ourselves that no erroneous or even...
The problematic commit has been in the repository for almost eight months now, and has still not been reverted. At this point, I find it very difficult to trust the...
@tmatth I'm pretty sure your patch is not correct. IsPartitionHead should be checking the Z bit in the AV1 aggregation header. That's bit 0x80, see https://aomediacodec.github.io/av1-rtp-spec/#44-av1-aggregation-header. You'll also need some...
Right. Neighbours are indexed by (adress, interface). It is perfectly normal to see the same neighbour on two interfaces: if a router A has two radios tuned at the same...