Extend the current WebRTC-focused mDNS implementation to full RFC 6762/6763 compliance with service discovery and non-blocking APIs.
Current state: Partial RFC 6762 + WebRTC ICE draft. Monolithic Conn struct, limited to A/AAAA records, blocking queries, strict name filtering.
TODO
Original motivation
I am looking to use this library for backkem/matter which relies on full DNS-SD capabilities beyond the current Host Resolution (RFC 6762) implementation.
The library currently focuses on A/AAAA records. It explicitly filters out PTR, SRV, and TXT queries required for
Service Discovery.
I would like to contribute support for:
- Service Advertising (PTR responses).
- SRV and TXT record management (including updates).
- Service Subtypes (e.g., _custom._sub._service._udp).
Extend the current WebRTC-focused mDNS implementation to full RFC 6762/6763 compliance with service discovery and non-blocking APIs.
Current state: Partial RFC 6762 + WebRTC ICE draft. Monolithic
Connstruct, limited to A/AAAA records, blocking queries, strict name filtering.TODO
Original motivation
I am looking to use this library for backkem/matter which relies on full DNS-SD capabilities beyond the current Host Resolution (RFC 6762) implementation.
The library currently focuses on A/AAAA records. It explicitly filters out PTR, SRV, and TXT queries required for
Service Discovery.
I would like to contribute support for: