Re: Release criteria proposal: networking requirements

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

 



On Sat, Aug 29, 2020 at 1:57 AM 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?

I contact my machines (even VMs) through <hostname>.local every day, I'd be very angry if it didn't work, and I consider myself a significant amount of people ;o)

_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-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/test@xxxxxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux