nanog mailing list archives
Re: SIP on FTTH systems
From: Jay Ashworth <jra () baylink com>
Date: Fri, 07 Feb 2014 10:41:44 -0500
I would assume that this whole mostly depends on which particular protocols and approaches your edge equipment can implement most efficiently - efficiently enough, that is, to be able to do it on every single port in a chassis. On February 7, 2014 10:20:08 AM EST, Mark Tinka <mark.tinka () seacom mu> wrote:
On Friday, February 07, 2014 03:30:08 PM Frank Bulk wrote:Rather than assign residential and business customers their own /30, to conserve space we give those customers a /32 out of a /24. But when one of these static IP customers wants to send email to another, or the employee wants to VPN into work, they can't.This is akin to Private VLAN's where ports in a shared VLAN are assigned numbers from the same subnet, but they can only communicate via the BNG rather than directly at the bridge level. I prefer EVC Split Horizon to Private VLAN's, though. Mark.
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Current thread:
- Re: SIP on FTTH systems, (continued)
- Re: SIP on FTTH systems Mark Tinka (Feb 08)
- Re: SIP on FTTH systems Anders Löwinger (Feb 11)
- Re: SIP on FTTH systems Mikael Abrahamsson (Feb 11)
- Re: SIP on FTTH systems Anders Löwinger (Feb 11)
- RE: SIP on FTTH systems Frank Bulk (Feb 11)
- RE: SIP on FTTH systems Mikael Abrahamsson (Feb 11)
- Re: SIP on FTTH systems Anders Löwinger (Feb 13)
- Re: SIP on FTTH systems Mark Tinka (Feb 13)
- RE: SIP on FTTH systems Frank Bulk (Feb 07)
- Re: SIP on FTTH systems Mark Tinka (Feb 07)
- Re: SIP on FTTH systems Jay Ashworth (Feb 07)
- Re: SIP on FTTH systems Mark Tinka (Feb 07)