Just a general reminder about project proposal policy... For project
proposal approval (as opposed to community proposal approval) the
"approval bar" is intentionally extremely low. A single qualified +1 vote
for a proposal constitues approval; and any opensolaris.org member is a
qualified voter. So, for example, James' message below actually does
count as a +1 vote for the 4over6 proposal. (Just to be safe, I also
confirmed this with him offline.)
Eric
On Tue, 24 Oct 2006, James Carlson wrote:
maoyi writes:
Our project is automatical 4over6 based on a data structure encapsulation table.
Each of element in encapsulation table maintains ipv6 and ipv4 address for
address translating.
When a ipv4 packet wants to 4over6 the packet will be encapsulated with a ipv6
header to go through ipv6 network when it reaches decaped the ipv6 header.
The work is done by router automatically.Because we have the encapsulation
table.
This sounds like something interesting to discuss on
[EMAIL PROTECTED] I agree this probably should be a
project.
(Unfortunately, I don't get a vote. :-/)
Our model is in draft-wu-softwire-mesh-framework-00.
I'm not sure what you mean by "model" here. Are you implementing that
draft? If so, then it requires the use of BGP. You'll want to get
the Quagga folks involved on this.
Or are you implementing something that's just 'similar' to the draft?
If so, then in what ways is it different? Does it still rely on BGP?
We implement it using stream and put the module between ipv4 and ipv6 module.
That seems both unnecessary and impossible.
It seems unnecessary, because Solaris already has IPv4-over-IPv6
tunnel support -- see tun(7M). All that's necessary to support the
tunneling mode described by the I-D you're citing is extensions to the
Quagga BGP implementation to handle softwire signaling and the tunnel
set-up using the existing tunneling facilities.
It seems impossible, because Solaris doesn't actually have separate
IPv4 and IPv6 STREAMS modules, so there's no way to insert a module
between them.
--
James Carlson, KISS Network <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
