Template:Infobox_networking_protocol
Template:Infobox networking protocol
| Communication protocol | |
| Abbreviation | {{{abbreviation}}} |
|---|---|
| Purpose | {{{purpose}}} |
| Developer(s) | {{{developer}}} |
| Introduction | {{{date}}} |
| Based on | {{{based on}}} |
| Influenced | {{{influenced}}} |
| OSI layer | {{{osilayer}}} |
| Port(s) | {{{ports}}} |
| RFC(s) | {{{rfcs}}} |
| Hardware | {{{hardware}}} |
| Website | {{{website}}} |
Usage
You can copy and paste the following empty skeleton template into the article and fill it in as you see fit, in case you wish to use source editor instead of VisualEditor. |logo caption= is deliberately omitted to discourage the use of this oft-abused parameter.
| Communication protocol | |
| [[File:{{{logo}}}|{{{logo size}}}|alt={{{logo alt}}}]] {{{logo caption}}} | |
| [[File:{{{image}}}|{{{image size}}}|alt={{{image alt}}}]] {{{caption}}} | |
| Purpose | {{{purpose}}} |
|---|---|
| Developer(s) | {{{developer}}} |
| Introduction | {{{date}}} |
| Based on | {{{based on}}} |
| Influenced | {{{influenced}}} |
| OSI layer | {{{osilayer}}} |
| Port(s) | {{{ports}}} |
| RFC(s) | {{{rfcs}}} |
| Hardware | {{{hardware}}} |
{{Infobox networking protocol
| title =
| logo =
| logo alt =
| image =
| image alt =
| caption =
| is stack =
| abbreviation =
| purpose =
| developer =
| date = {{Start date and age| | | }}<!--Fill in: Year (4 digits), month and day (2 digits)-->
| based on =
| influenced =
| osilayer =
| ports =
| rfcs =
| hardware =
}}
Syntax
TemplateData for Infobox networking protocol
| Parameter | Description | Type | Status | |
|---|---|---|---|---|
| Title or name | title name | Title or name of the subject of infobox focus. | String | required |
| Is stack? | is stack | If set to "yes" specifies whether the article is about a protocol stack, instead of a communications protocol
| Boolean | optional |
| Logo | logo | Name of the image pertaining the logo of the protocol or suite. A file name is enough.
| File | optional |
| Logo size | logo size | Size of the logo. Number and a CSS unit of measurement is accepted. e.g. 250px, x64px or 250x64px. | String | optional |
| Logo's alternative text | logo alt | Alternative text in case the logo cannot be displayed by the target web browser or cannot be seen by the target user. | String | optional |
| Logo's caption text | logo caption | A text caption to be displayed under the logo. Use of this field is discouraged, unless there is something of monumental importance to be said. Deletion notification templates go here as well. | Unbalanced wikitext | optional |
| Image | image | Name of an image pertaining the protocol or suite, such as a diagram. A file name is enough. Use only when absolutely necessary. | File | optional |
| Image size | image size | Size of the image. Number and a CSS unit of measurement is accepted. e.g. 250px, x64px or 250x64px. Defaults to 300px. Use only when absolutely necessary and try to keep it with in the vicinity of 300 pixels in width. Smaller images are hard to see and larger images resize the infobox. | String | optional |
| Image's alternative text | image alt | Alternative text in case the image cannot be displayed by the target web browser or cannot be seen by the target user. | String | optional |
| Image caption | caption | Caption text for the image. Must be present when the image is present. | String | optional |
| Purpose | purpose | A short sentence explaining the purpose of the protocol or stack succinctly. Use only when absolutely needed. | String | optional |
| Developer(s) | developer | Names of entities who developed the protocol or worked in concert with the developers for publicizing the protocol. | String | optional |
| Introduction date | date | The date in which the protocol is introduced. Use {{start date and age}} template. | String | optional |
| Based on | based on | Names of protocols, standards or specification from which the protocol in question is derived. | String | optional |
| Influenced | influenced | Name of protocols that derive from this protocol | String | optional |
| RFC(s) | rfcs | RFC(s) describing this protocol | String | optional |
| Port(s) | ports | TCP/UDP ports if used by the protocol | String | optional |
| OSI layer | osilayer | OSI layer this protocol works in | String | optional |
| Associated hardware | hardware | Name of the hardware created specifically to work with this protocol. | String | optional |
This infobox helps display important preliminary details about a protocol in an article.
Example
| Communication protocol | |
| Purpose | Allows clients to perform remote Web content authoring operations |
|---|---|
| Developer(s) | Jim Whitehead, Internet Engineering Task Force (IETF) |
| Introduction | 1996; 28 years ago (1996) |
| Based on | Hypertext Transfer Protocol (HTTP) |
| Influenced | Delta-V, CalDAV, GroupDAV |
| OSI layer | Application layer |
| Port(s) | 80, 443 |
| RFC(s) | RFC 2518, RFC 4918 |
{{Infobox networking protocol
| title = WebDAV
| is stack = no
| purpose = Allows clients to perform remote Web content authoring operations
| developer = [[Jim Whitehead]], [[Internet Engineering Task Force]] (IETF)
| date = {{Start date and age|1996}}
| based on = [[Hypertext Transfer Protocol]] (HTTP)
| influenced = [[Delta-V]], [[CalDAV]], GroupDAV
| osilayer = [[Application layer]]
| ports = 80, 443
| rfcs = RFC 2518, RFC 4918
}}
See also
Editors can experiment in this template's sandbox (edit | diff) and testcases (edit) pages.
Add categories to the /doc subpage. Subpages of this template.