|
On Sat, Aug 23, 2008 at 5:22 PM, Joseph Mack NA3T <jmack@xxxxxxxx> wrote:
> On Sat, 23 Aug 2008, Graeme Fowler wrote:
>
>> This also gives us a development timeline that we can offer to
>> interested parties, along the lines of:
>
> we aren't a commercial shop. This is all being done by volunteers. In which
> case features arrive in the time and order that the coder(s) do it.
>
> I don't think we should promise anything.
Right, we can only do our best, and even then we can't make
guarantuees about mainline inclusion...
>> 2008-10 Minimal IPv6 functionality
This is what we have as an experimental version right now. Meaning,
'works for us without problems, but not well tested or reviewed - any
help welcome'.
>> 2008-?? Full IPv6 functionality matching IPv4 features, no IPv6 sync
For fragmentation and other extension headers support, we would
probably need people with more knowledge of the rest of the IPv6 stack
to contribute. However, both features aren't common (especially
fragmentation with IPv6) in this situation, so missing them is not
likely to hurt a lot of people.
The other missing features are the 4 missing schedulers (DH, SH, LBLC,
LBLCR) and the FTP application helper.
>> 2009-?? Restructured sync daemon with full IPv4 and IPv6 support
This seems pretty doable once a protocol is decided upon and should be
done before the previous step, IMO.
Julius
--
Julius Volz
Corporate Operations - SysOps
Google Switzerland GmbH
Identification No.:
CH-020.4.028.116-1
--
To unsubscribe from this list: send the line "unsubscribe lvs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
|
