Pol leta bo, odkar je RIPE posnel video inteview z Randy Bushem, kjer so ga vprašali, naj pove svoje razmišljanje o uvedbi IPv6 na splošno. Še enkrat sem si ogledal posnetek in o vsem skupaj na novo razmislil. Njegove izjave, trditve, smernice in strahovi so veljali takrat in veljajo še sedaj, pol leta po datumu posnetka. Kaj nam da to misliti? A se mogoče vse skupaj odvija prepočasi?

V momentu, ko se bomo zaleteli v IPv4 zid, bodo na voljo dva tipa strokovnjakov: tisti, ki bodo imeli IPv6 izkušnje ter znanje in tisti ki tega ne bodo imeli. Ah, kako preprosto…

Nesmiselno se mi zdi direkt prevajati, kaj je Randy povedal, zato bom kar tu dodal transkript videa:

We really think, that everybody else should not test and deploy IPv6. It’ll be great for us.

We started in the mid 90s. We had a parallel network, based on the KAME stack in BSD that was running IPv6; so we could supply IPv6 to a customer and IPv4. But they came over separate wires; dual stack didn’t exist. Every time that two transports or two layers have not been congruent it’s been deadly in the NOC with debugging. If you and I want to experiment with a new protocol, we just install it on our two computers and the Internet doesn’t have to change. If we put all the smarts in the middle and if we have to put a bunch of NATs and carrier grade NATs in the middle of the network that kills that.

The actual problems in deploying today. There’s some key problems:

– Customer Premises Equipment (CPE)
– For the content people: Load balancers
– Intrusion Detection Systems and security products; checkpoint etc. – very poor, very poor.

And what the user wants (don’t give them a list of features!) is parity with IPv4. All the things I use in IPv4, I want in IPv6. It’s what’s been called the chicken and the egg problem because the customer doesn’t want it. They’re never going to want it. They want the results, they don’t care how they’re delivered. That’s my problem, not their problem. They just want their MTV, and their email and their DNS, and whatever it is.

And the problem is, because it doesn’t make sense economically right now. The IPv6 backbones are poorly interconnected, there’s a bunch of tunneling, there’s a bunch of MTU problems. As I said, there are these blockers at the vendors. Because there’s not real money there, there’s no real economic social pressure to fix those things.

As we hit the IPv4 wall, that economic pressure will be there. Three years from now when they can’t get IPv4 space there are going to be two kinds of players in the game. Those that have IPv6 experience, and paid for it incrementally and they’re just going to keep going like this. And there are going to be those who had no IPv6 experience and didn’t prepare and their dollar curve or Euro curve or Yen curve is going to be like this. Their learning curve is going to be like this. The vendors who did not do early IPv6 development are going to say, “We’ll give you a product in a year or two,” while the vendors who did say “Now”, and you know who is going to survive, it’s what’s called present value.

So, three years out, you are going to have this cost. What’s the present value of reducing that cost by 50%? And what you’re willing to spend now, to do that. And I think it’s worth it.

Our enterprise customers, which are a big customer base, they have dual stack. It’s not even a question we ask. We’re putting NAT-PT equivalent in those little boxes so those people can run a pure IPv6 network if they want, not even dual stack and still get to the IPv4 Internet. So, people should go out and do their front end. Just put a little makeup on your face, you don’t have to change your life. Fix your DNS, make it dual stack. Take your mail server, make it dual stack. Take your web server, make it dual stack. For two reasons: you gain experience and secondly, what faces the world is dual stack, and that will increase the economic pressure that’s going to get the kinks out of the system, to have enough experience to say “ok, I can’t get senior management to buy off on what I need for the transition. I at least know what I’m going to need for the transition.”

If you start now, you have a reasonable planning horizon. You’re talking years. If you don’t start now and you wait three years, you’re not going to have a reasonable planning horizon. There’s toolset parity essentially between IPv4 and IPv6. So what you’re used to, you’re not really going to have to learn a lot more. As Gaurab Upadhaya said: “96 more bits, no magic.” But we need these these 96 more bits, desperately. Desperately!

Get the experience. Get the experience. Otherwise, you are going to be blindfolded when you walk into the wall!

Vaš IP naslov (ali ste na IPv6 ?):
3.133.132.25

Comments(0)