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

IETF · RFC · RFC4642

RFC4642 · Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)

Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)

This memo defines an extension to the Network News Transfer Protocol (NNTP) that allows an NNTP client and server to use Transport Layer Security (TLS). The primary goal is to provide encryption for single-link confidentiality purposes, but data integrity, (optional) certificate-based peer entity authentication, and (optional) data compression are also possible. [STANDARDS-TRACK]

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

This memo defines an extension to the Network News Transfer Protocol (NNTP) that allows an NNTP client and server to use Transport Layer Security (TLS). The primary goal is to provide encryption for single-link confidentiality purposes, but data integrity, (optional) certificate-based peer entity authentication, and (optional) data compression are also possible. [STANDARDS-TRACK]

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

updated_by: RFC8143, RFC8996

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

Полные импортированные сведения карточки
{
  "id": "RFC4642",
  "number": 4642,
  "title_en": "Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)",
  "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 memo defines an extension to the Network News Transfer Protocol (NNTP) that allows an NNTP client and server to use Transport Layer Security (TLS). The primary goal is to provide encryption for single-link confidentiality purposes, but data integrity, (optional) certificate-based peer entity authentication, and (optional) data compression are also possible. [STANDARDS-TRACK]",
  "authors": [
    "K. Murchison",
    "J. Vinocur",
    "C. Newman"
  ],
  "organizations": [],
  "publication_date": "2006-10-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": "nntpext",
  "source_draft": "draft-ietf-nntpext-tls-nntp-09",
  "page_count": 14,
  "doi": "10.17487/RFC4642",
  "keywords": [
    "encryption",
    "single link confidentiality"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC8143",
      "RFC8996"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc4642/",
    "html": "https://www.rfc-editor.org/rfc/rfc4642.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc4642.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc4642/"
  }
}