RE: SIP on FTTH systems

["Frank Bulk" <frnkblk () iname com>]

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.  MACFF is supposed to solve that (we haven't turned it on, yet, because the vendor's 
implementation requires us to do some work on our provisioning system to make it easier).

Frank

-----Original Message-----
From: Jay Ashworth [mailto:jra () baylink com] 
Sent: Thursday, February 06, 2014 11:59 PM
To: NANOG
Subject: Re: SIP on FTTH systems

----- Original Message -----
> From: "Frank Bulk" <frnkblk () iname com>

> And then you need MACFF to overcome the split-horizon to that
> customers in the same subnet can talk to each other. =)

In my not-at-all humble opinion, in an eyeball network, you almost *never*
want to make it easier for houses to talk to one another directly; there
isn't any "real" traffic there.  Just attack traffic.

Well, ok; slim chance of P2P, but carriers hate that anyway, right? :-)

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                       jra () baylink com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates       http://www.bcp38.info          2000 Land Rover DII
St Petersburg FL USA      BCP38: Ask For It By Name!           +1 727 647 1274