Hello, On 10/25/2013 06:53 PM, S.P.Zeidler wrote:
Thus wrote Shane Kerr (shane@time-travellers.org):
We saw two presentations by network architects at the RIPE meeting that used bits in their IPv6 addressing plan to carry meaning beyond simple network topology and packet routing.
For example, declaring a specific bit in the address to be 1 for voice traffic or 0 otherwise. [...]
What should we do about it? As a RIR, nothing.
what about as one of RIPE's WGs? Should we go on and produce a BCP document of some kind? As the author of this addressing plan (https://ripe67.ripe.net/presentations/222-ripe67-yanodd-ipv6-addressing.pdf) , my main motivation for presenting it was to show that it is possible to encode basic information in an addressing plan (without wasting too much space) and still keep it simple . For example, even IPv4 addressing plans were location-aware, that's nothing new. Well, its even easier and more effective in IPv6 addressing, because of the number of bits available. As far as encoding service type, no space is wasted because it is encoded after the /56 boundary ;) , even making it possible for QOS. As I mentioned in the presentation, this is our 3rd or 4th try over the past ~10 years. So far, with the help of some basic heuristics, it seems to be working out fine cheers, Yannis
Otherwise: violations of the KISS principle are rarely a good idea. In this case, you might find out that you snuck yourself into a straightjacket a few years down the line.
regards, spz