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

IETF · RFC · RFC6648

RFC6648 · Deprecating the "X-" Prefix and Similar Constructs in Application Protocols

Deprecating the "X-" Prefix and Similar Constructs in Application Protocols

Historically, designers and implementers of application protocols have often distinguished between standardized and unstandardized parameters by prefixing the names of unstandardized parameters with the string "X-" or similar constructs. In practice, that convention causes more problems than it solves. Therefore, this document deprecates the convention for newly defined parameters with textual (as opposed to numerical) names in application protocols. This memo documents an Internet Best Current Practice.

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

Historically, designers and implementers of application protocols have often distinguished between standardized and unstandardized parameters by prefixing the names of unstandardized parameters with the string "X-" or similar constructs. In practice, that convention causes more problems than it solves. Therefore, this document deprecates the convention for newly defined parameters with textual (as opposed to numerical) names in application protocols. This memo documents an Internet Best Current Practice.

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

is_also: BCP178

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

Полные импортированные сведения карточки
{
  "id": "RFC6648",
  "number": 6648,
  "title_en": "Deprecating the \"X-\" Prefix and Similar Constructs in Application Protocols",
  "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": "Historically, designers and implementers of application protocols have often distinguished between standardized and unstandardized parameters by prefixing the names of unstandardized parameters with the string \"X-\" or similar constructs. In practice, that convention causes more problems than it solves. Therefore, this document deprecates the convention for newly defined parameters with textual (as opposed to numerical) names in application protocols. This memo documents an Internet Best Current Practice.",
  "authors": [
    "P. Saint-Andre",
    "D. Crocker",
    "M. Nottingham"
  ],
  "organizations": [],
  "publication_date": "2012-06-01",
  "current_status": "BEST CURRENT PRACTICE",
  "current_status_ru": "Лучшая современная практика",
  "publication_status": "BEST CURRENT PRACTICE",
  "publication_status_ru": "Лучшая современная практика",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "art",
  "area_ru": "Приложения и взаимодействие в реальном времени",
  "working_group": "appsawg",
  "source_draft": "draft-ietf-appsawg-xdash-05",
  "page_count": 13,
  "doi": "10.17487/RFC6648",
  "keywords": [],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [
      "BCP178"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6648/",
    "html": "https://www.rfc-editor.org/rfc/rfc6648.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6648.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6648/"
  }
}