From: David Miller <davem@davemloft.net>
To: wildfire@progsoc.uts.edu.au
Cc: herbert@gondor.apana.org.au, ddaney@avtrex.com, netdev@vger.kernel.org
Subject: Re: RFC3927 ARP patch status?
Date: Fri, 02 Jun 2006 17:47:56 -0700 (PDT) [thread overview]
Message-ID: <20060602.174756.08320251.davem@davemloft.net> (raw)
In-Reply-To: <20060603003955.GJ549@progsoc.uts.edu.au>
RFC3927 seem to be an intellectual property mine field, I really don't
see how we can include this in the Linux kernel.
Go to "http://www.ietf.org/ipr", click on "Search the IPR
disclosures", then enter "3927" in the "Enter RFC number" field and
click SEARCH.
next prev parent reply other threads:[~2006-06-03 0:47 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 [this message]
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=20060602.174756.08320251.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ddaney@avtrex.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=wildfire@progsoc.uts.edu.au \
/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).