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

IETF · RFC · RFC3392

RFC3392 · Capabilities Advertisement with BGP-4

Capabilities Advertisement with BGP-4

Currently BGP-4 requires that when a BGP speaker receives an OPEN message with one or more unrecognized Optional Parameters, the speaker must terminate BGP peering. This complicates introduction of new capabilities in BGP. This document defines new Optional Parameter, called Capabilities, that is expected to facilitate introduction of new capabilities in BGP by providing graceful capability advertisement without requiring that BGP peering be terminated. This document obsoletes RFC2842.

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

Currently BGP-4 requires that when a BGP speaker receives an OPEN message with one or more unrecognized Optional Parameters, the speaker must terminate BGP peering. This complicates introduction of new capabilities in BGP. This document defines new Optional Parameter, called Capabilities, that is expected to facilitate introduction of new capabilities in BGP by providing graceful capability advertisement without requiring that BGP peering be terminated. This document obsoletes RFC2842.

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

obsoletes: RFC2842

obsoleted_by: RFC5492

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

Полные импортированные сведения карточки
{
  "id": "RFC3392",
  "number": 3392,
  "title_en": "Capabilities Advertisement with BGP-4",
  "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": "Currently BGP-4 requires that when a BGP speaker receives an OPEN message with one or more unrecognized Optional Parameters, the speaker must terminate BGP peering. This complicates introduction of new capabilities in BGP. This document defines new Optional Parameter, called Capabilities, that is expected to facilitate introduction of new capabilities in BGP by providing graceful capability advertisement without requiring that BGP peering be terminated. This document obsoletes RFC2842.",
  "authors": [
    "R. Chandra",
    "J. Scudder"
  ],
  "organizations": [],
  "publication_date": "2002-11-01",
  "current_status": "DRAFT STANDARD",
  "current_status_ru": "Проект стандарта (устаревшая стадия)",
  "publication_status": "DRAFT STANDARD",
  "publication_status_ru": "Проект стандарта (устаревшая стадия)",
  "lifecycle": "superseded",
  "lifecycle_ru": "Заменён",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "rtg",
  "area_ru": "Маршрутизация",
  "working_group": "idr",
  "source_draft": "draft-ietf-idr-rfc2842bis-01",
  "page_count": 6,
  "doi": "10.17487/RFC3392",
  "keywords": [
    "BGP",
    "border gateway protocol"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [
      "RFC2842"
    ],
    "obsoleted_by": [
      "RFC5492"
    ],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3392/",
    "html": "https://www.rfc-editor.org/rfc/rfc3392.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3392.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3392/"
  }
}