Praveen,
> Should the draft stick to only those reqirements that are
> essential and steer clear of the others ?? After all it might be
> tough to capture all optional features in the draft.
I think that the draft should capture most all of the basic
IPv6 RFCs at the level needed. For some, su
In your previous mail you wrote:
As Erik explained before, having per-socket knob provides better control
on the implementation pieces
=> no, it gives the same kind of control, and only in modified pieces
of code.
and it can also satisfy per process behavior.
=> this is not true: I
Jim may have a point here about the server in a helicopter. But where
do we draw the limit? How do we know that 3000 kg IBM mainframe
isn't being flown around in a cargo aircraft? Also, the type of
the interface on the device may have significance. Or the application;
a sensor reporting its finding
Has Multi6 done anything that we we can reference?
Nope. Just heads up. It hopefully will be transparent.
Going back through my mail box I tried to find the mail pointing out
what it was that Jim wanted from multi6 but I can't find it. Could you
elaborate? Or do you want to take it to the mult
