{"action":"created","issue":{"url":"https://api.github.com/repos/thomas-fossati/draft-tls-cid/issues/5","repository_url":"https://api.github.com/repos/thomas-fossati/draft-tls-cid","labels_url":"https://api.github.com/repos/thomas-fossati/draft-tls-cid/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/thomas-fossati/draft-tls-cid/issues/5/comments","events_url":"https://api.github.com/repos/thomas-fossati/draft-tls-cid/issues/5/events","html_url":"https://github.com/thomas-fossati/draft-tls-cid/issues/5","id":189623337,"number":5,"title":"Server's options when receiving invalid CID","user":{"login":"sophokles73","id":5682135,"avatar_url":"https://avatars.githubusercontent.com/u/5682135?v=3","gravatar_id":"","url":"https://api.github.com/users/sophokles73","html_url":"https://github.com/sophokles73","followers_url":"https://api.github.com/users/sophokles73/followers","following_url":"https://api.github.com/users/sophokles73/following{/other_user}","gists_url":"https://api.github.com/users/sophokles73/gists{/gist_id}","starred_url":"https://api.github.com/users/sophokles73/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sophokles73/subscriptions","organizations_url":"https://api.github.com/users/sophokles73/orgs","repos_url":"https://api.github.com/users/sophokles73/repos","events_url":"https://api.github.com/users/sophokles73/events{/privacy}","received_events_url":"https://api.github.com/users/sophokles73/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-11-16T08:04:23Z","updated_at":"2016-11-17T17:01:55Z","closed_at":null,"body":"Section 3 reads:\r\n> A server which receives a ‘cid’ value which is not expected (e.g., a value outside its advertised window) MAY ignore the packet.\r\n\r\nIt is unclear what a server might want to do otherwise. Are there any other feasible strategies to deal with invalid CIDs, e.g. terminating the connection? I think it would be helpful to implementors to get some guidance here. Or can we simply make this mandatory, i.e. \"... MUST ignore the packet\"?"},"comment":{"url":"https://api.github.com/repos/thomas-fossati/draft-tls-cid/issues/comments/261304618","html_url":"https://github.com/thomas-fossati/draft-tls-cid/issues/5#issuecomment-261304618","issue_url":"https://api.github.com/repos/thomas-fossati/draft-tls-cid/issues/5","id":261304618,"user":{"login":"thomas-fossati","id":9195842,"avatar_url":"https://avatars.githubusercontent.com/u/9195842?v=3","gravatar_id":"","url":"https://api.github.com/users/thomas-fossati","html_url":"https://github.com/thomas-fossati","followers_url":"https://api.github.com/users/thomas-fossati/followers","following_url":"https://api.github.com/users/thomas-fossati/following{/other_user}","gists_url":"https://api.github.com/users/thomas-fossati/gists{/gist_id}","starred_url":"https://api.github.com/users/thomas-fossati/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thomas-fossati/subscriptions","organizations_url":"https://api.github.com/users/thomas-fossati/orgs","repos_url":"https://api.github.com/users/thomas-fossati/repos","events_url":"https://api.github.com/users/thomas-fossati/events{/privacy}","received_events_url":"https://api.github.com/users/thomas-fossati/received_events","type":"User","site_admin":false},"created_at":"2016-11-17T17:01:55Z","updated_at":"2016-11-17T17:01:55Z","body":"Hi Kai, this is interesting.\r\n\r\n(Sorry for the pedantry...a received CID could be unknown, or maybe unexpected, but it can't be invalid, I guess.)\r\n\r\n_Unknown_ means it's not found in the lookup table.  I can imagine this happening for a couple of reasons:\r\n\r\n1. server reboots and looses its state, in which case it should reply with an error indication to force client to re-establish the security context\r\n\r\n1. genuine bug either in client or server code, or even somewhere on the network path.  This one as well should return an error indication to make diagnostic / debug easier\r\n\r\nA CID might be _unexpected_ if it existed but it's been already shifted.  This could happen if the packet is delayed or replayed.  In both cases I think the recommendation to silently ignore would be OK.\r\n"}}
{"actor":{"display_login":"thomas-fossati"}}