So I was curious, has anyone managed to penetrate the black hole that
appears to be surrounding any actual details on Verizon FIOS IPv6
deployment? Their last official announcement indicated they would start
deploying it in 2012, and clearly that didn't happen. I've been asking on
and off for a couple of years, and never been able to get any actual answer
as to when it might be available or why it is being so delayed. Comcast has
www.comcast6.net, which evidently tells you when you're going to get it, if
you don't *already* have it. From what I can tell, most large providers, if
not already providing it, at least have some reasonable timeline as to their
progress...
If you find the answer, you win the prize.
I've tried shaking numerous trees (front-line customer service, my VZB sales person for $dayjob, other people I know who work at Verizon, etc...) to get an answer on this and each time I got different responses. I heard everything from trials being done somewhere in Florida (about a year ago, but Florida does me no good), to the rollout was on hold because the set-top boxes didn't work with it (wasn't about to explain dual-stack to them), to "Verizon has plenty of version 4 addresses, so there's no rush to deploy IPv6". More than one response included the caveat that "we haven't been trained on any IPv6 stuff yet", so I guess any sort of large-scale rollout is not in the immediate future.
I don't fault the front-line customer service folks for this. If they don't know, they don't know. What I do find fault with is that the people the front-line reps can escalate to either don't know, won't tell, or won't ask their escalation points. Attempts to speak directly to an escalation point were met with "well, I can put a note in your account that you asked about it...".
It's 2014. Comcast is kicking Verizon's butt at v6 deployment (I've told VZ reps that several times as well...). There really is no excuse for total silence from Verizon on this.
I have a tunnel through HE and it works very well, but it would be great to have native v6 at home.
jms
We have fios for some office locations and can't get jack out of our
sales rep; just the same well it's being tested bs. It's as if the only
people at VZ that know IPv6 went to the wireless side, where I can do
native dual stack all day long on my phone, tablet and hotspot, but the
Fios folks have absolutely no clue. It's really quite annoying. Even a
wait 24 months would be better than nothing at all.
We have fios for some office locations and can't get jack out of our
sales rep; just the same well it's being tested bs. It's as if the only
... snip...
Fios folks have absolutely no clue. It's really quite annoying. Even a
wait 24 months would be better than nothing at all.
I think the word you are looking for here is 'shameful', not 'annoying'.
The only luck I've had with IPV6 on FIOS is via he.net 
You would think in 2014
they would have their act together, even Comcast has deployed it pretty widely.
I've heard of folk in and around the NYC metro getting set up for v6
by escalating through their commercial account teams, or the field
service managers who went out to their homes to supervise their
early-adopter [X]GPON ONT installations. This isn't to say the
process was particularly easy or fun for those involved, however there
is a light at the end of the tunnel.
It's not immediately clear the extent of configuration work needed
behind the curtains -- whether routing and addressing needed to be set
up in an ad hoc manner, or if there was merely a magic "allow v6
ethertype" checkbox in an OSS needing to be checked to make RAs start
working, however I've heard various rumblings pointing at the latter.
However you slice it, I agree their laid-back approach at
implementation is shameful, and should be called out wherever
possible.
HTH,
-a
I've heard of folk in and around the NYC metro getting set up for v6
by escalating through their commercial account teams, or the field
'commercial account teams' == business customers?
service managers who went out to their homes to supervise their
early-adopter GPON ONT installations. This isn't to say the
wow, sounds super scalable.
process was particularly easy or fun for those involved, however there
is a light at the end of the tunnel.
ha! double joke!
It's not immediately clear the extent of configuration work needed
behind the curtains -- whether routing and addressing needed to be set
up in an ad hoc manner, or if there was merely a magic "allow v6
ethertype" checkbox in an OSS needing to be checked to make RAs start
if it's just some clicky thing in the OSS I'm betting 2yrs til the IT
department gets that automated 
working, however I've heard various rumblings pointing at the latter.
However you slice it, I agree their laid-back approach at
'laid-back'... you sir, have a way with words.
implementation is shameful, and should be called out wherever
possible.
yes it's nice that the Networx contract didn't require any ipv6 readiness...
Sorry, yes, that is correct: one way to get IPv6 FIOS at the home is
to escalate through your (701/VZB) account team.
I should probably add that there was a real router plugged into the
ethernet port on the ONT, given a lack of support in the ActionTec
code ... but what self-respecting network geek uses those in the first
place? 
YMMV, etc.,
-a
> I've heard of folk in and around the NYC metro getting set up for v6
> by escalating through their commercial account teams, or the field'commercial account teams' == business customers?
As a FIOS business customer, I can say that I've had no progress on that
front, though I've bugged them about it often enough... Perhaps I shall
try again though. I would truely love to hear from one of these folks
in NYC who managed to get it...
> implementation is shameful, and should be called out wherever
> possible.yes
There's a US government mandate for government public websites to
support IPv6 and quite a few of those do- in some cases through Networx.
I don't recall agencies complaining about the inability to get IPv6 for
public websites via Networx either. Additionally, most of the services
under the Networx contract are more traditional telecom services which
don't particularly care what you run over them.
As for having Networx require IPv6 support for all services- some of us
tried, and while a nice idea, I doubt it would have lasted terribly long
post-award even if it had been included for the few IP-based services
which were part of the original contract. Sadly, having been involved
in government contracting, it's amazing what happens when the vendor
says "we want to provide $awesome, but we need you to waive this *one*
little thing" and there isn't a mandate (afair...) for agencies to run
IPv6 internally (tho they're supposed to be buying devices which
*support* it).
I will say that the more the agencies complain to GSA the highest the
chance of something being done about it.
Thanks,
Stephen
You fared better than I did. I also am a Verizon Business customer,
and when I called and inquired about ipv6 I was told that they didn't
carry that channel.
Andrew Fried
andrew.fried@gmail.com
Interestingly, I have one of the later-generation ActionTecs, and VZ
pushed a software update to it at some point and it sprouted IPv6 config.
https://plus.google.com/u/0/+WesleyGeorge/posts/hZR5nRgKyQ4
And no, clicking ³enable² doesn¹t do anything, least it didn¹t last time I
fiddled with it.
They¹ve at least updated this page from ³later in 2012² to ³starting in
2013² but clearly that¹s still not very helpful.
http://www.verizon.com/Support/Residential/Internet/HighSpeed/General+Suppo
rt/Top+Questions/QuestionsOne/ATLAS8742.htm
Wes George
Anything below this line has been added by my company¹s mail server, I
have no control over it.
I noticed the same thing on my router several months ago, but when I called to see if I could get IPv6 turned on for my account, no go.
jms
I've been barking at them for a couple years now, I never get much.
They're good about staffing their front line support with flowchart
monkeys. My internet facing device is constantly listening for any sort of
indication that native IPv6 is starting up, but never hears anything. So I
rock HE like many of you. It works pretty well, and I'm, guessing I get a
lot more address space via HE than VZ would give me.
The only major ISP that I seen so far that has rolled out is Comcast. Been
probing the TW Cable people for months to see what their plans are for IPv6
in Ohio and all I have gotten is a million different stories.
The only major ISP that I seen so far that has rolled out is Comcast. Been
probing the TW Cable people for months to see what their plans are for
IPv6
in Ohio and all I have gotten is a million different stories.
TWC Ohio (residential service): Real Soon Now.
For what it's worth, AT&T also has a significant rollout on U-Verse.
http://www.worldipv6launch.org/measurements/
I've read in some forums that there are pockets of FiOS users with IPv6
running. I've seen LLA on ActionTec modems. Something tells me that they
will sneak up on us with a sudden deployment.
Lee
would be grand if they'd let folk know it's coming
# tcpdump -n -i em0 ip6
tcpdump: listening on em0, link-type EN10MB
especially for business customers who don't have moca and don't use
the actioncrap...
My actiontec router has had that IPv6 page for a while now. I'm 20 minutes outside NYC. However when I enable it, I still don't get a broadband IPv6 address in the System Monitoring tab.
So I rock HE like many of you. It works pretty well, and I'm, guessing I get a lot more address space via HE than VZ would give me.
I have a tunnel through HE and it is solid.
Verizon states on their "What is IPv6?" page that they will provide a /56 to customers. At least they fixed the typo that up until recently said that a /56 was 56 LANs, so at least that's a step in the right direction.
My guesses for the foot-dragging, re: v6 deployment on FiOS:
1. Can't get their set-top boxes working on it yet. One customer service
rep told me this. I didn't feel up to starting the whole "what's wrong with dual-stack?" argument.
2. Still working out how to update back-end provisioning systems.
3. Dealing with different vintages of premise routers (older Actiontecs
don't support it), ONTs, and possibly aggregation routers.
4. Still developing M&Ps and training materials for provisioners and front-line customer service reps.
5. They haven't hit a critical mass of non-static customers bitching about performance problems due to LSN.
6. Layer 8-10 issues.
I do know Verizon is a very siloed organization. VZO doesn't communicate much with VZW or VZB, and vice versa, which is a shame. v6 on my VZW 4G LTE phone just plain works.
jms
From: Justin M. Streiner [mailto:streiner@cluebyfour.org]
Sent: Tuesday, January 07, 2014 6:02 PMIf you find the answer, you win the prize.
Can the prize be the Verizon employees that should have been keeping us in
the loop on this in a dunk tank ;)?
I've tried shaking numerous trees (front-line customer service, my VZB
sales person for $dayjob, other people I know who work at Verizon, etc...)
to get an answer on this and each time I got different responses.
Same story, I've tried many different avenues over the past couple of years
with no luck.
You'd think somebody on the list would be friends with a Verizon employee in
the know they could take out and get drunk and wheedle something out of :).
Or have sufficient business with Verizon to have enough clout to demand an
answer <sigh>.
From: Adam Rothschild [mailto:asr@latency.net]
Sent: Tuesday, January 07, 2014 8:10 PMSorry, yes, that is correct: one way to get IPv6 FIOS at the home is
to escalate through your (701/VZB) account team.
Hmm, I actually have business FIOS at home (static IP highway robbery
<grumble>), and have had no luck escalating requests for details on IPv6
through business support. Could you possibly provide more details on the
process or appropriate contacts?
but what self-respecting network geek uses those in the first
place?
Damn straight. It's annoying they make us waste money on buying them in the
first place 8-/. Although my brother-in-law did appreciate the donation of
my actiontec paperweight to extend his consumer fios network to the other
side of his house over coax and have better wireless coverage.
Thanks.