Re: [EME] EME charter

On Mon, 2006-11-13 at 10:29 -0800, Joe Touch wrote:
> > To the extent that the lack of middle-to-end and end-to-middle
> > communication prevents middleboxes from being truly transparent (to
> the
> > app layer) or fully visible (to the network layer), EME resolves to
> > address the problem IMHO.
> 
> That was (is) the goal of MIDCOM, as Melinda pointed out. What will
> this WG do beyond that? 

EME is different from MIDCOM in that the MIDCOM model is of an endpoint
signaling *to the line of middle boxes* in front of it (i.e E-M), while
the the EME model is the endpoint signaling *to the other endpoint*
through the line of middle boxes in front of both of them (i.e. E-M-E).

On Mon, 2006-11-13 at 13:09 -0500, Melinda Shore wrote: 
> as long as the
> endpoint needs to know the location of the middlebox in order to
> transmit requests to it you haven't eliminated the lack of tranparency,
> you've just moved it somewhere else.

Agreed. If the signaling destination is the other endpoint which in turn
requires an end-to-end signaling plane, then there is an opportunity to
discover the middleboxes that need to be signaled individually.

-- 
Saikat

Re: [EME] EME charter

Attachment: signature.asc