RFC2280 · Routing Policy Specification Language (RPSL)
Routing Policy Specification Language (RPSL)
This memo is the reference document for the 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]
IETF · RFCОфициальная английская аннотация
This memo is the reference document for the 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]
{
"id": "RFC2280",
"number": 2280,
"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": "This memo is the reference document for the 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]",
"authors": [
"C. Alaettinoglu",
"T. Bates",
"E. Gerich",
"D. Karrenberg",
"D. Meyer",
"M. Terpstra",
"C. Villamizar"
],
"organizations": [],
"publication_date": "1998-01-01",
"current_status": "PROPOSED STANDARD",
"current_status_ru": "Предлагаемый стандарт",
"publication_status": "PROPOSED STANDARD",
"publication_status_ru": "Предлагаемый стандарт",
"lifecycle": "superseded",
"lifecycle_ru": "Заменён",
"stream": "IETF",
"stream_ru": "IETF",
"area": "ops",
"area_ru": "Эксплуатация и управление",
"working_group": "rps",
"source_draft": "draft-ietf-rps-rpsl-03",
"page_count": 53,
"doi": "10.17487/RFC2280",
"keywords": [
"RPSL",
"network",
"operator",
"AS",
"autonomous",
"system",
"database"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [
"RFC2622"
],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc2280/",
"html": "https://www.rfc-editor.org/rfc/rfc2280.html",
"txt": "https://www.rfc-editor.org/rfc/rfc2280.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc2280/"
}
}