[168109] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Verizon FIOS IPv6?

daemon@ATHENA.MIT.EDU (Stephen Frost)
Thu Jan 9 08:41:42 2014

Date: Thu, 9 Jan 2014 08:41:30 -0500
From: Stephen Frost <sfrost@snowman.net>
To: Geert Bosch <bosch@adacore.com>
In-Reply-To: <4B201062-4499-49DD-BA0B-86262D26B4F9@adacore.com>
Cc: "nanog@nanog.org list" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


--bPg9NdpM9EETxvqt
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Geert Bosch (bosch@adacore.com) wrote:
> On Jan 8, 2014, at 17:03, Justin M. Streiner <streiner@cluebyfour.org> wr=
ote:
> > I have a tunnel through HE and it is solid.
[...]
> --- XXXX.gnat.com ping6 statistics ---
> 20 packets transmitted, 20 packets received, 0.0% packet loss
> round-trip min/avg/max/std-dev =3D 15.204/16.911/18.721/0.941 ms
>=20
> This really is good latency, especially considering the tunnel.
> Note that my MacBook Pro is using a WiFi connection, adding a
> millisecond or two as well.=20
>=20
> --- XXXX ping statistics ---
> 20 packets transmitted, 20 packets received, 0.0% packet loss
> round-trip min/avg/max/stddev =3D 26.280/28.259/31.289/1.254 ms

I'm really curious how *that* is working out.  My IPv6 tunnel is only a
ms or two slower than IPv4 (and it's all sub-15ms), but there is
something very odd if the tunnel is *faster*.  Have you tried working
out where the difference is coming from (eg: mtr or similar)?

> This is fine, but not great. The Apple Base station does NAT-ing,
> but did the same for my previous DSL link to Bway, which had <16ms
> ping times, so I can rule out NAT-related delays. At this point
> in time I'm not holding my breath for VZ to do anything to accommodate
> IPv6 or provide good routing, and know that if, for my company or=20
> otherwise, I'll have an option to chose HE, I will.

Spent another hour with the FIOS folks last night and, while the tech
folks knew what IPv6 was, they weren't able to provide any info about
timelines or, really, much of anything.

> PS. Today I changed my FIOS autopay method with VZ (as somehow they
> ignored the info I gave at signup) and got notified it would take
> up to 60 days (!!!) for the changes to take effect. Clearly, VZ is
> (and always will be) a phone company.

Sadly, Verizon is *both* a phone company and an Internet company- it's
just that FIOS is part of the phone company half.  Verizon Enterprise
has supported IPv6 for a number of years and we were able to turn it
up at my last job w/o too much trouble, once I convinced the necessary
folks that we should ask for it.

	Thanks,

		Stephen

--bPg9NdpM9EETxvqt
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJSzqcKAAoJEO1sijiDR2RVEHkP/iB7c5sL8AmUTOwzyQLpMBm4
7ZBujsQmj8Zc8W+I7f6CMuzNajO/0xjCHVMIN4mCp8/wM2rPrPJyoIvtCVO3+mE+
r3AJ68Vgbl0s+AgXt3Dp2rMtgYfv44sZZGI0mJgpSaGqBLV74vjJbensQ+H19lND
R3hTSvxfiloJe1xr2mLM+vRrjPOB7QTB645ALxC6PQBgmqXk3BRuegnDo2NsyrrS
dRfdGbEzpdNrvyCFcyAiEPoDkKEcRENkKY87L9ZFIMhVd0GJLuSEACYcKlmvkUJx
nrrvMK6RxUDcvMxWik6izPCMlVZmNZFg/QZpNwVkqmQpYCZ/Xk2wWScBTGX/kYkl
zqH4SZZKk9IUi2FVLiMD/KUXZzg3NCf8xJLUMamNtEmFuV2cKQueSRp65QjX0gvt
cApkPXNpquDpsYyabq7oYvU9HWglzojexKDxTv2T8IA3ROFr1rDpICL/KRRxyO1x
OkbNPrrK9txGz5G2mRaUC7+iARa29wN2a+XfZ4DrK6RX7dVKBNCeGJ/j5aDejCAk
AL3F8xr1j6Cs97GW53Unpn8Atde894n+IzTYJzoJ5mCaelu61UfF4Q1JWPux8EBD
SN8HDy0u9OLztL0y+DMu2AIa36zoHbv2iykPzt2CWWYw6XtNmWNoZqr8SH0EFYkQ
xpDR4S3GSthzfB7UkLWN
=1hoj
-----END PGP SIGNATURE-----

--bPg9NdpM9EETxvqt--


home help back first fref pref prev next nref lref last post