Home › Entities › request_for_comments › RFC 5966: DNS Transport over TCP - Implementation Requirements

RFC 5966: DNS Transport over TCP - Implementation Requirements

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

RFC 5966: DNS Transport over TCP - Implementation Requirements

Summary

RFC 5966: DNS Transport over TCP - Implementation Requirements is a Request for Comments[1].

Key Facts

  • RFC 5966: DNS Transport over TCP - Implementation Requirements's instance of is recorded as DNS Transport over TCP - Implementation Requirements — instance of (P31): Request for Comments[2].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's publisher is recorded as DNS Transport over TCP - Implementation Requirements — publisher (P123): Internet Engineering Task Force[3].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's based on is recorded as DNS Transport over TCP - Implementation Requirements — based on (P144): RFC 1035: Domain names - implementation and specification[4].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's based on is recorded as DNS Transport over TCP - Implementation Requirements — based on (P144): RFC 1123: Requirements for Internet Hosts - Application and Support[5].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's DOI is recorded as 10.17487/RFC5966[6].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's language of work or name is recorded as DNS Transport over TCP - Implementation Requirements — language of work or name (P407): English[7].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's publication date is recorded as +2010-08-01T00:00:00Z[8].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's RfC ID is recorded as 5966[9].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's main subject is recorded as DNS Transport over TCP - Implementation Requirements — main subject (P921): DNS over TCP[10].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's work available at URL is recorded as https://tools.ietf.org/html/rfc5966[11].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's work available at URL is recorded as https://tools.ietf.org/rfc/rfc5966.txt[12].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc5966.txt[13].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc5966.txt.pdf[14].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's number of pages is recorded as {'unit': '1', 'amount': '+7'}[15].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's replaced by is recorded as DNS Transport over TCP - Implementation Requirements — replaced by (P1366): RFC 7766: DNS Transport over TCP - Implementation Requirements[16].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's title is recorded as DNS Transport over TCP - Implementation Requirements[17].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's author name string is recorded as R. Bellis[18].
  • RFC 5966: DNS Transport over TCP - Implementation Requirements's DBLP publication ID is recorded as journals/rfc/rfc5966[19].

Body

Designation and Status

RFC 5966: DNS Transport over TCP - Implementation Requirements's instance of is recorded as DNS Transport over TCP - Implementation Requirements — 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] ↑ . RFC Index. Retrieved . wikidata.org.
  9. [10] ↑ . 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] ↑ . 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 5966: DNS Transport over TCP - Implementation Requirements. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-5966-dns-transport-over-tcp-implementation-requirements
MLA “RFC 5966: DNS Transport over TCP - Implementation Requirements.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-5966-dns-transport-over-tcp-implementation-requirements.
BibTeX @misc{4ortxyz_rfc-5966-dns-transport-over-tcp-implementation-requirements_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 5966: DNS Transport over TCP - Implementation Requirements}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-5966-dns-transport-over-tcp-implementation-requirements}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 5966: DNS Transport over TCP - Implementation Requirements — https://4ort.xyz/entity/rfc-5966-dns-transport-over-tcp-implementation-requirements (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-5966-dns-transport-over-tcp-implementation-requirements · Last refreshed: