...

Motivations

The DID Method did:web  has found great method has started to get signifiant adoption, but it is still fundamentally flawed by it's trust in DNS and DNS's from a security standpoint by its reliance on DNS trust infrastructure, which is susceptibility to hijacking attacks (among others.other issues). In addition, the did:web method adds further vulnerat

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

`did:webs` can help to bridge the gap between existing 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 defined in the W3C Decentralized Identifiers (DIDs) 1.0 specification, including creation, resolution, updating, and deactivation of DID documents along with retreival of secure cryptographic key material. See the following illustration:

Deliverables

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

Chairs

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

• Kevin Griffin, GLEIF Kevin Griffin GLEIF 

Members

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

• Primary Editors
  • Drummond Reed, Gen

• Secondary Editors

• Primary Reviewers

• Secondary Reviewers

• Observers

Meeting Schedule

TBD

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

See latest documentation in the GitHub Repo here: LINK

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 the IPR terms from the TSWG JDF Charter. These include:

• Copyright mode: Apache2 and IETF Copyright
• Patent mode: Apache2
• Source code: Apache 2.0, available 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-didwebs-tf
• Github: This TF will use GitHub issues for substantive conversations on topics, not Slack. This way the conversation is source controlled.

Specification Generation

We may alternatively use the following formats:

...