{"action":"closed","issue":{"url":"https://api.github.com/repos/anima-wg/constrained-voucher/issues/22","repository_url":"https://api.github.com/repos/anima-wg/constrained-voucher","labels_url":"https://api.github.com/repos/anima-wg/constrained-voucher/issues/22/labels{/name}","comments_url":"https://api.github.com/repos/anima-wg/constrained-voucher/issues/22/comments","events_url":"https://api.github.com/repos/anima-wg/constrained-voucher/issues/22/events","html_url":"https://github.com/anima-wg/constrained-voucher/issues/22","id":354227800,"node_id":"MDU6SXNzdWUzNTQyMjc4MDA=","number":22,"title":"assertion enum should be mapped to a number in CBOR?","user":{"login":"EskoDijk","id":15609950,"node_id":"MDQ6VXNlcjE1NjA5OTUw","avatar_url":"https://avatars1.githubusercontent.com/u/15609950?v=4","gravatar_id":"","url":"https://api.github.com/users/EskoDijk","html_url":"https://github.com/EskoDijk","followers_url":"https://api.github.com/users/EskoDijk/followers","following_url":"https://api.github.com/users/EskoDijk/following{/other_user}","gists_url":"https://api.github.com/users/EskoDijk/gists{/gist_id}","starred_url":"https://api.github.com/users/EskoDijk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/EskoDijk/subscriptions","organizations_url":"https://api.github.com/users/EskoDijk/orgs","repos_url":"https://api.github.com/users/EskoDijk/repos","events_url":"https://api.github.com/users/EskoDijk/events{/privacy}","received_events_url":"https://api.github.com/users/EskoDijk/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-08-27T08:29:45Z","updated_at":"2018-08-28T14:13:37Z","closed_at":"2018-08-28T14:13:37Z","author_association":"NONE","body":"currently the \"assertion\" field is a string, while RFC 8366 defines it as an enumeration with either \"proximity\", \"logged\" or \"verified\". For compactness it is better to define this value as an enum; so should the enum values be defined in this draft?\r\n(or better, some a priori order could be specified like alphabetical or following the order of the formal YANG definition of the enum)"}}
{"actor":{"display_login":"mcr"}}