julian.reschke at gmx.de
Tue Jan 26 17:31:43 PST 2010
Henning Schulzrinne wrote:
> In theory, yes. In practice, how many people outside the IETF crowd (which does not need any URL, since they can presumably find RFCs using telnet if they had to) would know what to do with this, even assuming that there's a resolution mechanism in place for those URNs? With a DOI, every grad student can figure it out (and will have figured it out by the first semester, since IEEE Xplore and the ACM DL both use them, along with Springer and the other publishers). If they don't, the reference librarian will gladly show them.
> All they get when they type in that URN is
> Safari can’t open “urn:ietf:rfc:1000” because Mac OS X doesn’t recognize Internet addresses starting with “urn:”.
> The only real use for any RFC-related identifier is for people *outside* the normal IETF crowd. The reason we got an ISSN for the RFC series was to make it easier for "outsiders" to reference RFCs, except that they only identify the whole series. Same idea here.
The way "people" reference things nowadays is by specifying an HTTP URI.
That's at least my experience. And that's why I asked for the best one.
Nobody I work of *ever* heard about DOIs.
Best regards, Julian
More information about the rfc-interest