Yes, I was mistaken on this point. I got confused over someone's discussion of RFC 1918 with what the standard actually said. I should have checked closer before I posted that point. But I still don't see the reason for this function. In today's networking, the actual value you should use for a mask on an interface on the public Internet is decided by a combination of the address range you have and how it is divided by your local networking people. On the private networks, it is entirely up to the local networking people. The value returned by this function is only a guess, and I think it is more likely to mislead than to inform.
On Friday, March 8, 2019 at 12:51:41 PM UTC-5, Tristan Colgate wrote: > > Just on a point of clarity. DefaultMask is returning the mask associates > with the network class. RFC1918 specifies a bunch of class A,B and C > networks for private use. E.g. 192.168/16 is a set of 256 class C networks. > The correct netmask for one of those class Cs is 255.255.255.0 (/24). So > the function returns the correct thing by the RFC. > > > >> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
