1. Yes, it'd be a compromise, for a future of having v6 actually adopted. I'm surprised nobody has yet mentioned that it'd burn ~32 bits of the v6 address space just for v4 addresses. Once your network is all-v6 and nothing is relying on the mapped addresses, you drop this.

2. Because a bunch of those are also stuck running v4 on the side and would probably love for v6 adoption to move forward so they can drop the technical debt.

3. https://www.google.com/search?client=firefox-b-1-d&q=what+is...

4. My v6 addr is different from my v4, is what I'm saying.

5. My bad, I mixed up "octal" and "octet." It's decimal notation, which is made of octets.

6. Yeah, idk, it's what they said. Do people memorize IPs, probably not, except for local 192. or 10. ones. Do people note them in short-term memory while debugging, yes. The colon-separated hex is more annoying to me, maybe because I'm used to decimal, but then again so are most people.

7. I would say then, common workaround for enterprises that actually need/want to use ipv6 sooner or later.

8. Gee, I'm sorry for the mixup. Seems you got which one I meant anyway.

9. It probably is too late to do this everywhere. Maybe ISPs could hand out 4-mapped v6 addresses at least, idk if that's possible.