netdev - Re: [PATCH 00/05] ipv6: RFC4214 Support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20071107.145550.50882731.yoshfuji@linux-ipv6.org>
Date:	Wed, 07 Nov 2007 14:55:50 +0900 (JST)
From:	YOSHIFUJI Hideaki / 吉藤英明 
	<yoshfuji@...ux-ipv6.org>
To:	davem@...emloft.net, Fred.L.Templin@...ing.com
Cc:	dlstevens@...ibm.com, netdev@...r.kernel.org,
	yoshfuji@...ux-ipv6.org
Subject: Re: [PATCH 00/05] ipv6: RFC4214 Support

In article <20071106.213750.91637349.davem@...emloft.net> (at Tue, 06 Nov 2007 21:37:50 -0800 (PST)), David Miller <davem@...emloft.net> says:

> From: David Stevens <dlstevens@...ibm.com>
> Date: Tue, 6 Nov 2007 21:26:15 -0800
> 
> > Last I heard, there are Intellectual Property claims with ISATAP,
> > which is why the RFC is not standards track and which makes it
> > effectively a proprietary protocol.
> > 
> > Unless that's been resolved, I think the claim by the IP owner is
> > that it can't be distributed without a license from them. So, maybe
> > not worth the effort for an experimental RFC.
> 
> If this is the case, I agree, we cannot include ISATAP
> support in the kernel.

I guess license is no longer required for implementers of ISATAP.
Is it right, Fred?

https://datatracker.ietf.org/ipr/550/

--yoshfuji


-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html