From: Sebastien Tricaud <sebastien.tricaud@wengo.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@lists.netfilter.org, Patrick McHardy <kaber@trash.net>
Subject: Re: Change Packet Payload
Date: Thu, 15 Feb 2007 15:45:40 +0100 [thread overview]
Message-ID: <45D47214.8000508@wengo.com> (raw)
In-Reply-To: <45D3AB00.7080505@netfilter.org>
Hi Pablo,
I can't find any information for licensing issues for Stevens material.
However for IETF stuff, reading RFC 3978 section 3.3 seems pretty clear.
In short :
"the Contributor, and each named co-Contributor, and the organization he
or she represents or is sponsored by (if any) grant a perpetual,
irrevocable, non-exclusive, royalty-free, world-wide right and license
to the ISOC and the IETF under all intellectual property rights in the
Contribution:"
"to extract, copy, publish, display, distribute, modify and incorporate
into other works, for any purpose (and not limited to use within the
IETF Standards Process) any executable code or code fragments that are
included in any IETF Document (such as MIB and PIB modules)"
Then there is a follow up to section 5 which states that taking code or
quotes requires the following :
"Copyright (C) The Internet Society <year>. This version of this MIB
module is part of RFC XXXX; see the RFC itself for full legal notices."
As for checksum computation. I think it is bad to have shared code in
several libraries. How about putting everything in nfnetlink ? I that
appropriated ?
Thanks,
Sebastien.
Pablo Neira Ayuso wrote:
>
> The code seems very similar to the one that is available in RFC1071. I
> recently added initial support for message checksumming to conntrackd
> and used that code (slightely modified) indicating the source, thus not
> explicitely licensing that part as GPL since I don't own the copyright
> of it. Can we consider examples available in a RFC as public domain code?
>
>
next prev parent reply other threads:[~2007-02-15 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 9:10 Change Packet Payload Luis Campo Giralte
2007-02-09 9:31 ` Eric Leblond
2007-02-09 9:48 ` Henrik Nordstrom
2007-02-13 22:10 ` Pablo Neira Ayuso
2007-02-14 9:39 ` Sebastien Tricaud
2007-02-14 9:47 ` Sebastien Tricaud
2007-02-14 9:52 ` Patrick McHardy
2007-02-14 9:55 ` Sebastien Tricaud
2007-02-14 10:05 ` Sebastien Tricaud
2007-02-14 10:09 ` Patrick McHardy
2007-02-15 0:36 ` Pablo Neira Ayuso
2007-02-15 14:45 ` Sebastien Tricaud [this message]
2007-02-16 13:11 ` Sebastien Tricaud
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=45D47214.8000508@wengo.com \
--to=sebastien.tricaud@wengo.com \
--cc=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.