RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums

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

RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums

Summary

RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums is a Request for Comments[1].

Key Facts

  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums authored Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums — author (P50): Magnus Westerlund[2].
  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums authored Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums — author (P50): Gorry Fairhurst[3].
  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums's instance of is recorded as Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums — instance of (P31): Request for Comments[4].
  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums's publisher is recorded as Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums — publisher (P123): Internet Engineering Task Force[5].
  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums's DOI is recorded as 10.17487/RFC6936[6].
  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums's language of work or name is recorded as Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums — language of work or name (P407): English[7].
  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums's publication date is recorded as +2013-04-01T00:00:00Z[8].
  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums's RfC ID is recorded as 6936[9].
  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums's work available at URL is recorded as https://tools.ietf.org/html/rfc6936[10].
  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums's work available at URL is recorded as https://tools.ietf.org/rfc/rfc6936.txt[11].
  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc6936.txt[12].
  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc6936.txt.pdf[13].
  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums's number of pages is recorded as {'unit': '1', 'amount': '+40'}[14].
  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums's title is recorded as Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums[15].
  • RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums's DBLP publication ID is recorded as journals/rfc/rfc6936[16].

Body

Designation and Status

RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums's instance of is recorded as Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums — instance of (P31): Request for Comments[4].

References

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

Direct Wikidata claims

  1. [4] . RFC Index. Retrieved . wikidata.org.
  2. [2] . RFC Index. Retrieved . wikidata.org.
  3. [3] . 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 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-6936-applicability-statement-for-the-use-of-ipv6-udp-datagrams-with-zero-checksums
MLA “RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-6936-applicability-statement-for-the-use-of-ipv6-udp-datagrams-with-zero-checksums.
BibTeX @misc{4ortxyz_rfc-6936-applicability-statement-for-the-use-of-ipv6-udp-datagrams-with-zero-checksums_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-6936-applicability-statement-for-the-use-of-ipv6-udp-datagrams-with-zero-checksums}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 6936: Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums — https://4ort.xyz/entity/rfc-6936-applicability-statement-for-the-use-of-ipv6-udp-datagrams-with-zero-checksums (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-6936-applicability-statement-for-the-use-of-ipv6-udp-datagrams-with-zero-checksums · Last refreshed: