[168899] in North American Network Operators' Group
Re: SIP on FTTH systems
daemon@ATHENA.MIT.EDU (Mark Tinka)
Thu Feb 6 09:43:15 2014
From: Mark Tinka <mark.tinka@seacom.mu>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Date: Thu, 6 Feb 2014 16:42:46 +0200
In-Reply-To: <alpine.DEB.2.02.1402061514400.24915@uplift.swm.pp.se>
Cc: nanog@nanog.org
Reply-To: mark.tinka@seacom.mu
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--nextPart2934487.dq7L9J7khs
Content-Type: Text/Plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
On Thursday, February 06, 2014 04:17:42 PM Mikael=20
Abrahamsson wrote:
> You don't need a BNG. You need an L3 switch as the first
> hop the customer is talking to.
=46ine for FTTB, but not for FTTH where you're serving tens-
to-hundreds-of-thousands of customers.
If your FTTH deployments are low scale (measure of low or=20
large scale depends on each operator's point of view), the=20
case for doing without subscriber management technologies=20
can be made.
> If you have L3-in-vlan-per-customer at the first hop then
> you don't really need all of that. If you include
> rudimentary VRF support then you can even support
> wholesale. /64 per customer, DHCPv6(-PD) server support
> in the L3 switch and you're good to go.
I'm curious; in these deployments, what kind of customer=20
scale are you talking about? When someone says FTTH, I'm=20
thinking thousands and thousands of customers, in which case=20
not having a scalable susbcriber management system as well=20
as not having a scalable customer termination topology could=20
be difficult. Unless I misunderstand...
> There is
> equipment that already claim to do this (I never got to
> test their implementation based on my requirements
> because I switched jobs, but they claimed to have
> implemented everything last year).
Modern Metro-E switches that support full IP/MPLS in the=20
Access have a lot of good IPv4 and IPv6 features, including=20
DHCP_IA and DHCP_IA_PD, but again, these are more FTTB- than=20
=46TTH-focused, if you're talking about scale.
Cheers,
Mark.
--nextPart2934487.dq7L9J7khs
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
iQIcBAABAgAGBQJS859pAAoJEGcZuYTeKm+Gzz8P+wW0r44b5BQp9e0XinsQJU+N
Xlin64Z7ndKYr+Tw8pNEWkq5/neSyh1yjYj5I8sPzo2LhGUrM7IZLPatJi9U2lgi
6VStLBmu36qag0JTPjxMdX06qqnraGy2m2IqYliH1ADAXrNzex16Njo1JOFqAtmm
PiMaQBJcai9Z5QhT9FqfQZxryl/yClpyVS/9y8DYLcAqE9aw9r22VKb0d06Mtk2q
fhwJHkZBwF/vDyKgMSDzTh/wqwFDc/LGSnjy3GXqz3KugDB0/kQM1B4wceug2Ryv
xqJ3ohb6DBOCIHuhEV2COHkbarq4WVHp/fVBsol6U5aa3G3MejZo+fLkfyWv150J
qIUVCKjkgBqwDg2+ft9lFx1cSMb/sec+VKrLld82BKBJT0YPF0ad5FS61sGdAFr/
WpIKEwI5Q7pDCh4Z8TcPPjz0+ox0ryePNIAqwM0EdvXFDeBMR0K+RjM3bc5aqQi4
ZUSkuQReMSL3BDo3+17GeQFjPtQzpnVvSv2LMIi8I0rHkLbuz265viZ5mTK4UjKD
q8528ivvlyYuLUZGWcDNOvpjvCykbf30v227TtktVMAxYxBXc8FGThxjEdVPTsQd
tUENIFCzZhGjS2aKCVHbWfbA5i4mBECRaE4pMIB83eEPAtbZzi1BpuhANpOOnXcx
0u7nI5mvUvPSXQLQQg2H
=aChC
-----END PGP SIGNATURE-----
--nextPart2934487.dq7L9J7khs--
