Hmm, MUST is probably too strong here. The intent here is to guard for cases where *how* the resource is processed on the client is changed based on selected resource (e.g. DPR change), but there are also cases (e.g. resizing) where confirmation is not necessary -- also, confirmation != Vary.. different concepts.