There are several obstacles to overcome, IMHO
1. The companies at the mid size and smaller levels have to invest in newer
equipment that handles IPV6.
if they have gear made in the last 7yrs it's likely already got the
right bits for v6 support, right?
2. The network Admins at the above mentioned companies need to learn IPV6,
most will want there company to pay the bill for this.
for a large majority of the use cases it's just "configure that other
family on the interface" and done.
3. The vendors that make said equipment should lower the cost of said
equipment to prompt said companies into purchasing said equipment.
the equipment in question does both v4 and v6 ... so why lower pricing?
(also, see 'if made in the last 7 yrs, it's already done and you
probably don't have to upgrade')
There is a huge difference between IPV4 and IPV6 and there will be a lot of
'huge difference' ... pls quantify this. (unless you just mean colons
instead of periods and letters in the address along with numbers)
2. The network Admins at the above mentioned companies need to learn IPV6,
most will want there company to pay the bill for this.
for a large majority of the use cases it's just "configure that other
family on the interface" and done.
In the simplest cases, yes. Throw things that often exist in mid to large sized enterprises, like firewalls, DHCP servers, load balancers, log analyzers, etc, having to upgrade $XYZ to get IPv6 support or fix bugs, and there's a bit more to it. These are not insurmountable problems, but administrative/political/financial inertia is a real thing in many shops.
3. The vendors that make said equipment should lower the cost of said
equipment to prompt said companies into purchasing said equipment.
the equipment in question does both v4 and v6 ... so why lower pricing?
(also, see 'if made in the last 7 yrs, it's already done and you
probably don't have to upgrade')
There could be problems with things like DHCPv6, depending on how the user's ISP provisions service. SLAAC 'just works' for the most part, but if the FooTronics 1000 an all-in-one router/firewall/wireless AP/printer/
belt sander/toaster from $BIGBOXSTORE doesn't come with firewall settings that let IPv6 work just out of the box, or at least have a big, shiny "Make IPv6 work" button, support calls will be generated. ISPs and FooTronics both hate support calls.
Again, playing devil's advocate here. I just don't look forward to dealing with support calls from customers who bought kit from vendors who slammed in IPv6 support as quickly and cheaply as possible.
jms
For consumers I think I would phrase it more as the "next generation internet"
and you need IPv6 in order to be able to connect to it and that eventually
some sites you want to connect to may not be accessible over the current
internet. Something like that.
Ah, it's running Internet-As-A-Service in the Cloud using a Client-Server
architecture with time sharing. There's nothing there but buzzwords.
First figure out what consumers actually get for it. Only after you know
why they want it can you then figure out how to market it. Generally what
you're looking for is "good, fast, cheap," only more so than IPv4.
Lee
Teksavvy does it (tunnel I believe) if you ask.
Otherwise it's the usual:
- 'why do we need this?';
- 'It costs money to upgrade for something low-demand';
- 'What's the market?';
- 'I don't have time';
- 'Aw gee do I have to??'
wfms
Those all sounds like legit business questions.
-jim
Really. You're really completely discounting ICANN in having any
leadership or participative role in the IPv4/IPv6 transition?
Interesting.
Thank You for responding.
If mid to small companies have equipment made in the last 7 years, they will not need to replace equipment.
Most net admins at the mid to small companies have no idea about IPV6.
Cost is a major consideration at the mid to small size companies, if they need to upgrade equipment.
The difference between IPV4 and IPV6 for someone not familiar is huge,
1. There is a totally new format dotted decimal to colon.
2. The 32 bit to 128 bit is/or can be quite challenging for some net admins.
Thank You
We offer IPv6 over DSL and it's native, but it's opt-in at the moment. I
have the ability to enable it for all our DSL users but we're holding
off due to training issues more than anything.
-Gabe
Haven't seen any yet. Probably because you can't make money with IP addresses
like you can with TLD's....
(Now where's my Nomex overalls? 
What leadership position have you seen them take ASIDE from marketing
(in the last 2-3 yrs, but most of that has been ISOC not ICANN
directly) in the last 5 yrs or so?
-chris
In other words, upgrading or replacing liveware is more expensive than
getting the hardware upgraded....
2. The network Admins at the above mentioned companies need to learn
IPV6,
most will want there company to pay the bill for this.
for a large majority of the use cases it's just "configure that other
family on the interface" and done.
In the simplest cases, yes. Throw things that often exist in mid to large
sized enterprises, like firewalls, DHCP servers, load balancers, log
sure thing, except that the poster did not talk about mid/large
enterprises, his point was about small ones... where v6 probably
doesn't matter for things listed except firewalls.
analyzers, etc, having to upgrade $XYZ to get IPv6 support or fix bugs, and
there's a bit more to it. These are not insurmountable problems, but
administrative/political/financial inertia is a real thing in many shops.
3. The vendors that make said equipment should lower the cost of said
equipment to prompt said companies into purchasing said equipment.
the equipment in question does both v4 and v6 ... so why lower pricing?
(also, see 'if made in the last 7 yrs, it's already done and you
probably don't have to upgrade')
There could be problems with things like DHCPv6, depending on how the user's
ISP provisions service. SLAAC 'just works' for the most part, but if the
FooTronics 1000 an all-in-one router/firewall/wireless AP/printer/
belt sander/toaster from $BIGBOXSTORE doesn't come with firewall settings
that let IPv6 work just out of the box, or at least have a big, shiny "Make
IPv6 work" button, support calls will be generated. ISPs and FooTronics
both hate support calls.
sure.
Again, playing devil's advocate here. I just don't look forward to dealing
with support calls from customers who bought kit from vendors who slammed in
IPv6 support as quickly and cheaply as possible.
yup. I sort of don't think the arguement about 'business connections'
is even relevant though. I'd bet that the vast majority of connections
to the 'net are actually consumer ones... Fixing those shoudl be the
goal for the ISP side, so they can continue to grow customer bases
without worrying about CGN and other associated expenses.
Once you solve out the consumer problems the business link ones should
'just work'. Whether the enterprise wants to upgrade/install/side-step
into v6 is not relevant.
these seem like the smallest of v6 problems, actually... and I would bet:
http://getipv6.info
would be helpful (eventually when small/mid-sized businesses start
trying to transition)
Can we stop with the lame "every person, and their dog!" numbering plans. The same MISTAKE has been repeated so many times in recent history you'd think people would know better. It's the exact same wrong-think that was applied to the 32bit IPv4 addressing in an era where there were a few dozen computers worldwide. (also that IPv4 was an "experiment" that was never imagined to be this big.)
We're smart enough to mis-manage *any* resource. It's just a matter of "when" that it'll be back to haunt us. ("not within my lifetime" seems to be a very popular compromise.)
How much IPv6 space would you propose an ISP provisions for each of its residential users?
jms
You are correct, but this is the tip of the iceberg as other configurations will need to come into play as pointed out by several people on this thread.
This learning curve is not impossible, if the net admin really applies his/her self to learning it.
Thank You
Brian -
Any suggestions on how ARIN should reach those CIO's in the meantime?
(so as to reduce the number who experience such surprise) We've done
some attempts at outreach to that community, and have advice from PR
firms, etc., but I'm interested in a more "real world" perspective on
getting their attention before we hit the wall...
Thanks!
/John
John Curran
President and CEO
ARIN
I'd still say that for uptake across the board the mid/small business
(and even large business) isn't relevant. The numbers of these are so
small as to be insignificant to the problem.
Solving the problem for end-users seems like where ISP folk should
spend their time, and really it's in their best interest to do that so
they can keep expanding their customer base as ipv4 resources become
less available in their networks and globally.
That is a good question and I wish I had a good answer. I'm trying to beat
the drums where I work for IPv6 and it is tough because nobody has thought
about it and in our situation I actuallly have a good case. We develop
mobile apps and with the amount of IPv6 VZW and T-mobile are doing having
at least IPv6 to the load balancer at least needs to be thought about.
It is just tough because most organizations have just not been thinking
about IPv6 at all and it is going to take "something" to get it on their
radar.
But I thought ICANN was supposed to be the new and future nexus for
all things internet governance?