Home › Entities › request_for_comments › RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status

RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status

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

RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status

Summary

RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status is a Request for Comments[1].

Key Facts

  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status authored Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — author (P50): Lars René Eggert[2].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's instance of is recorded as Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — instance of (P31): Request for Comments[3].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's publisher is recorded as Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — publisher (P123): Internet Engineering Task Force[4].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's based on is recorded as Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — based on (P144): RFC 4614: A Roadmap for Transmission Control Protocol (TCP) Specification Documents[5].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's DOI is recorded as 10.17487/RFC6247[6].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's language of work or name is recorded as Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — language of work or name (P407): English[7].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's publication date is recorded as +2011-05-01T00:00:00Z[8].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's RfC ID is recorded as 6247[9].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's work available at URL is recorded as https://tools.ietf.org/html/rfc6247[10].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's work available at URL is recorded as https://tools.ietf.org/rfc/rfc6247.txt[11].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc6247.txt[12].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc6247.txt.pdf[13].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's number of pages is recorded as {'unit': '1', 'amount': '+4'}[14].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's replaces is recorded as Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — replaces (P1365): RFC 1072: TCP extensions for long-delay paths[15].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's replaces is recorded as Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — replaces (P1365): RFC 1106: TCP big window and NAK options[16].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's replaces is recorded as Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — replaces (P1365): RFC 1110: Problem with the TCP big window option[17].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's replaces is recorded as Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — replaces (P1365): RFC 1145: TCP alternate checksum options[18].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's replaces is recorded as Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — replaces (P1365): RFC 1146: TCP alternate checksum options[19].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's replaces is recorded as Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — replaces (P1365): RFC 1379: Extending TCP for Transactions -- Concepts[20].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's replaces is recorded as Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — replaces (P1365): RFC 1644: T/TCP -- TCP Extensions for Transactions Functional Specification[21].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's replaces is recorded as Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — replaces (P1365): RFC 1693: An Extension to TCP : Partial Order Service[22].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's title is recorded as Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status[23].
  • RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's DBLP publication ID is recorded as journals/rfc/rfc6247[24].

Body

Designation and Status

RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status's instance of is recorded as Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — instance of (P31): Request for Comments[3].

References

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

Direct Wikidata claims

  1. [3] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [2] ↑ . RFC Index. Retrieved . wikidata.org.
  3. [4] ↑ . 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] ↑ . RFC Index. Retrieved . 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] ↑ . RFC Index. Retrieved . wikidata.org.
  20. [21] ↑ . RFC Index. Retrieved . wikidata.org.
  21. [22] ↑ . RFC Index. Retrieved . wikidata.org.
  22. [23] ↑ . RFC Index. Retrieved . wikidata.org.
  23. [24] ↑ . 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 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-6247-moving-the-undeployed-tcp-extensions-rfc-1072-rfc-1106-rfc-1110-rfc-1145-rfc-1146-rfc-1379-rfc-1644-and-rfc-1693-to-historic-status
MLA “RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-6247-moving-the-undeployed-tcp-extensions-rfc-1072-rfc-1106-rfc-1110-rfc-1145-rfc-1146-rfc-1379-rfc-1644-and-rfc-1693-to-historic-status.
BibTeX @misc{4ortxyz_rfc-6247-moving-the-undeployed-tcp-extensions-rfc-1072-rfc-1106-rfc-1110-rfc-1145-rfc-1146-rfc-1379-rfc-1644-and-rfc-1693-to-historic-status_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-6247-moving-the-undeployed-tcp-extensions-rfc-1072-rfc-1106-rfc-1110-rfc-1145-rfc-1146-rfc-1379-rfc-1644-and-rfc-1693-to-historic-status}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 6247: Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status — https://4ort.xyz/entity/rfc-6247-moving-the-undeployed-tcp-extensions-rfc-1072-rfc-1106-rfc-1110-rfc-1145-rfc-1146-rfc-1379-rfc-1644-and-rfc-1693-to-historic-status (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-6247-moving-the-undeployed-tcp-extensions-rfc-1072-rfc-1106-rfc-1110-rfc-1145-rfc-1146-rfc-1379-rfc-1644-and-rfc-1693-to-historic-status · Last refreshed: