Document: draft-ietf-intarea-proxy-config Title: Communicating Proxy Configurations in Provisioning Domains Reviewer: Florian Obser Review result: Ready with Nits
I have been selected as the DNS Directorate reviewer for this draft. The DNS Directorate seeks to review all DNS or DNS-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to provide assistance to the ADs. For more information about the DNS Directorate, please see https://wiki.ietf.org/en/group/dnsdir This reviewer is not familiar with proxies nor provisioning domains, so the review will solely focus on DNS. I've not found any issues so I'm marking this as "Ready with Nits". | 2. Fetching PvD Additional Information for proxies | Note that all proxies that are co-located on the same host share the | same PvD Additional Information. Proxy deployments that need | separate PvD configuration properties MUST use different hosts. This is probably blatantly obvious to people familiar with proxies, but what does "host" mean here? A different IP address? A different hostname? I.e. do http servers co-located with proxies support http host headers and SNI? | 2.1. Discovery via HTTPS/SVCB Records | The presentation and wire-format values for pvd SvcParamKey MUST be empty. That is an odd thing to say, there is only one value and it MUST be empty. The value cannot have a presentation format that is non-empty and a wire-format that is empty. If this is the outcome of a lengthy WG discussion and the only way to reach consensus then I guess you can leave it since it's not technically wrong, it's just weird. Otherwise, I'd suggest: | The value of the pvd SvcParamKey MUST be empty. | 6. Security Considerations OLD | Configuration advertised via PvD Additional Information, such DNS | zones or associated proxies NEW (adding "as" in front of DNS) | Configuration advertised via PvD Additional Information, such as DNS | zones or associated proxies _______________________________________________ Int-area mailing list -- [email protected] To unsubscribe send an email to [email protected]
