{"action":"opened","issue":{"url":"https://api.github.com/repos/ietf-teep/architecture/issues/38","repository_url":"https://api.github.com/repos/ietf-teep/architecture","labels_url":"https://api.github.com/repos/ietf-teep/architecture/issues/38/labels{/name}","comments_url":"https://api.github.com/repos/ietf-teep/architecture/issues/38/comments","events_url":"https://api.github.com/repos/ietf-teep/architecture/issues/38/events","html_url":"https://github.com/ietf-teep/architecture/issues/38","id":389400605,"node_id":"MDU6SXNzdWUzODk0MDA2MDU=","number":38,"title":"trust anchor fingerprint","user":{"login":"hannestschofenig","id":1016643,"node_id":"MDQ6VXNlcjEwMTY2NDM=","avatar_url":"https://avatars3.githubusercontent.com/u/1016643?v=4","gravatar_id":"","url":"https://api.github.com/users/hannestschofenig","html_url":"https://github.com/hannestschofenig","followers_url":"https://api.github.com/users/hannestschofenig/followers","following_url":"https://api.github.com/users/hannestschofenig/following{/other_user}","gists_url":"https://api.github.com/users/hannestschofenig/gists{/gist_id}","starred_url":"https://api.github.com/users/hannestschofenig/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hannestschofenig/subscriptions","organizations_url":"https://api.github.com/users/hannestschofenig/orgs","repos_url":"https://api.github.com/users/hannestschofenig/repos","events_url":"https://api.github.com/users/hannestschofenig/events{/privacy}","received_events_url":"https://api.github.com/users/hannestschofenig/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-10T17:12:06Z","updated_at":"2018-12-10T17:12:06Z","closed_at":null,"author_association":"COLLABORATOR","body":"From IETF#103:\r\n\r\nv01 now includes text to define and distinguish between\r\n- Trust Anchor\r\n- Root of Trust\r\nEric Norrmark: over the course of the device lifecycle, there are times when more than\r\none trust anchor will be present (for example, when transitioning from one trust anchor\r\nto its replacement). Follow-up question: does the architecture define any mechanism\r\nother than an expiry date in a certificate, to indicate when a trust anchor should be\r\nreplaced.\r\nRuss H: suggests adding text to define 'trust anchor fingerprint' and its role as part of\r\nthe validation/replacement process for trust anchors.\r\nNancy C-W where would this term be used in the documentation as a whole?\r\nDave T: rather than add as a discrete term definition, append this text to the definition\r\nof 'trust anchor'.\r\nGeneral “nod’ from the participants in the room\r\n"}}
{"actor":{"display_login":"hannestschofenig"}}