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

[Joe Touch]

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



Brian E Carpenter wrote:
> Joe,
> 
> Without going into specifics, I think we have to consider what
> will survive LaTeX processing with typical class files, and actually
> appear in the published citation.

Sure. I was asked what I'd put into the fields; if there are other
considerations, these can be left blank IMO.

Joe

> In my experience, putting
> something into its most logical container in a raw BibTeX file
> doesn't always cause it to appear in the finished paper as one
> would wish. For many publications in our area, the ACM or CCR
> class files are common, and I would certainly want any
> recommended BibTeX template to produce a good result with
> those class files.
> 
>     Brian
> 
> 
> On 2009-08-29 04:06, Joe Touch wrote:
> 
> 
> RJ Atkinson wrote:
>>>> On  28 Aug 2009, at 11:37, Joe Touch wrote:
>>>>> 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.
>>>>     Which value(s) do you believe should be put into the "INSTITUTION"
>>>> field of a BIB entry for an RFC ?  :-)
> Not all fields need to be populated. I'd like to suggest:
> 
> 	editor		ISOC
> 
> 	institution	IETF			non indep-stream
> 			authors' insitution(s)	indep stream
> 
> Joe
_______________________________________________
rfc-interest mailing list
rfc-interest at rfc-editor.org
http://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqYQt8ACgkQE5f5cImnZruoGQCgoinvgIhm/FRjnQyT6/cBM9SQ
IX4An39c9KDOP5xk/nRemLXVV0dhR/EJ
=uhZI
-----END PGP SIGNATURE-----