Re: [homenet] Site-local multicast [was: Updating DNS]

2016-04-24 Thread Dino Farinacci
> Assuming you've got only transitive links, then any multicast routing > protocol should work fine at the scale we envision for Homenet as long as > it is able to avoid wireless links whenever possible. Pierre was > suggesting PIM-BIDIR, and actually provided a suitable implementation [1]. > Some

Re: [homenet] Moving forward.

2015-08-11 Thread Dino Farinacci
> Dino Farinacci wrote: >>> WiFi is build on the assumption that single SSID is singe IP subnet >>> and that stations can roam between AP's without loss of connections. I >>> think this is great. > >> We can do this today when LISP runs on the device

Re: [homenet] Despair

2015-08-06 Thread Dino Farinacci
> So just to put myself in the line of fire now, it appears that we have had > good progress on Babel (yeah I know the WG gap - but that can be fixed can't > it?), but what technological reason is there which makes just going with this > so problematic? Had the case been the same for IS-IS for

Re: [homenet] Moving forward.

2015-08-06 Thread Dino Farinacci
> WiFi is build on the assumption that single SSID is singe IP subnet and that > stations can roam between AP's without loss of connections. I think this is > great. We can do this today when LISP runs on the device. And you only need a single IPv6 address! I am asking the question because I w

Re: [homenet] Despair

2015-08-05 Thread Dino Farinacci
. Dino > On Aug 5, 2015, at 10:26 AM, Ted Lemon wrote: > > On Aug 5, 2015, at 1:01 PM, Dino Farinacci wrote: >> Let’s just keep the discussions technical. > > This is a great sentiment, but in fact on a technical level there is no > reason to prefer Babel(now) over IS-IS(la

Re: [homenet] Despair

2015-08-05 Thread Dino Farinacci
Chopps gave me the abridge version. I think its a good idea. But I don’t think its applicable in this use-case. Dino > On Aug 5, 2015, at 10:33 AM, Acee Lindem (acee) wrote: > > Hey Dino, > > On 8/5/15, 1:01 PM, "homenet on behalf of Dino Farinacci" > wrote: >

Re: [homenet] Despair

2015-08-05 Thread Dino Farinacci
There are a lot of things wrong in the IETF. And there are some good things about the IETF. Let’s just keep the discussions technical. We may have to be subjective, but that is the right of openness. But folks shouldn’t take it personally. I want to make one comment about Babel, or more to the

Re: [homenet] Moving forward.

2015-08-05 Thread Dino Farinacci
> On Aug 4, 2015, at 11:35 PM, Teco Boot wrote: > > >> Op 4 aug. 2015, om 20:22 heeft Dino Farinacci het >> volgende geschreven: >> >> IS-IS hellos are sent by default roughly every 10 seconds. CSNPs to keep the >> link-state database in sync is sen

Re: [homenet] Moving forward.

2015-08-05 Thread Dino Farinacci
You have to decide what your interface damping algorithm is if this link is not considered down by the implementation. If you can observe 50% packet loss in a short period of time, the implementation should take the link down and allow the IGP to converge to a new path. If there aren’t enough r

Re: [homenet] Moving forward.

2015-08-04 Thread Dino Farinacci
> On Aug 4, 2015, at 11:01 AM, Ted Lemon wrote: > > On Aug 4, 2015, at 1:32 PM, Dino Farinacci wrote: >> I could guess you are referring to the lack of multicast performance over >> wifi. If not, please be clear about “L3 routing over WIFI working/stable” >> me

Re: [homenet] Moving forward.

2015-08-04 Thread Dino Farinacci
> But if we go for IS IS we're apparently going to have to wait (perhaps > forever) to get L3 routing over WIFI working/ stable. Something that we've > pointedly failed to do in professionally managed office networks in the last > 20 years. What is so unstable about it? I could guess you are

Re: [homenet] Moving forward.

2015-07-26 Thread Dino Farinacci
And what makes you think I do not understand the context? I attended last Homenet WG in Dallas and then joined the list. So I've been reading the list for 3 months and catching up on all documents. Dino > On Jul 26, 2015, at 4:13 PM, Ted Lemon wrote: > >> On Jul 26, 2015,

Re: [homenet] Moving forward.

2015-07-25 Thread Dino Farinacci
> This whole thread is really patronizing. The email wasn't intended to be, honest. I was trying to be helpful. And as I said ignore my email if you wish to. Dino ___ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet

Re: [homenet] Moving forward.

2015-07-25 Thread Dino Farinacci
> What it *does* tell us is that ISIS is a mightily complex protocol that > took 20+ years to get right for the *best* minds in the routing industry. Correction. It took about 2 years to get it right and 18 years of usage and new features additions (like IPv6 about 15 years ago). But most feature

Re: [homenet] Moving forward.

2015-07-25 Thread Dino Farinacci
> Someone needs to put the foot down and choose. Either you choose IETF process > as a tie-breaker, in which case ISIS is the obvious choice, or you choose > some other tie-breaker and then it might be another choice or no choice. Then I’ll be the foot if anyone cares. My 2 cents. You can ignore