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

IETF · RFC · RFC4810

RFC4810 · Long-Term Archive Service Requirements

Long-Term Archive Service Requirements

There are many scenarios in which users must be able to prove the existence of data at a specific point in time and be able to demonstrate the integrity of data since that time, even when the duration from time of existence to time of demonstration spans a large period of time. Additionally, users must be able to verify signatures on digitally signed data many years after the generation of the signature. This document describes a class of long-term archive services to support such scenarios and the technical requirements for interacting with such services. This memo provides information for the Internet community.

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

There are many scenarios in which users must be able to prove the existence of data at a specific point in time and be able to demonstrate the integrity of data since that time, even when the duration from time of existence to time of demonstration spans a large period of time. Additionally, users must be able to verify signatures on digitally signed data many years after the generation of the signature. This document describes a class of long-term archive services to support such scenarios and the technical requirements for interacting with such services. This memo provides information for the Internet community.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC4810",
  "number": 4810,
  "title_en": "Long-Term Archive Service Requirements",
  "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": "There are many scenarios in which users must be able to prove the existence of data at a specific point in time and be able to demonstrate the integrity of data since that time, even when the duration from time of existence to time of demonstration spans a large period of time. Additionally, users must be able to verify signatures on digitally signed data many years after the generation of the signature. This document describes a class of long-term archive services to support such scenarios and the technical requirements for interacting with such services. This memo provides information for the Internet community.",
  "authors": [
    "C. Wallace",
    "U. Pordesch",
    "R. Brandner"
  ],
  "organizations": [],
  "publication_date": "2007-03-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "app",
  "area_ru": "app",
  "working_group": "ltans",
  "source_draft": "draft-ietf-ltans-reqs-10",
  "page_count": 17,
  "doi": "10.17487/RFC4810",
  "keywords": [
    "data integrity",
    "digital signatures"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc4810/",
    "html": "https://www.rfc-editor.org/rfc/rfc4810.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc4810.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc4810/"
  }
}