Home › Entities › request_for_comments › RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status

RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status

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

RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status

Summary

RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status is a Request for Comments[1].

Key Facts

  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's instance of is recorded as Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status — instance of (P31): Request for Comments[2].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's publisher is recorded as Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status — publisher (P123): Internet Engineering Task Force[3].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's DOI is recorded as 10.17487/RFC4966[4].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's language of work or name is recorded as Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status — language of work or name (P407): English[5].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's publication date is recorded as +2007-07-01T00:00:00Z[6].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's RfC ID is recorded as 4966[7].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's work available at URL is recorded as https://tools.ietf.org/html/rfc4966[8].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's work available at URL is recorded as https://tools.ietf.org/rfc/rfc4966.txt[9].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc4966.txt[10].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc4966.txt.pdf[11].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's number of pages is recorded as {'unit': '1', 'amount': '+25'}[12].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's replaces is recorded as Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status — replaces (P1365): RFC 2766: Network Address Translation - Protocol Translation (NAT-PT)[13].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's title is recorded as Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status[14].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's author name string is recorded as C. Aoun[15].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's author name string is recorded as E. Davies[16].
  • RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's DBLP publication ID is recorded as journals/rfc/rfc4966[17].

Body

Designation and Status

RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status's instance of is recorded as Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status — 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] ↑ . 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] ↑ . 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 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-4966-reasons-to-move-the-network-address-translator-protocol-translator-nat-pt-to-historic-status
MLA “RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-4966-reasons-to-move-the-network-address-translator-protocol-translator-nat-pt-to-historic-status.
BibTeX @misc{4ortxyz_rfc-4966-reasons-to-move-the-network-address-translator-protocol-translator-nat-pt-to-historic-status_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-4966-reasons-to-move-the-network-address-translator-protocol-translator-nat-pt-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 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status — https://4ort.xyz/entity/rfc-4966-reasons-to-move-the-network-address-translator-protocol-translator-nat-pt-to-historic-status (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-4966-reasons-to-move-the-network-address-translator-protocol-translator-nat-pt-to-historic-status · Last refreshed: