Community Call — August 24, 2022

[expede]

Sign up: https://lu.ma/ucan

Suggested Agenda

• Updates @expede
  • AWAKE
  • Bearer header
  • IPLD Schema
    • SIWE
• XMPP @sunkist4013

In Attendance

• @expede
• @matheus23
• @hugomrdias
• @alanhkarp
• @cdata

Video

Chat Log

00:05:16	Philipp Krüger:	https://github.com/ucan-wg/spec/discussions/89
00:08:40	Philipp Krüger:	https://github.com/ucan-wg/ucan-as-bearer-token
00:09:17	Philipp Krüger:	https://github.com/ucan-wg/ucan-ipld/pull/1
00:09:48	Philipp Krüger:	I CAN RELATE
00:09:58	Philipp Krüger:	This is the first time I saw the bearer token spec myself lol
00:10:28	Philipp Krüger:	Brooke's output is quite impressive
00:10:53	Hugo Dias:	yes, i have notice that 😆
00:13:25	Chris "cdata" Joel :	Should we have a standard reconciliation protocol for the case where individual UCANs need to be sync'd between two parties?

Without such a thing, a long tail of clients may err on the side of sending all UCANs all the time to avoid the complexity of sync'ing them.
00:13:56	Philipp Krüger:	Would love to discuss this afterwards chris!
00:29:02	Brooklyn Zelenka (@expede):	We need to run Minibus over CAR Pool
00:31:20	Brooklyn Zelenka (@expede):	https://github.com/fission-codes/spec/blob/main/car-pool/README.md
00:32:04	Chris "cdata" Joel :	UCAN preflight request? :D
00:34:37	Hugo Dias:	car pool looks really interesting !!! another set of docs that i need to read you are killing me 🙀
00:34:54	Brooklyn Zelenka (@expede):	😁
00:35:37	Mohsin Zaidi:	Hey, sorry for joining late. Was in another meeting. Great discussion so far!Wanted to find out the plans for SIWE. Will you be considering CACAO?
00:42:57	Chris "cdata" Joel :	Cookbook +1
00:43:58	Chris "cdata" Joel :	Yah, failing over to car mirror would be a nice pattern
00:48:12	Hugo Dias:	brooklyn is the car mirror presentation in the ipfs thing youtube list ?
00:48:20	Chris "cdata" Joel :	I have a random question that I can move to a github discussion if we don't have time to talk about it:

Long-lived UCANs are kind of an enigma for me. OTOH, I definitely want to use a UCAN chain as a "proof" that some change of state I'm reviewing in IPLD is valid at the time it was made. OTOH, I can't have an infinitely live UCAN, and also long-lived UCANs seem like they should be avoided in the service invocation case. Does anyone here deal with this duality, and how do you think about it?
00:50:26	Alan Karp:	We used long-lived certificates in E-Speak.  They basically lived as long as the contract between business partners.  We relied on revocation rather than expiration.
00:51:31	Chris "cdata" Joel :	💭🙏
00:51:37	Alan Karp:	Any interaction with GNAP?
00:51:43	Hugo Dias:	https://www.youtube.com/watch?v=gbqDgsfeiac&list=PLuhRWgmPaHtQGr0f6gT1ADwM7AXluztK8&index=4 CAR Pool talk
00:53:16	Philipp Krüger:	gnap: https://datatracker.ietf.org/wg/gnap/documents/
00:54:22	Philipp Krüger:	yeah UCANs are much more like spki
00:57:03	Chris "cdata" Joel :	I'm reposting my question on Github 

Notes

[sunkist4013]

'XMPP' with OMEMO encryption private chat room, audio, videos, conférences, documents and books, privacy cryptocurrency, casino games, privacy mobile communications over satellites; Why UCAN will play a role in many ways.