Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There's more hope than you think as a developer to recognize those types of IPv6 addresses at a glance. The :: shortcut alone also acts a shortcut for pattern matching. You may have network designs where things like {prefix}::110 is the network printer and {prefix}::beef is the cafeteria's new meat printer. Whether or not you bother to remember what exactly {prefix} is or if in worst case it changes regularly and you can mostly ignore it (after briefly pattern matching that it looks close enough to other IPs in your network).

There's different "rules" from IPv4, but as a developer those mostly don't matter and if your network engineer wants you pattern matching your network's machines, then you can just as easily pattern match your network's machines as with IPv4. (That said, there's privacy reasons your network engineers might not want that, security through obscurity and all that. That can be just as true in IPv4, but fewer companies have enough IPv4 address space to truly obfuscate the network patterns. Life is harder for network engineers in IPv6 not entirely because it "has to be" but because "privacy and security is 'easier' if we use a more complicated approach to IPv6 than we did with IPv4 where we would just sequentially number machines within our allotted space".)



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: