Home › Entities › request_for_comments › RFC 6918: Formally Deprecating Some ICMPv4 Message Types

RFC 6918: Formally Deprecating Some ICMPv4 Message Types

request for comments publication
Place request_for_comments Q47466518
Press Enter · cited answer in seconds

RFC 6918: Formally Deprecating Some ICMPv4 Message Types

Summary

RFC 6918: Formally Deprecating Some ICMPv4 Message Types is a Request for Comments[1].

Key Facts

  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types authored Formally Deprecating Some ICMPv4 Message Types — author (P50): Carlos Pignataro[2].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types authored Formally Deprecating Some ICMPv4 Message Types — author (P50): Fernando Gont[3].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's instance of is recorded as Formally Deprecating Some ICMPv4 Message Types — instance of (P31): Request for Comments[4].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's publisher is recorded as Formally Deprecating Some ICMPv4 Message Types — publisher (P123): Internet Engineering Task Force[5].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's based on is recorded as Formally Deprecating Some ICMPv4 Message Types — based on (P144): RFC 792: Internet Control Message Protocol[6].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's based on is recorded as Formally Deprecating Some ICMPv4 Message Types — based on (P144): RFC 950: Internet Standard Subnetting Procedure[7].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's DOI is recorded as 10.17487/RFC6918[8].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's language of work or name is recorded as Formally Deprecating Some ICMPv4 Message Types — language of work or name (P407): English[9].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's publication date is recorded as +2013-04-01T00:00:00Z[10].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's RfC ID is recorded as 6918[11].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's main subject is recorded as Formally Deprecating Some ICMPv4 Message Types — main subject (P921): Internet Control Message Protocol[12].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's work available at URL is recorded as https://tools.ietf.org/html/rfc6918[13].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's work available at URL is recorded as https://tools.ietf.org/rfc/rfc6918.txt[14].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc6918.txt[15].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc6918.txt.pdf[16].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's number of pages is recorded as {'unit': '1', 'amount': '+8'}[17].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's replaces is recorded as Formally Deprecating Some ICMPv4 Message Types — replaces (P1365): RFC 1788: ICMP Domain Name Messages[18].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's title is recorded as Formally Deprecating Some ICMPv4 Message Types[19].
  • RFC 6918: Formally Deprecating Some ICMPv4 Message Types's DBLP publication ID is recorded as journals/rfc/rfc6918[20].

Body

Designation and Status

RFC 6918: Formally Deprecating Some ICMPv4 Message Types's instance of is recorded as Formally Deprecating Some ICMPv4 Message Types — instance of (P31): Request for Comments[4].

References

Programmatic citations — every numbered marker resolves to a verifiable graph row below.

Direct Wikidata claims

  1. [4] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [2] ↑ . RFC Index. Retrieved . wikidata.org.
  3. [3] ↑ . RFC Index. Retrieved . wikidata.org.
  4. [5] ↑ . RFC Index. Retrieved . wikidata.org.
  5. [6] ↑ . RFC Index. Retrieved . wikidata.org.
  6. [7] ↑ . RFC Index. Retrieved . wikidata.org.
  7. [8] ↑ . RFC Index. Retrieved . wikidata.org.
  8. [9] ↑ . RFC Index. Retrieved . wikidata.org.
  9. [10] ↑ . RFC Index. Retrieved . wikidata.org.
  10. [11] ↑ . RFC Index. Retrieved . wikidata.org.
  11. [12] ↑ . wikidata.org.
  12. [13] ↑ . RFC Index. Retrieved . wikidata.org.
  13. [14] ↑ . RFC Index. Retrieved . wikidata.org.
  14. [15] ↑ . RFC Index. Retrieved . wikidata.org.
  15. [16] ↑ . RFC Index. Retrieved . wikidata.org.
  16. [17] ↑ . RFC Index. Retrieved . wikidata.org.
  17. [18] ↑ . RFC Index. Retrieved . wikidata.org.
  18. [19] ↑ . RFC Index. Retrieved . wikidata.org.
  19. [20] ↑ . DBLP Dataset 2021-01-02. Retrieved . wikidata.org.

Class ancestry

  1. [1] ↑ . Wikidata. wikidata.org.

📑 Cite this page

Use these citations when quoting this entity in research, articles, AI prompts, or wherever provenance matters. We aggregate Wikidata + Wikipedia + authoritative open-data sources; the stitched, scored, cross-referenced view is what 4ort.xyz contributes.

APA 4ort.xyz Knowledge Graph. (2026). RFC 6918: Formally Deprecating Some ICMPv4 Message Types. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-6918-formally-deprecating-some-icmpv4-message-types
MLA “RFC 6918: Formally Deprecating Some ICMPv4 Message Types.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-6918-formally-deprecating-some-icmpv4-message-types.
BibTeX @misc{4ortxyz_rfc-6918-formally-deprecating-some-icmpv4-message-types_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 6918: Formally Deprecating Some ICMPv4 Message Types}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-6918-formally-deprecating-some-icmpv4-message-types}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 6918: Formally Deprecating Some ICMPv4 Message Types — https://4ort.xyz/entity/rfc-6918-formally-deprecating-some-icmpv4-message-types (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-6918-formally-deprecating-some-icmpv4-message-types · Last refreshed: