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

IETF · RFC · RFC6382

RFC6382 · Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted Services

Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted Services

This document makes recommendations regarding the use of unique origin autonomous system numbers (ASNs) per node for globally anycasted critical infrastructure services in order to provide routing system discriminators for a given anycasted prefix. Network management and monitoring techniques, or other operational mechanisms, may employ this new discriminator in whatever manner best accommodates their operating environment. This memo documents an Internet Best Current Practice.

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

This document makes recommendations regarding the use of unique origin autonomous system numbers (ASNs) per node for globally anycasted critical infrastructure services in order to provide routing system discriminators for a given anycasted prefix. Network management and monitoring techniques, or other operational mechanisms, may employ this new discriminator in whatever manner best accommodates their operating environment. This memo documents an Internet Best Current Practice.

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

is_also: BCP169

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

Полные импортированные сведения карточки
{
  "id": "RFC6382",
  "number": 6382,
  "title_en": "Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted Services",
  "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 makes recommendations regarding the use of unique origin autonomous system numbers (ASNs) per node for globally anycasted critical infrastructure services in order to provide routing system discriminators for a given anycasted prefix. Network management and monitoring techniques, or other operational mechanisms, may employ this new discriminator in whatever manner best accommodates their operating environment. This memo documents an Internet Best Current Practice.",
  "authors": [
    "D. McPherson",
    "R. Donnelly",
    "F. Scalzo"
  ],
  "organizations": [],
  "publication_date": "2011-10-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": "ops",
  "area_ru": "Эксплуатация и управление",
  "working_group": "grow",
  "source_draft": "draft-ietf-grow-unique-origin-as-01",
  "page_count": 10,
  "doi": "10.17487/RFC6382",
  "keywords": [
    "BGP",
    "SIDR",
    "RPKI",
    "security",
    "routing",
    "operations",
    "root",
    "TLD",
    "DNS",
    "DDOS",
    "peering",
    "RIR",
    "IRR",
    "MITM"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [
      "BCP169"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6382/",
    "html": "https://www.rfc-editor.org/rfc/rfc6382.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6382.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6382/"
  }
}