From: bert hubert <ahu@ds9a.nl>
To: Pekka Savola <pekkas@netcore.fi>
Cc: "John S. Denker" <jsd@monmouth.com>, netdev <netdev@oss.sgi.com>
Subject: Re: ?completeness of IPsec feature-set
Date: Fri, 28 Mar 2003 11:19:57 +0100 [thread overview]
Message-ID: <20030328101957.GA11075@outpost.ds9a.nl> (raw)
In-Reply-To: <Pine.LNX.4.44.0303280827570.25478-100000@netcore.fi>
On Fri, Mar 28, 2003 at 08:32:48AM +0200, Pekka Savola wrote:
> It seems SSH and ipunplugged offer RF terms (to the extent of implementing
> the IETF standards track implementation, which it isn't at the moment)
> while Microsoft and Cisco don't.
>
> I'm particularly interested if this is considered to be a problem.
The suggestion from Linus is to continue coding and leave this to people who
can actually read and understand legalese. We are not qualified to determine
what is allowed and what is not.
There is some precedent, IBM holds a blanket patent on 'compression' but has
promised not to enforce it, I think. There is libz in the kernel.
But leave it to the people who care and code onwards is what Linus says and
I would tend to agree.
Regards,
bert
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
http://netherlabs.nl Consulting
prev parent reply other threads:[~2003-03-28 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 11:13 ?completeness of IPsec feature-set John S. Denker
2003-03-27 13:36 ` bert hubert
2003-03-27 21:48 ` John S. Denker
2003-03-27 21:58 ` bert hubert
2003-03-27 22:58 ` John S. Denker
2003-03-27 23:21 ` James Morris
2003-03-28 6:32 ` Pekka Savola
2003-03-28 10:19 ` bert hubert [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=20030328101957.GA11075@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=jsd@monmouth.com \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
/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).