W3C home > Mailing lists > Public > www-tag@w3.org > September 2017

Re: Local service location advice

From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 12 Sep 2017 09:45:19 +1000
Message-ID: <CABkgnnXJn=kSnQHUQr2Adiq198u9PYjD=ZmA7RkFebRDJXT=UA@mail.gmail.com>
To: T Guild <ted@w3.org>
Cc: Public TAG List <www-tag@w3.org>
On Tue, Sep 12, 2017 at 5:51 AM, Ted Guild <ted@w3.org> wrote:
> In the present spec draft we have a hard-coded hostname, wwwivi. It
> will be used in wss:// and potentially later https:// URIs.

If this remains, the IAB [1] might have some things to say about the
use of the global namespace.  It seems like in terms of names, .local
is a better fit for your use case.  Though I suspect that you are
looking for something more than just the right name to give the thing.

There's the question of how this thing might be authenticated, for
instance - which I see you have some thoughts on already.

On that broader topic, you are right that this is possibly the same
problem as other groups are facing.  I can't claim to have a good
answer, though I have heard MANY ideas.  Your assumed model
(preprovisioning certificates if I understand it) might make your
particular situation different enough that it doesn't run afoul of the
standard set of issues with authenticating local services, just the
standard set of preprovisioning problems.

[1] This one: https://iab.org, and not that one: https://iab.com
Received on Monday, 11 September 2017 23:45:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:57:16 UTC