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

IETF · RFC · RFC7854

RFC7854 · BGP Monitoring Protocol (BMP)

BGP Monitoring Protocol (BMP)

This document defines the BGP Monitoring Protocol (BMP), which can be used to monitor BGP sessions. BMP is intended to provide a convenient interface for obtaining route views. Prior to the introduction of BMP, screen scraping was the most commonly used approach to obtaining such views. The design goals are to keep BMP simple, useful, easily implemented, and minimally service affecting. BMP is not suitable for use as a routing protocol.

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

This document defines the BGP Monitoring Protocol (BMP), which can be used to monitor BGP sessions. BMP is intended to provide a convenient interface for obtaining route views. Prior to the introduction of BMP, screen scraping was the most commonly used approach to obtaining such views. The design goals are to keep BMP simple, useful, easily implemented, and minimally service affecting. BMP is not suitable for use as a routing protocol.

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

updated_by: RFC8671, RFC9069, RFC9515, RFC9736

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

Полные импортированные сведения карточки
{
  "id": "RFC7854",
  "number": 7854,
  "title_en": "BGP Monitoring Protocol (BMP)",
  "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": "This document defines the BGP Monitoring Protocol (BMP), which can be used to monitor BGP sessions. BMP is intended to provide a convenient interface for obtaining route views. Prior to the introduction of BMP, screen scraping was the most commonly used approach to obtaining such views. The design goals are to keep BMP simple, useful, easily implemented, and minimally service affecting. BMP is not suitable for use as a routing protocol.",
  "authors": [
    "J. Scudder",
    "R. Fernando",
    "S. Stuart"
  ],
  "organizations": [],
  "publication_date": "2016-06-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": "ops",
  "area_ru": "Эксплуатация и управление",
  "working_group": "grow",
  "source_draft": "draft-ietf-grow-bmp-17",
  "page_count": 27,
  "doi": "10.17487/RFC7854",
  "keywords": [
    "IDR",
    "BGP",
    "GROW",
    "BMP"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC8671",
      "RFC9069",
      "RFC9515",
      "RFC9736"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc7854/",
    "html": "https://www.rfc-editor.org/rfc/rfc7854.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc7854.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7854/"
  }
}