News for hackers. Stuff that matters.
Re:HTTP/2 Frequently Asked Questions by nl on Friday October 03, 2014 @05:31AM (#8404821)
I've recently done some work using SRV (for Minecraft, which uses it).

I agree it's a pretty decent system, and something I'd like to see more systems adopt it.

Interestingly, I can't actually think of a reason why a (customised) web browser couldn't use it now. If a browser understood SRV records it could use the correct port. There might be some odd interactions with the HTTP 1.1 Host header, but I haven't thought about it much.

Of course, browsers that don't understand it wouldn't be able to follow links that use it which is something of a downside I guess.

Re:HTTP/2 Frequently Asked Questions by teddyh on Friday October 03, 2014 @06:01AM (#8404870)
According to the RFC for SRV records, applications SHOULD NOT use SRV records unless explicitly allowed in the standard/RFC for that protocol. There is no mention of SRV records in either the old HTTP RFC or the new HTTP/2 draft RFC; therefore, clients are not permitted to use SRV records.

(I wrote about this previously here on HN: https://news.ycombinator.com/item?id=7522208)

Re:HTTP/2 Frequently Asked Questions by nl on Friday October 03, 2014 @06:23AM (#8404921)
SHOULD NOT prohibits nothing.

Indeed, since the HTTP/1.1 RFC was issued in 1999 and the SRV RFC in 2000 there is no way it could have mentioned it.

If there are technical reasons why it can't work that's one thing. If some verbiage in the RFC is all that holds it back it's easy to fix: try it out, then issue a new RFC.

The whole RFC process embraces changes like this.

Re:HTTP/2 Frequently Asked Questions by gsnedders on Friday October 03, 2014 @08:30AM (#8405186)
For those unaware of the RFC 2119 definition:

   SHOULD NOT   This phrase, or the phrase "NOT RECOMMENDED" mean that
   there may exist valid reasons in particular circumstances when the
   particular behavior is acceptable or even useful, but the full
   implications should be understood and the case carefully weighed
   before implementing any behavior described with this label.
Re:HTTP/2 Frequently Asked Questions by teddyh on Friday October 03, 2014 @07:05AM (#8404991)
> SHOULD NOT prohibits nothing.

And an RFC is not a standard, and all life is meaningless? No, a SHOULD NOT should be taken seriously, not ignored.

The SRV RFC included that language for a reason, and probably had HTTP in mind when they wrote it, and therefore wanted HTTP clients not to use SRV records randomly. Since then, HTTP has has plenty of time to add SRV usage in its minor revisions, but has chosen not to. But now, with HTTP/2, a major revision, it is the perfect time to add this kind of thing.

Re:HTTP/2 Frequently Asked Questions by nl on Friday October 03, 2014 @08:00AM (#8405120)
I'm sorry - I just read that other thread you linked to. Others made the same point to you then, and you still seem stuck on that point.

RFCs are not like ISO standards. The name says it all: "request for comments".

RFCs reflect the ideal of "rough consensus and running code".

The SRV RFC was written by an author from Microsoft aimed at domain controller discovery. They probably didn't think of HTTP at all.

There's an expired draft RFC for SRV+HTTP[1].

You are right: SHOULD NOT should be taken seriously. But if you are (say) Mozilla, Microsoft or Google and writing a webbrowser you probably know enough to understand when you can break a RFC.

How do you think TCP-fast-start happened?

[1] http://tools.ietf.org/html/draft-andrews-http-srv-01

Re:HTTP/2 Frequently Asked Questions by teddyh on Friday October 03, 2014 @08:17AM (#8405151)
Different RFCs have different levels. RFC 2782 is a “Standards Track” RFC and a “Proposed Standard”, and should be taken seriously indeed (there is only one “higher” level).

The SRV RFC was not by Microsoft. It has three authors, the other two being one Arnt Gulbrandsen from Troll Tech (of the Qt library fame) and Paul Vixie of the Internet Software Consortium, who is also the author of BIND. I actually am inclined to think that they did consider HTTP seriously.