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

IETF · RFC · RFC6047

RFC6047 · iCalendar Message-Based Interoperability Protocol (iMIP)

iCalendar Message-Based Interoperability Protocol (iMIP)

This document, "iCalendar Message-Based Interoperability Protocol (iMIP)", specifies a binding from the iCalendar Transport-independent Interoperability Protocol (iTIP) to Internet email-based transports. Calendaring entries defined by the iCalendar Object Model (iCalendar) are wrapped using constructs from RFC 5322 and MIME (RFC 2045, RFC 2046, RFC 2047, and RFC 2049), and then transported over SMTP. [STANDARDS-TRACK]

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

This document, "iCalendar Message-Based Interoperability Protocol (iMIP)", specifies a binding from the iCalendar Transport-independent Interoperability Protocol (iTIP) to Internet email-based transports. Calendaring entries defined by the iCalendar Object Model (iCalendar) are wrapped using constructs from RFC 5322 and MIME (RFC 2045, RFC 2046, RFC 2047, and RFC 2049), and then transported over SMTP. [STANDARDS-TRACK]

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

obsoletes: RFC2447

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

Полные импортированные сведения карточки
{
  "id": "RFC6047",
  "number": 6047,
  "title_en": "iCalendar Message-Based Interoperability Protocol (iMIP)",
  "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, \"iCalendar Message-Based Interoperability Protocol (iMIP)\", specifies a binding from the iCalendar Transport-independent Interoperability Protocol (iTIP) to Internet email-based transports. Calendaring entries defined by the iCalendar Object Model (iCalendar) are wrapped using constructs from RFC 5322 and MIME (RFC 2045, RFC 2046, RFC 2047, and RFC 2049), and then transported over SMTP. [STANDARDS-TRACK]",
  "authors": [
    "A. Melnikov"
  ],
  "organizations": [],
  "publication_date": "2010-12-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": "app",
  "area_ru": "app",
  "working_group": "calsify",
  "source_draft": "draft-ietf-calsify-rfc2447bis-11",
  "page_count": 22,
  "doi": "10.17487/RFC6047",
  "keywords": [
    "IMIP",
    "electronic mail",
    "transport",
    "itip",
    "iCalendar Transport-independent Interoperability Protocol",
    "iCalendar Object Model"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [
      "RFC2447"
    ],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6047/",
    "html": "https://www.rfc-editor.org/rfc/rfc6047.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6047.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6047/"
  }
}