Template:Cite IETF

From Wikipedia, the free encyclopedia
Jump to: navigation, search

.

Documentation icon Template documentation[view] [edit] [history] [purge]

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

Usage[edit]

Note: All parameter names must be in lowercase.

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= |coauthors= |editor1-last= |editor1-first= |editor1-link= |others= |date= |year= |month= |origyear= |publisher=[[Internet Engineering Task Force|IETF]] |location= |language= |format= |accessdate= |url= |section-url= |page-url= |autolink= |id= |idanchor= |idlink= |idlinktype= |doi= |doi_brokendate= |issn= |archiveurl= |archivedate= |quote= |nopp= |nosec= |ref= |laysummary= |laydate= |separator= |postscript= |lastauthoramp= }}
Most commonly used parameters (use this and you won't have to delete as much)
{{cite IETF |title= |rfc= |sectionname= |section= |page= |last= |first= |authorlink= |coauthors= |year= |month= |publisher=[[Internet Engineering Task Force|IETF]] |accessdate= }}
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. |year= 2006 |month= September |publisher=[[Internet Engineering Task Force|IETF]] |accessdate=October 20, 2009}}

Hoffman, P.; Harris, S. (September 2006). The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force. IETF. FYI 17. RFC 4677. https://tools.ietf.org/html/rfc4677. 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.
| authorlink1 = Jon Postel
| last2 = Reynolds
| first2 = J.
| authorlink2 = Joyce K. Reynolds
| year = 1983
| month = May
| publisher = [[Internet Engineering Task Force|IETF]]
| accessdate =October 20, 2009
}}

Postel, J.; Reynolds, J. (May 1983). "Are You There (AYT)". Telnet protocol specification. IETF. p. 8. STD 8. RFC 854. https://tools.ietf.org/html/rfc854#page-8. Retrieved October 20, 2009.

Vertical list Prerequisites Brief instructions
{{cite IETF
| title       = 
| rfc         = 
| std         = 
| bcp         = 
| fyi         = 
| draft       = 
| ien         = 
| rtr         = 
| sectionname = 
| section     = 
| sections    = 
| appendix    = 
| referenceid = 
| page        = 
| pages       = 
| last        = 
| first       = 
| authorlink  = 
| authormask  = 
| coauthors   = 
| lastN       = 
| firstN      = 
| authorN-link = 
| editor      = 
| editorN     = 
| editorN-last = 
| editorN-first = 
| editor-link = 
| editorN-link = 
| others      = 
| date        = 
| year        = 
| month       = 
| origyear    = 
| publisher   = 
| location    = 
| language    = 
| format      = 
| accessdate  = 
| url         = 
| section-url = 
| page-url    = 
| autolink    = 
| id          = 
| idanchor    = 
| idlink      = 
| idlinktype  = 
| doi         = 
| doi_brokendate = 
| issn        = 
| archiveurl  = 
| archivedate = 
| quote       = 
| nopp        = 
| nosec       = 
| ref         = 
| laysummary  = 
| laydate     = 
| separator   = 
| postscript  = 
| lastauthoramp = 
}}
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
last
last
 
last
 
lastN
 
 
 
 
editorN-last
editor or editor-last
editorN or editorN-last
 
 
 
year
year or date
 
publisher
 
 
rfc, std, bcp, fyi, draft, ien, rtr, or url
 
sectionname
sectionname
rfc, std, bcp, fyi, draft, ien, rtr, or url
 
id, rfc, std, bcp, fyi, draft, ien, or rtr
id, rfc, std, bcp, fyi, draft, ien, or rtr
idanchor or idlink
 
doi
 
url, rfc, std, bcp, fyi, draft, ien, or rtr
archiveurl
 
page or pages
section, sections, or appendix
 
 
laysummary
 
 
coauthors or >1 lastN
 
 
(no wikilink) RFC number; 4677
(no wikilink) STD number
(no wikilink) BCP number
(no wikilink) FYI number; 17
(no wikilink) I-D (internet draft) name
(no wikilink) IEN number
(no wikilink) RTR number
 
(no wikilink) section number; 3.3
(no wikilink) section range (can be used together with the section parameter)
(no wikilink) appendix number; A.1
(no wikilink) reference id
(no wikilink) page number
(no wikilink) page range (can be used together with the page parameter)
 
(no wikilink)
(no wikilink)
 
 
alternative to first2, last2...first9, last9
(no wikilink) N=1 through 9
N=1 through 9
N=1 through 9
 
N=1 through 4
N=1 through 4
N=1 through 4
 
N=1 through 4
 
preferred (no wikilink) This is the preferred parameter with its alternates listed below.
alternative to date
 
 
should be [[Internet Engineering Task Force|IETF]] for IETF documents.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
hides automatic 'p.' or 'pp.'
hides automatic 'sec.'
 
 
 
 
 
 
 

Examples[edit]

  • {{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 | year = 1999 | month = June | publisher = [[Internet Engineering Task Force|IETF]] }}
    Fielding, R.; Gettys, J.; Mogul, J.; Frystyk, H.; Masinter, L.; Leach, P.; Berners-Lee, T. (June 1999). Hypertext Transfer Protocol -- HTTP/1.1. IETF. RFC 2616. https://tools.ietf.org/html/rfc2616.
  • {{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 | year = 1987 | month = November | publisher = [[Internet Engineering Task Force|IETF]] | accessdate =August 3, 2008 | 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. RFC 1034. https://tools.ietf.org/html/rfc1034#section-3.1. 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 ' '."

Parameters[edit]

Syntax[edit]

Nested parameters rely on their parent parameters:

  • parent
  • OR: parent2—may be used instead of parent
    • child—may be used with parent (and is ignored if parent is not used)
    • OR: child2—may be used instead of child (and is ignored if parent2 is not used)
Where aliases are listed, only one of the parameters may be defined; if multiple aliased parameters are defined, then only one will show.

This template embeds COinS metadata in the HTML output, allowing reference management software to retrieve bibliographic metadata. See: Wikipedia:COinS. As a general rule, only one data item per parameter. Do not include explanatory or alternate text:

  • Use |date=27 September 2007 not |date=27 September 2007 (print version 25 September)

Use of templates within the citation template, is generally discouraged as many of these templates will add a lot of extraneous HTML or CSS that will be rendered in the metadata. Also, HTML entities, for example  , –, etc, should not be used in parameters that contribute to the metadata.

COinS metadata is created for these parameters:

  • |periodical=, |journal=, |newspaper=, |magazine=, |work=, |website=, |encyclopedia=, |encyclopaedia=, |dictionary=
  • |chapter=, |contribution=, |entry=, |article=, |section=
  • |title=
  • |publicationplace=, |publication-place=
  • |date=, |year=, |publicationdate=, |publication-date=
  • |series=
  • |volume=
  • |issue=, |number=
  • |page=, |pages=, |at=
  • |edition=
  • |publisher=, |distributor=, |institution=
  • |url=
  • |chapterurl=, |chapter-url=, |contributionurl=, |contribution-url=, |sectionurl=
  • |author#=, |Author#=, |authors#=, |author#-last=, |author-last#=, |last#=, |surname#=
  • any of the identifiers (|isbn=, |issn=, |doi=, |pmc=, etc)

By default, sets of fields are terminated with a period (.). This can be an issue when the last field uses an abbreviation or initial that ends with a period, as then two periods will display (..). The only solution is to not include the last period in the value for the set of fields.

Description[edit]

Authors[edit]

  • last: Surname of author. Do not wikilink—use authorlink instead. Where the surname is usually written first—as in Chinese—or for corporate authors, simply use last to include the same format as the source. Aliases: last1, author, authors, author1.
    • first: Given or first names of author, including title(s); for example: Firstname Middlename or Firstname M. or Dr. Firstname M., Sr. Do not wikilink—use authorlink instead. Aliases: first1. Requires last; first name will not display if last is empty.
    • OR: for multiple authors, use last1, first1 through last9, first9 for up to nine authors. By default, if nine authors are defined, then only eight will show and "et al." will show in place of the last author. See the display parameters to change. Aliases: author1 through author9.
  • authorlink: Title of existing Wikipedia article about the author—not the author's website; do not wikilink. Aliases: authorlink1, author-link, author1-link, author1link.
  • OR: for multiple authors, use authorlink1 through authorlink9. Aliases: author1-link through author9-link.
  • others: To record other contributors to the work, such as Illustrated by John Smith or Translated by John Smith.
When using shortened footnotes or parenthetical referencing styles with templates, do not use multiple names in one field or else the anchor will not match the inline link.

Title[edit]

  • title: Title of the document; displays in italics. If 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.
Titles containing certain characters will display and link incorrectly unless those characters are encoded.
newline [ ] |
space [ ] |
  • sectionname: The section name or section title of the document, written in full; displays before title and enclosed in quotes.
  • language: The language the source is written in, if not English. Displays in parentheses with "in" before the language name. Use the full language name; do not use icons or templates.

Date[edit]

  • date: Date of source being referenced. Can be full date (day, month, and year) or partial date (month and year, year). Use same format as other publication dates in the citations.[date 1] Required when year is used to disambiguate {{sfn}} links to multiple-work citations by the same author in the same year.[more] Do not wikilink. Displays after the authors and is enclosed in parentheses. If there is no author, then displays after publisher.
  • OR:
    • year: Year of source being referenced. Required with some types of {{sfn}} citations;[more] otherwise use date.
    • month: Name of the month or season of publication. If you also have the day, use date instead. Do not wikilink.
  • origyear: Original publication year; displays after the date or year. For clarity, please supply specifics. For example: |origyear=First published 1859 or |origyear=Composed 1904.
  1. ^ Publication dates in references within an article should all have the same format. This may be a different format from that used for archive and access dates. See: MOS:DATEUNIFY.

Publisher[edit]

  • publisher: Name of publisher; may be wikilinked if relevant. Not normally included for periodicals. Corporate designations such as "Ltd", "Inc" or "GmbH" are not usually included. Displays after title.
Should normally be set to IETF for RFC, STD, BCP, FYI, I-D (internet draft), IEN, and RTR documents.
Note: There are reasons this can't just be the default; see Template talk:Cite IETF#Make publisher always IETF?
  • location: Geographical place of publication; generally not wikilinked; omit when the name of the work includes the location (examples: The Boston Globe, The Times of India). Displays preceding publisher.

In-source locations[edit]

  • page: Page in the source that supports the content. Displays preceded with p. unless |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 pp. unless |nopp=y.
    • nopp: Set to y to suppress the p. or pp. notations where this is inappropriate; for example, where |page=Front cover.
  • 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"
  • OR: 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.
  • 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 |nosec=y to hide the sec. notation.

URL[edit]

  • url: URL of an online location where the text of the publication can be found. Cannot be used if title is wikilinked. If applicable, the link may point to the specific page(s) referenced. Remove spurious tracking parameters from URLs, e.g. #ixzz2rBr3aO94 or ?utm_source=google&utm_medium=...&utm_term=...&utm_campaign=.... Do not link to any commercial booksellers, such as Amazon.com. See: WP:PAGELINKS.
    • accessdate: Full date when original URL was accessed; use the same format as other access and archive dates in the citations; requires url.[date 1] Do not wikilink. Not required for web pages or linked documents that do not change; mainly for use of web pages that change frequently or have no publication date. Can be hidden or styled by registered editors.
    • archiveurl: The URL of an archived copy of a web page, if or in case the url becomes unavailable. Typically used to refer to services like WebCite (see: Wikipedia:Using WebCite) and Internet Archive (see: Wikipedia:Using the Wayback Machine); requires archivedate and url.
      • archivedate: Date when the original URL was archived; preceded by default text "archived from the original on". Use the same format as other access and archive dates in the citations. This does not necessarily have to be the same format that was used for citing publication dates.[date 1] Do not wikilink.
      • deadurl: When the URL is still live, but pre-emptively archived, then set |deadurl=no. This changes the display order with the title retaining the original link and the archive linked at the end.
    • template doc demo: The archive parameters will be error checked to ensure that all the required parameters are included, or else {{citation error}} is invoked. With errors, main, help and template pages are placed into Category:Articles with incorrect citation syntax. Set |template doc demo=true to disable categorization; mainly used for documentation where the error is demonstrated.
  • format: Format of the work referred to by url; for example: PDF, DOC, or XLS; displayed in parentheses after title. HTML is implied and should not be specified. Does not change the external link icon. Note: External link icons do not include alt text; thus, they do not add format information for the visually impaired.
URLs must begin with a supported URI scheme. http:// and https:// will be supported by all browsers; however, ftp://, gopher://, irc://, ircs://, mailto: and news: will require a plug-in or an external application and should normally be avoided. IPv6 host-names are currently not supported.
If URLs in citation template parameters contain certain characters, then they will not display and link correctly. Those characters need to be percent-encoded. For example, a space must be replaced by %20. To encode the URL, replace the following characters with:
sp " ' < > [ ] { | }
 %20  %22  %27  %3c  %3e  %5b  %5d  %7b  %7c  %7d
Single apostrophes do not need to be encoded; however, unencoded multiples will be parsed as italic or bold markup. Single curly closing braces also do not need to be encoded; however, an unencoded pair will be parsed as the double closing braces for the template transclusion.
  1. ^ a b Accessdate and archivedate in references should all have the same format – either the format used for publication dates, or YYYY-MM-DD. See: MOS:DATEUNIFY.
  • 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 |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 |url=, if any.
  • 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)

Anchor[edit]

Identifiers[edit]

  • 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 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 |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.
  • doi: A digital object identifier for the document, such as 10.1038/news070508-7. The field must not be wikilinked as the template automatically creates a link.
    • doi_brokendate: The date that the DOI was determined to be broken
  • issn: International Standard Serial Number for the document; 8 characters; may be split into two groups of four using a hyphen. The field must not be wikilinked as the template automatically creates a link.

Quote[edit]

  • quote: Relevant text quoted from the source. Displays enclosed in quotes. When supplied, the citation terminator (a period by default) is suppressed, so the quote needs to include terminating punctuation.

Editors[edit]

  • editor-last: Surname of editor. Do not wikilink—use editor-link instead. Where the surname is usually written first—as in Chinese—or for corporate authors, simply use editor-last to include the same format as the source. Aliases: editor1-last, editor, editors.
    • editor-first: Given or first names of editor, including title(s); example: Firstname Middlename or Firstname M. or Dr. Firstname M., Sr. Do not wikilink—use editor-link instead. Aliases: editor1-first.
    • OR: for multiple editors, use editor1-last, editor1-first through editor4-last, editor4-first for up to four editors.
  • editor-link: Title of existing Wikipedia article about the editor—not the editor's website; do not wikilink. Aliases: editor1-link.
  • OR: for multiple editors, use editor1-link through editor4-link.
Display:
If authors: Authors are first, followed by the editors and the included work, then the main work.
If no authors: Editors appear before the included work; a single editor is followed by "ed."; multiple editors are followed by "eds."; more than three editors will be followed by "et al., eds."

Laysummary[edit]

  • laysummary: URL link to a non-technical summary or review of the source; the URL title is set to "Lay summary".
    • laysource: Name of the source of the laysummary. Displays in italics and preceded by an endash.
    • laydate: Date of the summary. Displays in parentheses.

Display options[edit]

  • author-mask: Replaces the name of the first author with em dashes or text. Set author-mask to a numeric value n to set the dash n em spaces wide; set author-mask to a text value to display the text without a trailing author separator; for example, "with". You must still include the values for all authors for metadata purposes. Primarily intended for use with bibliography styles where multiple works by a single author are listed sequentially. Do not use in a list generated by {{reflist}}, <references /> or similar as there is no control of the order in which references are displayed.
  • author-name-separator: Controls the separator between last and first names; defaults to a comma and space (, ); if the parameter is present, but blank, no separator punctuation will be used; a space must be encoded as &#32; do not use an asterisk (*), colon (:) or hash (#) as they will be interpreted as wikimarkup.
  • author-separator: Controls the separator between authors; defaults to a semicolon and space (; ); if the parameter is present, but blank, no separator punctuation will be used; a space must be encoded as &#32; do not use an asterisk (*), colon (:) or hash (#) as they will be interpreted as wikimarkup.
  • display-authors: Controls the number of author names that are displayed when a citation is published. To control the displayed number of author names, set display-authors to the desired number. For example, |display-authors=2 will display only the first two authors in a citation. By default, the only the first eight cited authors are displayed; subsequent authors beyond eight are represented in the published citation by "et al." If a citation contains nine author names and one wishes all nine author names to display, "et al." may be suppressed by setting |display-authors=9. Aliases: displayauthors.
  • lastauthoramp: Switches the separator between the last two names of the author list to space ampersand space ( & ) when set to any value. Example: |lastauthoramp=yes
  • postscript: Controls the closing punctuation for a citation; defaults to a period (.); if the parameter is present, but blank, no terminating punctuation will be used. Ignored if quote is defined.
  • separator: Controls the punctuation used to separate lists of authors, editors, etc. Defaults to a period (.); if the parameter is present, but blank, no separator punctuation will be used; a space must be encoded as &#32; do not use an asterisk (*), colon (:) or hash (#) as they will be interpreted as wikimarkup.

Citation styles[edit]

Established citation styles for coauthors:

  • MLA style: Last, First and First Last. "If there are more than three authors, you may list only the first author followed by the phrase et al."
  • APA style: Last, F. & Last, F.
  • Chicago Manual of Style: Last, First, and First Last.
  • Turabian: same as Chicago Reference List, above.
  • Harvard: Last, F., Last, F. & Last, F.

Technical notes[edit]

Regression testing[edit]

Regression tests are available here:

Subtemplates[edit]

{{Cite IETF}} uses the following subtemplates:

URL generation[edit]

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

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 tools.ietf.org/html/[14][15] and are linked via:

http://tools.ietf.org/html/rfc<document number>
http://tools.ietf.org/html/bcp<document number>
http://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:

http://tools.ietf.org/rfcmarkup?doc=std<document number>
http://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:

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

URL anchor generation[edit]

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[edit]

  1. ^ Hoffman, Paul; Harris, Susan (September 2006). The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force. IETF. FYI 17. RFC 4677. https://tools.ietf.org/html/rfc4677. 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. RFC 1739. https://tools.ietf.org/html/rfc1739#section-4. Retrieved November 2, 2009.
  3. ^ "Request for Comments (RFCs)". pp. 36 – 38. sec. 4.1. RFC 1739. https://tools.ietf.org/html/rfc1739#section-4.1.
  4. ^ Bradner, Scott O. (October 1996). The Internet Standards Process -- Revision 3. IETF. BCP 9. RFC 2026. https://tools.ietf.org/html/rfc2026. Retrieved November 2, 2009.
  5. ^ "Internet Standards". pp. 38 – 39. sec. 4.2. RFC 1739. https://tools.ietf.org/html/rfc1739#section-4.2.
  6. ^ Postel, Jon; Rekhter, Yakov; Li, Tony (August 1995). Best Current Practices. IETF. BCP 1. RFC 1818. https://tools.ietf.org/html/rfc1818. 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. FYI 1. RFC 1150. https://tools.ietf.org/html/rfc1150. Retrieved November 2, 2009.
  8. ^ "For Your Information Documents". p. 39. sec. 4.3. RFC 1739. https://tools.ietf.org/html/rfc1739#section-4.3.
  9. ^ "RARE Technical Reports". p. 40. sec. 4.4. RFC 1739. https://tools.ietf.org/html/rfc1739#section-4.4.
  10. ^ Levkowetz, Henrik (October 16, 2009). "Rfcmarkup Tool". IETF. Retrieved November 2, 2009. 
  11. ^ Levkowetz, Henrik (October 16, 2009). "rfcmarkup-1.85.tgz (25 KB)". IETF. Retrieved November 2, 2009. 
  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[edit]

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