RFC8516 · "Too Many Requests" Response Code for the Constrained Application Protocol

{
  "id": "RFC8516",
  "number": 8516,
  "title_en": "\"Too Many Requests\" Response Code for the Constrained Application Protocol",
  "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": "A Constrained Application Protocol (CoAP) server can experience temporary overload because one or more clients are sending requests to the server at a higher rate than the server is capable or willing to handle. This document defines a new CoAP response code for a server to indicate that a client should reduce the rate of requests.",
  "authors": [
    "A. Keranen"
  ],
  "organizations": [],
  "publication_date": "2019-01-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-too-many-reqs-06",
  "page_count": 6,
  "doi": "10.17487/RFC8516",
  "keywords": [
    "CoAP"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8516/",
    "html": "https://www.rfc-editor.org/rfc/rfc8516.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8516.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8516/"
  }
}