Re: RFC3927 ARP patch status?

[David Daney <ddaney@avtrex.com>]

Anand Kumria wrote:
> Herbert,
> 
> On Sat, Jun 03, 2006 at 09:12:06AM +1000, Herbert Xu wrote:
> 
>>David Daney <ddaney@avtrex.com> wrote:
>>
>>>There were some discussions about whether it made sense for the kernel 
>>>to support the behavior required by the RFC.  Other comments debated the 
>>>wisdom of using a tightly targeted patch specific to the RFC, or whether 
>>>a more general but intrusive solution would be better.
>>
>>I think we've made it quite clear what needs to be done for it to be
>>accepted.  All that remains is for someone to implement it.  If anyone
>>really cares about this, then please write the code instead of talking
>>about it.
> 
> 
> Okay, to confirm: you want a patch which looks at the scope value and if 
> the scope is link-local then we broadcast rather than do a directed ARP?
> 

I don't think that was the plan.  In an earlier e-mail Herbert Xu said 
(and I concur):

------------------------------
I like the idea of allowing user-space to control what addresses cause
broadcasts.  However, I'm uncomfortable with overloading existing flags
even though they might appear to fit the bill on the face of it.

People may be using this for completely different reasons (address
selection) and it's not polite to suddenly turn all their ARPs into
broadcasts.

So how about a new address flag? We still have some vacancies there.
------------------------------

The idea was to add a new flag, *not* reuse the scope value.


David Daney