Re: [whatwg/fetch] Acknowledge interaction with draft-ietf-dnsop-svcb-https scheme redirect (#1325)

@davidben approved this pull request.

Agreed this is reasonable for now. Reworking HSTS to be a redirect would be good, but we can do that separately. The boundary between Fetch and various RFCs is also a little odd (having to respecify stuff, etc.), but I think that's a broader problem to work out.

> +   or a congruent match (with or without an asserted <code>includeSubDomains</code> directive); or
+   DNS resolution for the request finds a matching HTTPS RR per
+   <a href=https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https#section-8.5>HTTP Strict Transport Security</a>.

The link "HTTP Strict Transport Security" should be to section 9.5, but it's also a little confusing because "HTTP Strict Transport Security" is the name of the other feature. Perhaps...

```suggestion
   or a congruent match (with or without an asserted <code>includeSubDomains</code> directive) [[!HSTS]]; or
   DNS resolution for the request finds a matching HTTPS RR per
   <a href=https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https#section-9.5>section 9.5</a>
   of [[!SVCB]].
```

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1325#pullrequestreview-923697745
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1325/review/923697745@github.com>