From dme at sun.com  Thu Aug  9 03:25:00 2007
From: dme at sun.com (David Edmondson)
Date: Thu, 9 Aug 2007 11:25:00 +0100
Subject: [ethbridge-discuss] [dme@sun.com: Re: Re: Re: brctl:
	open(/devices/pseudo/b ridg	e@0:0) failed]
Message-ID: <20070809102500.GF25713@enoexec.uk.sun.com>

Oops, wrong mailing list address.
-------------- next part --------------
An embedded message was scrubbed...
From: David Edmondson <dme at sun.com>
Subject: Re: Re: Re: brctl: open(/devices/pseudo/b ridg e at 0:0) failed
Date: Thu, 9 Aug 2007 11:08:49 +0100
Size: 3795
URL: <http://mail.opensolaris.org/pipermail/ethbridge-discuss/attachments/20070809/5c2ce338/attachment.mht>

From dme at sun.com  Fri Aug 10 00:52:04 2007
From: dme at sun.com (David Edmondson)
Date: Fri, 10 Aug 2007 08:52:04 +0100
Subject: [ethbridge-discuss] What next for the ethbridge project?
Message-ID: <20070810075204.GT25713@enoexec.uk.sun.com>

With the recent surge of interest[1] in the ethernet bridging
implementation, it seems worth reviewing the current state and
discussing some possible next steps.

1. The currently available code is around 18 months old.
2. It's not integrated into the ON build.
3. It has a few bugs.
4. The STP implementation is not complete.
5. The "DLPI promiscuous mode loopback" problem is not addressed.

However, some people are obviously interested in and playing with the
code.

As a side-effect of the Solaris on Xen[2] project we did some work on
2, 3 and 5 (mostly Dong-Hai). In the end we didn't use that work, so
it's sitting around in a workspace somewhere un-loved.

The RBridges project[3] has an interest in ethernet bridging, and the
web page suggests that perhaps the implementation from "this" project
would be useful.

So, what to do next? Here are some options that occurred to me:

* Produce an updated version of the code in its' current form
  (i.e. standalone build, no DLPI changes),
* Produce an ON derived gate with the bridging code and DLPI
  promiscious mode changes integrated,
* Nothing - leave things limping along,
* Abandon the current bits and close down the project.

The first of these would be relatively simple and, presumably, useful
to the people who are using the existing code.

The second would be more useful to some (due to the loopback changes),
but is incomplete (the loopback changes were not finished) and more
difficult to build (because you have to build ON). This version would
work as well as the first when built.

The last two would be sad.

Footnotes: 
[1]  Maybe "surge" is overstating things a bit :-)
[2]  http://www.opensolaris.org/os/community/xen
[3]  http://www.opensolaris.org/os/project/rbridges/



From james.d.carlson at sun.com  Fri Aug 10 07:26:03 2007
From: james.d.carlson at sun.com (James Carlson)
Date: Fri, 10 Aug 2007 10:26:03 -0400
Subject: [ethbridge-discuss] [dme@sun.com: What next for the
	ethbridge	project?]
In-Reply-To: <20070810080712.GU25713@enoexec.uk.sun.com>
References: <20070810080712.GU25713@enoexec.uk.sun.com>
Message-ID: <18108.30075.554376.527751@gargle.gargle.HOWL>

David Edmondson writes:
> With the recent surge of interest[1] in the ethernet bridging
> implementation, it seems worth reviewing the current state and
> discussing some possible next steps.

Agreed.  (As I said in the project announcement, I was hoping to have
discussions like this one on networking-discuss, because they're wider
than just the RBridges project team details.  If you can redirect
there, that'd be helpful.)

> 1. The currently available code is around 18 months old.
> 2. It's not integrated into the ON build.
> 3. It has a few bugs.
> 4. The STP implementation is not complete.
> 5. The "DLPI promiscuous mode loopback" problem is not addressed.

Also, one of the leaders (Mike Ditto) is gone and the project state is
unclear.

> As a side-effect of the Solaris on Xen[2] project we did some work on
> 2, 3 and 5 (mostly Dong-Hai). In the end we didn't use that work, so
> it's sitting around in a workspace somewhere un-loved.

It'd be good to get that stuff up on opensolaris.org, at least.

> The RBridges project[3] has an interest in ethernet bridging, and the
> web page suggests that perhaps the implementation from "this" project
> would be useful.

Yes.  At this point, we don't know.

For what it's worth, RBridges is just _me_ right now.  It's a little
thin.  We have more people (Paul Jakma and Rishi) coming on board in a
couple of months, depending on their current projects.  So, some
things, such as who is going to do the underlying bridging support,
have been ignored.

I'd like to have someone else do the underlying generic bridging work
because they're motivated.  That'd be great, and I'd welcome
collaboration with an active ethbridge project.  Failing that, though,
we'll have to figure out what makes sense for our project, even if
that means reinventing a wheel.

This is the sort of thing that an active Networking Community should
also help drive.  :-/

> So, what to do next? Here are some options that occurred to me:
> 
> * Produce an updated version of the code in its' current form
>   (i.e. standalone build, no DLPI changes),
> * Produce an ON derived gate with the bridging code and DLPI
>   promiscious mode changes integrated,
> * Nothing - leave things limping along,
> * Abandon the current bits and close down the project.

In order to determine which of these is the right direction, I think
it'd be helpful to have a design document for the existing bridging
code.  Does that exist?  Other than a README and a few discussions, I
don't see one.

If we don't have that, it'd be good to have access to the source.  I
assume that the 19-month-old ethbridge-0.9.tar.gz isn't the latest
stuff ... does anyone know what is?  (Should I contact Dong-Hai or
someone else?)

> The first of these would be relatively simple and, presumably, useful
> to the people who are using the existing code.
> 
> The second would be more useful to some (due to the loopback changes),
> but is incomplete (the loopback changes were not finished) and more
> difficult to build (because you have to build ON). This version would
> work as well as the first when built.

I suspect that (1) would be the quickest way to a prototype.  Given
the complexities in the rest of the RBridges project -- handling TRILL
and updating IS-IS with bridging data -- I'm very much in favor of
having prototype bits around for significant chunks.  (This is why I
ported the Quagga IS-IS code to Solaris first.)

For RBridges, we need to get the learned MAC addresses up into user
space where the IS-IS work is done.  This is also where something like
STP (as a control plane item) ought to be running.  We also need to
control L2 forwarding entries from user space.  I think we share a lot
of architectural issues.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
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


From dme at sun.com  Fri Aug 10 07:49:15 2007
From: dme at sun.com (David Edmondson)
Date: Fri, 10 Aug 2007 15:49:15 +0100
Subject: [ethbridge-discuss] What next for the ethbridge project?
In-Reply-To: <18108.30075.554376.527751@gargle.gargle.HOWL>
References: <20070810080712.GU25713@enoexec.uk.sun.com>
	<18108.30075.554376.527751@gargle.gargle.HOWL>
Message-ID: <20070810144915.GA25713@enoexec.uk.sun.com>

On Fri, Aug 10, 2007 at 10:26:03AM -0400, James Carlson wrote:
> David Edmondson writes:
> > With the recent surge of interest[1] in the ethernet bridging
> > implementation, it seems worth reviewing the current state and
> > discussing some possible next steps.
> 
> Agreed.  (As I said in the project announcement, I was hoping to have
> discussions like this one on networking-discuss, because they're wider
> than just the RBridges project team details.  If you can redirect
> there, that'd be helpful.)

Okay (I kept the ethbridge-discuss list in case there are people who
live just there).

> > As a side-effect of the Solaris on Xen[2] project we did some work on
> > 2, 3 and 5 (mostly Dong-Hai). In the end we didn't use that work, so
> > it's sitting around in a workspace somewhere un-loved.
> 
> It'd be good to get that stuff up on opensolaris.org, at least.

Agreed.

> I'd like to have someone else do the underlying generic bridging
> work because they're motivated.  That'd be great, and I'd welcome
> collaboration with an active ethbridge project.  Failing that,
> though, we'll have to figure out what makes sense for our project,
> even if that means reinventing a wheel.

At the moment I don't know of anyone with a particular interest in
working on the code. As mentioned before, the Solaris on Xen project
used the code for a while but then switched to VNICs.

> > So, what to do next? Here are some options that occurred to me:
> > 
> > * Produce an updated version of the code in its' current form
> >   (i.e. standalone build, no DLPI changes),
> > * Produce an ON derived gate with the bridging code and DLPI
> >   promiscious mode changes integrated,
> > * Nothing - leave things limping along,
> > * Abandon the current bits and close down the project.
> 
> In order to determine which of these is the right direction, I think
> it'd be helpful to have a design document for the existing bridging
> code.  Does that exist?  Other than a README and a few discussions,
> I don't see one.

I know of nothing more.

> If we don't have that, it'd be good to have access to the source.  I
> assume that the 19-month-old ethbridge-0.9.tar.gz isn't the latest
> stuff ... does anyone know what is?  (Should I contact Dong-Hai or
> someone else?)

Dong-Hai worked specifically on the DLPI promiscious loopback
problem. Most of the bridge related fixes were me. The code I have is
a snapshot of the Solaris on Xen gate from some time ago. It has the
bridging code (integrated into ON) and the DLPI loopback changes (as
well as a bunch of unrelated Xen stuff, obviously).

> > The first of these would be relatively simple and, presumably, useful
> > to the people who are using the existing code.
> > 
> > The second would be more useful to some (due to the loopback changes),
> > but is incomplete (the loopback changes were not finished) and more
> > difficult to build (because you have to build ON). This version would
> > work as well as the first when built.
> 
> I suspect that (1) would be the quickest way to a prototype.

Okay. I'll extract the latest bits I have, make them build stand-alone
and then put them in a repository on hg.opensolaris.org.

Is there a particular date by which you need this?

dme.


From james.d.carlson at sun.com  Fri Aug 10 08:09:59 2007
From: james.d.carlson at sun.com (James Carlson)
Date: Fri, 10 Aug 2007 11:09:59 -0400
Subject: [ethbridge-discuss] [networking-discuss] What next for the
	ethbridge project?
In-Reply-To: <20070810144915.GA25713@enoexec.uk.sun.com>
References: <20070810080712.GU25713@enoexec.uk.sun.com>
	<18108.30075.554376.527751@gargle.gargle.HOWL>
	<20070810144915.GA25713@enoexec.uk.sun.com>
Message-ID: <18108.32711.581759.910157@gargle.gargle.HOWL>

David Edmondson writes:
> On Fri, Aug 10, 2007 at 10:26:03AM -0400, James Carlson wrote:
> > I'd like to have someone else do the underlying generic bridging
> > work because they're motivated.  That'd be great, and I'd welcome
> > collaboration with an active ethbridge project.  Failing that,
> > though, we'll have to figure out what makes sense for our project,
> > even if that means reinventing a wheel.
> 
> At the moment I don't know of anyone with a particular interest in
> working on the code. As mentioned before, the Solaris on Xen project
> used the code for a while but then switched to VNICs.

In that case, when we get to it, we'll pick it up.

It's hard to keep up without a program, but looks like neither Yukun
Zhang nor Mike Ditto is with Sun or active anymore on opensolaris.org.
If that's true, that leaves the ethbridge project itself without
leaders and without a rudder.

I'll try to ping them, but if that doesn't pan out, I think the
Networking or Xen core contributors ought to either find live owners
for this project, or the endorsements should be withdrawn.  It's a bit
of a distraction otherwise.

> > In order to determine which of these is the right direction, I think
> > it'd be helpful to have a design document for the existing bridging
> > code.  Does that exist?  Other than a README and a few discussions,
> > I don't see one.
> 
> I know of nothing more.

OK.

> > > The second would be more useful to some (due to the loopback changes),
> > > but is incomplete (the loopback changes were not finished) and more
> > > difficult to build (because you have to build ON). This version would
> > > work as well as the first when built.
> > 
> > I suspect that (1) would be the quickest way to a prototype.
> 
> Okay. I'll extract the latest bits I have, make them build stand-alone
> and then put them in a repository on hg.opensolaris.org.

Great!  Thanks.

> Is there a particular date by which you need this?

Nope.  We're off to a slow start, and much of the work we need to do
is in figuring out how the new IS-IS and TRILL code should operate.
Bridging is obviously important, but we've got enough to stay busy for
some time.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
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


From Donghai.Han at Sun.COM  Fri Aug 10 09:03:06 2007
From: Donghai.Han at Sun.COM (Dong-Hai Han)
Date: Sat, 11 Aug 2007 00:03:06 +0800
Subject: [ethbridge-discuss] [networking-discuss] What next for the
	ethbridge project?
In-Reply-To: <18108.32711.581759.910157@gargle.gargle.HOWL>
References: <20070810080712.GU25713@enoexec.uk.sun.com>
	<18108.30075.554376.527751@gargle.gargle.HOWL>
	<20070810144915.GA25713@enoexec.uk.sun.com>
	<18108.32711.581759.910157@gargle.gargle.HOWL>
Message-ID: <fcc394fbd05.46bcfcba@sun.com>

Yes I made the solution to DLPI loopback issue, and Meem reviewed it. 
However, this project was suspended so I just left the code untouched till now.
Given that GLDv3 has been changed a lot since then, and Crossbow/Clearview
is changing it too, I think that code need a lot of changes.

Before the project was suspended, I have made stp work, but no serious test
was done to make sure it can talk to real switches. (stp enabled switches are,
en, expensive.)

In my workspace a lot of the bugs have been fixed (guess some dup work with
David's) too.

That's the current status on my side.

David,
We can merge our work and update the stand-alone build (it's still the case in
my local workspace).

Best,

Donghai.


----- Original Message -----
From: James Carlson <James.D.Carlson at Sun.COM>
Date: Friday, August 10, 2007 11:18 pm
Subject: Re: [networking-discuss] What next for the ethbridge project?
To: David Edmondson <dme at sun.com>
Cc: ethbridge-discuss at opensolaris.org, networking-discuss at opensolaris.org

> David Edmondson writes:
> > On Fri, Aug 10, 2007 at 10:26:03AM -0400, James Carlson wrote:
> > > I'd like to have someone else do the underlying generic bridging
> > > work because they're motivated.  That'd be great, and I'd welcome
> > > collaboration with an active ethbridge project.  Failing that,
> > > though, we'll have to figure out what makes sense for our project,
> > > even if that means reinventing a wheel.
> > 
> > At the moment I don't know of anyone with a particular interest in
> > working on the code. As mentioned before, the Solaris on Xen project
> > used the code for a while but then switched to VNICs.
> 
> In that case, when we get to it, we'll pick it up.
> 
> It's hard to keep up without a program, but looks like neither Yukun
> Zhang nor Mike Ditto is with Sun or active anymore on opensolaris.org.
> If that's true, that leaves the ethbridge project itself without
> leaders and without a rudder.
> 
> I'll try to ping them, but if that doesn't pan out, I think the
> Networking or Xen core contributors ought to either find live owners
> for this project, or the endorsements should be withdrawn.  It's a bit
> of a distraction otherwise.
> 
> > > In order to determine which of these is the right direction, I 
> think> > it'd be helpful to have a design document for the existing 
> bridging> > code.  Does that exist?  Other than a README and a few 
> discussions,> > I don't see one.
> > 
> > I know of nothing more.
> 
> OK.
> 
> > > > The second would be more useful to some (due to the loopback 
> changes),> > > but is incomplete (the loopback changes were not 
> finished) and more
> > > > difficult to build (because you have to build ON). This 
> version would
> > > > work as well as the first when built.
> > > 
> > > I suspect that (1) would be the quickest way to a prototype.
> > 
> > Okay. I'll extract the latest bits I have, make them build stand-
> alone> and then put them in a repository on hg.opensolaris.org.
> 
> Great!  Thanks.
> 
> > Is there a particular date by which you need this?
> 
> Nope.  We're off to a slow start, and much of the work we need to do
> is in figuring out how the new IS-IS and TRILL code should operate.
> Bridging is obviously important, but we've got enough to stay busy for
> some time.
> 
> -- 
> James Carlson, Solaris Networking              
> <james.d.carlson at sun.com>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_______________________________________________
> networking-discuss mailing list
> networking-discuss at opensolaris.org
> 


From Darren.Reed at Sun.COM  Fri Aug 10 09:03:13 2007
From: Darren.Reed at Sun.COM (Darren Reed)
Date: Fri, 10 Aug 2007 18:03:13 +0200
Subject: [ethbridge-discuss] [networking-discuss] What next for the
	ethbridge project?
In-Reply-To: <18108.32711.581759.910157@gargle.gargle.HOWL>
References: <20070810080712.GU25713@enoexec.uk.sun.com>
	<18108.30075.554376.527751@gargle.gargle.HOWL>
	<20070810144915.GA25713@enoexec.uk.sun.com>
	<18108.32711.581759.910157@gargle.gargle.HOWL>
Message-ID: <46BC8C41.9060503@Sun.COM>

James Carlson wrote:
> ...
> In that case, when we get to it, we'll pick it up.
>
> It's hard to keep up without a program, but looks like neither Yukun
> Zhang nor Mike Ditto is with Sun or active anymore on opensolaris.org.
> If that's true, that leaves the ethbridge project itself without
> leaders and without a rudder.
>
> I'll try to ping them, but if that doesn't pan out, I think the
> Networking or Xen core contributors ought to either find live owners
> for this project, or the endorsements should be withdrawn.  It's a bit
> of a distraction otherwise.
>   

While I haven't been following ethbridge-discuss (YAML!), I actively 
pursued it back in
2005/2006 inside Sun.  There's lots of interest in the security 
community in such a thing
when combined with IPFilter to do "stealth firewalling".  This was 
around the time that
TRILL and r-bridges were just starting to make an appearance.  Ideally 
layer 2 filtering
should come into the picture here too.

Darren



From james.d.carlson at Sun.COM  Fri Aug 10 09:12:39 2007
From: james.d.carlson at Sun.COM (James Carlson)
Date: Fri, 10 Aug 2007 12:12:39 -0400
Subject: [ethbridge-discuss] [networking-discuss] What next for the
	ethbridge project?
In-Reply-To: <46BC8C41.9060503@Sun.COM>
References: <20070810080712.GU25713@enoexec.uk.sun.com>
	<18108.30075.554376.527751@gargle.gargle.HOWL>
	<20070810144915.GA25713@enoexec.uk.sun.com>
	<18108.32711.581759.910157@gargle.gargle.HOWL>
	<46BC8C41.9060503@Sun.COM>
Message-ID: <18108.36471.190171.335105@gargle.gargle.HOWL>

Darren Reed writes:
> While I haven't been following ethbridge-discuss (YAML!), I actively 
> pursued it back in
> 2005/2006 inside Sun.  There's lots of interest in the security 
> community in such a thing
> when combined with IPFilter to do "stealth firewalling".  This was 
> around the time that
> TRILL and r-bridges were just starting to make an appearance.  Ideally 
> layer 2 filtering
> should come into the picture here too.

Yep.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
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


From ford at omnicron.com  Sun Aug 12 02:53:19 2007
From: ford at omnicron.com (Mike "Ford" Ditto)
Date: Sun, 12 Aug 2007 02:53:19 -0700
Subject: [ethbridge-discuss] [dme@sun.com: What next for the ethbridge
	project?]
In-Reply-To: <18108.30075.554376.527751@gargle.gargle.HOWL> (message from
	James Carlson on Fri, 10 Aug 2007 10:26:03 -0400)
References: <20070810080712.GU25713@enoexec.uk.sun.com>
	<18108.30075.554376.527751@gargle.gargle.HOWL>
Message-ID: <46BED88F.1AF1@han.omnicron.com>

David Edmondson wrote:
> So, what to do next? Here are some options that occurred to me:
> 
> * Produce an updated version of the code in its' current form
>   (i.e. standalone build, no DLPI changes),

(And do so in the form of an hg repository instead of a tar file.)

I'm willing to do this, especially if Dong-Hai will toss his updates
over the wall for me to integrate.  I do prefer keeping it in a
standalone form, and that way I'll test it (at least to the level of
building, loading, and configuring the driver) on Solaris 10 and a few
Nevada builds.

What I can't offer to do right now is to do any real STP testing on a
non-trivial (multiple bridges) network, nor to maintain a current onnv
workspace and build machine.


James Carlson wrote:
> Also, one of the leaders (Mike Ditto) is gone and the project state is
> unclear.

I'm gone in some sense, but not every sense.  At the very least, I still
clear out the spam from the mailing list.  :-)

> In order to determine which of these is the right direction, I think
> it'd be helpful to have a design document for the existing bridging
> code.  Does that exist?  Other than a README and a few discussions, I
> don't see one.

The README is the design document.  :-)  I'm willing to put it in a more
formal format or fill in more meat, especially if you point out any
details you think are missing.  (I expect at least a description of
packet flow through the different files/functions would be valuable.)


> If we don't have that, it'd be good to have access to the source.  I
> assume that the 19-month-old ethbridge-0.9.tar.gz isn't the latest
> stuff ... does anyone know what is?  (Should I contact Dong-Hai or
> someone else?)

Dong-Hai had a version that included the rest of the NetBSD STP code and
had been merged into an ON tree, but hadn't been tested much.  This code
never made it into the "project" per se but I hope it's still around.


> It's hard to keep up without a program, but looks like neither Yukun
> Zhang nor Mike Ditto is with Sun or active anymore on opensolaris.org.
> If that's true, that leaves the ethbridge project itself without
> leaders and without a rudder.

I'm still a rudder or a keel or something, if someone else does some
rowing.  I didn't know Yukun wasn't with Sun anymore.  Anyone with
inclination, please volunteer to fill in his place as a project leader.

				-=] Mike [=-


From Darren.Reed at Sun.COM  Wed Aug 15 20:40:51 2007
From: Darren.Reed at Sun.COM (Darren.Reed at Sun.COM)
Date: Wed, 15 Aug 2007 20:40:51 -0700
Subject: [ethbridge-discuss] [networking-discuss] [dme@sun.com:
 What	next for the ethbridge project?]
In-Reply-To: <46BED88F.1AF1@han.omnicron.com>
References: <20070810080712.GU25713@enoexec.uk.sun.com>
	<18108.30075.554376.527751@gargle.gargle.HOWL>
	<46BED88F.1AF1@han.omnicron.com>
Message-ID: <46C3C743.6090209@Sun.COM>

Mike Ford Ditto wrote:

> ...
>
>I'm still a rudder or a keel or something, if someone else does some
>rowing.  I didn't know Yukun wasn't with Sun anymore.  Anyone with
>inclination, please volunteer to fill in his place as a project leader.
>  
>

I'm willing to put my hand up for this.

Darren



From james.d.carlson at sun.com  Tue Aug 21 07:34:36 2007
From: james.d.carlson at sun.com (James Carlson)
Date: Tue, 21 Aug 2007 10:34:36 -0400
Subject: [ethbridge-discuss] [dme@sun.com: What next for the ethbridge
 project?]
In-Reply-To: <46BED88F.1AF1@han.omnicron.com>
References: <20070810080712.GU25713@enoexec.uk.sun.com>
	<18108.30075.554376.527751@gargle.gargle.HOWL>
	<46BED88F.1AF1@han.omnicron.com>
Message-ID: <18122.63484.700474.318484@gargle.gargle.HOWL>

Mike "Ford" Ditto writes:
> David Edmondson wrote:
> > So, what to do next? Here are some options that occurred to me:
> > 
> > * Produce an updated version of the code in its' current form
> >   (i.e. standalone build, no DLPI changes),
> 
> (And do so in the form of an hg repository instead of a tar file.)
> 
> I'm willing to do this, especially if Dong-Hai will toss his updates
> over the wall for me to integrate.  I do prefer keeping it in a
> standalone form, and that way I'll test it (at least to the level of
> building, loading, and configuring the driver) on Solaris 10 and a few
> Nevada builds.

I suspect we'll end up needing to abandon S10 at some point in order
to stay close to Nemo.

> James Carlson wrote:
> > Also, one of the leaders (Mike Ditto) is gone and the project state is
> > unclear.
> 
> I'm gone in some sense, but not every sense.  At the very least, I still
> clear out the spam from the mailing list.  :-)

Cool.  ;-}

> > In order to determine which of these is the right direction, I think
> > it'd be helpful to have a design document for the existing bridging
> > code.  Does that exist?  Other than a README and a few discussions, I
> > don't see one.
> 
> The README is the design document.  :-)  I'm willing to put it in a more
> formal format or fill in more meat, especially if you point out any
> details you think are missing.  (I expect at least a description of
> packet flow through the different files/functions would be valuable.)

The packet flows would help, as would locking assumptions, reference
counts, and allocate/deallocate rules.

> > It's hard to keep up without a program, but looks like neither Yukun
> > Zhang nor Mike Ditto is with Sun or active anymore on opensolaris.org.
> > If that's true, that leaves the ethbridge project itself without
> > leaders and without a rudder.
> 
> I'm still a rudder or a keel or something, if someone else does some
> rowing.  I didn't know Yukun wasn't with Sun anymore.  Anyone with
> inclination, please volunteer to fill in his place as a project leader.

Since we have a burning need for this functionality in RBridges, I'll
(also) volunteer.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
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


From ford at omnicron.com  Thu Aug 23 17:49:02 2007
From: ford at omnicron.com (Mike "Ford" Ditto)
Date: Thu, 23 Aug 2007 17:49:02 -0700
Subject: [ethbridge-discuss] New project leaders
In-Reply-To: <46C3C743.6090209@Sun.COM> (Darren.Reed@Sun.COM)
References: <20070810080712.GU25713@enoexec.uk.sun.com>
	<18108.30075.554376.527751@gargle.gargle.HOWL>
	<46BED88F.1AF1@han.omnicron.com> <46C3C743.6090209@Sun.COM>
Message-ID: <46CE2AFE.3B37@han.omnicron.com>

So the ethbridge project has two new leaders.  Thanks for volunteering,
Darren and Jim.

I'm going to write up a design document that corresponds to the
"prototype" code that is currently on the project site, with some notes
describing things that are incomplete or should be done differently in a
"release" version.  I will post a draft this weekend.

					-=] Mike [=-