{"action":"created","issue":{"url":"https://api.github.com/repos/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/161","repository_url":"https://api.github.com/repos/OpenMobileAlliance/OMA_LwM2M_for_Developers","labels_url":"https://api.github.com/repos/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/161/labels{/name}","comments_url":"https://api.github.com/repos/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/161/comments","events_url":"https://api.github.com/repos/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/161/events","html_url":"https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/161","id":185010559,"number":161,"title":"DTLS failure causes losing notifications","user":{"login":"kiemlicz","id":7331452,"avatar_url":"https://avatars.githubusercontent.com/u/7331452?v=3","gravatar_id":"","url":"https://api.github.com/users/kiemlicz","html_url":"https://github.com/kiemlicz","followers_url":"https://api.github.com/users/kiemlicz/followers","following_url":"https://api.github.com/users/kiemlicz/following{/other_user}","gists_url":"https://api.github.com/users/kiemlicz/gists{/gist_id}","starred_url":"https://api.github.com/users/kiemlicz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kiemlicz/subscriptions","organizations_url":"https://api.github.com/users/kiemlicz/orgs","repos_url":"https://api.github.com/users/kiemlicz/repos","events_url":"https://api.github.com/users/kiemlicz/events{/privacy}","received_events_url":"https://api.github.com/users/kiemlicz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2016-10-25T03:33:55Z","updated_at":"2016-11-04T11:06:03Z","closed_at":null,"body":"Given following information:\n\n(from CoAP Observe RFC)\n- \"All notifications resulting from a GET request with an Observe Option MUST be returned within the same epoch of the same connection as the request.\"\n- \"An acknowledgement message signals to the server that the client is alive and interested in receiving further notifications; if the server does not receive an acknowledgement in reply to a confirmable notification, it will assume that the client is no longer interested and will eventually remove the associated entry from the list of observers\" In this example, the LwM2M client is observation server.\n\nIn case of losing the DTLS state, (according to quoted RFCs) established observations are no longer valid.\nThe LwM2M server won't see any notifications (which will be ok if he didn't specify pmin and pmax), LwM2M client will drop the observation.\nIs it even possible that LWM2M server will know that something went wrong?\n"},"comment":{"url":"https://api.github.com/repos/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/comments/258404211","html_url":"https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/161#issuecomment-258404211","issue_url":"https://api.github.com/repos/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/161","id":258404211,"user":{"login":"sbernard31","id":840294,"avatar_url":"https://avatars.githubusercontent.com/u/840294?v=3","gravatar_id":"","url":"https://api.github.com/users/sbernard31","html_url":"https://github.com/sbernard31","followers_url":"https://api.github.com/users/sbernard31/followers","following_url":"https://api.github.com/users/sbernard31/following{/other_user}","gists_url":"https://api.github.com/users/sbernard31/gists{/gist_id}","starred_url":"https://api.github.com/users/sbernard31/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sbernard31/subscriptions","organizations_url":"https://api.github.com/users/sbernard31/orgs","repos_url":"https://api.github.com/users/sbernard31/repos","events_url":"https://api.github.com/users/sbernard31/events{/privacy}","received_events_url":"https://api.github.com/users/sbernard31/received_events","type":"User","site_admin":false},"created_at":"2016-11-04T11:06:03Z","updated_at":"2016-11-04T11:06:03Z","body":"For me https://tools.ietf.org/html/draft-fossati-tls-iot-optimizations-00 fixed a DTLS issue but not the CoAP one. This is 2 different issues.\r\n\r\nSee discussion [here](https://mailarchive.ietf.org/arch/search/?email_list=core&gbt=1&index=0vwuEnq6IRHJc70l3BTggX6p9vs).\r\n\r\nI think sentence below should be removed from the spec  :\r\n\"When a new DTLS Session is started, or in NoSec mode when the LWM2M Client IP address changes, the Client MUST register again to the LWM2M Server.\"\r\n\r\nWe should not couple this concept. For security purpose the TLS spec advice to define session lifetime to 24h. With this constraint, thats means that most of the time a registration will live only for 24h ... or Users will extend TLS session lifetime  for a bad reason ...."}}
{"actor":{"display_login":"sbernard31"}}