On 5/12/2018 1:01 PM, John R Levine wrote:
The best I can guess is that there is an underlying assumption that
normative language only applies to formally published specifications,
but there's nothing in the current draft language to support that.
No, it's that standards are about
I don't want to rathole on MUST vs. SHOULD because the more I think about
it the less I understand the difference.
Consider the long history of email header fields that weren't registered but
which interoperated quite nicely...
Sort of. Everything interoperated fine in the sense that we
On 5/11/2018 7:41 PM, John Levine wrote:
I'd change all of the SHOULD to MUST, as in
you have to do this if you want to interoperate.
The working group should consider the choice of normative level, but
where I landed is that a MUST is not needed and actually could be
