Closed raulk closed 4 years ago
A Recommendation has at least TWO implementations demonstrating interoperability.
A Candidate Recommendation has ONE implementation serving as the Reference Implementation.
This mDNS spec currently has no known libp2p implementations.
mDNS support in go-libp2p and js-libp2p are non-compliant because they predate this spec, and this spec introduces breakages.
Hence, as per above, we demote this specification to the maturity stage it belongs to: Working Draft.
I've also implemented in .Net (c#) see peer-talk
A Recommendation has at least TWO implementations demonstrating interoperability.
A Candidate Recommendation has ONE implementation serving as the Reference Implementation.
This mDNS spec currently has no known libp2p implementations.
mDNS support in go-libp2p and js-libp2p are non-compliant because they predate this spec, and this spec introduces breakages.
Hence, as per above, we demote this specification to the maturity stage it belongs to: Working Draft.