MUST->SHOULD for not publishing colliding config_id values.
This is a little more than editorial maybe but later text in any case seems to handle config_id collisions so given the MUST here is really on DNS provisioning code and not ECH code anyway, I'll claim it's editorial:-) I'd also be fine with s/MUST/should/ if that were thought better.
I also suggest deleting a sentence that looks like it no longer belongs. ("This process...") It could be that ought be shifted to later where trial decryption is discussed, not sure.
sftcd
commented
3 years ago
MUST->SHOULD for not publishing colliding config_id values.
This is a little more than editorial maybe but later text in any case seems to handle config_id collisions so given the MUST here is really on DNS provisioning code and not ECH code anyway, I'll claim it's editorial:-) I'd also be fine with s/MUST/should/ if that were thought better.
I also suggest deleting a sentence that looks like it no longer belongs. ("This process...") It could be that ought be shifted to later where trial decryption is discussed, not sure.