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

IETF · RFC · RFC8256

RFC8256 · Requirements for Hitless MPLS Path Segment Monitoring

Requirements for Hitless MPLS Path Segment Monitoring

One of the most important Operations, Administration, and Maintenance (OAM) capabilities for transport-network operation is fault localization. An in-service, on-demand path segment monitoring function of a transport path is indispensable, particularly when the service monitoring function is activated only between endpoints. However, the current segment monitoring approach defined for MPLS (including the MPLS Transport Profile (MPLS-TP)) in RFC 6371 "Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks" has drawbacks. This document provides an analysis of the existing MPLS-TP OAM mechanisms for the path segment monitoring and provides requirements to guide the development of new OAM tools to support Hitless Path Segment Monitoring (HPSM).

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

One of the most important Operations, Administration, and Maintenance (OAM) capabilities for transport-network operation is fault localization. An in-service, on-demand path segment monitoring function of a transport path is indispensable, particularly when the service monitoring function is activated only between endpoints. However, the current segment monitoring approach defined for MPLS (including the MPLS Transport Profile (MPLS-TP)) in RFC 6371 "Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks" has drawbacks. This document provides an analysis of the existing MPLS-TP OAM mechanisms for the path segment monitoring and provides requirements to guide the development of new OAM tools to support Hitless Path Segment Monitoring (HPSM).

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

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

Полные импортированные сведения карточки
{
  "id": "RFC8256",
  "number": 8256,
  "title_en": "Requirements for Hitless MPLS Path Segment Monitoring",
  "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": "One of the most important Operations, Administration, and Maintenance (OAM) capabilities for transport-network operation is fault localization. An in-service, on-demand path segment monitoring function of a transport path is indispensable, particularly when the service monitoring function is activated only between endpoints. However, the current segment monitoring approach defined for MPLS (including the MPLS Transport Profile (MPLS-TP)) in RFC 6371 \"Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks\" has drawbacks. This document provides an analysis of the existing MPLS-TP OAM mechanisms for the path segment monitoring and provides requirements to guide the development of new OAM tools to support Hitless Path Segment Monitoring (HPSM).",
  "authors": [
    "A. D'Alessandro",
    "L. Andersson",
    "S. Ueno",
    "K. Arai",
    "Y. Koike"
  ],
  "organizations": [],
  "publication_date": "2017-10-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "rtg",
  "area_ru": "Маршрутизация",
  "working_group": "mpls",
  "source_draft": "draft-ietf-mpls-tp-temporal-hitless-psm-14",
  "page_count": 16,
  "doi": "10.17487/RFC8256",
  "keywords": [
    "HPSM",
    "MPLS",
    "MPLS Transport Profile",
    "mpls-tp",
    "OAM",
    "monitoring",
    "Hitless Path Segment Monitoring",
    "Path Segment Monitoring"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8256/",
    "html": "https://www.rfc-editor.org/rfc/rfc8256.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8256.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8256/"
  }
}