Some questions about your would-like expectations for this project: *Path MTU detection*: >> Yes, a statistical approach is probably the only viable option since it's very difficult to set Don't Fragment from within Java. (Is this still true with recent versions?). I mostly thought about it in context of an unpleasant issue with traditional MTU discovery - on-the-way routers with disabled ICMP functionality - which can be avoided by implementing something similar to rfc 4821 (I don't think it'd be an overkill for transport layer). And, all in all, this kind of per-connection statistics could still be useful in other aspects of implementation. But the question about DF bit and general control over IP layer is crucial. Does anyone know, are we still only able to hard-hack it with native interfaces or it can nowadays be accessed directly from Java? Intermediate searching has shown only unfavorable results.. * * *Congestion control*: Since transport layer behaves in a similar to TCP way, should the new version of congestion control be also inherited from TCP or are there any important issues that need to be taken into account when designing the algorithm?
Also, where there any wishes about what can be changed between operating over a lossy- or stable- link types? Now I'm thinking about possible varying of packet sizes (which is currently already done automatically, if I'm not mistaken) and timeouts, retransmit and acknowledge policies. And, in case somebody has already planned this out roughly - what interface for configuration should the transport layer provide upwards (ponder over subsequent implementation of transport plugins)? P.s. I'm not quite sure whether mailing list is the right place to discuss it. Should I rather ask in IRC? Thank you all! Quadrocube.
_______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
