* Anfinsen, Ragnar > My goal with my question was to find sensible arguments for keeping IPv4 > as a native service for now
Maybe I'm being dense, but you seem to already have all the answers to this question yourself? For example: - «The cost/benefit of doing anything else than keeping IPv4 as a native service for now does not add up» - «Spending money on IPv4 addresses and keeping IPv4 as a native service is for now far cheaper than any alternative like MAP, lw4o6, or CGN» - «Doing something else than keeping IPv4 as a native service doesn't work in the real world, even though the ideology is nice» - «We are not yet at the magic threshold where we can realistically look into any alternatives to keeping IPv4 as a native service» - «Doing something else than keeping IPv4 as a native service is out of the question because it will make or service no longer "premium"» - «Doing something else than keeping IPv4 as a native service won't fly with the business side of the company» Considering the business side of your company is apparently already persuaded by these arguments and are on board with your desire to keep IPv4 as a native service for now, I am somewhat puzzled as to why you see a need for further arguments to bolster your position. But again, I'm probably just being dense. Tore
