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

IETF · RFC · RFC5593

RFC5593 · Internet Message Access Protocol (IMAP) - URL Access Identifier Extension

Internet Message Access Protocol (IMAP) - URL Access Identifier Extension

The existing IMAP URL specification (RFC 5092) lists several <access> identifiers and <access> identifier prefixes that can be used to restrict access to URLAUTH-generated URLs. However, these identifiers do not provide facilities for new services such as streaming. This document proposes a set of new <access> identifiers as well as an IANA mechanism to register new <access> identifiers for future applications. This document updates RFC 5092. [STANDARDS-TRACK]

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

The existing IMAP URL specification (RFC 5092) lists several <access> identifiers and <access> identifier prefixes that can be used to restrict access to URLAUTH-generated URLs. However, these identifiers do not provide facilities for new services such as streaming. This document proposes a set of new <access> identifiers as well as an IANA mechanism to register new <access> identifiers for future applications. This document updates RFC 5092. [STANDARDS-TRACK]

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

updates: RFC5092

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

Полные импортированные сведения карточки
{
  "id": "RFC5593",
  "number": 5593,
  "title_en": "Internet Message Access Protocol (IMAP) - URL Access Identifier Extension",
  "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 existing IMAP URL specification (RFC 5092) lists several <access> identifiers and <access> identifier prefixes that can be used to restrict access to URLAUTH-generated URLs. However, these identifiers do not provide facilities for new services such as streaming. This document proposes a set of new <access> identifiers as well as an IANA mechanism to register new <access> identifiers for future applications. This document updates RFC 5092. [STANDARDS-TRACK]",
  "authors": [
    "N. Cook"
  ],
  "organizations": [],
  "publication_date": "2009-06-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": "",
  "area_ru": "",
  "working_group": "NON WORKING GROUP",
  "source_draft": "draft-ncook-urlauth-accessid-02",
  "page_count": 10,
  "doi": "10.17487/RFC5593",
  "keywords": [
    "urlauth",
    "imap url"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC5092"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc5593/",
    "html": "https://www.rfc-editor.org/rfc/rfc5593.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc5593.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc5593/"
  }
}