[169080] in North American Network Operators' Group
RE: SIP on FTTH systems
daemon@ATHENA.MIT.EDU (Frank Bulk)
Tue Feb 11 23:48:22 2014
From: "Frank Bulk" <frnkblk@iname.com>
To: =?iso-8859-1?Q?'Anders_L=F6winger'?= <anders@abundo.se>
In-Reply-To: <52FAC12B.8080102@abundo.se>
Date: Tue, 11 Feb 2014 22:47:35 -0600
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
In the scenario you're describing does each PC get its own /64 (or /56 =
or
/48) directly from the service provider? Or are they in the same =
netblock?
Frank
-----Original Message-----
From: Anders L=F6winger [mailto:anders@abundo.se]=20
Sent: Tuesday, February 11, 2014 6:33 PM
To: Mikael Abrahamsson
Cc: nanog@nanog.org
Subject: Re: SIP on FTTH systems
On 2014-02-11 23:41, Mikael Abrahamsson wrote:
>> Is there not an issue with this if the customer is connected directly =
to
the
>> access device over L2? They will not communicate with each other =
direcly,
>> all traffic will be exchanged through the default gateway?
>
> Yes, what's the problem with that?
Bad description by me. I'll try again.
If I have two PCs in my home, connected with GE to a L2 switch and I buy =
10=20
Mbit Internet access, I don't want traffic between my two PCs to be
exchanged=20
through the default route.
They could possible communicate directly using link-local, but I'm not =
sure=20
how they would find each other?
Default gw could send a redirect...
> I'd venture to say that any IPv6 implementation that doesn't support =
this
is
> broken and should be fixed by the implementor.
Agree.
/Anders
