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

IETF · RFC · RFC5666

RFC5666 · Remote Direct Memory Access Transport for Remote Procedure Call

Remote Direct Memory Access Transport for Remote Procedure Call

This document describes a protocol providing Remote Direct Memory Access (RDMA) as a new transport for Remote Procedure Call (RPC). The RDMA transport binding conveys the benefits of efficient, bulk-data transport over high-speed networks, while providing for minimal change to RPC applications and with no required revision of the application RPC protocol, or the RPC protocol itself. [STANDARDS-TRACK]

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

This document describes a protocol providing Remote Direct Memory Access (RDMA) as a new transport for Remote Procedure Call (RPC). The RDMA transport binding conveys the benefits of efficient, bulk-data transport over high-speed networks, while providing for minimal change to RPC applications and with no required revision of the application RPC protocol, or the RPC protocol itself. [STANDARDS-TRACK]

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

obsoleted_by: RFC8166

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

Полные импортированные сведения карточки
{
  "id": "RFC5666",
  "number": 5666,
  "title_en": "Remote Direct Memory Access Transport for Remote Procedure Call",
  "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": "This document describes a protocol providing Remote Direct Memory Access (RDMA) as a new transport for Remote Procedure Call (RPC). The RDMA transport binding conveys the benefits of efficient, bulk-data transport over high-speed networks, while providing for minimal change to RPC applications and with no required revision of the application RPC protocol, or the RPC protocol itself. [STANDARDS-TRACK]",
  "authors": [
    "T. Talpey",
    "B. Callaghan"
  ],
  "organizations": [],
  "publication_date": "2010-01-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "superseded",
  "lifecycle_ru": "Заменён",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "wit",
  "area_ru": "Веб и транспорт Интернета",
  "working_group": "nfsv4",
  "source_draft": "draft-ietf-nfsv4-rpcrdma-09",
  "page_count": 34,
  "doi": "10.17487/RFC5666",
  "keywords": [
    "Network File System",
    "NFS",
    "ONC RPC",
    "RDMA",
    "RDDP",
    "iWARP",
    "InfiniBand"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [
      "RFC8166"
    ],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc5666/",
    "html": "https://www.rfc-editor.org/rfc/rfc5666.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc5666.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc5666/"
  }
}