Skip to content

2023 02 13 Meeting Minutes

Jump to bottom
Tracy Kuhrt edited this page Feb 13, 2023 · 1 revision

Recording

Agenda

  • DIDComm - Sam Curren

Discussion

Chat Log

12:06:23 From Alex Andrei to Everyone:
	libp2p is also being worked on 
12:11:39 From Drummond Reed to Everyone:
	Since DIDComm has its own security, why would HTTPS be needed?
12:12:18 From Drummond Reed to Everyone:
	Good answer
12:12:23 From Hart Montgomery to Everyone:
	HTTPS is pretty low overhead, yeah.
12:12:41 From Daniel Bachenheimer to Everyone:
	so which protocol adds the peer-to-peer pseudonymous encryption?  I thought that was DIDcomm… I'm likely wrong
12:12:57 From Tom Jones to Everyone:
	TLS 1.3 has perfect forward security
12:13:31 From Daniel Bachenheimer to Everyone:
	thanks!
12:14:05 From Markus Sabadello to Everyone:
	My understanding is that did:peer was more natively integrated with DIDComm v1, whereas in DIDComm v2 did:peer is treated like any other DID method.
12:14:25 From Daniel Bachenheimer to Everyone:
	Reacted to "My understanding is ..." with 👍🏻
12:14:31 From Alex Andrei to Everyone:
	Reacted to "My understanding i..." with 👍
12:15:11 From Drummond Reed to Everyone:
	Reacted to "My understanding is ..." with 👍🏻
12:16:56 From Markus Sabadello to Everyone:
	add 👍🏻
12:16:56 From Markus Sabadello to Everyone:
	remove 👍🏻
12:16:58 From Markus Sabadello to Everyone:
	add 👍🏻
12:16:58 From Markus Sabadello to Everyone:
	remove 👍🏻
12:16:59 From Markus Sabadello to Everyone:
	add 👍🏻
12:17:00 From Markus Sabadello to Everyone:
	remove 👍🏻
12:23:41 From Dmitri Zagidulin to Everyone:
	omg I'm dead over the pigeon <3
12:23:57 From Viky Manaila to Everyone:
	+1 🙂)
12:24:29 From Drummond Reed to Everyone:
	Wins “best tech presentation icon of the year so far” 😆
12:24:40 From Viky Manaila to Everyone:
	Reacted to "Wins “best tech pres..." with 😂
12:27:25 From Lance Byrd to Everyone:
	Daniel slides are the best..... DanielComm?
12:27:34 From Daniel Bachenheimer to Everyone:
	I have some biometrics slides for yo
12:27:38 From Sam Curren (TelegramSam) to Everyone:
	https://thenounproject.com/icon/carrier-pigeon-4900791/
12:31:13 From Viky Manaila to Tracy Kuhrt(Direct Message):
	Hi Tracy, where are the recordings of the meetings published?
12:31:33 From Sam Curren (TelegramSam) to Everyone:
	To be clear: passing the keys directly into the library was a design choice in building these initial libraries. It is not required in any way by DIDComm itself.
	
	We imagine most libraries will be included or adapted to remove this requirement in environments with key management appliances.
12:32:10 From Tracy Kuhrt to Viky Manaila(Direct Message):
	https://github.com/openwallet-foundation/architecture-task-force/wiki
12:32:31 From Viky Manaila to Tracy Kuhrt(Direct Message):
	thanks a lot!
12:33:18 From Lance Byrd to Everyone:
	Common DIDComm v2 protocols are searchable here https://didcomm.org/search/?page=1
12:33:20 From Drummond Reed to Everyone:
	Good
12:34:48 From Tom Jones to Everyone:
	using persistence keys for encryption will limit the encryption to RSA would it not?
12:36:08 From Sam Curren (TelegramSam) to Everyone:
	The Content Encryption Key (unique for each message) is encrypted to the recipient using any type of encryption necessary.
12:36:49 From Markus Sabadello to Everyone:
	Which DID methods does this library support, and can it use a Universal Resolver endpoint as a fallback?
12:38:22 From Sam Curren (TelegramSam) to Everyone:
	DIDComm itself doesn't have an opinion about DID Resolution - falling back to a universal resolver is a common strategy.
12:41:05 From Lance Byrd to Everyone:
	RootsID hosted DIDComm v2 mediator https://mediator.rootsid.cloud/
12:41:23 From Lance Byrd to Everyone:
	open source code here https://github.com/roots-id/didcomm-mediator
12:41:25 From Sam Curren (TelegramSam) to Everyone:
	Slides: https://docs.google.com/presentation/d/18ZFSxHNzZsfxgoQINcXx2lFZb98BRm5YX8Wzcnp93rY/edit?usp=sharing
12:41:42 From Lance Byrd to Everyone:
	i see them
12:41:44 From Lance Byrd to Everyone:
	thx!
12:42:04 From Alex Andrei to Everyone:
	https://github.com/roots-id/didcomm-mediator/tree/owf_demo/sample-notebooks
12:46:04 From Alex Andrei to Everyone:
	you could do onion routing if you are paranoid lol 
12:46:42 From Markus Sabadello to Everyone:
	What's the vision for DIDComm in OWF? Will OWF host DIDComm components?
12:50:41 From Diego Zuluaga to Everyone:
	Are there any specific industries or organizations that have adopted or implemented the DIDCOM protocol in their operations?
12:52:54 From Lance Byrd to Everyone:
	Aries DIDComm v2 WG meets on Mondays https://wiki.hyperledger.org/display/ARIES/Aries+DIDCommV2+Working+Group
12:52:58 From Diego Zuluaga to Everyone:
	Thanks, Sam!
12:53:56 From Stephen Curran to Everyone:
	Regards routing — each entity controls only the routing of inbound messages to them. They don’t have any say on what any other entity does. 
	
	From the sender perspective — the route is simply one endpoint and a sequence of keys for encryption. Each key triggers another layer of encryption.
12:56:04 From Tracy Kuhrt to Everyone:
	Last week’s meeting link: https://github.com/openwallet-foundation/architecture-task-force/wiki/2023-02-06-Meeting-Minutes
12:56:17 From Drummond Reed to Everyone:
	ToIP Trust Spanning Protocol Task Force: https://wiki.trustoverip.org/display/HOME/Trust+Spanning+Protocol+Task+Force
12:56:51 From Drummond Reed to Everyone:
	See the ToIP calendar for details of the next TSPTF meeting this coming Wednesday at 08:00-09:00 PT / 16:00-17:00 UTC: https://wiki.trustoverip.org/display/HOME/Calendar+of+ToIP+Meetings
12:57:16 From Drummond Reed to Everyone:
	The topic of that meeting is a presentation by Daniel Hardman about the relationship of DIDComm to the trust spanning protocol.
12:58:19 From Tom Jones to Everyone:
	call for comments to the NIST cybersecurity framework are due on 3/3.  Since there will not be an opportunity to discuss how we might impact them. let me know if you have an opinion that needs to be articulated. https://www.nist.gov/system/files/documents/2023/01/19/CSF_2.0_Concept_Paper_01-18-23.pdf
12:58:39 From Judith Fleenor (Trust Over IP) to Everyone:
	If you are new to the ToIP Trust Spanning Protocol topic, this is a good introduction BLOG from when that task force was started: https://trustoverip.org/blog/2023/01/05/the-toip-trust-spanning-protocol/
13:00:01 From Judith Fleenor (Trust Over IP) to Everyone:
	We’d love to see you at our meeting this Wednesday.  Drummond posted the information above.  Also, interesting discussion are happening via our GitHub discussions.
13:02:35 From Drummond Reed to Everyone:
	Great job Sam and Ddreeei
Clone this wiki locally