2 ms·
Beat me to it, I was also wondering if the OP proposal hasn't been completely obsoleted by SVCB/HTTPS at this point. Still reveals a sad picture of the ecosyst
by xg15 4y ago
Beat me to it, I was also wondering if the OP proposal hasn't been completely obsoleted by SVCB/HTTPS at this point.
Still reveals a sad picture of the ecosystem that a standard which addressed the same shortcomings existed since 2009 but was completely ignored until Cloudflare reinvented it in a proprietary fashion.
On the other hand, expecting that end users suddenly start typing "https+srv://" everywhere for exactly no added benefit except to make standards wonks happy, doesn't exactly inspire much confidence in the standard's authors either...
- mananaysiempre 4y agoThe -00 draft[1] did not require the +srv. I would guess the blame lies with security problems when user agents with support for the SRV record see one thing and those without see another. (The drafts go up to -05, though this is not apparent from the posted link.) [1] https://datatracker.ietf.org/doc/html/draft-jennings-http-srv-00 https://datatracker.ietf.org/doc/html/draft-jennings-http-sr...