Home › Entities › request_for_comments › RFC 158: Telnet Protocol: A Proposed Document

RFC 158: Telnet Protocol: A Proposed Document

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

RFC 158: Telnet Protocol: A Proposed Document

Summary

RFC 158: Telnet Protocol: A Proposed Document is a Request for Comments[1].

Key Facts

  • RFC 158: Telnet Protocol: A Proposed Document's instance of is recorded as Telnet Protocol: A Proposed Document — instance of (P31): Request for Comments[2].
  • RFC 158: Telnet Protocol: A Proposed Document's publisher is recorded as Telnet Protocol: A Proposed Document — publisher (P123): Internet Engineering Task Force[3].
  • RFC 158: Telnet Protocol: A Proposed Document's based on is recorded as Telnet Protocol: A Proposed Document — based on (P144): RFC 139: Discussion of Telnet Protocol[4].
  • RFC 158: Telnet Protocol: A Proposed Document's DOI is recorded as 10.17487/RFC0158[5].
  • RFC 158: Telnet Protocol: A Proposed Document's language of work or name is recorded as Telnet Protocol: A Proposed Document — language of work or name (P407): English[6].
  • RFC 158: Telnet Protocol: A Proposed Document's publication date is recorded as +1971-05-01T00:00:00Z[7].
  • RFC 158: Telnet Protocol: A Proposed Document's RfC ID is recorded as 158[8].
  • RFC 158: Telnet Protocol: A Proposed Document's main subject is recorded as Telnet Protocol: A Proposed Document — main subject (P921): Telnet[9].
  • RFC 158: Telnet Protocol: A Proposed Document's work available at URL is recorded as https://tools.ietf.org/html/rfc158[10].
  • RFC 158: Telnet Protocol: A Proposed Document's work available at URL is recorded as https://tools.ietf.org/rfc/rfc158.txt[11].
  • RFC 158: Telnet Protocol: A Proposed Document's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc158.txt[12].
  • RFC 158: Telnet Protocol: A Proposed Document's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc158.txt.pdf[13].
  • RFC 158: Telnet Protocol: A Proposed Document's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc158.pdf[14].
  • RFC 158: Telnet Protocol: A Proposed Document's number of pages is recorded as {'unit': '1', 'amount': '+11'}[15].
  • RFC 158: Telnet Protocol: A Proposed Document's replaced by is recorded as Telnet Protocol: A Proposed Document — replaced by (P1366): RFC 495: Telnet Protocol specifications[16].
  • RFC 158: Telnet Protocol: A Proposed Document's title is recorded as Telnet Protocol: A Proposed Document[17].
  • RFC 158: Telnet Protocol: A Proposed Document's author name string is recorded as T.C. O'Sullivan[18].
  • RFC 158: Telnet Protocol: A Proposed Document's amended by is recorded as Telnet Protocol: A Proposed Document — amended by (P2567): RFC 318: Telnet Protocols[19].
  • RFC 158: Telnet Protocol: A Proposed Document's DBLP publication ID is recorded as journals/rfc/rfc158[20].

Body

Designation and Status

RFC 158: Telnet Protocol: A Proposed Document's instance of is recorded as Telnet Protocol: A Proposed Document — instance of (P31): Request for Comments[2].

References

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

Direct Wikidata claims

  1. [2] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [3] ↑ . 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] ↑ . 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] ↑ . 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 158: Telnet Protocol: A Proposed Document. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-158-telnet-protocol-a-proposed-document
MLA “RFC 158: Telnet Protocol: A Proposed Document.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-158-telnet-protocol-a-proposed-document.
BibTeX @misc{4ortxyz_rfc-158-telnet-protocol-a-proposed-document_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 158: Telnet Protocol: A Proposed Document}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-158-telnet-protocol-a-proposed-document}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 158: Telnet Protocol: A Proposed Document — https://4ort.xyz/entity/rfc-158-telnet-protocol-a-proposed-document (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-158-telnet-protocol-a-proposed-document · Last refreshed: