{"action":"created","issue":{"url":"https://api.github.com/repos/theupdateframework/taps/issues/37","repository_url":"https://api.github.com/repos/theupdateframework/taps","labels_url":"https://api.github.com/repos/theupdateframework/taps/issues/37/labels{/name}","comments_url":"https://api.github.com/repos/theupdateframework/taps/issues/37/comments","events_url":"https://api.github.com/repos/theupdateframework/taps/issues/37/events","html_url":"https://github.com/theupdateframework/taps/issues/37","id":232675502,"node_id":"MDU6SXNzdWUyMzI2NzU1MDI=","number":37,"title":"Discussion of TAP 8: Key rotation and explicit self-revocation","user":{"login":"vladimir-v-diaz","id":3520883,"node_id":"MDQ6VXNlcjM1MjA4ODM=","avatar_url":"https://avatars2.githubusercontent.com/u/3520883?v=4","gravatar_id":"","url":"https://api.github.com/users/vladimir-v-diaz","html_url":"https://github.com/vladimir-v-diaz","followers_url":"https://api.github.com/users/vladimir-v-diaz/followers","following_url":"https://api.github.com/users/vladimir-v-diaz/following{/other_user}","gists_url":"https://api.github.com/users/vladimir-v-diaz/gists{/gist_id}","starred_url":"https://api.github.com/users/vladimir-v-diaz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vladimir-v-diaz/subscriptions","organizations_url":"https://api.github.com/users/vladimir-v-diaz/orgs","repos_url":"https://api.github.com/users/vladimir-v-diaz/repos","events_url":"https://api.github.com/users/vladimir-v-diaz/events{/privacy}","received_events_url":"https://api.github.com/users/vladimir-v-diaz/received_events","type":"User","site_admin":false},"labels":[{"id":438545191,"node_id":"MDU6TGFiZWw0Mzg1NDUxOTE=","url":"https://api.github.com/repos/theupdateframework/taps/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":24,"created_at":"2017-05-31T19:48:08Z","updated_at":"2018-10-17T22:35:27Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"TAP 8 proposal is available at https://github.com/theupdateframework/taps/blob/master/tap8.md\r\n\r\nPull requests related to TAP 8:\r\nhttps://github.com/theupdateframework/taps/pull/20\r\n\r\nDiscussion of TAP 8 on the TUF mailing list:\r\nhttps://groups.google.com/d/msg/theupdateframework/Yj1z3PkMRZc/n8wXM4VZBgAJ"},"comment":{"url":"https://api.github.com/repos/theupdateframework/taps/issues/comments/430813124","html_url":"https://github.com/theupdateframework/taps/issues/37#issuecomment-430813124","issue_url":"https://api.github.com/repos/theupdateframework/taps/issues/37","id":430813124,"node_id":"MDEyOklzc3VlQ29tbWVudDQzMDgxMzEyNA==","user":{"login":"JustinCappos","id":857871,"node_id":"MDQ6VXNlcjg1Nzg3MQ==","avatar_url":"https://avatars2.githubusercontent.com/u/857871?v=4","gravatar_id":"","url":"https://api.github.com/users/JustinCappos","html_url":"https://github.com/JustinCappos","followers_url":"https://api.github.com/users/JustinCappos/followers","following_url":"https://api.github.com/users/JustinCappos/following{/other_user}","gists_url":"https://api.github.com/users/JustinCappos/gists{/gist_id}","starred_url":"https://api.github.com/users/JustinCappos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JustinCappos/subscriptions","organizations_url":"https://api.github.com/users/JustinCappos/orgs","repos_url":"https://api.github.com/users/JustinCappos/repos","events_url":"https://api.github.com/users/JustinCappos/events{/privacy}","received_events_url":"https://api.github.com/users/JustinCappos/received_events","type":"User","site_admin":false},"created_at":"2018-10-17T22:35:27Z","updated_at":"2018-10-17T22:35:27Z","author_association":"MEMBER","body":">\n> Role names:\n> The TUF spec does not specifically forbid roles with the same role name,\n> but in practice it would not work as the role's metadata file is named\n> rolename.json.\n>\nOkay, thanks!  This makes sense.\n\n> I think another question is whether we want the rotate mechanism to\n> replace delegation here. If the delegator is allowed to continue handling\n> key rotation, they have to be allowed to re-delegate to the same rolename\n> (they delegate to role A with key a, then later change this to role A with\n> key b). If we want to eliminate this re-delegation use case, we could\n> prevent role name reuse by delegators. I think taking this power away from\n> delegators will lead to a lot of confusion (for example, they delegate to a\n> developer role, then to developer_1 role, etc until they are delegating to\n> developer_42 which I think makes the role's purpose less clear).\n>\n\nRight, but it also seems easier to make a mistake when delegating if you\nhave the same name w/ multiple keys (some revoked).\n\nI'm not sure what is better here.  @Hannes Mehnert <hannes@mehnert.org>,\ncan you chime in?\n\n>\n"}}
{"actor":{"display_login":"JustinCappos"}}