David I. Lehn: Hi, my name is Dave Lehn, I work for Digital Bazaar with Dave and Manu working on technologies related to payments, identity, and blockchain. ✪
Topic: Announcements
Kim Hamilton Duffy: Next week's agenda will be spent mostly on planning next year's work ✪
... No meeting on Dec 26 or Jan 2
... First meeting in 2018 will be Jan 9th
... Virtual Hackathon will take place in week January 15th-19th
Joe Andrieu: We are talking about modification rather than authz ✪
Christopher Allen: How about add text "plus method specific information to support proof and key management" ✪
Drummond Reed: +1 To "modify" or "update" ("update" being one of the CRUD terms) ✪
Kim Hamilton Duffy: Also +1 to "modify" or "update" ✪
Christopher Allen: Method needed for updating the document ✪
Drummond Reed: Key management isn't always method-specific. Methods MAY have method-specific key management, but there's also key management that's not method-specific. ✪
Manu Sporny: DID doc is not only about key management. ✪
Dave Longley: +1 DID doc is not just about key management ✪
Manu Sporny: Is it about update and modification or general authz ✪
Drummond Reed: I would never say it's "just" about key management. But I think key management is a key part (sic) of what DID documents are about. ✪
Dave Longley: I think a DID doc is about establishing an independent entity and being able to authenticate that certain activities/actions were performed by that entity -- and to interact with that entity via services. ✪
Manu Sporny: We cannot control what people will put in DID docs ✪
Manu Sporny: But we have to say how keys, authn and authz are dealt with ✪
Joe Andrieu: Keys are technology specific. there will be other mechanisms in the future. "Authentication" is an attempt to embrace other potential means for vetting actors ✪
Manu Sporny: This discussion will continue in the DID hardening meetings ✪
#34 Move standard key descriptions to separate specification. ✪
Drummond Reed: I agree with Manu that we need to close on the DID spec hardening discussions before we know what the structure of a key description registry will look like. ✪
Manu Sporny: We are less certain about this PR than the other ones ✪
#33 Split DID Method Registry out of specification. ✪
Ryan Grant: +1 For splitting out registry, and this pull request ✪
Drummond Reed: +1 To the overall idea of having a separate key description registry. It's an alternative to the super-structured and heavyweight approach of https://tools.ietf.org/html/rfc7517.✪
Manu Sporny: This is straightforward PR. Should not be any objections to it ✪
Drummond Reed: No objection to splitting out the DID method registry. ✪
Topic: Other Topics
Ryan Grant: Manu can you point us to tools for creating html docs with gif images ✪
Manu Sporny: Htmldif is a tool you can run on the command line ✪
Christopher Allen: Is there a good doc on creating/modifying respect docs? ✪
Manu Sporny: Do we keep on with DID hardening or move onto another topic ✪
Drummond Reed: Goal of DID hardening meetings is to close the issues ✪
Drummond Reed: Still have 4 or 5 more issues on the list ✪
Christopher Allen: Can we get some of the people that are not active in CCG, but coming hardening, at virtual hackathon? ✪
Kim Hamilton Duffy: The hackathon would be a good place to work on DID hardening ✪
Dave Longley: +1 To take care of easier points first :) ✪
Drummond Reed: Ok, what I could volunteer to do is do a refresh on the DID spec hardening Google doc to prioritize issues by (what appear to be) easiest to hardest, and then work from easiest to hardest if that will work best. ✪
Christopher Allen: Can we separate issues into easy topics, ones that need more discussion in January etc. ✪
Manu Sporny: +1 To Drummond's proposal... feels like that has the best morale outcome :P ✪
Christopher Allen: We need to move DID hardening back to CCG calls ✪
Dave Longley: That also gives more time for the harder items to stew and be discussed in other channels ✪
Drummond Reed: Yes, I'm thinking we may want to start moving some of the DID spec hardening issues over to github so we can have dedicated discussion threads about them. ✪
Drummond Reed: I can do PRs on the ones we've resolved, if you'd like... [scribe assist by Manu Sporny] ✪