RFC2919 · List-Id: A Structured Field and Namespace for the Identification of Mailing Lists
List-Id: A Structured Field and Namespace for the Identification of Mailing Lists
Software that handles electronic mailing list messages (servers and user agents) needs a way to reliably identify messages that belong to a particular mailing list. With the advent of list management headers, it has become even more important to provide a unique identifier for a mailing list regardless of the particular host that serves as the list processor at any given time. [STANDARDS-TRACK]
IETF · RFCОфициальная английская аннотация
Software that handles electronic mailing list messages (servers and user agents) needs a way to reliably identify messages that belong to a particular mailing list. With the advent of list management headers, it has become even more important to provide a unique identifier for a mailing list regardless of the particular host that serves as the list processor at any given time. [STANDARDS-TRACK]
{
"id": "RFC2919",
"number": 2919,
"title_en": "List-Id: A Structured Field and Namespace for the Identification of Mailing Lists",
"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": "Software that handles electronic mailing list messages (servers and user agents) needs a way to reliably identify messages that belong to a particular mailing list. With the advent of list management headers, it has become even more important to provide a unique identifier for a mailing list regardless of the particular host that serves as the list processor at any given time. [STANDARDS-TRACK]",
"authors": [
"R. Chandhok",
"G. Wenger"
],
"organizations": [],
"publication_date": "2001-03-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-chandhok-listid-04",
"page_count": 9,
"doi": "10.17487/RFC2919",
"keywords": [
"server",
"clients",
"user agents"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc2919/",
"html": "https://www.rfc-editor.org/rfc/rfc2919.html",
"txt": "https://www.rfc-editor.org/rfc/rfc2919.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc2919/"
}
}