{"action":"closed","issue":{"url":"https://api.github.com/repos/sacmwg/draft-ietf-sacm-requirements/issues/17","labels_url":"https://api.github.com/repos/sacmwg/draft-ietf-sacm-requirements/issues/17/labels{/name}","comments_url":"https://api.github.com/repos/sacmwg/draft-ietf-sacm-requirements/issues/17/comments","events_url":"https://api.github.com/repos/sacmwg/draft-ietf-sacm-requirements/issues/17/events","html_url":"https://github.com/sacmwg/draft-ietf-sacm-requirements/issues/17","id":64771041,"number":17,"title":"G-011 - Unsolicited publication, updates,...","user":{"login":"jimsch","id":4946037,"avatar_url":"https://avatars.githubusercontent.com/u/4946037?v=3","gravatar_id":"","url":"https://api.github.com/users/jimsch","html_url":"https://github.com/jimsch","followers_url":"https://api.github.com/users/jimsch/followers","following_url":"https://api.github.com/users/jimsch/following{/other_user}","gists_url":"https://api.github.com/users/jimsch/gists{/gist_id}","starred_url":"https://api.github.com/users/jimsch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jimsch/subscriptions","organizations_url":"https://api.github.com/users/jimsch/orgs","repos_url":"https://api.github.com/users/jimsch/repos","events_url":"https://api.github.com/users/jimsch/events{/privacy}","received_events_url":"https://api.github.com/users/jimsch/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-03-27T14:19:01Z","updated_at":"2015-05-10T20:38:49Z","closed_at":"2015-05-10T20:38:49Z","body":"Version -04\r\n\r\nPush and Pull Access:  There MUST be support for three methods of data access.  The standard Pull model as well as solicited and unsolicited Push models.  All of the methods of data access must support the ability for the initiator to filter the set of posture assessment information to be delivered.  Additionally, the provider of the information needs to filter the set of posture assessment information based on the permissions of the recipient.  This requirement is driven by use cases 2.1.3, 2.1.4 and 2.1.5.\r\n\r\nWhat you currently have is unclear and messy.  \r\n- It does not have a pithy title\r\n- The \"title\" that is there does not correspond to all of the content of the paragraph.  TItle is unsolicited, but there is a sentence for solicited  and pull as well."}}