Page Comparison

...

RFC 496 - Transition to OOB and DID ExchangeExchange From 2021-11-16 Session

• To do: Chase wallet vendors, share findings, and update RFC Stephen Curran

...

Handling HTTP on mobile, since mobile OS's require an exemption to use HTTP. DIDComm over HTTPS results in double encryption. From 2021-11-16 Session

• To Do: PR to RFC 0025 Transports to make HTTPS a SHOULD since the UX to request an exemption is a Bad Thing Jason Leach

...

• Inversion of QR scanning flow where verifier scans holder's QR code
• Other mechanisms other than QR Code (e.g.: BLE)
• Todo: SUSummary of existing state for BLE
• Todo: Summary of existing state for NFC
• UX us

Original Topics List

• Mobile Infrastructure (2)
  • Mobile Verifiers
  • Device Recovery (Backup/Restore/Sync/Rotation to new keys)
  • Secure Element usage
  • SDK / Embedding Agents into existing Mobile Apps
• Credential UX (3)
  • SVG Cred Display
  • Auto-approval of presentation requests (e.g.: trusted verifier, trusted preset, etc ...)
  • Credential Theming (e.g. Icon, Colors, Description)
  • Revocation implications for Mobile
  • Consequences of Machine Readable Governance on UX
• Other User Experience (UX) (4)
  • UX of Invitations
  • Exposing errors / details to users & power users (404 and 503 like errors)
    • Unsupported DID Method
  • Glossary - naming conventions - how to hide technicalities in front of user
• QR / Invitations (1)
  • How are we really going to do deep-links?
  • RFC 496 - Transition to OOB and DID Exchange
  • RFC 700 - sending out-of-band as query parameters and enable redirect back.
  • HTTP Mobile exemptions
• Security
  • DID method specific
  • Immutability of schema and JSON-LD security issues
  • Biometrics/PIN unlock (overlap with UX)
• Protocols
  • DIF Credential Manifest attachment (followup from Issue Credential v2 json-ld attachment in AIPv2).
  • DIDComm v2 (and related)
    • DIDComm v2
    • WACI