0

How practical would it be for, say, an ISP's provider to develop a Bonjour-like protocol for the Internet? I can think of a few uses for this technology:

A businessperson who needs something printed at a FedEx office could select a FedEx print/request server as if the server were a local printer. FedEx could then charge the user when s/he picks up the print job.

A photographer who wants her photos printed at the local WalMart could select WalMart's photo print server as if it were a printer on the local network.

closed as primarily opinion-based by heavyd, fixer1234, JakeGould, DavidPostill, Nifle Mar 13 '15 at 23:17

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

  • “How practical would it be for, say, an ISP's provider to develop a Bonjour-like protocol for the Internet?” If you have ever worked with office LANs you know how much of a headache the networking traffic caused by Bonjour-like protocols are. It literally saturates networks to the point of making it unusable. Fine in a small home network though since you will never really reach the scale where it becomes an issue at home. But many places actually disable the broadcast traffic on their networks from the switch/router to kill this stuff. On an Internet scale? 100% no way. – JakeGould Mar 13 '15 at 5:17
  • @JakeGould: Bonjour doesn't use broadcast, and AFAIK it was specifically designed to let clients cache everything. Besides, just how many DNS queries exactly you need to saturate 100 Mbps? (If it was NetBIOS on the other hand, yes, I could believe it being painful.) – grawity Mar 13 '15 at 9:21
1

Ok, before this gets closed, I'll give you my thoughts on the matter. I believe that ISPs already implement everything in the IETFs zero-conf specification, using traditional DHCP and DNS. In the worst case (a completely unmanaged network) AVAHI is often sufficient.

The thing you seem to want, is service discovery, which is quite possible, but what you are missing is the matter of control. The service operator should always be in charge of deciding what to make discoverable, and how to do it. It is not the ISPs right to expose the services on my network at a pure TCP/IP level.

Secondly, the Internet at large is too large to ever be "discoverable" in a meaningful way, unless resolution is scoped, probably geographically. On the local level, the only reason that Bonjour works is that its scoped to a LAN. If iTunes ever even considered sharing my music with my neighbors, I would be forced to slay it mightily. Bonjour was made for people who can't be bothered to configure either end of a service provisioning.

Using the WWW as an overlay, server admins and developers can implement services over the web that are discoverable, using a wide array of underlying technologies to implement standards for discoverable services. We can discover them with search engines, and access them with whatever applications we write or otherwise obtain which were designed to consume their provisions. Fedex is free to manage the many printers in many differant locations, all of which are in some state (idle, printing, queueing, etc) at any given instant using software that is designed and configured as They want it, not the ISP.

If Fedex wanted to set up web printing, they could do so now, and you could print to them using the MS Internet Printing drivers to do so. line printing comms protocols were never really designed to provide the robustness you need to hit a printer on the other side of the world anyway. New drivers and protocols would be needed to directly access the device in the same way they do one connected via USB. Your OS might choose to show it to you, and make it look identical to a local printer, or they might not.

So, in sum, I would argue that we already have all the capability to do what you want if we choose to do it, and that freedom to do so or not is essential to keeping the Internet free and democratic. Placing the responsibility at the ISP level is inappropriate, and would cause wide divergence between ISPs in ways that really should be predictable commodities. imagine if your service was only available on one ISP, or even 4 out of every 5. It would be pandemonium, at first, until the entire internet degraded into sets of stagnating walled gardens like Apples. The internet cannot be allowed to become a cable package.

Not the answer you're looking for? Browse other questions tagged or ask your own question.