[168869] in North American Network Operators' Group
Re: SIP on FTTH systems
daemon@ATHENA.MIT.EDU (=?utf-8?B?TcOlbnM=?= Nilsson)
Thu Feb 6 02:20:18 2014
Date: Thu, 6 Feb 2014 08:19:59 +0100
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Jean-Francois Mezei <jfmezei_nanog@vaxination.ca>
In-Reply-To: <52F31523.4000602@vaxination.ca>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--FwyhczKCDPOVeYh6
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Subject: SIP on FTTH systems Date: Wed, Feb 05, 2014 at 11:52:51PM -0500 Qu=
oting Jean-Francois Mezei (jfmezei_nanog@vaxination.ca):
> Quick question:
>=20
> I am thinking in a possible wholesale FTTH environment operated by a
> telco where the end user is connected to ISP-X via PPPoE.
>=20
> ONTs have built-in ATAs that can provide POTS service to a house and do
> SIP/VoIP over the fibre with QoS system to ensure VoIP traffic gets throu=
gh.
>=20
> In a scenario where the data PPPoE connection is done by an external
> router, what are the options to operate the VoIP service so that
>=20
> - VoIP still uses the special lane on the GPON with QoS
>=20
> - VoIP gets IP from ISP-X and traffic flow via ISP-X so that telco is
> not involved in routing such traffic or allocating an IP address ?
Or, one could make sure everything has a globally unique IP address and is
using reasonably secured communications. The downside is that one
then can't defend the existence of those empire-building middleboxes. It
is not the telco way, so is of course unthinkable. Like anything beyond
WAP was on cell phones a decade ago.
Warum soll man es einfach machen,=20
wenn man es so sch=C3=B6n komplizieren kann?
(Why make things simple when you can=20
build them so beautifully complicated?)
--=20
M=C3=A5ns Nilsson primary/secondary/besserwisser/machina
MN-1334-RIPE +46 705 989668
We are now enjoying total mutual interaction in an imaginary hot tub ...
--FwyhczKCDPOVeYh6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlLzN58ACgkQ02/pMZDM1cW0EQCeNsDgeu29KnzjnhICxZogYV5c
gWkAoKQ7sJZp/CRUbYwzQTgCYS9A1B3t
=5KUu
-----END PGP SIGNATURE-----
--FwyhczKCDPOVeYh6--
