Re: Release criteria proposal: networking requirements

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Aug 28, 2020 at 5:56 PM Adam Williamson
<adamwill@xxxxxxxxxxxxxxxxx> wrote:
>
> On Thu, 2020-08-27 at 10:06 -0600, Chris Murphy wrote:
> > On Fri, Aug 21, 2020 at 6:11 PM Adam Williamson
> > <adamwill@xxxxxxxxxxxxxxxxx> wrote:
> > >
> > > ==== Basic networking ====
> > >
> > > It must be possible to establish both IPv4 and IPv6 network connections
> > > using DHCP and static addressing. The default network configuration
> > > tools for the console and for release-blocking desktops must work well
> > > enough to allow typical network connection configuration operations
> > > without major workarounds. Standard network functions such as address
> > > resolution and connections with common protocols such as ping, HTTP and
> > > ssh must work as expected.
> >
> > What about mDNS?
>
> ehhhhhhh
>
> I am probably a bit biased on this front because I always found mDNS to
> be a pile of garbage and gave up trying to use it a while back. :P But
> if a significant amount of people are actually using it and relying on
> it, adding it might make sense. Anyone else have input on this? Who out
> there does use mDNS?

The IPP Everywhere specification requires clients to support DNS-SD
(mDNS is part of that) or WS-Discovery. Printers are required to
support both DNS-SD and WS-Discovery. Avahi and systemd-resolved
support DNS-SD, functionally equating DNS-SD and mDNS.

Final release criterion says printing via the generic IPP driver must
work. This implies discovery or you can't print. Or accept a
craptastic user experience by fudging the requirement to say, well as
long as an IP address works, the criterion is met.

It's even less of a leap if folks can't discover other services like
SMB shares. That's more common than printing.

Between avahi and systemd-resolved, I'm not sure which one is more
dependable for blocking on. Or whether their maintainers would be on
board with such a criterion. At least for F33, Avahi is what we're
using on desktops for this. Both resolve and respond are disabled in
systemd-resolved so if it's better to do this with systemd-resolved,
then it probably needs a Fedora 34 feature proposal.


-- 
Chris Murphy
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux