⌕ Поиск по атласу

IETF · RFC · RFC8323

RFC8323 · CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets

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

The Constrained Application Protocol (CoAP), although inspired by HTTP, was designed to use UDP instead of TCP. The message layer of CoAP over UDP includes support for reliable delivery, simple congestion control, and flow control. Some environments benefit from the availability of CoAP carried over reliable transports such as TCP or Transport Layer Security (TLS). This document outlines the changes required to use CoAP over TCP, TLS, and WebSockets transports. It also formally updates RFC 7641 for use with these transports and RFC 7959 to enable the use of larger messages over a reliable transport.

Официальная английская аннотация

The Constrained Application Protocol (CoAP), although inspired by HTTP, was designed to use UDP instead of TCP. The message layer of CoAP over UDP includes support for reliable delivery, simple congestion control, and flow control. Some environments benefit from the availability of CoAP carried over reliable transports such as TCP or Transport Layer Security (TLS). This document outlines the changes required to use CoAP over TCP, TLS, and WebSockets transports. It also formally updates RFC 7641 for use with these transports and RFC 7959 to enable the use of larger messages over a reliable transport.

Связи документа

updates: RFC7641, RFC7959

updated_by: RFC8974

Официальный источник · 2018-02-01

Полные импортированные сведения карточки
{
  "id": "RFC8323",
  "number": 8323,
  "title_en": "CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets",
  "title_ru": "",
  "summary_ru": "",
  "purpose_ru": "",
  "use_ru": "",
  "full_translation_path": "",
  "full_translation_checked_at": "",
  "full_translation_source_sha256": "",
  "architect_note_ru": "",
  "topics_ru": [],
  "translation_state": "not_prepared",
  "verification_level": "not_prepared",
  "verification_level_ru": "Русская выжимка не подготовлена",
  "verification_note_ru": "",
  "abstract_en": "The Constrained Application Protocol (CoAP), although inspired by HTTP, was designed to use UDP instead of TCP. The message layer of CoAP over UDP includes support for reliable delivery, simple congestion control, and flow control. Some environments benefit from the availability of CoAP carried over reliable transports such as TCP or Transport Layer Security (TLS). This document outlines the changes required to use CoAP over TCP, TLS, and WebSockets transports. It also formally updates RFC 7641 for use with these transports and RFC 7959 to enable the use of larger messages over a reliable transport.",
  "authors": [
    "C. Bormann",
    "S. Lemay",
    "H. Tschofenig",
    "K. Hartke",
    "B. Silverajan",
    "B. Raymor"
  ],
  "organizations": [],
  "publication_date": "2018-02-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "wit",
  "area_ru": "Веб и транспорт Интернета",
  "working_group": "core",
  "source_draft": "draft-ietf-core-coap-tcp-tls-11",
  "page_count": 54,
  "doi": "10.17487/RFC8323",
  "keywords": [
    "CoAP",
    "Constrained Application Protocol",
    "REST",
    "IoT",
    "Internet of Things",
    "NAT Traversal",
    "CoAP in Browsers"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC7641",
      "RFC7959"
    ],
    "updated_by": [
      "RFC8974"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8323/",
    "html": "https://www.rfc-editor.org/rfc/rfc8323.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8323.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8323/"
  }
}