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:28:54 +0300 [thread overview]
Message-ID: <201205061728.54687.remi@remlab.net> (raw)
In-Reply-To: <1336313708.11610.11.camel@oc4748611672.ibm.com>
Le dimanche 6 mai 2012 17:15:08 Onkar, vous avez écrit :
> > But the copyright license does prevent example code from being copied
> > into the kernel (or any other GPL piece), in many cases.
>
> If the RFC proposes some solution to existing problem and this solution
> is proposed by some guys , at say CISCO or IBM , then does that solution
> have some kind of copyright which prevents people form other companies
> from implementing the RFC in the Linux kernel ?
Please refer to the copyright statements found in the RFC. netdev is not the
right place for lawyering.
> > Also some RFC have IPR separate claims.
>
> If possible , can you please give me one example on this as a reference.
You can find them on the IETF website.
--
Rémi Denis-Courmont
http://www.remlab.net/
http://fi.linkedin.com/in/remidenis
prev parent reply other threads:[~2012-05-06 14:28 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
2012-05-06 14:15 ` Onkar
2012-05-06 14:28 ` Rémi Denis-Courmont [this message]
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=201205061728.54687.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).