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

IETF · RFC · RFC4249

RFC4249 · Implementer-Friendly Specification of Message and MIME-Part Header Fields and Field Components

Implementer-Friendly Specification of Message and MIME-Part Header Fields and Field Components

Implementation of generators and parsers of header fields requires certain information about those fields. Interoperability is most likely when all such information is explicitly provided by the technical specification of the fields. Lacking such explicit information, implementers may guess, and interoperability may suffer. This memo identifies information useful to implementers of header field generators and parsers. This memo provides information for the Internet community.

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

Implementation of generators and parsers of header fields requires certain information about those fields. Interoperability is most likely when all such information is explicitly provided by the technical specification of the fields. Lacking such explicit information, implementers may guess, and interoperability may suffer. This memo identifies information useful to implementers of header field generators and parsers. This memo provides information for the Internet community.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC4249",
  "number": 4249,
  "title_en": "Implementer-Friendly Specification of Message and MIME-Part Header Fields and Field Components",
  "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": "Implementation of generators and parsers of header fields requires certain information about those fields. Interoperability is most likely when all such information is explicitly provided by the technical specification of the fields. Lacking such explicit information, implementers may guess, and interoperability may suffer. This memo identifies information useful to implementers of header field generators and parsers. This memo provides information for the Internet community.",
  "authors": [
    "B. Lilly"
  ],
  "organizations": [],
  "publication_date": "2006-01-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "",
  "area_ru": "",
  "working_group": "NON WORKING GROUP",
  "source_draft": "draft-lilly-field-specification-04",
  "page_count": 14,
  "doi": "10.17487/RFC4249",
  "keywords": [
    "header field generator",
    "header field parser"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc4249/",
    "html": "https://www.rfc-editor.org/rfc/rfc4249.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc4249.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc4249/"
  }
}