RFC 7252: The Constrained Application Protocol (CoAP)
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 7252: The Constrained Application Protocol (CoAP)
Summary
RFC 7252: The Constrained Application Protocol (CoAP) is a Request for Comments[1].
Key Facts
- RFC 7252: The Constrained Application Protocol (CoAP) authored The Constrained Application Protocol (CoAP) — author (P50): Carsten Bormann[2].
- RFC 7252: The Constrained Application Protocol (CoAP)'s instance of is recorded as The Constrained Application Protocol (CoAP) — instance of (P31): Request for Comments[3].
- RFC 7252: The Constrained Application Protocol (CoAP)'s publisher is recorded as The Constrained Application Protocol (CoAP) — publisher (P123): Internet Engineering Task Force[4].
- RFC 7252: The Constrained Application Protocol (CoAP)'s DOI is recorded as 10.17487/RFC7252[5].
- RFC 7252: The Constrained Application Protocol (CoAP)'s language of work or name is recorded as The Constrained Application Protocol (CoAP) — language of work or name (P407): English[6].
- RFC 7252: The Constrained Application Protocol (CoAP)'s publication date is recorded as +2014-06-01T00:00:00Z[7].
- RFC 7252: The Constrained Application Protocol (CoAP)'s RfC ID is recorded as 7252[8].
- RFC 7252: The Constrained Application Protocol (CoAP)'s main subject is recorded as The Constrained Application Protocol (CoAP) — main subject (P921): Constrained Application Protocol[9].
- RFC 7252: The Constrained Application Protocol (CoAP)'s work available at URL is recorded as https://tools.ietf.org/html/rfc7252[10].
- RFC 7252: The Constrained Application Protocol (CoAP)'s work available at URL is recorded as https://tools.ietf.org/rfc/rfc7252.txt[11].
- RFC 7252: The Constrained Application Protocol (CoAP)'s work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc7252.txt[12].
- RFC 7252: The Constrained Application Protocol (CoAP)'s work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc7252.txt.pdf[13].
- RFC 7252: The Constrained Application Protocol (CoAP)'s number of pages is recorded as {'unit': '1', 'amount': '+112'}[14].
- RFC 7252: The Constrained Application Protocol (CoAP)'s title is recorded as The Constrained Application Protocol (CoAP)[15].
- RFC 7252: The Constrained Application Protocol (CoAP)'s author name string is recorded as Z. Shelby[16].
- RFC 7252: The Constrained Application Protocol (CoAP)'s author name string is recorded as K. Hartke[17].
- RFC 7252: The Constrained Application Protocol (CoAP)'s amended by is recorded as The Constrained Application Protocol (CoAP) — amended by (P2567): RFC 7959: Block-Wise Transfers in the Constrained Application Protocol (CoAP)[18].
- RFC 7252: The Constrained Application Protocol (CoAP)'s amended by is recorded as The Constrained Application Protocol (CoAP) — amended by (P2567): RFC 8613: Object Security for Constrained RESTful Environments (OSCORE)[19].
- RFC 7252: The Constrained Application Protocol (CoAP)'s amended by is recorded as The Constrained Application Protocol (CoAP) — amended by (P2567): RFC 8974: Extended Tokens and Stateless Clients in the Constrained Application Protocol (CoAP)[20].
- RFC 7252: The Constrained Application Protocol (CoAP)'s amended by is recorded as The Constrained Application Protocol (CoAP) — amended by (P2567): RFC 9175: Constrained Application Protocol (CoAP): Echo, Request-Tag, and Token Processing[21].
- RFC 7252: The Constrained Application Protocol (CoAP)'s DBLP publication ID is recorded as journals/rfc/rfc7252[22].
Body
Designation and Status
RFC 7252: The Constrained Application Protocol (CoAP)'s instance of is recorded as The Constrained Application Protocol (CoAP) — instance of (P31): Request for Comments[3].