Re: [v6ops] As promised...

That’s sort of akin to saying “DDoS must not disrupt a device’s normal operation”.

If you flood a link with traffic, stuff’s going to break.

There are scenarios where multicast traffic can get out of control, including RA and related.

Reducing the number of multicast RAs to those periodic ones necessary to refresh timers of every host on the link just makes sense.

As such, I think the consequences are perfectly valid justification in addition to the other points raised.

Owen

> On Jul 23, 2015, at 10:39 , Francisco Paletta <francisco@assembler.com.br> wrote:
> 
> Hello,
> 
> I believe it's a good "best practice".
> 
> I just have suggestions regarding the "3. Consequences" points 2 and 3. Despite the fact that frequent RA messages are causing those consequences, they should not be used as base to support this recommendation.
> 
> In my opinion, the frequency or broadness of RA messages should not cause a device to disrupt it's communication. The device must deal with it another way. Obviously they can benefit from the changes in RA messages behaviors. But should not be the motivation.
> 
> Nevertheless I agree that once the device receives an information and have to deal with it, it spends power on that process and we should control that to favor battery-powered devices.
> 
> Regards,
> 
> Francisco Paletta
> 
> 
> 2015-07-23 10:10 GMT-03:00 Fred Baker (fred) <fred@cisco.com <mailto:fred@cisco.com>>:
> https://tools.ietf.org/html/draft-ietf-v6ops-reducing-ra-energy-consumption <https://tools.ietf.org/html/draft-ietf-v6ops-reducing-ra-energy-consumption>
>   "Reducing energy consumption of Router Advertisements", Andrew
>   Yourtchenko, Lorenzo Colitti, 2015-07-23,
> 
> We had quite a bit of discussion Tuesday, especially considering the length (or brevity) of this draft.
> 
> I'd suggest you read it. Especially given the number of "+2" comments on the list, I tend to think we can come to consensus relatively quickly on it. If there are lingering issues, let's get them out of the way.
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org <mailto:v6ops@ietf.org>
> https://www.ietf.org/mailman/listinfo/v6ops <https://www.ietf.org/mailman/listinfo/v6ops>
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops