I am sure it has come up a number of times, but with IPv6 you can make up fancy addresses that are (almost) complete words or phrases. Making it almost as easy to remember as the resolved name.
It'd be nice in a weird geek sort of way (but totally impractical) to be able to request IPv6 blocks that have some sort of fancy name of your choice.
2001:db8:dead:beef::
dead:beef::
dead::beef
As seen on http://en.wikipedia.org/wiki/Magic_number_(programming)
"DEADBEEF Famously used on IBM systems such as the RS/6000, also used in the original Mac OS operating systems, OPENSTEP Enterprise, and the Commodore Amiga. On Sun Microsystems' Solaris, marks freed kernel memory (KMEM_FREE_PATTERN)"
Bonus points if your organisation's name only contains HEX characters.
able to request IPv6 blocks that have some sort of fancy name of your
choice.
4-character or shorter hex words, for your reference:
aced
ace5
ac1d
Thanks.
I wonder about 2001:db8
The person who made it up must like the movie "2001: a space odyssey" and Aston Martin. Even though I don't think they ever made a db8, but they made or make db2, db4, db5, db6, db7 and db9 amongst others.
For IPv6 I consider it "address spam". My content filter will give you some extra tiny score if your MX uses such an address.
If you want to do it, make sure you do understand the restrictions that apply to IPv6 addresses, like U/G bits, etc. Too many people unfortunately just think it's cool in a weird geeky sense and violate RFCs with them. I was very close to write an article about that after W6D...
In a message written on Fri, Jun 24, 2011 at 09:10:53AM +0000, Bjoern A. Zeeb wrote:
If you want to do it, make sure you do understand the restrictions that apply to IPv6 addresses, like U/G bits, etc. Too many people unfortunately just think it's cool in a weird geeky sense and violate RFCs with them. I was very close to write an article about that after W6D...
Perhaps I missed something in an RFC somewhere, but I believe those
bits only have meaning locally on an Ethernet LAN. They have no
meaning when used on non-Ethernet networks, for instance POS or on
a Loopback. If someone wanted to use them for a /128 virtual for
their web site for instance that would be ok.
Or, turning that around, if you assume an IPv6 address is part of a /64
on an Ethernet network, you have made a false assumption.
In a message written on Fri, Jun 24, 2011 at 09:10:53AM +0000, Bjoern A. Zeeb wrote:
If you want to do it, make sure you do understand the restrictions that apply to IPv6 addresses, like U/G bits, etc. Too many people unfortunately just think it's cool in a weird geeky sense and violate RFCs with them. I was very close to write an article about that after W6D...
Perhaps I missed something in an RFC somewhere, but I believe those
bits only have meaning locally on an Ethernet LAN. They have no
meaning when used on non-Ethernet networks, for instance POS or on
a Loopback. If someone wanted to use them for a /128 virtual for
their web site for instance that would be ok.
Or, turning that around, if you assume an IPv6 address is part of a /64
on an Ethernet network, you have made a false assumption.
A load-balancer attached to it's first hop router via a /126 may well advertise the virtual ip's it's serving (and treat them) as /128s. the assumption that links are /64s falls down a lot (even on ethernet) when most of them are point-to-point.
