The question really is how elaborate homenet wants to be. 

Given how i suffered for a good while due to broken transceivers
in LAN equipment resulting in persistent 0.5% loss on links,
i would like homenet to be a lot better than your average
enterprise network is on this. 

Sure, in my case there was ECMP, so one COULD have done intelligent
routing changes. But more often than not, alerting the user is
the primary action to take.

"Check the cable on portX/routerY. You may need to try a different cable"
"Put the poor AP further away from the microwave"

I really can't see how to build successfull home  wireless without
good diagnostics and suggestion system. Some of the higher end
home AP vendors seem to start doing this with smartphone apps
as the user interface. PowerLine equally has a lot of gotchas.

I have also seen crazy things like failing linux-PC starting
to blast multicast packets, killing a whole LAN segments until
the PC rebooted. Sure, a lot of enterprise switching gear can
throttle this, but alerting the user should be even more
important.

On Sun, Mar 01, 2015 at 05:54:09PM +0100, Henning Rogge wrote:
> On Sun, Mar 1, 2015 at 5:08 PM, Curtis Villamizar <cur...@ipv6.occnc.com> 
> wrote:
> > Henning,
> >
> > That sounds like a good strategy.  Negotiating a rate among two
> > parties is not a hard protocol problem, nor is changing it.
> >
> > Note that PPP LQM (link quality monitoring) or MPLS-TP LM (loss
> > monitoring) is not probe data.  For example, one cycle of LQM packet
> > every 10 seconds yields the exact number of packets sent and recieved
> > and the exact number dropped in both directions over a 10 second
> > period.  One cycle is three packets, with two in one direction.
> 
> The Neighborhood Discovery Protocol (RFC 6130) has a similar
> mechanism... each node collects local link quality information and
> then shares them from time to time with all neighbors, which means
> everyone knows about both directions of a link.
> 
> Henning Rogge

_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet

Reply via email to