(I'm sending this feedback here because Azure feedback via official channels is printed out and then fed directly into a shredder.)
Can you answer why -- for the love of God -- why Azure IPv6 networking is doled out in microscopically small /124 blocks (16 addresses)!?
The standard is a /64 at a minimum for residential connections, and /48 is recommended for most premises, particularly business connections. Azure could easily obtain a /32 for each of their regions, providing a very roomy 4 billion /64 scopes per data centre.
Right now, if I want to "embrace IPv6" and all of its advantages, such as a flat address space and the elimination of NATs, I will have to either:
1) Juggle a bunch of /124 prefixes and carefully allocate services to them. This is a load of fiddly scripting or manual work.
2) Probably be forced to NAT anyway!
3) Pay for addresses that ought to be too cheap to meter.
Can you answer why -- for the love of God -- why Azure IPv6 networking is doled out in microscopically small /124 blocks (16 addresses)!?
The standard is a /64 at a minimum for residential connections, and /48 is recommended for most premises, particularly business connections. Azure could easily obtain a /32 for each of their regions, providing a very roomy 4 billion /64 scopes per data centre.
Right now, if I want to "embrace IPv6" and all of its advantages, such as a flat address space and the elimination of NATs, I will have to either:
1) Juggle a bunch of /124 prefixes and carefully allocate services to them. This is a load of fiddly scripting or manual work.
2) Probably be forced to NAT anyway!
3) Pay for addresses that ought to be too cheap to meter.