{"action":"created","issue":{"url":"https://api.github.com/repos/netconf-wg/server-model/issues/43","labels_url":"https://api.github.com/repos/netconf-wg/server-model/issues/43/labels{/name}","comments_url":"https://api.github.com/repos/netconf-wg/server-model/issues/43/comments","events_url":"https://api.github.com/repos/netconf-wg/server-model/issues/43/events","html_url":"https://github.com/netconf-wg/server-model/issues/43","id":63303908,"number":43,"title":"keep-alive, linger, reconnect interval defaults OK?","user":{"login":"kwatsen","id":2255354,"avatar_url":"https://avatars.githubusercontent.com/u/2255354?v=3","gravatar_id":"","url":"https://api.github.com/users/kwatsen","html_url":"https://github.com/kwatsen","followers_url":"https://api.github.com/users/kwatsen/followers","following_url":"https://api.github.com/users/kwatsen/following{/other_user}","gists_url":"https://api.github.com/users/kwatsen/gists{/gist_id}","starred_url":"https://api.github.com/users/kwatsen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kwatsen/subscriptions","organizations_url":"https://api.github.com/users/kwatsen/orgs","repos_url":"https://api.github.com/users/kwatsen/repos","events_url":"https://api.github.com/users/kwatsen/events{/privacy}","received_events_url":"https://api.github.com/users/kwatsen/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/netconf-wg/server-model/labels/Open","name":"Open","color":"eb6420"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-03-20T20:45:47Z","updated_at":"2015-03-29T20:13:51Z","closed_at":null,"body":"Juergen:\r\n\r\n  - is there a motivation for the 15 seconds default for the call home\r\n    keep alive timer?\r\n  - is there a motivation for 30 seconds default linger time and 5\r\n    minutes default reconnect time?\r\n\r\nKent\r\n\r\nFor all of these, I just figured they were sensible choices.  Do they\r\nseem OK to you?\r\n"},"comment":{"url":"https://api.github.com/repos/netconf-wg/server-model/issues/comments/87467718","html_url":"https://github.com/netconf-wg/server-model/issues/43#issuecomment-87467718","issue_url":"https://api.github.com/repos/netconf-wg/server-model/issues/43","id":87467718,"user":{"login":"kwatsen","id":2255354,"avatar_url":"https://avatars.githubusercontent.com/u/2255354?v=3","gravatar_id":"","url":"https://api.github.com/users/kwatsen","html_url":"https://github.com/kwatsen","followers_url":"https://api.github.com/users/kwatsen/followers","following_url":"https://api.github.com/users/kwatsen/following{/other_user}","gists_url":"https://api.github.com/users/kwatsen/gists{/gist_id}","starred_url":"https://api.github.com/users/kwatsen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kwatsen/subscriptions","organizations_url":"https://api.github.com/users/kwatsen/orgs","repos_url":"https://api.github.com/users/kwatsen/repos","events_url":"https://api.github.com/users/kwatsen/events{/privacy}","received_events_url":"https://api.github.com/users/kwatsen/received_events","type":"User","site_admin":false},"created_at":"2015-03-29T20:13:51Z","updated_at":"2015-03-29T20:13:51Z","body":"This issue was discussed during and after the Dallas meeting with the\r\nfollowing status:\r\n\r\n[1]  .../connection-type/persistent/keep-alives/interval-secs:\r\nThis issue is still open - please reply on it if so inclined.  Some felt that a keep-alive every 15 seconds was too often, and suggested that a 2­ hour value would be better.   Searching on this for awhile, it seems that many use 300 seconds and many others use 15 seconds,  Note, this is a keep-alive message being sent every 15 to 300 seconds, with a default count-max of '3', results in a new connection after 45 to 900 seconds - that's 3/4 of a minute to 15 minutes to proactively bring up a failed session.  Some of the issue surrounds how the TCP-level  timeout is set. The introduction in RFC5482 says:\r\n\r\n   In the absence of an application-specified user timeout, the TCP\r\n   specification [RFC0793] defines a default user timeout of 5 minutes.\r\n   The Host Requirements RFC [RFC1122] refines this definition by\r\n   introducing two thresholds, R1 and R2 (R2 > R1), that control the\r\n   number of retransmission attempts for a single segment.  It suggests\r\n   that TCP should notify applications when R1 is reached for a segment,\r\n   and close the connection when R2 is reached.  [RFC1122] also defines\r\n   the recommended values for R1 (3 retransmissions) and R2 (100\r\n   seconds), noting that R2 for SYN segments should be at least 3\r\n   minutes.  Instead of a single user timeout, some TCP implementations\r\n   offer finer-grained policies.  For example, Solaris supports\r\n   different timeouts depending on whether a TCP connection is in the\r\n   SYN-SENT, SYN-RECEIVED, or ESTABLISHED state [SOLARIS].\r\n\r\nI wonder if we should *add* configuration know for a tcp timeout as well?\r\n\r\n\r\n[2] .../connection-type/periodic/linger-secs:\r\nThis leaf is to be removed as it is best to let the NETCONF/RESTCONF client decide when to close the session ­ the server should leave the session open, up until the /session-options/idle-timeout limit.\r\n\r\n\r\n[3] .../reconnect-strategy/interval-secs:\r\nThis leaf is to be removed.  It doesn't have enough value to leave exposed as a configurable know.\r\n\r\n\r\nDue to [1] being still open, this issue only moves to the OPEN state - not the VERIFY state.\r\n\r\nReference:  https://github.com/netconf-wg/server-model/issues/43\r\n\r\nThanks,\r\nKent"}}