{"action":"created","issue":{"url":"https://api.github.com/repos/weppos/publicsuffix-go/issues/31","repository_url":"https://api.github.com/repos/weppos/publicsuffix-go","labels_url":"https://api.github.com/repos/weppos/publicsuffix-go/issues/31/labels{/name}","comments_url":"https://api.github.com/repos/weppos/publicsuffix-go/issues/31/comments","events_url":"https://api.github.com/repos/weppos/publicsuffix-go/issues/31/events","html_url":"https://github.com/weppos/publicsuffix-go/issues/31","id":184919652,"number":31,"title":"Accept A-labels","user":{"login":"jsha","id":220205,"avatar_url":"https://avatars.githubusercontent.com/u/220205?v=3","gravatar_id":"","url":"https://api.github.com/users/jsha","html_url":"https://github.com/jsha","followers_url":"https://api.github.com/users/jsha/followers","following_url":"https://api.github.com/users/jsha/following{/other_user}","gists_url":"https://api.github.com/users/jsha/gists{/gist_id}","starred_url":"https://api.github.com/users/jsha/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jsha/subscriptions","organizations_url":"https://api.github.com/users/jsha/orgs","repos_url":"https://api.github.com/users/jsha/repos","events_url":"https://api.github.com/users/jsha/events{/privacy}","received_events_url":"https://api.github.com/users/jsha/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2016-10-24T18:33:50Z","updated_at":"2016-10-26T18:55:06Z","closed_at":null,"body":"In https://github.com/letsencrypt/boulder/pull/2278 we have an issue where TLDs that are IDNs are not recognized by Boulder as ending in a public suffix. Boulder currently calls `publicsuffix.DefaultList.Find` with the A-label form of the domain.\r\n\r\nWe have a few options:\r\n 1. Boulder could convert to U-label for querying `publicsuffix`\r\n 2. `publicsuffix-go` could switch to looking up by A-label by default\r\n 3. `publicsuffix-go` could offer a different set of methods for looking up by A-label.\r\n\r\nI think (2) is my ideal solution. What do you think?"},"comment":{"url":"https://api.github.com/repos/weppos/publicsuffix-go/issues/comments/256443675","html_url":"https://github.com/weppos/publicsuffix-go/issues/31#issuecomment-256443675","issue_url":"https://api.github.com/repos/weppos/publicsuffix-go/issues/31","id":256443675,"user":{"login":"sleevi","id":1487399,"avatar_url":"https://avatars.githubusercontent.com/u/1487399?v=3","gravatar_id":"","url":"https://api.github.com/users/sleevi","html_url":"https://github.com/sleevi","followers_url":"https://api.github.com/users/sleevi/followers","following_url":"https://api.github.com/users/sleevi/following{/other_user}","gists_url":"https://api.github.com/users/sleevi/gists{/gist_id}","starred_url":"https://api.github.com/users/sleevi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sleevi/subscriptions","organizations_url":"https://api.github.com/users/sleevi/orgs","repos_url":"https://api.github.com/users/sleevi/repos","events_url":"https://api.github.com/users/sleevi/events{/privacy}","received_events_url":"https://api.github.com/users/sleevi/received_events","type":"User","site_admin":false},"created_at":"2016-10-26T18:55:06Z","updated_at":"2016-10-26T18:55:06Z","body":"@gerv I'll poke jshin on that, but I think it would at least highlight a 'possibility' where the U-label form is valuable - to allow consistent decomposition to the A-label in both IDNA2003 and IDNA2008 apps. Of course, I wish we'd just go with IDNA2008.\r\n\r\nPerhaps an interim solution is convert to A-label across the board (which will certainly break Chrome's PSL implementation, and presumably Firefox, but we can fix both of those easily) in IDNA2008, and then perhaps add a consistency check as part of the PSL's tests to make sure the IDNA2003 and 2008 representations are consistent, until the PSL full throws IDNA2003 under the bus?"}}
{"actor":{"display_login":"sleevi"}}