...

Motivations

The DID Method did:web  has found great method specification has started to get significant adoption, but it is still fundamentally flawed by it's trust in DNS and DNS's susceptibility from a security standpoint by its reliance on DNS trust infrastructure, which is susceptible to hijacking attacks among others.

Analogous to http and https `did:web` needs a securing mechanism and that will be specified by did:webs 

(among other issues). In addition, the did:web method adds further vulnerabilities due to the reliance on storing a DID document (that is entirely authoritative for the associated cryptographic keys) on a Web server.

Just as Web infrastructure made the progression from the insecure http:  to the secure https:  protocol, the goal of the did:webs method is to specify a secure version of did:web.

The did:webs specification can also help `did:webs` can help to bridge the gap between existing didcomm DIDComm-based ecosystems and KERI-based ecosystems, originally referred to as the "Beautiful Island Problem".

Purpose

To author deliver a specification describing for the did:webs  and did doc resolution along with key material retrieval. DID method meeting the requirements of DID method specifications defined in the W3C Decentralized Identifiers (DIDs) 1.0 specification, including creation, resolution, updating, and deactivation of DID documents with secure cryptographic key material. See the following illustration:

Deliverables

The table below lists all the deliverables of the KERI Task Forcethis task force:

Chairs

Please add your name to this list if you wish to be a chair:

Chairs

• Phil Feairheller , GLEIF
• Lance Byrd , GLEIFKevin Griffin, GLEIF Kevin Griffin 

Members

Please add your name to this list in any desired role:

• Kevin Griffin , GLEIF

• Markus Sabadello 

• Wenjing Chu , Futurewei
• Drummond Reed, Gen
• Charles Lanahan , Stealth Mode Startup Company
• Henk van Cann
• Primary Editors

• Secondary Editors

• Primary Reviewers

• Secondary Reviewers

• Observers

Meeting Schedule

TBDSee did:webs Meeting Page

For all authoritative meeting logistics and Zoom links, please see the ToIP Calendar.

See the latest documentation in the GitHub Repo here: LINK:

https://github.com/trustoverip/tswg-did-method-webs-specification

Meeting Agendas and Notes

All meeting agendas and notes are recorded on the did:webs Meeting Page.

Intellectual Property Rights (Copyright, Patent, Source Code)

As a Task Force (TF) of the Technology Stack WG (TSWG), the did:webs TF inherits DWTF inherits the IPR terms from the TSWG JDF Charter. These include:

• Copyright mode: Apache2 and IETF Copyright: OWFa 1.0 (available at https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owfa-1-0)
• Patent mode: OWFa 1.0 (available at https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owfa-1-0)Patent mode: Apache2
• Source code: Apache 2.0 , (available at at http://www.apache.org/licenses/LICENSE-2.0.html. )

Mailing List and Communications

This task force uses the following for communications

• Slack: This TF has its own dedicated Slack channel: #tswg-did-didwebswebs-tf
• GithubGitHub: This TF will use GitHub issues for substantive conversations on topics, not Slack. This way the conversation is source controlled..
  • https://github.com/trustoverip/tswg-did-method-webs-specification

Specification Generation

We may alternatively use the following formats:

...