Talk:Zero-configuration networking/Archive 1

IPstack template?
Question: Why is the IPstack template (the "Internet Protocol Suite" box) on this page? Per the fact that Zeroconf is no longer listed there (if it ever was), I personally think that it should be removed. If the community is against that, I would suggest that Zeroconf be added, but please note that there has been much discussion (read: arguing) about exactly which articles are listed. Anyone have any ideas? I'd hate to remove IPstack if someone had a good reason it should be there.


 * I agree the IP stack can be removed. (by the way, please don't forget to sign you comments next time!) -- Macfreek 12:07, 21 September 2005 (UTC)


 * I agree, since Zeroconf is not a protocol and definitely not a standard part of TCP/IP. -- HarrisX 13:43, 9 January 2006 (UTC)

Proposed move to Zero configuration networking

 * Since this is a description of a "set of techniques" shouldn't the article's name be Zero configuration networking instead of Zeroconf? As the introduction notes, the article is about a set of techniques involving multiple and sometimes competing protocols and technologies.  The current name, possibly originating from an IETF working group, is an abbreviation which gives the impression of being the name of a specific product or piece of technology.  72.244.201.28 (talk) 16:40, 28 May 2008 (UTC).
 * ✅. Anthony Appleyard (talk) 04:43, 3 June 2008 (UTC)

Wording
I disagree with the wording changes. Zeroconf is not merely Link-local address configuration. It provides standards for service discovery and DNS services in addition to choosing apropriate IP addresses. I think the previous wording of "set of techniques" is more appropriate. Furthermore, the change to the list "Problems Zeroconf solves" doesn't make sense. Autodiscovery of services is not a problem, it is a solution. Either the list title should be changed or the wording should revert back to the original. TMC1221 (talk) 20:27, 5 July 2008 (UTC)

Yes, I agree with your assessment. I have reverted to prior language. I want to get the formal term for address configuration into the introduction because it's used in other articles, but I put it, admittedly, in the wrong place. Kbrose (talk) 21:29, 5 July 2008 (UTC)

I also changed the heading in the list (of problems), which I had overlooked, because I didn't think they were 'problems' in the first place, and the language used wasn't very professional. Thanks for watching out. Kbrose (talk) 21:39, 5 July 2008 (UTC)

Nice work. TMC1221 (talk) 22:11, 5 July 2008 (UTC)

Abbreviation
The page uses the name 'zeroconfig", every reference on this page (so far) is "zeroconf". Google gives these results: 266,000 for "zeroconf" and 13,000 for "zeroconfig".I'm going to change the abbreviation. -- Aronzak (talk) 12:16, 17 May 2009 (UTC)

APIPA
APIPA is redirected here but not explictly explained or mentioned. Pretty important technology as most Windows boxes (i.e. the majority of the World's desktops) default to this behaviour when there are no IP addresses defined and there is no DHCP server. So either it needs it's own page or a section here. IMO, this article is not very authoritive if it doesn't bother to explain APIPA. —Preceding unsigned comment added by 128.40.192.51 (talk) 11:01, 26 November 2009 (UTC)
 * According to msdn, APIPA is a procedure and set of guidelines for performing these configuration functions, not an actual protocol. It first appeared on the Windows platform in Windows 2000. Given I'm not into the subject, if you think APIPA is worth mentioning then be bold and expand the "Link-local IPv4 addresses" section, or edit APIPA to make it a new article. tankmiche feedback? 13:33, 26 November 2009 (UTC)

NetBIOS
Souldn't NetBIOS be mentioned under the section about Windows? While not a part of zeroconf, it does provide name resolution and some other basic elements of zeroconf-like systems. 212.159.69.172 16:42, 28 January 2007 (UTC)
 * Yes. NetBIOS is the multi-cast name resolution part of zero-conf. MS RFC3927 is the Address Configuration. NetBIOS has been partly replaced by uPnP, but in practice it is still a common implementation: The HP printer I am configuring today supports mDNS and NetBIOS, not uPnP.203.206.162.148 (talk) 04:44, 25 July 2011 (UTC)

mDNS Packet structure contribution
I revived Multicast DNS and relocated the new contribution of mDNS packet structure there. --Kvng (talk) 14:46, 4 September 2011 (UTC)