{"action":"created","issue":{"url":"https://api.github.com/repos/sacmwg/draft-ietf-sacm-information-model/issues/68","repository_url":"https://api.github.com/repos/sacmwg/draft-ietf-sacm-information-model","labels_url":"https://api.github.com/repos/sacmwg/draft-ietf-sacm-information-model/issues/68/labels{/name}","comments_url":"https://api.github.com/repos/sacmwg/draft-ietf-sacm-information-model/issues/68/comments","events_url":"https://api.github.com/repos/sacmwg/draft-ietf-sacm-information-model/issues/68/events","html_url":"https://github.com/sacmwg/draft-ietf-sacm-information-model/issues/68","id":186580828,"number":68,"title":"discuss IM/DM related questions","user":{"login":"djhaynes","id":1210879,"avatar_url":"https://avatars.githubusercontent.com/u/1210879?v=3","gravatar_id":"","url":"https://api.github.com/users/djhaynes","html_url":"https://github.com/djhaynes","followers_url":"https://api.github.com/users/djhaynes/followers","following_url":"https://api.github.com/users/djhaynes/following{/other_user}","gists_url":"https://api.github.com/users/djhaynes/gists{/gist_id}","starred_url":"https://api.github.com/users/djhaynes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/djhaynes/subscriptions","organizations_url":"https://api.github.com/users/djhaynes/orgs","repos_url":"https://api.github.com/users/djhaynes/repos","events_url":"https://api.github.com/users/djhaynes/events{/privacy}","received_events_url":"https://api.github.com/users/djhaynes/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-01T16:33:57Z","updated_at":"2016-11-01T16:51:17Z","closed_at":null,"body":"There are many existing collection mechanisms and data models.  Does SACM need new data models? Or, does SACM just need to describe how an implementer can leverage these existing data models? Furthermore, does SACM need a single unifying data model or just a framework for communicating information expressed in any available data model?"},"comment":{"url":"https://api.github.com/repos/sacmwg/draft-ietf-sacm-information-model/issues/comments/257621209","html_url":"https://github.com/sacmwg/draft-ietf-sacm-information-model/issues/68#issuecomment-257621209","issue_url":"https://api.github.com/repos/sacmwg/draft-ietf-sacm-information-model/issues/68","id":257621209,"user":{"login":"david-waltermire-nist","id":9871976,"avatar_url":"https://avatars.githubusercontent.com/u/9871976?v=3","gravatar_id":"","url":"https://api.github.com/users/david-waltermire-nist","html_url":"https://github.com/david-waltermire-nist","followers_url":"https://api.github.com/users/david-waltermire-nist/followers","following_url":"https://api.github.com/users/david-waltermire-nist/following{/other_user}","gists_url":"https://api.github.com/users/david-waltermire-nist/gists{/gist_id}","starred_url":"https://api.github.com/users/david-waltermire-nist/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/david-waltermire-nist/subscriptions","organizations_url":"https://api.github.com/users/david-waltermire-nist/orgs","repos_url":"https://api.github.com/users/david-waltermire-nist/repos","events_url":"https://api.github.com/users/david-waltermire-nist/events{/privacy}","received_events_url":"https://api.github.com/users/david-waltermire-nist/received_events","type":"User","site_admin":false},"created_at":"2016-11-01T16:51:16Z","updated_at":"2016-11-01T16:51:16Z","body":"This is something that we should explore more. The alternative is to essentially remodel all of the existing data models. IMHO, remodeling the world of posture modelling is a non-starter. We will be at this forever, we will always be chasing what has been modeled within management protocols (e.g., MIB, Yang, etc), and we will likely end up with something that won’t get implemented in software products. In short, a remodeling approach does not scale.\r\n\r\nInstead, we may be able to focus on characterizing the key subjects (e.g., endpoints, software, hardware, configuration settings) in a standardized way to provide a framework for expressing the subject of data provided by another model. This allows a consumer to query for this data in the same way, and determine if a piece of posture information is interesting or not. Understanding the payload is a different matter. We may want to think about a transcoding approach that would allow conversion of data between two different, but similar data models. This would allow a consumer to get the information it needs in a form it understands.\r\n\r\nThoughts?\r\n\r\nDave\r\n\r\nFrom: Danny Haynes [mailto:notifications@github.com]\r\nSent: Tuesday, November 01, 2016 12:34 PM\r\nTo: sacmwg/draft-ietf-sacm-information-model <draft-ietf-sacm-information-model@noreply.github.com>\r\nSubject: [sacmwg/draft-ietf-sacm-information-model] discuss IM/DM related questions (#68)\r\n\r\n\r\nThere are many existing collection mechanisms and data models. Does SACM need new data models? Or, does SACM just need to describe how an implementer can leverage these existing data models? Furthermore, does SACM need a single unifying data model or just a framework for communicating information expressed in any available data model?\r\n\r\n—\r\nYou are receiving this because you are subscribed to this thread.\r\nReply to this email directly, view it on GitHub<https://github.com/sacmwg/draft-ietf-sacm-information-model/issues/68>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AJaiaJqPreFxD9UOFzkQMROW_gumfBx1ks5q52n1gaJpZM4KmStl>.\r\n"}}
{"actor":{"display_login":"david-waltermire-nist"}}