W3C home > Mailing lists > Public > public-webid@w3.org > June 2019

WebID-DNS

From: Timothy Holborn <timothy.holborn@gmail.com>
Date: Wed, 5 Jun 2019 19:39:45 +1000
Message-ID: <CAM1Sok3L-6-xnQQgP0FtMqOcFKqpfGuovOQED3gYnX3tC5rgfw@mail.gmail.com>
To: public-webid <public-webid@w3.org>
Doing some solid related work.  There's a group of issues i'm looking into;

1. decentralising discovery

2. energy waste & DLT alternatives
I'm building a spreadsheet that's forming some sense of taxonomy to help
figure out differentiations, that can serve a number of purposes[1]

3. core enhancements.

there's a bunch of work that's going into providing infrastructure for
identity, verifiable claims, micro-payment (related) capabilities
(payments); but the biggest, is really all about discovery.

Therein: it would be nice to drop the cost of asserting some critical 'web
of trust' features.

Reviewing DNS records[2] i wondered how WebID-TLS related functional
attributes might be used with DNS records as to forge a new type of
problem, that might perhaps remove the problem about the UX with WebID-TLS
(whilst getting a better outcome).

This might also relate to use with DNS over TLS  - but i wanted to first
pose the question.

Has anyone looked at this type of thing as a possible solution?

If so, any pointers to relevant records?

basic (unbaked) theory could be; that there's a URI record and record
containing the public key; with support for the devices (holding the
private keys) to be named in DNS.

Timothy Holborn

[1]
https://docs.google.com/spreadsheets/d/1EZHjCnQZRUC6Dkqv2yA4H9Djd5Sf6z04-SfyquIV0YI/edit#gid=0

[2] https://en.wikipedia.org/wiki/List_of_DNS_record_types
Received on Wednesday, 5 June 2019 09:40:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 June 2019 09:40:45 UTC