Home › Entities › request_for_comments › RFC 454: File Transfer Protocol - meeting announcement and a new proposed document

RFC 454: File Transfer Protocol - meeting announcement and a new proposed document

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

RFC 454: File Transfer Protocol - meeting announcement and a new proposed document

Summary

RFC 454: File Transfer Protocol - meeting announcement and a new proposed document is a Request for Comments[1].

Key Facts

  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document authored File Transfer Protocol - meeting announcement and a new proposed document — author (P50): Alex McKenzie[2].
  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's instance of is recorded as File Transfer Protocol - meeting announcement and a new proposed document — instance of (P31): Request for Comments[3].
  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's publisher is recorded as File Transfer Protocol - meeting announcement and a new proposed document — publisher (P123): Internet Engineering Task Force[4].
  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's based on is recorded as File Transfer Protocol - meeting announcement and a new proposed document — based on (P144): RFC 354: File Transfer Protocol[5].
  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's DOI is recorded as 10.17487/RFC0454[6].
  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's language of work or name is recorded as File Transfer Protocol - meeting announcement and a new proposed document — language of work or name (P407): English[7].
  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's publication date is recorded as +1973-02-01T00:00:00Z[8].
  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's RfC ID is recorded as 454[9].
  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's work available at URL is recorded as https://tools.ietf.org/html/rfc454[10].
  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's work available at URL is recorded as https://tools.ietf.org/rfc/rfc454.txt[11].
  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc454.txt[12].
  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc454.txt.pdf[13].
  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's number of pages is recorded as {'unit': '1', 'amount': '+35'}[14].
  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's title is recorded as File Transfer Protocol - meeting announcement and a new proposed document[15].
  • RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's DBLP publication ID is recorded as journals/rfc/rfc454[16].

Body

Designation and Status

RFC 454: File Transfer Protocol - meeting announcement and a new proposed document's instance of is recorded as File Transfer Protocol - meeting announcement and a new proposed document — 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] ↑ . 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 454: File Transfer Protocol - meeting announcement and a new proposed document. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-454-file-transfer-protocol-meeting-announcement-and-a-new-proposed-document
MLA “RFC 454: File Transfer Protocol - meeting announcement and a new proposed document.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-454-file-transfer-protocol-meeting-announcement-and-a-new-proposed-document.
BibTeX @misc{4ortxyz_rfc-454-file-transfer-protocol-meeting-announcement-and-a-new-proposed-document_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 454: File Transfer Protocol - meeting announcement and a new proposed document}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-454-file-transfer-protocol-meeting-announcement-and-a-new-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 454: File Transfer Protocol - meeting announcement and a new proposed document — https://4ort.xyz/entity/rfc-454-file-transfer-protocol-meeting-announcement-and-a-new-proposed-document (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-454-file-transfer-protocol-meeting-announcement-and-a-new-proposed-document · Last refreshed: