Is it simpler to ban escapes or not in the presentation syntax?

[davidben]

The presentation language currently says:

The presentation value of the SvcParamValue is a comma-separated list ({{Appendix A.1 of I-D.ietf-dnsop-svcb-https}}) of decimal integers between 0 and 65535 (inclusive) in ASCII. Any other value is a syntax error. To enable simpler parsing, this SvcParam MUST NOT contain escape sequences.

@martinthomson points out it's better to avoid special parsing rules. I think I borrowed this from https://www.rfc-editor.org/rfc/rfc9460.html#section-7.2-2 and inferred that avoiding the special parsing rule was the convention for presentation of 16-bit integers.

I don't care either way and figure we should do whatever is conventional/convenient here. The behavior of "port" is a point towards banning escapes. But if folks think allowing them is better, that's cool too.

See #3 (comment)