netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Kumria <wildfire@progsoc.uts.edu.au>
To: David Daney <ddaney@avtrex.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>, netdev@vger.kernel.org
Subject: Re: RFC3927 ARP patch status?
Date: Sat, 3 Jun 2006 12:50:02 +1000	[thread overview]
Message-ID: <20060603025001.GK549@progsoc.uts.edu.au> (raw)
In-Reply-To: <4480DEB3.2060806@avtrex.com>

On Fri, Jun 02, 2006 at 05:58:27PM -0700, David Daney wrote:
> 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.
> 

[...]

Sorry, I can't find any email with any of those words in it by Herbert.
Could you tell me the message-id, so I can read some of the surrounding
context?

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

I guess it would be something set during RTM_NEWADDR (and returned by
RTM_GETADDR?). How does IFA_DIRECTEDARP sound? With a value type of int;
defaulting to 1.  When set to 0, generate a broadcast ARP for the
address.

Thanks,
Anand

-- 
 `When any government, or any church for that matter, undertakes to say to
  its subjects, "This you may not read, this you must not see, this you are
  forbidden to know," the end result is tyranny and oppression no matter how
  holy the motives' -- Robert A Heinlein, "If this goes on --"

  reply	other threads:[~2006-06-03  2:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060602143837.GF549@progsoc.uts.edu.au>
2006-06-02 16:36 ` RFC3927 ARP patch status? David Daney
2006-06-02 17:31   ` Anand Kumria
2006-06-02 23:12   ` Herbert Xu
2006-06-03  0:39     ` Anand Kumria
2006-06-03  0:47       ` David Miller
2006-06-03  0:55         ` David Daney
2006-06-03  1:00           ` David Miller
2006-06-03  0:58       ` David Daney
2006-06-03  2:50         ` Anand Kumria [this message]
2006-06-03  4:52           ` Herbert Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060603025001.GK549@progsoc.uts.edu.au \
    --to=wildfire@progsoc.uts.edu.au \
    --cc=ddaney@avtrex.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).