[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

When is a wedge a wedge? [Re: architecture draft]

Iljitsch,

Thanks for starting the debate. Let's all *please* try to separate out issues
at the level of the subject line... it makes systematic analysis so much
easier, just one step short of a formal issue tracker.

I will just comment on one of your points:

  "As an alternative to insertion of a new protocol stack element into
   the protocol architecture, an alternative approach is to modify an
   existing protocol stack element to include the functionality
   performed by the EIP element. This modification could be undertaken
   within the transport protocol stack element, or within the
   internetworking stack element."

Is there really a difference between having a wedge between the transport 
> and network layers and implementing the functionality in the "upper part"
> of the IP protocol?

That may turn out to be just an implementation detail, but I think Geoff
is correct to identify it as an architectural question at this stage. We
shouldn't jump to a conclusion on this, since TCP/IP stacks vary a lot
in their internal architecture.

Brian