On Thu, 20 May 2021, Martin Thomson wrote:
I also want to add to what Tommy (P) said about deployment. We've deployed the current wire format (that's what you get when you assign a codepoint people!) Changes would have serious implications.
It looks like the early code point was assigned at 2020-06-30, at draft-ietf-dnsop-svcb-https version 00. I think that might have been premature, as that is technically at the same time the IETF _starts_ looking at it. This unfortunately makes it appear the IETF was only to be used to rubberstamp it. Documents are adopted as a starting point for discuccion, not as the final code point definition with no wiggle room for change. Not changing a document when concerns have been raised will have the possibility of future "serious implications" that would in fact be, more serious, as then we have an even larger install base dealing with the problem. This discussion should be around reasonable and secure wire and presentation formats, not about "but we already deployed this". It should surely be taken into account if changing at this point gives enough benefits, but the idea of changing should not be dismissed out of hand. Paul _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
