[rfc-i] Using LaTeX & BibTeX to cite RFCs

Joe Touch touch at ISI.EDU
Mon Aug 31 07:00:28 PDT 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Bob Braden wrote:
> Joe Touch wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> The "publisher" is the ISOC, at least for the later RFCs. Even for older
>> RFCs that predate ISOC involvement, the ISOC is the basis for making
>> them available (even the Independent stream) and is thus the publisher
>> at least in a sort.
>>
>> I would never say the publisher was the RFC Editor - that's the editor,
>> not the publisher.
>>
>> Joe
>>   
> Joe,
> 
> the RFC Editor web site says "[The RFC Editor is] funded by the Internet
> Society to edit and publish RFCs." Jon published the RFCs, and the RFC
> Editor at ISI has continued to do so.  Only in the new regime after Dec
> 2009 will editing and publishing be divorced (but not really, as it
> turns out).  Even then, I expect the collection of functions that
> include RFC publication to continue to be called loosely "the RFC Editor".

In the paper publishing world, the publisher owns the rights. They don't
always run the printing presses.

AFAICT, the ISOC has been the publisher since they started inserting
rights clauses. The fact that they farm out the editing or printing
processes to the RFC Editor doesn't necessarily replace the ISOC as
publisher of record for things like citations.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqb13wACgkQE5f5cImnZrtrqQCgn3aTZhiOid1UCH9XeHAxgwFh
GvcAnAnGKuiDjUi5XpjqpGItmh+d+l0O
=g/dl
-----END PGP SIGNATURE-----


More information about the rfc-interest mailing list