You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a way know when a peer is dead so we can free up resources (e.g., session keys) allocated to that peer. This requires us to tell apart nodes that are dead from nodes that are still alive but simply there's not been any need to exchange data recently. A simple keepalive protocol (like TCP's) would satisfy this, and it'd also allow us to continue rotating session keys.
The text was updated successfully, but these errors were encountered:
gnarea
changed the title
Draft "session keepalive" protocol to identify dead nodes and keep session alive with live-yet-inactive nodes
Draft "session keepalive" protocol to identify dead nodes and keep session alive with inactive nodes
Apr 27, 2020
gnarea
changed the title
Draft "session keepalive" protocol to identify dead nodes and keep session alive with inactive nodes
Draft "session keepalive" protocol to identify dead nodes and to rotate session keys with inactive nodes
Apr 27, 2020
gnarea
changed the title
Draft "session keepalive" protocol to identify dead nodes and to rotate session keys with inactive nodes
Draft "session keepalive" protocol to identify dead nodes and rotate session keys with inactive nodes
Apr 27, 2020
gnarea
changed the title
Draft "session keepalive" protocol to identify dead nodes and rotate session keys with inactive nodes
Draft "channel keepalive" protocol to identify dead nodes and rotate session keys with inactive nodes
Apr 27, 2020
Executive summary
We need a way know when a peer is dead so we can free up resources (e.g., session keys) allocated to that peer. This requires us to tell apart nodes that are dead from nodes that are still alive but simply there's not been any need to exchange data recently. A simple keepalive protocol (like TCP's) would satisfy this, and it'd also allow us to continue rotating session keys.
The text was updated successfully, but these errors were encountered: