Content-Security-Policy: referrer always

I was reading the draft spec for the content-security-policy referrer
directive, and I was hoping that there could be a way to convey that the
"always" option may be unsafe for HTTPS. Similar to the existing
"unsafe-eval" and "unsafe-inline" directives, perhaps this could be
"unsafe-always" instead.

It has been pointed out to me that this sounds too much like "always
unsafe", so perhaps there is a better name to be found.

Thanks heaps,
--Tom.