I believe the port is in progress. I want the nss-mdns functionality without the avahi dependency, that way we would have a "native" mDNS implementation, and by that I mean, have gethostbyname and friends resolve .local hostnames by mDNS. We would also need a mDNS responder daemon.
avahi depends on a bunch of software, and to my knowledge it's main concern is with DNS-SD, the mDNS stack is in nss-mdns. nss-mdns in turns uses avahi as the responder daemon. We could think of having the other zeroconf stuff after having a solid mDNS stack (mainly ipv4 address selection). Later we could integrate avahi with our mDNS stack and ipv4 address selection and have proper DNS-SD. What do you guys think ? >From mdns site: nss-mdns is a plugin for the GNU Name Service Switch (NSS) functionality of the GNU C Library (glibc) providing host name resolution via Multicast DNS (aka Zeroconf, aka Apple Rendezvous, aka Apple Bonjour), effectively allowing name resolution by common Unix/Linux programs in the ad-hoc mDNS domain .local. nss-mdns provides client functionality only, which means that you have to run a mDNS responder daemon seperately from nss-mdns if you want to register the local host name via mDNS. I recommend Avahi.
