- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Sat, 03 Dec 2016 22:58:07 +0000
- To: public-webrtc-logs@w3.org
I'd be hesitant to claim that it's normal to send refresh(0) when freeing a TURN candidate. RFC 5766 only says (section 5): The time-to-expiry is the time in seconds left until the allocation expires. Each Allocate or Refresh transaction sets this timer, which then ticks down towards 0. By default, each Allocate or Refresh transaction resets this timer to the default lifetime value of 600 seconds (10 minutes), but the client can request a different value in the Allocate and Refresh request. Allocations can only be refreshed using the Refresh request; sending data to a peer does not refresh an allocation. When an allocation expires, the state data associated with the allocation can be freed. Only use of the word "freed" I could find. But yes, knowing if a candidate has been freed makes sense. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/89#issuecomment-264671349 using your GitHub account
Received on Saturday, 3 December 2016 22:58:17 UTC