3 ms·
To me, a design document is something you write for yourself, once you’ve decided on the design; whereas an RFC is something you write for others, and others wr
by derefr 8y ago
To me, a design document is something you write for yourself, once you’ve decided on the design; whereas an RFC is something you write for others, and others write for you, to communicate a potential design when a final design hasn’t yet been “selected.”
It’s effectively a way of brainstorming that doesn’t get quashed by “that’ll never work” half-way through the 1000-ft abstract, because all the details are already there on the page to prove it will work. It’s just a question of which of the proposed designs works best (and then of attempting to maybe incorporate some of the alternatives’ ideas into the winner, though not necessarily.)
Or, in short: it’s a debate where everyone is doing an “argument by constructive proof” for their POV.
The cryptographic-primitive standardization “competitions” for things like SHA, are RFC processes under another name.