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: netdev@vger.kernel.org
Subject: Re: RFC3927 ARP patch status?
Date: Sat, 3 Jun 2006 03:31:44 +1000	[thread overview]
Message-ID: <20060602173144.GG549@progsoc.uts.edu.au> (raw)
In-Reply-To: <44806926.1050509@avtrex.com>

On Fri, Jun 02, 2006 at 09:36:54AM -0700, David Daney wrote:
> Anand Kumria wrote:
> >Hi David,
> >
> >Do you know the status of your RFC3927 ARP patch? Is it likely to make
> >it into a mainline kernel?
> >
> 
> That would be up to the kernel network maintainers.
> 
> There were some discussions about whether it made sense for the kernel 
> to support the behavior required by the RFC.  Other comments debated the 

Hmm, well the behaviour at the moment is certainly suboptimal. Any
compliant RFC3927 implementation has to generate an additional broadcast
ARP -- the kernel will send a directed response, which isn't enough.

> The patch is there.  I signed-off-by on it.
> 
> If you need RFC3927 compliance, you are free to apply the patch.  If the 
>  network maintainers are so inclined, they can do the necessary things 
> to get it into the mainline.

Okay, 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-02 17:31 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 [this message]
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
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=20060602173144.GG549@progsoc.uts.edu.au \
    --to=wildfire@progsoc.uts.edu.au \
    --cc=ddaney@avtrex.com \
    --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).