From what I read from the charter below it seems to at least address some of
There's a couple of subtle points here.
- First of all, the WG does not have a charter yet. It has drafted a
charter, but IESG and IAB are not required to accept that charter
verbatim. Before approving a charter, IESG may change it in any way
that it sees fit (and that is required to get IESG and IAB to approve
- The message sent to the new-work list (and thus to ietf-announce)
contains a description of the work, which is not the same as the
charter. It is this description to which I was objecting.
Since we do not know what version of the charter will actually be
discussed by IESG, the message to the new-work list is the best we
have to go on.
- Now please notice the difference between the text that you quoted
(apparently from the WG's draft charter) and the description posted
From the draft charter:
] Intermediary services provided in this way are not transparent: They have to
] be authorized by either the content requestor or the provider, corresponding
] to who the service being provided for.
From the description posted to new-work:
] Intermediary services provided in this way are not transparent:
] Either the content requestor or provider will be aware that a
] tranformation has been performed.
Answer to these concerns should come from a collaborative
architecture/engineering effort within an IETF WG.
Obviously the details could not entirely be worked out by IESG.
But this work is potentially so dangerous that IMHO IESG should either
place strict constraints on the WG while chartering it at all, or
require those details to be worked out by the WG before chartering
it to do further work.