Difference between revisions of "Template:Cite IETF/doc"

From blackwiki
Jump to navigation Jump to search
imported>Trappist the monk
m (ce;)
imported>Debresser
m (Add dash to "access-date".)
 
(5 intermediate revisions by 4 users not shown)
Line 13: Line 13:
 
| date        = September 2006
 
| date        = September 2006
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
| accessdate  = November 2, 2009
+
| access-date = November 2, 2009
 
| doi        = 10.17487/RFC4677
 
| doi        = 10.17487/RFC4677
 
}}</ref><ref>{{cite IETF
 
}}</ref><ref>{{cite IETF
Line 26: Line 26:
 
| date        = December 1994
 
| date        = December 1994
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
| accessdate  = November 2, 2009
+
| access-date = November 2, 2009
 
| doi        = 10.17487/RFC1739
 
| doi        = 10.17487/RFC1739
 
| ref        = ietf
 
| ref        = ietf
Line 47: Line 47:
 
| date        = October 1996
 
| date        = October 1996
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
| accessdate  = November 2, 2009
+
| access-date = November 2, 2009
 
| doi        = 10.17487/RFC2026
 
| doi        = 10.17487/RFC2026
 
}}</ref><ref>{{cite IETF
 
}}</ref><ref>{{cite IETF
Line 71: Line 71:
 
| date        = August 1995
 
| date        = August 1995
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
| accessdate  = November 2, 2009
+
| access-date = November 2, 2009
 
| doi        = 10.17487/RFC1818
 
| doi        = 10.17487/RFC1818
 
}}</ref>
 
}}</ref>
Line 85: Line 85:
 
| date        = March 1990
 
| date        = March 1990
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
| accessdate  = November 2, 2009
+
| access-date = November 2, 2009
 
| doi        = 10.17487/RFC1150
 
| doi        = 10.17487/RFC1150
 
}}</ref><ref>{{cite IETF
 
}}</ref><ref>{{cite IETF
Line 114: Line 114:
  
 
===cite IETF specific parameters===
 
===cite IETF specific parameters===
====Title====
+
*{{para|appendix}} – Appendix number of the document. {{para|appendix|A.1}} produces "sec. A.1" Also used to create an anchor link for the document's URL.
* '''title''': Title of the document; displays in italics. If {{em|both}} '''title''' and '''sectionname''' are omitted, then the template will attempt to auto-generate a title using the first of the '''rfc''', '''std''', '''bcp''', '''fyi''', '''draft''', '''ien''', '''rtr''' or '''id''' document identifier parameters, in that order.
+
*{{para|autolink}} – {{para|autolink|<var>yes</var>}} or {{para|autolink|<var>no</var>}} Automatically generate a link to ietf.org for documents specified with {{para|rfc}}, {{para|std}}, {{para|bcp}}, {{para|fyi}}, {{para|draft}}, {{para|ien}}, or {{para|rtr}}. (enabled by default)
* '''sectionname''': The section name or section title of the document, written in full; displays before '''title''' and enclosed in quotes.
+
*{{para|bcp}} – Number of the [[Best Current Practice]] (BCP) document. Also used to automatically generate a link to ietf.org.
 +
*{{para|draft}} – Name of the [[Internet Draft]] (I-D) document, including the leading draft-. Also used to automatically generate a link to ietf.org.
 +
*{{para|fyi}} – Number of the [[For Your Information]] (FYI) document. Also used to automatically generate a link to ietf.org.
 +
*{{para|idanchor}} – Anchor link target. By default, no anchor link is generated. The special value {{para|idanchor|ietf}} generates an anchor link suitable for use with this template's '''ref''' parameter. Requires one of '''id''', '''rfc''', '''std''', '''bcp''', '''fyi''', '''draft''', '''ien''' or '''rtr''' fields to be present for the anchor link text.
 +
*{{para|idlink}} – Internal document anchor or title of a Wikipedia article to link via the document identifier. Article should already exist. Must not be wikilinked itself. Do not use this on its own, but along with '''id''', '''rfc''', '''std''', '''bcp''', '''fyi''', '''draft''', '''ien''' or '''rtr'''.
 +
*{{para|idlinktype}} – One of the values: '''id''', '''rfc''', '''std''', '''bcp''', '''fyi''', '''draft''', '''ien''' or '''rtr''' can be given to '''idlinktype''' to force the template to use the specified document identifier as the link text for '''idanchor''' or '''idlink'''. Do not use this on its own, but along with '''idanchor''' or '''idlink''' and '''id''', '''rfc''', '''std''', '''bcp''', '''fyi''', '''draft''', '''ien''' or '''rtr'''.
 +
*{{para|ien}} – Number of the [[Internet Experiment Note]] (IEN) document. Also used to automatically generate a link to ietf.org.
 +
*{{para|nosec}} – Using '''section''', ''''sections''', or '''appendix''' automatically places the sec. notation. Se {{para|nosec|y}} to hide the sec. notation.
 +
*{{para|referenceid}} – Reference id for the document. Used to create an anchor link for the document's URL.
 +
*{{para|rfc}} – Number of the [[Request for Comments]] (RFC) document. Also used to automatically generate a link to ietf.org.
 +
*{{para|rtr}} – Number of the [[Réseaux Associés pour la Recherche Européenne|RARE]] Technical Reports (RTR) document. Also used to automatically generate a link to ietf.org.
 +
*{{para|section}} – Section number of the document. {{para|section|4.3.1}} produces "sec. 4.3.1" Also used to create an anchor link for the document's URL. Can also be used in combination with '''sections''' to link to the first section in the given section range.
 +
*{{para|sections}} – Section range of the document. {{para|sections|4.3-4.7}} produces "sec. 4.3-4.7"
 +
*{{para|sectionname}} – The section name or section title of the document, written in full; displays before '''title''' and enclosed in quotes.
 +
*{{para|std}} – Number of the [[Internet Standard]] (STD) document. Also used to automatically generate a link to ietf.org.
  
====In-source locations====
+
As with all cs1|2 templates, {{para|title}} is required.  If omitted, the template will attempt to auto-generate a title using the first of '''rfc''', '''std''', '''bcp''', '''fyi''', '''draft''', '''ien''', '''rtr''' or '''id''' document identifier parameters, in that order.
* '''page''': Page in the source that supports the content. Displays preceded with {{code|p.}} unless {{para|nopp|y}}. Also used to create an anchor link for the document's URL. If either '''section''' or '''appendix''' is also given, the anchor will link to the section or appendix instead of the page. Can also be used in combination with '''pages''' to link to the first page in the given page range if '''section''' and '''appendix''' are not specified.
 
* OR: '''pages''': Pages in the source that supports the content; separate page ranges with an en dash (–); separate non-sequential pages with a comma (,); do not use to indicate the total number of pages in the source. Displays preceded with {{code|pp.}} unless {{para|nopp|y}}.
 
** '''nopp''': Set to <var>y</var> to suppress the {{code|p.}} or {{code|pp.}} notations where this is inappropriate; for example, where {{para|page|Front cover}}.
 
* '''section''': Section number of the document. {{para|section|4.3.1}} produces "sec. 4.3.1" Also used to create an anchor link for the document's URL. Can also be used in combination with '''sections''' to link to the first section in the given section range.
 
* '''sections''': Section range of the document. {{para|sections|4.3-4.7}} produces "sec. 4.3-4.7"
 
* OR: '''appendix''': Appendix number of the document. {{para|appendix|A.1}} produces "sec. A.1" Also used to create an anchor link for the document's URL.
 
* OR: '''referenceid''': Reference id for the document. Used to create an anchor link for the document's URL.
 
* '''nosec''': Using '''section''', ''''sections''', or '''appendix''' automatically places the sec. notation. Se {{para|nosec|y}} to hide the sec. notation.
 
 
 
====URL====
 
* '''section-url''': URL to an individual section of the document (including an anchor if required). Overrides an automatically generated URL and should not be specified unless absolutely necessary. Should be at the same site as {{para|url}}, if any.
 
* '''page-url''': URL to an individual page of the document (including an anchor if required). Overrides an automatically generated URL and should not be specified unless absolutely necessary. Should be at the same site as {{para|url}}, if any.
 
* '''autolink''': {{para|autolink|<var>yes</var>}} or {{para|autolink|<var>no</var>}} Automatically generate a link to ietf.org for documents specified with {{para|rfc}}, {{para|std}}, {{para|bcp}}, {{para|fyi}}, {{para|draft}}, {{para|ien}}, or {{para|rtr}}. (enabled by default)
 
 
 
====Anchor====
 
* <span id="csdoc_ref" ></span>'''ref''': ID for anchor. By default, no anchor is generated. The ordinary nonempty value {{para|ref|<var>ID</var>}} generates an anchor with the given <var>ID</var>; such a linkable reference can be made the target of [[Wikipedia:Citing sources/Further considerations#Wikilinks to full references|wikilinks to full references]], especially useful in short citations like [[Wikipedia:Citing sources#Shortened footnotes|shortened notes]] and [[Wikipedia:Parenthetical referencing|parenthetical referencing]]. The special value {{para|ref|harv}} generates an anchor suitable for the {{tl|harv}} template. See: [[Template:Citation/doc#Anchors for Harvard referencing templates|Anchors for Harvard referencing templates]]. The special value {{para|ref|ietf}} generates an anchor suitable for use with this template's '''idanchor''' parameter.
 
 
 
====Identifiers====
 
* '''rfc''': Number of the [[Request for Comments]] (RFC) document. Also used to automatically generate a link to ietf.org.
 
* '''std''': Number of the [[Internet Standard]] (STD) document. Also used to automatically generate a link to ietf.org.
 
* '''bcp''': Number of the [[Best Current Practice]] (BCP) document. Also used to automatically generate a link to ietf.org.
 
* '''fyi''': Number of the [[For Your Information]] (FYI) document. Also used to automatically generate a link to ietf.org.
 
* '''draft''': Name of the [[Internet Draft]] (I-D) document, including the leading draft-. Also used to automatically generate a link to ietf.org.
 
* '''ien''': Number of the [[Internet Experiment Note]] (IEN) document. Also used to automatically generate a link to ietf.org.
 
* '''rtr''': Number of the [[Réseaux Associés pour la Recherche Européenne|RARE]] Technical Reports (RTR) document. Also used to automatically generate a link to ietf.org.
 
* '''id''': A [[unique identifier]] for the document, used if none of the above are applicable. Overrides automatically generated document identifiers—'''rfc''', '''std''', '''bcp''', '''fyi''', '''draft''', '''ien''' or '''rtr'''—and should not be specified unless absolutely necessary. If used, you also need to specify the kind of identifier you are using. Don't wikilink, use '''idlink''' instead.
 
* '''idanchor''': Anchor link target. By default, no anchor link is generated. The special value {{para|idanchor|ietf}} generates an anchor link suitable for use with this template's '''ref''' parameter. Requires one of '''id''', '''rfc''', '''std''', '''bcp''', '''fyi''', '''draft''', '''ien''' or '''rtr''' fields to be present for the anchor link text.
 
* OR: '''idlink''': Internal document anchor or title of a Wikipedia article to link via the document identifier. Article should already exist. Must not be wikilinked itself. Do not use this on its own, but along with '''id''', '''rfc''', '''std''', '''bcp''', '''fyi''', '''draft''', '''ien''' or '''rtr'''.
 
* '''idlinktype''': One of the values: '''id''', '''rfc''', '''std''', '''bcp''', '''fyi''', '''draft''', '''ien''' or '''rtr''' can be given to '''idlinktype''' to force the template to use the specified document identifier as the link text for '''idanchor''' or '''idlink'''. Do not use this on its own, but along with '''idanchor''' or '''idlink''' and '''id''', '''rfc''', '''std''', '''bcp''', '''fyi''', '''draft''', '''ien''' or '''rtr'''.
 
  
 
Copy a blank version to use. Remember to use the "|" (pipe) character between each parameter. Please delete any unused parameters to avoid clutter in the edit window.
 
Copy a blank version to use. Remember to use the "|" (pipe) character between each parameter. Please delete any unused parameters to avoid clutter in the edit window.
Line 155: Line 140:
 
|- width="50%" style="vertical-align:top;"
 
|- width="50%" style="vertical-align:top;"
 
| colspan="3" |
 
| colspan="3" |
:<code><nowiki>{{cite IETF |title= |rfc= |std= |bcp= |fyi= |draft= |ien= |rtr= |sectionname= |section= |sections= |appendix= |referenceid= |page= |pages= |last1= |first1= |authorlink1= |last2= |first2= |authorlink2= |authormask= |editor1-last= |editor1-first= |editor1-link= |others= |date= |year= |orig-year= |publisher=[[Internet Engineering Task Force|IETF]] |location= |language= |format= |access-date= |url= |section-url= |page-url= |autolink= |id= |idanchor= |idlink= |idlinktype= |doi= |doi-broken-date= |issn= |archive-url= |archive-date= |quote= |nopp= |nosec= |ref= |lay-summary= |lay-date= |postscript= |last-author-amp= }}</nowiki></code>
+
:<code><nowiki>{{cite IETF |title= |rfc= |std= |bcp= |fyi= |draft= |ien= |rtr= |sectionname= |section= |sections= |appendix= |referenceid= |page= |pages= |last1= |first1= |authorlink1= |last2= |first2= |authorlink2= |authormask= |editor1-last= |editor1-first= |editor1-link= |others= |date= |year= |orig-year= |publisher=[[Internet Engineering Task Force|IETF]] |location= |language= |format= |access-date= |url= |section-url= |page-url= |autolink= |id= |idanchor= |idlink= |idlinktype= |doi= |doi-broken-date= |issn= |archive-url= |archive-date= |quote= |nopp= |nosec= |ref= |lay-summary= |lay-date= |postscript= |last-author-amp=}}</nowiki></code>
 
|- width="50%" style="vertical-align:top;"
 
|- width="50%" style="vertical-align:top;"
 
! colspan="3" | Most commonly used parameters (use this and you won't have to delete as much)
 
! colspan="3" | Most commonly used parameters (use this and you won't have to delete as much)
 
|- width="50%" style="vertical-align:top;"
 
|- width="50%" style="vertical-align:top;"
 
| colspan="3" |
 
| colspan="3" |
:<code><nowiki>{{cite IETF |title= |rfc= |sectionname= |section= |page= |last= |first= |author-link= |year= |publisher=[[Internet Engineering Task Force|IETF]] |access-date= |doi= }}</nowiki></code>
+
:<code><nowiki>{{cite IETF |title= |rfc= |sectionname= |section= |page= |last= |first= |author-link= |date= |publisher=[[Internet Engineering Task Force|IETF]] |access-date= |doi=}}</nowiki></code>
 
|- width="50%" style="vertical-align:top;"
 
|- width="50%" style="vertical-align:top;"
 
! Example 1
 
! Example 1
Line 216: Line 201:
 
| date        = March 2014
 
| date        = March 2014
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
| accessdate  = November 26, 2017
+
| access-date = November 26, 2017
 
| doi        = 10.17487/RFC7159
 
| doi        = 10.17487/RFC7159
 
}}</nowiki><br/>→ <span style="background:white">{{cite IETF
 
}}</nowiki><br/>→ <span style="background:white">{{cite IETF
Line 227: Line 212:
 
| date        = March 2014
 
| date        = March 2014
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
| accessdate  = November 26, 2017
+
| access-date = November 26, 2017
 
| doi        = 10.17487/RFC7159
 
| doi        = 10.17487/RFC7159
 
}}</span>
 
}}</span>
Line 252: Line 237:
 
| last7      = Berners-Lee
 
| last7      = Berners-Lee
 
| authorlink7 = Tim Berners-Lee
 
| authorlink7 = Tim Berners-Lee
| year        = 1999
+
|date=June 1999
| month      = June
 
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| doi        = 10.17487/RFC2616
 
| doi        = 10.17487/RFC2616
Line 277: Line 261:
 
| last7      = Berners-Lee
 
| last7      = Berners-Lee
 
| authorlink7 = Tim Berners-Lee
 
| authorlink7 = Tim Berners-Lee
| year        = 1999
+
|date=June 1999
| month      = June
 
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| doi        = 10.17487/RFC2616
 
| doi        = 10.17487/RFC2616
Line 290: Line 273:
 
| author      = P. Mockapetris
 
| author      = P. Mockapetris
 
| authorlink  = Paul Mockapetris
 
| authorlink  = Paul Mockapetris
| year        = 1987
+
|date=November 1987
| month      = November
 
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
| accessdate = August 3, 2008
+
| access-date = August 3, 2008
 
| doi        = 10.17487/RFC1034
 
| doi        = 10.17487/RFC1034
 
| quote      = A domain is a subdomain of another domain if it is contained within that domain. This relationship can be tested by seeing if the subdomain's name ends with the containing domain's name. For example, A.B.C.D is a subdomain of B.C.D, C.D, D, and ' '.
 
| quote      = A domain is a subdomain of another domain if it is contained within that domain. This relationship can be tested by seeing if the subdomain's name ends with the containing domain's name. For example, A.B.C.D is a subdomain of B.C.D, C.D, D, and ' '.
Line 303: Line 285:
 
| author      = P. Mockapetris
 
| author      = P. Mockapetris
 
| authorlink  = Paul Mockapetris
 
| authorlink  = Paul Mockapetris
| year        = 1987
+
|date=November 1987
| month      = November
 
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
| accessdate  = August 3, 2008
+
| access-date = August 3, 2008
 
| doi        = 10.17487/RFC1034
 
| doi        = 10.17487/RFC1034
 
| quote      = A domain is a subdomain of another domain if it is contained within that domain. This relationship can be tested by seeing if the subdomain's name ends with the containing domain's name. For example, A.B.C.D is a subdomain of B.C.D, C.D, D, and ' '.
 
| quote      = A domain is a subdomain of another domain if it is contained within that domain. This relationship can be tested by seeing if the subdomain's name ends with the containing domain's name. For example, A.B.C.D is a subdomain of B.C.D, C.D, D, and ' '.
Line 327: Line 308:
 
| url        = https://tools.ietf.org/tools/rfcmarkup/
 
| url        = https://tools.ietf.org/tools/rfcmarkup/
 
| title      = Rfcmarkup Tool
 
| title      = Rfcmarkup Tool
| accessdate  = November 26, 2017
+
| access-date = November 26, 2017
 
| last        = Levkowetz
 
| last        = Levkowetz
 
| first      = Henrik
 
| first      = Henrik
Line 335: Line 316:
 
| url        = https://tools.ietf.org/tools/rfcmarkup/rfcmarkup-1.121.tgz
 
| url        = https://tools.ietf.org/tools/rfcmarkup/rfcmarkup-1.121.tgz
 
| title      = rfcmarkup-1.121.tgz (29.7 KB)
 
| title      = rfcmarkup-1.121.tgz (29.7 KB)
| accessdate  = November 26, 2017
+
| access-date = November 26, 2017
 
| last        = Levkowetz
 
| last        = Levkowetz
 
| first      = Henrik
 
| first      = Henrik
Line 345: Line 326:
 
| url        = https://tools.ietf.org/html/
 
| url        = https://tools.ietf.org/html/
 
| title      = IETF Documents
 
| title      = IETF Documents
| accessdate  = November 2, 2009
+
| access-date = November 2, 2009
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
}}</ref><ref>{{cite web
 
}}</ref><ref>{{cite web
 
| url        = https://tools.ietf.org/html/code.txt
 
| url        = https://tools.ietf.org/html/code.txt
 
| title      = HTTP 404 handler for a directory of htmlized documents
 
| title      = HTTP 404 handler for a directory of htmlized documents
| accessdate  = November 2, 2009
+
| access-date = November 2, 2009
 
| date        = October 14, 2009
 
| date        = October 14, 2009
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
Line 384: Line 365:
 
| date        = May 2008
 
| date        = May 2008
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
| accessdate = November 2, 2009
+
| access-date = November 2, 2009
 
| doi        = 10.17487/RFC5000
 
| doi        = 10.17487/RFC5000
 
}}
 
}}
Line 400: Line 381:
 
| date        = April 1995
 
| date        = April 1995
 
| publisher  = [[Internet Engineering Task Force|IETF]]
 
| publisher  = [[Internet Engineering Task Force|IETF]]
| accessdate  = November 2, 2009
+
| access-date = November 2, 2009
 
| doi        = 10.17487/RFC1796
 
| doi        = 10.17487/RFC1796
 
}}
 
}}
Line 406: Line 387:
 
| url        = http://www.livinginternet.com/i/ia_rfc_ref.htm
 
| url        = http://www.livinginternet.com/i/ia_rfc_ref.htm
 
| title      = Related RFC's, BCP, FYI, IEN, RTR, STD
 
| title      = Related RFC's, BCP, FYI, IEN, RTR, STD
| accessdate  =November 2, 2009
+
| access-date = November 2, 2009
 
| last        = Stewart
 
| last        = Stewart
 
| first      = William
 
| first      = William
Line 416: Line 397:
 
{{UF-COinS}}
 
{{UF-COinS}}
  
<includeonly>{{#ifeq:{{SUBPAGENAME}}|sandbox |
+
<includeonly>{{Sandbox other|
 
| <!-- CATEGORIES BELOW THIS LINE, PLEASE: -->
 
| <!-- CATEGORIES BELOW THIS LINE, PLEASE: -->
 
[[Category:Citation Style 1 specific-source templates]]
 
[[Category:Citation Style 1 specific-source templates]]
 
[[Category:Specific-source templates]]
 
[[Category:Specific-source templates]]
 
[[Category:Templates generating COinS]]
 
[[Category:Templates generating COinS]]
 +
[[Category:Computer networking templates]]
 
}}</includeonly>
 
}}</includeonly>

Latest revision as of 20:26, 30 August 2020

This is a template to cite IETF documents[1][2] including:

Usage

This template supports most of the parameters available to {{citation}}. For information about those parameters see that template's documentation.

Note: All parameter names must be in lowercase.

cite IETF specific parameters

  • |appendix= – Appendix number of the document. |appendix=A.1 produces "sec. A.1" Also used to create an anchor link for the document's URL.
  • |autolink=|autolink=yes or |autolink=no Automatically generate a link to ietf.org for documents specified with |rfc=, |std=, |bcp=, |fyi=, |draft=, |ien=, or |rtr=. (enabled by default)
  • |bcp= – Number of the Best Current Practice (BCP) document. Also used to automatically generate a link to ietf.org.
  • |draft= – Name of the Internet Draft (I-D) document, including the leading draft-. Also used to automatically generate a link to ietf.org.
  • |fyi= – Number of the For Your Information (FYI) document. Also used to automatically generate a link to ietf.org.
  • |idanchor= – Anchor link target. By default, no anchor link is generated. The special value |idanchor=ietf generates an anchor link suitable for use with this template's ref parameter. Requires one of id, rfc, std, bcp, fyi, draft, ien or rtr fields to be present for the anchor link text.
  • |idlink= – Internal document anchor or title of a Wikipedia article to link via the document identifier. Article should already exist. Must not be wikilinked itself. Do not use this on its own, but along with id, rfc, std, bcp, fyi, draft, ien or rtr.
  • |idlinktype= – One of the values: id, rfc, std, bcp, fyi, draft, ien or rtr can be given to idlinktype to force the template to use the specified document identifier as the link text for idanchor or idlink. Do not use this on its own, but along with idanchor or idlink and id, rfc, std, bcp, fyi, draft, ien or rtr.
  • |ien= – Number of the Internet Experiment Note (IEN) document. Also used to automatically generate a link to ietf.org.
  • |nosec= – Using section, 'sections, or appendix automatically places the sec. notation. Se |nosec=y to hide the sec. notation.
  • |referenceid= – Reference id for the document. Used to create an anchor link for the document's URL.
  • |rfc= – Number of the Request for Comments (RFC) document. Also used to automatically generate a link to ietf.org.
  • |rtr= – Number of the RARE Technical Reports (RTR) document. Also used to automatically generate a link to ietf.org.
  • |section= – Section number of the document. |section=4.3.1 produces "sec. 4.3.1" Also used to create an anchor link for the document's URL. Can also be used in combination with sections to link to the first section in the given section range.
  • |sections= – Section range of the document. |sections=4.3-4.7 produces "sec. 4.3-4.7"
  • |sectionname= – The section name or section title of the document, written in full; displays before title and enclosed in quotes.
  • |std= – Number of the Internet Standard (STD) document. Also used to automatically generate a link to ietf.org.

As with all cs1|2 templates, |title= is required. If omitted, the template will attempt to auto-generate a title using the first of rfc, std, bcp, fyi, draft, ien, rtr or id document identifier parameters, in that order.

Copy a blank version to use. Remember to use the "|" (pipe) character between each parameter. Please delete any unused parameters to avoid clutter in the edit window.

Full version (copy and paste text below and delete parameters you don't need)
{{cite IETF |title= |rfc= |std= |bcp= |fyi= |draft= |ien= |rtr= |sectionname= |section= |sections= |appendix= |referenceid= |page= |pages= |last1= |first1= |authorlink1= |last2= |first2= |authorlink2= |authormask= |editor1-last= |editor1-first= |editor1-link= |others= |date= |year= |orig-year= |publisher=[[Internet Engineering Task Force|IETF]] |location= |language= |format= |access-date= |url= |section-url= |page-url= |autolink= |id= |idanchor= |idlink= |idlinktype= |doi= |doi-broken-date= |issn= |archive-url= |archive-date= |quote= |nopp= |nosec= |ref= |lay-summary= |lay-date= |postscript= |last-author-amp=}}
Most commonly used parameters (use this and you won't have to delete as much)
{{cite IETF |title= |rfc= |sectionname= |section= |page= |last= |first= |author-link= |date= |publisher=[[Internet Engineering Task Force|IETF]] |access-date= |doi=}}
Example 1

{{cite IETF |title=The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force |rfc=4677 |fyi=17 |last1=Hoffman |first1=P. |authorlink1=Paul Hoffman (VPNC) |last2=Harris |first2=S. |date=September 2006 |publisher=[[Internet Engineering Task Force|IETF]] |access-date=October 20, 2009 |doi=10.17487/RFC4677}}

Hoffman, P.; Harris, S. (September 2006). The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force. IETF. doi:10.17487/RFC4677. FYI 17. RFC 4677. Retrieved October 20, 2009.

Example 2
{{cite IETF
| title = Telnet protocol specification
| rfc = 854
| std = 8
| sectionname = Are You There (AYT)
| page = 8
| last1 = Postel
| first1 = J.
| author-link1 = Jon Postel
| last2 = Reynolds
| first2 = J.
| author-link2 = Joyce K. Reynolds
| date = May 1983
| publisher = [[Internet Engineering Task Force|IETF]]
| access-date = October 20, 2009
| doi = 10.17487/RFC0854
}}

Postel, J.; Reynolds, J. (May 1983). "Are You There (AYT)". Telnet protocol specification. IETF. p. 8. doi:10.17487/RFC0854. STD 8. RFC 854. Retrieved October 20, 2009.

Examples

  • {{cite IETF | title = JSON | rfc = 7159 | sectionname = IANA Considerations | section = 11 | author = T. Bray | authorlink = Tim Bray | date = March 2014 | publisher = [[Internet Engineering Task Force|IETF]] | access-date = November 26, 2017 | doi = 10.17487/RFC7159 }}
    T. Bray (March 2014). "IANA Considerations". JSON. IETF. sec. 11. doi:10.17487/RFC7159. RFC 7159. Retrieved November 26, 2017.
  • {{cite IETF | title = Hypertext Transfer Protocol -- HTTP/1.1 | rfc = 2616 | first1 = R. | last1 = Fielding | authorlink1 = Roy Fielding | first2 = J. | last2 = Gettys | authorlink2 = Jim Gettys | first3 = J. | last3 = Mogul | first4 = H. | last4 = Frystyk | authorlink4 = Henrik Frystyk Nielsen | first5 = L. | last5 = Masinter | first6 = P. | last6 = Leach | first7 = T. | last7 = Berners-Lee | authorlink7 = Tim Berners-Lee |date=June 1999 | publisher = [[Internet Engineering Task Force|IETF]] | doi = 10.17487/RFC2616 }}
    Fielding, R.; Gettys, J.; Mogul, J.; Frystyk, H.; Masinter, L.; Leach, P.; Berners-Lee, T. (June 1999). Hypertext Transfer Protocol -- HTTP/1.1. IETF. doi:10.17487/RFC2616. RFC 2616.
  • {{cite IETF | title = Domain names - concepts and facilities | rfc = 1034 | sectionname = Name space specifications and terminology | section = 3.1 | author = P. Mockapetris | authorlink = Paul Mockapetris |date=November 1987 | publisher = [[Internet Engineering Task Force|IETF]] | access-date = August 3, 2008 | doi = 10.17487/RFC1034 | quote = A domain is a subdomain of another domain if it is contained within that domain. This relationship can be tested by seeing if the subdomain's name ends with the containing domain's name. For example, A.B.C.D is a subdomain of B.C.D, C.D, D, and ' '. }}
    P. Mockapetris (November 1987). "Name space specifications and terminology". Domain names - concepts and facilities. IETF. sec. 3.1. doi:10.17487/RFC1034. RFC 1034. Retrieved August 3, 2008. A domain is a subdomain of another domain if it is contained within that domain. This relationship can be tested by seeing if the subdomain's name ends with the containing domain's name. For example, A.B.C.D is a subdomain of B.C.D, C.D, D, and ' '.

Technical notes

Regression testing

Regression tests are available here:

Subtemplates

{{Cite IETF}} uses the following subtemplates:

URL generation

HTML versions of the IETF documents are created with the Rfcmarkup tool from Henrik Levkowetz.[10][11]

Request for Comments (RFC), Best Current Practice (BCP), and Internet Draft (I-D) documents which have been processed by the Rfcmarkup tool are cached by https://tools.ietf.org/html/[12][13] and are linked via:

https://tools.ietf.org/html/rfc<document number>
https://tools.ietf.org/html/bcp<document number>
https://tools.ietf.org/html/draft-<draft name>

Internet Standard (STD) and For Your Information (FYI) documents are linked via the Rfcmarkup tool using the doc= parameter:

https://tools.ietf.org/rfcmarkup?doc=std<document number>
https://tools.ietf.org/rfcmarkup?doc=fyi<document number>

Internet Experiment Note (IEN) and RARE Technical Reports (RTR) documents are linked via the Rfcmarkup tool using the url= parameter and a path to the document:

https://tools.ietf.org/rfcmarkup?url=ftp://ftp.rfc-editor.org/in-notes/ien/ien<document number>.txt
https://tools.ietf.org/rfcmarkup?url=ftp://ftp.rfc-editor.org/in-notes/museum/RAREreports/rtr<document number>.txt

URL anchor generation

Anchors are generated for the URL using four parameters:

|section=number generates #section-<number>
|appendix=number generates #appendix-<number>
|referenceid=id generates #ref-<id>
|page=number generates #page-<number>

The template will give priority to the first of the parameters: |section=, |appendix=, |referenceid=, or |page= in this order and create an anchor using the first matching parameter.

References

  1. Hoffman, Paul; Harris, Susan (September 2006). The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force. IETF. doi:10.17487/RFC4677. FYI 17. RFC 4677. Retrieved November 2, 2009.
  2. Kessler, Gary C.; Shepard, Steven D. (December 1994). "Internet Documentation". A Primer On Internet and TCP/IP Tools. IETF. sec. 4. doi:10.17487/RFC1739. RFC 1739. Retrieved November 2, 2009.
  3. "Request for Comments (RFCs)". A Primer On Internet and TCP/IP Tools. pp. 36–38. sec. 4.1. doi:10.17487/RFC1739. RFC 1739.
  4. Bradner, Scott O. (October 1996). The Internet Standards Process -- Revision 3. IETF. doi:10.17487/RFC2026. BCP 9. RFC 2026. Retrieved November 2, 2009.
  5. "Internet Standards". A Primer On Internet and TCP/IP Tools. pp. 38–39. sec. 4.2. doi:10.17487/RFC1739. RFC 1739.
  6. Postel, Jon; Rekhter, Yakov; Li, Tony (August 1995). Best Current Practices. IETF. doi:10.17487/RFC1818. BCP 1. RFC 1818. Retrieved November 2, 2009.
  7. Malkin, Gary Scott; Reynolds, Joyce K. (March 1990). F.Y.I. on F.Y.I.: Introduction to the F.Y.I. Notes. IETF. doi:10.17487/RFC1150. FYI 1. RFC 1150. Retrieved November 2, 2009.
  8. "For Your Information Documents". A Primer On Internet and TCP/IP Tools. p. 39. sec. 4.3. doi:10.17487/RFC1739. RFC 1739.
  9. "RARE Technical Reports". A Primer On Internet and TCP/IP Tools. p. 40. sec. 4.4. doi:10.17487/RFC1739. RFC 1739.
  10. Levkowetz, Henrik (March 7, 2017). "Rfcmarkup Tool". IETF. Retrieved November 26, 2017.
  11. Levkowetz, Henrik (July 13, 2016). "rfcmarkup-1.121.tgz (29.7 KB)". IETF. Retrieved November 26, 2017.
  12. "IETF Documents". IETF. Retrieved November 2, 2009.
  13. "HTTP 404 handler for a directory of htmlized documents". IETF. October 14, 2009. Retrieved November 2, 2009.

Further reading

This template produces COinS metadata; see COinS in Wikipedia for background information.