On Sun, Jun 8, 2025 at 9:30 PM Ben Olden-Cooligan <[email protected]> wrote:
> > > On Wed, Jun 4, 2025 at 9:02 AM Ralph Little <[email protected]> wrote: > >> Hi, >> OK, I will draft something up for the standard. >> >> If there is anything else to update the standard with, perhaps people >> could let me know. >> Just to be clear, I am not changing the interface with this update, just >> adding come clarification, so if anybody feels that there is anything else >> unclear in the standard, they should possibly raise it now. >> > > Something that would be nice (though perhaps a bigger ask): document how > network discovery (with Avahi/Zeroconf/Bonjour/mDNS) and TCP connection > works with the saned/net. The current version of the spec says "SANE does > not specify a specific transport protocol" but it would be nice if it > contained enough information to implement an actual alternative sane-net > client or server. > > According to here, it looks like the mDNS service type is "_sane-port._tcp", > but I'm not sure about the rest. > > https://gitlab.com/sane-project/backends/-/blob/master/frontend/saned.c#L171 > > The network protocol is pretty well specified in the SANE spec <https://sane-project.gitlab.io/standard/1.01/net.html>, there are many frontends that implement sane-net clients: http://www.sane-project.org/sane-frontends.html. I wrote the jfreesane frontend, and I've also written a wireshark dissector for the sane net protocol, all using the spec. I don't think the spec addresses automatic discovery. >
