News for hackers. Stuff that matters.
Re:QUIC is now RFC 9000 by infogulch on Thursday May 27, 2021 @08:58PM (#27310573)
Should have waited for 9001.

Oh my mistake, they have several RFCs from 8999-9002.

Re:QUIC is now RFC 9000 by CobrastanJorji on Thursday May 27, 2021 @11:26PM (#27311416)
Sure, and that's one good meme. But we also get to make some HAL 9000 jokes about Google now, and that's even better (though ironic, given that it was intended to be IBM jokes).
Re:QUIC is now RFC 9000 by imhoguy on Friday May 28, 2021 @03:14AM (#27312579)
Borg vs HAL9000 - that may be an absolute blockbuster ;)
Re:QUIC is now RFC 9000 by verst on Thursday May 27, 2021 @09:02PM (#27310599)
From the article :)

> The IETF just published QUIC as RFC 9000, supported by RFC 9001, RFC 9002, and RFC 8999

Re:QUIC is now RFC 9000 by 1MachineElf on Thursday May 27, 2021 @09:26PM (#27310754)
Haven't heard this meme for a long time now. Reminds me of the old days when my main email was [email protected] simply to get laughs out of people. (That email service shut down roughly 5 years ago.)
Re:QUIC is now RFC 9000 by ucarion on Thursday May 27, 2021 @10:08PM (#27310985)
Yeah, they form a "cluster" of documents: https://www.rfc-editor.org/cluster_info.php?cid=C430, so that the earlier-numbered RFCs can reference later ones. For instance, rfc9000 normatively refers to rfc9001 and rfc9002.
Re:QUIC is now RFC 9000 by infogulch on Thursday May 27, 2021 @11:28PM (#27311428)
Curious, why isn't it numbered the other way? My programming brain is telling me that if you're reading rfc9000 you can't reference rfc9001 because it hasn't been initialized yet. :D
Re:QUIC is now RFC 9000 by anyfoo on Thursday May 27, 2021 @11:41PM (#27311490)
It's in a lot of ways more about not being defined (but possibly declared) yet, rather than initialized. You'd be super sad if you could not reference a function defined later in a source file.

Yeah, I'm absolutely great at parties!

Re:QUIC is now RFC 9000 by infogulch on Thursday May 27, 2021 @11:51PM (#27311548)
Ok, that explanation works for me. And if there was ever an appropriate time to be pedantic it would be in a discussion on RFCs. :)
Re:QUIC is now RFC 9000 by capableweb on Friday May 28, 2021 @08:08AM (#27314403)
> You'd be super sad if you could not reference a function defined later in a source file.

Would you? Most of the environments I'm in requires you to define the thing before you can use it, I'm not that sad about that. In fact, that seems to make a lot more sense than that you can define something after you use it, I'd expect that to lead to a compiler/interpreter error.

Re:QUIC is now RFC 9000 by jopsen on Friday May 28, 2021 @08:25AM (#27314532)
So no recursion?
Re:QUIC is now RFC 9000 by salawat on Friday May 28, 2021 @01:08PM (#27317930)
You totally can.

Remember, it's all about tokenizing. You're associating chunks of machine code to tokens that tell the machine where to go to get the actual definition, or where to plop the machine code if statically linking.

Nobody said that RFC numbering implied any sort of temporal order. You are the Linker. Be the Linker.

Re:QUIC is now RFC 9000 by capableweb on Friday May 28, 2021 @12:36PM (#27317503)
Depends on the compiler/interpreter. Function body could be parsed/evaled after the initial function definition.
Re:QUIC is now RFC 9000 by anyfoo on Friday May 28, 2021 @12:37PM (#27317510)
What environments are those?
Re:QUIC is now RFC 9000 by dzamo_norton on Sunday May 30, 2021 @05:21AM (#27331842)
E.g. Python
Re:QUIC is now RFC 9000 by ucarion on Friday May 28, 2021 @12:05AM (#27311624)
Perhaps I should clarify: rfc9001 normatively refers to rfc9000 (and vice versa). There are cyclical references between RFCs, so there isn't any topological ordering.

It works out because RFCs convey ideas, not code. The authors and editors take care to make sure the cyclical dependencies don't imply circular definitions or other incoherences.

Re:QUIC is now RFC 9000 by dcow on Friday May 28, 2021 @01:34AM (#27312063)
It works in code too. It’s the difference between declaration and initialization. Very commonly existence of a symbol is declared in a header so that it can be referenced only later does the real implementation get linked in.
Re:QUIC is now RFC 9000 by snuxoll on Thursday May 27, 2021 @10:21PM (#27311064)
Is QUIC really worthy of the over 9000 meme? I can’t help but feel we wasted a once in a lifetime opportunity.
Re:QUIC is now RFC 9000 by saagarjha on Saturday June 05, 2021 @06:43PM (#27409025)
I mean every RFC over 9000 is an "over 9000" opportunity.
Re:QUIC is now RFC 9000 by vincnetas on Friday May 28, 2021 @01:35AM (#27312068)
To be used as 9000 meme it should have been "over 9000"

https://en.wikipedia.org/wiki/It%27s_Over_9000!

Re:QUIC is now RFC 9000 by snuxoll on Friday May 28, 2021 @08:45AM (#27314729)
As GP’s edit pointed out, it actually is RFC 8999-9002 - so yes, it’s over 9000.
Re:QUIC is now RFC 9000 by salawat on Friday May 28, 2021 @01:09PM (#27317954)
No, that's just a sine-wave centered around 9000 where someone forgot to take instrument precision into account.