Remove threat-based justification of ALDR

[laurencelundblade]

There's text that justifies the need for ALDR to defend a threat from wayward serialization schemes (e.g., from badly conceived eCBOR, fCBOR and gCBOR). That threat doesn't really exist, so this text is unnecessary and confusing.

It's in several places in the document. not just the appendix.

I think the main frame up for ALDR should be orient around helping designers of deterministic protocols. I think that's what the readers need.

[hildjj]

Can you point to sections in the current version that you are worried about, so I'm sure I'm looking at the right places, please?

[cabo]

I cannot find the word "threat" in the current document, and the above question is unanswered.

(Apart from that, his threat definitely exists, motivated by the toybox approach used by RFC 8949 Core DE Requirements; it is just exacerbated when people don't know about the architecture.)

Can this be closed?