From: "Rémi Denis-Courmont" <remi@remlab.net>
To: netdev@vger.kernel.org
Subject: Re: Implementing RFCs from IETF
Date: Sun, 6 May 2012 17:07:49 +0300 [thread overview]
Message-ID: <201205061707.50204.remi@remlab.net> (raw)
In-Reply-To: <1336312774.11610.7.camel@oc4748611672.ibm.com>
Le dimanche 6 mai 2012 16:59:34 Onkar, vous avez écrit :
> Do RFCs on IETF contain some kind of copyright with the
> authors (and their respective companies )who have written the RFC which
> prohibits the RFC from being implemented in the Linux kernel.
Of course not.
But the copyright license does prevent example code from being copied into the
kernel (or any other GPL piece), in many cases.
Also some RFC have IPR separate claims.
--
Rémi Denis-Courmont
http://www.remlab.net/
http://fi.linkedin.com/in/remidenis
next prev parent reply other threads:[~2012-05-06 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 13:59 Implementing RFCs from IETF Onkar
2012-05-06 14:07 ` Rémi Denis-Courmont [this message]
2012-05-06 14:15 ` Onkar
2012-05-06 14:28 ` Rémi Denis-Courmont
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=201205061707.50204.remi@remlab.net \
--to=remi@remlab.net \
--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).