in SRV we added a port number to the rdata because the /etc/services file was painful to keep globally updated. SRV was protocol independent.
HTTPSSVC is protocol specific, and when it copied SRV, it included the port number in the rdata, which i think is both unnecessary and error-prone. managed private networks who want to permit outbound HTTP/3 are going to add a rule like "if the far end port number is 443, add a stateful rule". anyone who uses the port number field (if it exists) in HTTPSSVC to specify a different port number is going to suffer, as will many of the clients trying to access that service. i suggest that the port 443 assumption for HTTP/3 be baked in, and that this field be removed from the HTTPSSVC rdata. -- Paul _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
