RFC7944 · Diameter Routing Message Priority

{
  "id": "RFC7944",
  "number": 7944,
  "title_en": "Diameter Routing Message Priority",
  "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": "When making routing and resource allocation decisions, Diameter nodes currently have no generic mechanism to determine the relative priority of Diameter messages. This document addresses this by defining a mechanism to allow Diameter endpoints to indicate the relative priority of Diameter transactions. With this information, Diameter nodes can factor that priority into routing, resource allocation, and overload abatement decisions.",
  "authors": [
    "S. Donovan"
  ],
  "organizations": [],
  "publication_date": "2016-08-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": "ops",
  "area_ru": "Эксплуатация и управление",
  "working_group": "dime",
  "source_draft": "draft-ietf-dime-drmp-07",
  "page_count": 18,
  "doi": "10.17487/RFC7944",
  "keywords": [
    "Diameter",
    "Overload"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc7944/",
    "html": "https://www.rfc-editor.org/rfc/rfc7944.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc7944.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7944/"
  }
}