> agreed. that's why I'm leaning towards spec'g it with quoted-string at this > time. It future-proofs the spec
Quoted-string provides no "future-proofing". <token> supports about 77 chars; <quoted-string> adds about 18 more -- there are another 100,000 chars to support (and even more code points) if you actually want future- proofing. Supporting quoted-string is all about past compromises. It adds no value to a new header. Consistency with other headers is theoretically valuable, but consistency without the limits (no unicode...) and baggage (ISO8849-1...) of quoted-string would be considerably better. -- James Manger _______________________________________________ websec mailing list [email protected] https://www.ietf.org/mailman/listinfo/websec
