[experimental api] mDNS APIs for IoT and p2p extensions

RESOLVED INCOMPLETE

Status

enhancement
P5
normal
RESOLVED INCOMPLETE
a year ago
11 months ago

People

(Reporter: dietrich, Unassigned)

Tracking

(Blocks 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

a year ago
Create experimental WebExtension APIs for mDNS for p2p and IoT experimentation purposes. The WoT project and also our dweb explorations will utilize these.

This is distinct from bug 1342724, which is about implementing Chrome's apps API for mDNS.
Component: WebExtensions: General → WebExtensions: Request Handling
Whiteboard: [design-decision-needed]
Hi Dietrich, this has been added to the agenda for the WebExtensions APIs triage on May 29, 2018. Would you be able to join us? 

Here’s a quick overview of what to expect at the triage: 

* We normally spend 5 minutes per bug
* The more information in the bug, the better
* The goal of the triage is to give a general thumbs up or thumbs down on a proposal; we won't be going deep into implementation details

Relevant Links: 

* Wiki for the meeting: https://wiki.mozilla.org/WebExtensions/Triage#Next_Meeting
* Meeting agenda: https://docs.google.com/document/d/1Y_oYPldTT_kQOOouyJbC-8y3ASIizScLKFRhQfsDQWI/edit#heading=h.v63i1wz9d1pc
* Vision doc for WebExtensions: https://wiki.mozilla.org/WebExtensions/Vision
Hey dveditz, could you help us out with a security review for this proposal? 

If it looks like the code will be maintained and dveditz is ok with the proposal, we will approve the design.
Flags: needinfo?(mixedpuppy)
Flags: needinfo?(dveditz)
It looks like mdns has not been touched since 2016, and was landed and maintained solely for the flyweb project.  IMO this places the api into unmaintained mode.  

Either there are some platform plans (jduell? any idea) or there are product plans (mconca? could you find out) that could indicate the mdns support has legs, or we'd have to potentially take on maintenance to use it as an api.
Flags: needinfo?(mixedpuppy)
Flags: needinfo?(mconca)
Flags: needinfo?(jduell.mcbugs)
Another note on this:

I just re-read comment 0 and it mentions creating an experimental api for this.  There is no reason that cannot be done.  Dietrich, can you shed some light?  If experimental APIs are fine enough for now, no design-decision is necessary.
Flags: needinfo?(dietrich)
Reporter

Comment 5

a year ago
I wish I'd gotten a ni? for the meeting. I definitely would've joined if I'd seen that this conversation was happening!

Shane, your last comment is correcto:

* Irakli and and I are going to be prototyping out a set of experimental WebExtension APIs for a set of primitives that enable a set of p2p/dweb/IoT use-cases.

* The purpose of these experiments are not to put them on a track to being adopted as WebExtension APIs. We're not ruling that out at some point in the future, but it's not a goal at this time.

I'm filing the bug so that the request is officially logged, and so that we can point people asking about it at these requests.

Feel free to close all these bugs if they're interfering with your product development process - we can point people at the closed bugs easily enough.

I'm canceling the ni?s since they're not really needed at this point.
Flags: needinfo?(mconca)
Flags: needinfo?(jduell.mcbugs)
Flags: needinfo?(dveditz)
Flags: needinfo?(dietrich)
Whiteboard: [design-decision-needed]
Summary: mDNS APIs for local network discoverability for IoT and p2p extensions → [experimental api] mDNS APIs for IoT and p2p extensions
Marking this as P5 incomplete until we have clear directive.
Status: NEW → RESOLVED
Last Resolved: a year ago
Priority: -- → P5
Resolution: --- → INCOMPLETE

Updated

11 months ago
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.