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

IETF · RFC · RFC2622

RFC2622 · Routing Policy Specification Language (RPSL)

Routing Policy Specification Language (RPSL)

RPSL allows a network operator to be able to specify routing policies at various levels in the Internet hierarchy; for example at the Autonomous System (AS) level. At the same time, policies can be specified with sufficient detail in RPSL so that low level router configurations can be generated from them. RPSL is extensible; new routing protocols and new protocol features can be introduced at any time. [STANDARDS-TRACK]

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

RPSL allows a network operator to be able to specify routing policies at various levels in the Internet hierarchy; for example at the Autonomous System (AS) level. At the same time, policies can be specified with sufficient detail in RPSL so that low level router configurations can be generated from them. RPSL is extensible; new routing protocols and new protocol features can be introduced at any time. [STANDARDS-TRACK]

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

obsoletes: RFC2280

updated_by: RFC4012, RFC7909

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

Полные импортированные сведения карточки
{
  "id": "RFC2622",
  "number": 2622,
  "title_en": "Routing Policy Specification Language (RPSL)",
  "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": "RPSL allows a network operator to be able to specify routing policies at various levels in the Internet hierarchy; for example at the Autonomous System (AS) level. At the same time, policies can be specified with sufficient detail in RPSL so that low level router configurations can be generated from them. RPSL is extensible; new routing protocols and new protocol features can be introduced at any time. [STANDARDS-TRACK]",
  "authors": [
    "C. Alaettinoglu",
    "C. Villamizar",
    "E. Gerich",
    "D. Kessens",
    "D. Meyer",
    "T. Bates",
    "D. Karrenberg",
    "M. Terpstra"
  ],
  "organizations": [],
  "publication_date": "1999-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": "rps",
  "source_draft": "draft-ietf-rps-rpsl-v2-03",
  "page_count": 69,
  "doi": "10.17487/RFC2622",
  "keywords": [
    "RPSL",
    "Routing Policy Specification Language",
    "internet",
    "policy",
    "hierarchy",
    "network",
    "configuration"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [
      "RFC2280"
    ],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC4012",
      "RFC7909"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc2622/",
    "html": "https://www.rfc-editor.org/rfc/rfc2622.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc2622.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc2622/"
  }
}