Home › Entities › request_for_comments › RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets

RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets

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

RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets

Summary

RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets is a Request for Comments[1].

Key Facts

  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets authored CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets — author (P50): Hannes Tschofenig[2].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets authored CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets — author (P50): Carsten Bormann[3].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's instance of is recorded as CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets — instance of (P31): Request for Comments[4].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's publisher is recorded as CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets — publisher (P123): Internet Engineering Task Force[5].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's based on is recorded as CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets — based on (P144): RFC 7641: Observing Resources in the Constrained Application Protocol (CoAP)[6].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's based on is recorded as CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets — based on (P144): RFC 7959: Block-Wise Transfers in the Constrained Application Protocol (CoAP)[7].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's DOI is recorded as 10.17487/RFC8323[8].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's language of work or name is recorded as CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets — language of work or name (P407): English[9].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's publication date is recorded as +2018-02-01T00:00:00Z[10].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's RfC ID is recorded as 8323[11].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's work available at URL is recorded as https://tools.ietf.org/html/rfc8323[12].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's work available at URL is recorded as https://tools.ietf.org/rfc/rfc8323.txt[13].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc8323.txt[14].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc8323.txt.pdf[15].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's number of pages is recorded as {'unit': '1', 'amount': '+54'}[16].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's title is recorded as CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets[17].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's author name string is recorded as S. Lemay[18].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's author name string is recorded as K. Hartke[19].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's author name string is recorded as B. Silverajan[20].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's author name string is recorded as B. Raymor[21].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's amended by is recorded as CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets — amended by (P2567): RFC 8974: Extended Tokens and Stateless Clients in the Constrained Application Protocol (CoAP)[22].
  • RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's DBLP publication ID is recorded as journals/rfc/rfc8323[23].

Body

Designation and Status

RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets's instance of is recorded as CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets — 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] ↑ . 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] ↑ . RFC Index. Retrieved . wikidata.org.
  20. [21] ↑ . RFC Index. Retrieved . wikidata.org.
  21. [22] ↑ . RFC Index. Retrieved . wikidata.org.
  22. [23] ↑ . 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 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-8323-coap-constrained-application-protocol-over-tcp-tls-and-websockets
MLA “RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-8323-coap-constrained-application-protocol-over-tcp-tls-and-websockets.
BibTeX @misc{4ortxyz_rfc-8323-coap-constrained-application-protocol-over-tcp-tls-and-websockets_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-8323-coap-constrained-application-protocol-over-tcp-tls-and-websockets}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets — https://4ort.xyz/entity/rfc-8323-coap-constrained-application-protocol-over-tcp-tls-and-websockets (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-8323-coap-constrained-application-protocol-over-tcp-tls-and-websockets · Last refreshed: