Note that only permanent documents should be cited as references. Other items, such as Web pages or working groups, should be cited inline (i.e., see the Open Grid Forum, https://www.ogf.org) or as a footnote. In-text citations can refer to work in progress. To refer to a current working draft, an inline citation might simply read, (the XYZ working group has a draft in progress to address this topic. It may be found via the WG’s Web page at www.example.org). Hyperlinks to transient documents should be avoided (for example, a link to a current draft of a document should not be used, if the document is likely to be replaced in the near future)
References should conform to a standard such as used by IEEE[1], ACM[2], MLA[3], Chicago[4] or similar. Include an author, year, title, publisher, place of publication. For online materials, also add a URL and an access date. It may be useful, but is not required to separate out “normative references,” as described in [BUSH].
Some sample citations:
[2] https://www.acm.org/publications/authors/reference-formatting
[3] https://library.concordia.ca/help/citing/mla.php
[4] https://www.chicagomanualofstyle.org/tools_citationguide.html
Abbreviation
Reference
[BRADNER]
Scott Bradner. Key Words for Use in RFCs to Indicate Requirement Levels, RFC 2119. The Internet Society. March 1997. https://tools.ietf.org/html/rfc2026
[BUSH]
Randy Bush, Thomas Narten. Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level. RFC 3967. The Internet Society. December 2004. https://tools.ietf.org/html/rfc3967
[CATLETT]
Charlie Catlett, Cees de Laat, David Martin, Gregory B. Newby, Dane Skow. GFD-C.152: Open Grid Forum Document Process and Requirements. Open Grid Forum. June 2009. https://www.ogf.org/documents/GFD.152.pdf
[RESCORLA]
Eric Rescorla, Brian Korver, Internet Architectures Board, Guidelines for Writing RFC Text on Security Considerations. RFC 3552. The Internet Society. July 2003. https://tools.ietf.org/html/rfc3552