Skip to content
Permalink
Browse files

Add role of domain name registrars and DNS lookup services

  • Loading branch information...
friedger authored and localredhead committed Apr 28, 2019
1 parent 5ae6aa0 commit 6a3b49c3026d88e684013a28d37a4947a8ee2f64
Showing with 6 additions and 2 deletions.
  1. +6 −2 did-methods/https-did-method.md
@@ -88,7 +88,10 @@ The definition of the https DID JSON-LD context is:

### Create (Register)

Creating a DID is done by creating the DID document JSON-LD file including a suitable keypair, e.g., using the
Creating a DID is done by
1. applying at a domain name registrar for use of a domain name and
1. storing the location of a hosting service, the IP address at a DNS lookup service
1. creating the DID document JSON-LD file including a suitable keypair, e.g., using the
Koblitz Curve, and storing the `did.json` file under the well-known URL.

For the domain name `w3c-ccg.github.io`, the `did.json` will be available under the following URL:
@@ -142,8 +145,9 @@ Examples of strong SSL/TLS configurations for now are:
It is recommended to adhere to [OWASP's](https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet)
latest recommendations for hardening TLS configurations.

Delete action can be performed by domain name registars or DNS lookup services.
## Reference Implementations

The code at [https://github.com/uport-project/https-did-resolver](https://github.com/uport-project/https-did-resolver)
is intended to present a reference implementation of this DID method. Any other implementations should ensure that
they pass the test suite described in `/src/__tests__` before claiming compatibility.
they pass the test suite described in `/src/__tests__` before claiming compatibility.

0 comments on commit 6a3b49c

Please sign in to comment.
You can’t perform that action at this time.