* Implementing RFCs from IETF
@ 2012-05-06 13:59 Onkar
2012-05-06 14:07 ` Rémi Denis-Courmont
0 siblings, 1 reply; 4+ messages in thread
From: Onkar @ 2012-05-06 13:59 UTC (permalink / raw)
To: netdev
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.
Regards,
onnm
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Implementing RFCs from IETF
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
0 siblings, 1 reply; 4+ messages in thread
From: Rémi Denis-Courmont @ 2012-05-06 14:07 UTC (permalink / raw)
To: netdev
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Implementing RFCs from IETF
2012-05-06 14:07 ` Rémi Denis-Courmont
@ 2012-05-06 14:15 ` Onkar
2012-05-06 14:28 ` Rémi Denis-Courmont
0 siblings, 1 reply; 4+ messages in thread
From: Onkar @ 2012-05-06 14:15 UTC (permalink / raw)
To: Rémi Denis-Courmont; +Cc: netdev
On Sun, 2012-05-06 at 17:07 +0300, Rémi Denis-Courmont wrote:
> 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.
>
Thanks for your reply Remi.
> 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 ?
> Also some RFC have IPR separate claims.
>
If possible , can you please give me one example on this as a reference.
Thank you very much.
- Onnm
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Implementing RFCs from IETF
2012-05-06 14:15 ` Onkar
@ 2012-05-06 14:28 ` Rémi Denis-Courmont
0 siblings, 0 replies; 4+ messages in thread
From: Rémi Denis-Courmont @ 2012-05-06 14:28 UTC (permalink / raw)
To: netdev
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-05-06 14:28 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).