Content/data is/are already being changed/modified/adapted/etc in transit and
the IETF must deal with it sooner or later.
that follows only if the IETF can make a useful contribution by "dealing with
it".
it's not clear whether this is the case.
Ensuring that the edge is dumb is not the way to protect the end-to-end model.
The proper way to do it is to ensure that the edge is an extension of the
source/origin.
agree, though I would add "or destination" to the end.
but this isn't what's controversial about OPES. what's controversial is the
notion
that the transformations enabled by OPES might also occur in the interior of
the
network, without being explicitly authorized by either the source or the
destination.
Keith