Template:Ref RFC/doc

Usage
Template Ref RFC is used to create references to IETF RFCs, generated from a repository of preformatted references. This way, all references are of high quality, with a minimal chance of errors, and you don't have to create each reference from scratch. You are explicitly invited to add new references or improve existing ones.

It uses templates Cite IETF and Rp to generate the reference itself.

Examples
The examples below generate a single full reference in the Reflist and can be referenced in the text many times.
 * yields a full reference:.
 * gives you an empty reference: . Make sure the full reference is created elsewhere. When using Ref RFC exclusively, references are generated automatically (thus having equal content everywhere). Specifying   is not necessary in that case, but may be helpful when the full reference was created by other means.
 * yields a reference with an inline page number: . The reference itself contains no page number. You can add another reference to the same RFC with inline page numbers, e.g. , without adding a new full reference in the list.
 * yields a reference to RFC 8200 without notes specifying which other RFC are affected by or are affecting this RFC. It is not possible to add the same reference with notes later.

References with section or page numbers or a quote are generated with an anonymous  pair, to create individual full references in the Reflist.
 * yields a reference to RFC 8201 with a section.
 * yields another reference to RFC 8201, now with page numbers and a quote.
 * yields another reference to RFC 8201, now with a section and a page number.

In some cases, you want the full reference, but not within tags:
 * which gives you:

Template data
{	"description": "Template is used to create references to RFCs. It uses a repository of preformatted reference texts.", "params": { "1": {			"description": "The number of the RFC to reference.", "example": "8200", "type": "string", "label": "RFC Number", "suggested": true },		"notes": { "description": "Display notes regarding the RFC or not (default: 'yes'). If set to 'no', no notes are displayed.", "example": "notes=no", "type": "string", "label": "Notes" },		"ref": { "description": "If set to 'no', no is generated, just the reference itself.", "example": "ref=no", "type": "string", "label": "Ref" },		"repeat": { "description": "This reference is a repeat of an earlier one. If set to 'yes', no new reference is created, just an empty one.", "example": "repeat=yes", "type": "string", "label": "Repeat" },		"rp": { "description": "Page number alongside the reference itself. Uses .", "type": "string", "example": "rp=37", "label": "Page number" },		"rpp": { "description": "Page numbers alongside the reference itself. Uses .", "type": "string", "example": "rpp=13-15", "label": "Page numbers" },		"p": { "description": "Page number to reference.", "type": "string", "example": "p=37", "label": "Page number" },		"pp": { "description": "Page numbers to reference.", "type": "string", "example": "pp=37,116-19", "label": "Page numbers" },		"quote": { "description": "A quote from the RFC.", "type": "string", "example": "quote=Nodes not implementing Path MTU Discovery must use the IPv6 minimum link MTU defined in [RFC8200] as the maximum packet size.", "label": "Quote" },		"section": { "description": "Section to reference. Displays as 'Sec'.", "type": "string", "example": "section=4.3", "label": "Section" }	},	"format": "inline" }