{"action":"opened","issue":{"url":"https://api.github.com/repos/mrisher/smtp-sts/issues/44","repository_url":"https://api.github.com/repos/mrisher/smtp-sts","labels_url":"https://api.github.com/repos/mrisher/smtp-sts/issues/44/labels{/name}","comments_url":"https://api.github.com/repos/mrisher/smtp-sts/issues/44/comments","events_url":"https://api.github.com/repos/mrisher/smtp-sts/issues/44/events","html_url":"https://github.com/mrisher/smtp-sts/issues/44","id":162997555,"number":44,"title":"The DNS TXT record is underspecified and unparsable.","user":{"login":"lbaudoin","id":11791081,"avatar_url":"https://avatars.githubusercontent.com/u/11791081?v=3","gravatar_id":"","url":"https://api.github.com/users/lbaudoin","html_url":"https://github.com/lbaudoin","followers_url":"https://api.github.com/users/lbaudoin/followers","following_url":"https://api.github.com/users/lbaudoin/following{/other_user}","gists_url":"https://api.github.com/users/lbaudoin/gists{/gist_id}","starred_url":"https://api.github.com/users/lbaudoin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lbaudoin/subscriptions","organizations_url":"https://api.github.com/users/lbaudoin/orgs","repos_url":"https://api.github.com/users/lbaudoin/repos","events_url":"https://api.github.com/users/lbaudoin/events{/privacy}","received_events_url":"https://api.github.com/users/lbaudoin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-06-29T18:42:56Z","updated_at":"2016-06-29T18:42:56Z","closed_at":null,"body":"Underspecified:\r\n1) There is no description of how to combine the 'v' and 'id' properties in a single record. Maybe copy from (or link) the DKIM spec? https://tools.ietf.org/html/rfc4871#section-3.2\r\n2) Mention if unknown fields should be ignored or rejected?\r\n\r\nParsing issue:\r\n - VCHAR is specified as \" VCHAR =  %x21-7E\" in RFC 5234 so it is not possible to know if a semi-colon is part of a policy id value or a delimiter. In the section 9.1 example the policy id could be \"randomstr\" or \"randomstr;\" \"id=foo;v=STS1\" could be interpreted as policy id = \"foo;v=STS1\".\r\n\r\nSuggestion: check if VALCHAR =  %x21-3A / %x3C-7E from the DKIM spec (RFC4871) would be better than VCHAR."}}
{"actor":{"display_login":"lbaudoin"}}