Range header and CORS

Someone has pointed me to some documentation indicating that while a request for a single range using the Range header is de jure simple, a request for multiple ranges is not, and therefore will/should trigger a CORS preflight request. We've had a number of discussions about the undesirability of preflight requests in the context of the patch IFT spec but I don't remember seeing anything about this for the range-request spec.

It seems like this would add a significant cost to any mechanism relying on range request for multiple ranges. Do we know if its true?

Skef