Reviewer: Joe Clarke Review result: Ready I have been assigned draft-ietf-dnsop-svcb-https to review on behalf of the Ops Directorate. This document describes two new RR types (Service Binding [SVCB] and HTTPS). From an operational standpoint, I think this document is ready, and I appreciate the attention paid to interoperability with approaches such as ECS, Alt-Svc, etc. I did find two issues with the document, however. On a more editorial front, I found a few references to "ServiceForm" and "AliasForm" (the former being in the appending, but the latter showing up in Security Considerations). These seem to be left over from a former revision and probably should be ServiceMode and AliasMode now, correct? Second, you use the term "SVCB-compatible" early on in Section 1, and you mention what its definition might be in Section 1.4, but I don't really get a clear picture of what makes an RR SVCB-compatible. I feel the document should expound on the minimum requirements to be considered as such. -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
