979 karma · joined December 31, 2018
Edit: alright, I saw that you mentioned password reuse in another reply, fair enough, it does help against that.
99% of Linux installs are done on some hypervisor... ISO files are absolutely awful for this use case. Yet everyone keeps using them because the tooling is already jumping through thousands of hoops to make it work.
1) Ability to get a personal prefix as a private individual or a small company (not a LIR or LIR-sponsored)
2) Ability to use that prefix with any ISP I choose - similar to how a consumer can migrate their cellphone number to a different provider.
3) RFC 6275 actually implemented
There are other bits and pieces, but I believe if these with 3 things were done, IPv6 would actually have a "killer app" which would make a strong argument for migrating over to v6.
> It simplifies aspects of address configuration
I assume this is referring to SLAAC? SLAAC is...fine. Most managed networks will want the extra control offered by DHCP though and DHCPv6 is currently in a much much worse state than DHCPv4. Also a single interface having at least 2, usually 3 or more (link-local, autogenerated, privacy) v6 addresses on the network is definitely not simpler in any way. Also clients still have not figured out which configuration methods they should actually support - Linux network managers generally default to SLAAC-only and DHCP needs to be explicitly enabled, for Windows setting managed flag in RA works, I believe. Android does not support DCHPv6 at all.
> network renumbering and router announcements when changing network connectivity providers.
Absolutely not. Network renumbering is a breeze when all you need to change is the public address of your gateway and the local network keeps the same local addresses. Prefix translation is awful and no firewalls have good tools to handle changing your v6 prefix.
> It simplifies processing of packets in routers by placing the responsibility for packet fragmentation into the end points.
With respect to fragmentation - yes, but overall this statement is blatantly false. v6 packet processing by routers is much much harder due to the variable length headers.
> The IPv6 subnet size is standardized by fixing the size of the host identifier portion of an address to 64 bits.
Ok, this one is true. Not entirely sure why the author considers this better, but sure, I'll agree.
Presentation - HTTP
Checkmate, OSI-haters.
Have you seen the size of disks and network bandwidth recently? There is absolutely no reason to bother with lossy audio compression.
Go away.
Alternatively, they have drank the microservice kool-aid and think that making a request to an AAA service every time the user wants to do something is just too much overhead (It isn't).
Cool, I need to look into Kubernetes way more then! There hasn't been any single development in the Linux world that has made my job as a sysadmin easier than systemd. Services, Timers and Networking that just works, is concisely defined and can be used across all relevant distros? Hell yeah, I don't ever want to go back into init.d/ifupdown/crontab world filled with bad configuration files, strange footguns and bugs that won't ever get fixed because someone's legacy system might depend on them.
* Human-readable and writable, including on systems where you have only very basic text editing tools * Easy to template (for example mass deployments via Ansible or other such tool) * Easy to use with grep/sed/etc
The format I've found that is easiest to work with is what sysctl and OpenWRT use for their configs. You can have complex hierarchies, but every line stands on its own. This means you don't have to be careful about where in the config a particular line is, if it is in the proper block, etc. Also getting information on a particular sub-item is as easy as running a single grep command.
The cool thing about DNS architecture is the fact that it is decentralized. Mozilla's plan with DoH tries to fix missing features in DNS by getting rid of arguably the biggest killer feature DNS has.
Furthermore, several governments use DNS right now to block websites deemed illegal in their country. Not just authoritarian states that attempt to censor material critical to the regime, but also western countries (copyright infringement, child porn, gambling, etc). Does Mozilla and Cloudflare seriously think they will just go "oh ok, I guess everything is unblocked again now". No, they will either force Cloudflare to do the same or force local ISPs to implement even stronger filtering controls.
"The DNS itself places only one restriction on the particular labels that can be used to identify resource records. That one restriction relates to the length of the label and the full name. The length of any one label is limited to between 1 and 63 octets. A full domain name is limited to 255 octets (including the separators). The zero length full name is defined as representing the root of the DNS tree, and is typically written and displayed as ".". Those restrictions aside, any binary string whatever can be used as the label of any resource record. Similarly, any binary string can serve as the value of any record that includes a domain name as some or all of its value (SOA, NS, MX, PTR, CNAME, and any others that may be added). Implementations of the DNS protocols must not place any restrictions on the labels that can be used."
You are correct that it can not be used in a hostname and I am not sure how it should be encoded when used in a URI, but for a domain name it is perfectly valid.
Indeed, I tested this on my local DNS server running Knot and I can create a domain name with colons in it and it also resolves using dig.