Discuss handling of untrusted profiles

[bemasc]

Is it a design goal of this draft to support secure connection, even if the compression template is distributed over an untrusted channel?

I believe it is a design goal, and I think it's probably achieved by the current draft (except for questions around the random and finishedSize keys), but it's not stated explicitly in the draft.