Autonomic functions need a control plane to communicate, which depends on some addressing and routing. This Autonomic Control Plane should ideally be self-managing and be as independent as possible of configuration. This document defines such a plane and calls it the "Autonomic Control Plane", with the primary use as a control plane for autonomic functions. It also serves as a "virtual out-of-band channel" for Operations, Administration, and Management (OAM) communications over a network that provides automatically configured, hop-by-hop authenticated and encrypted communications via automatically configured IPv6 even when the network is not configured or is misconfigured.
IETF · RFCОфициальная английская аннотация
Autonomic functions need a control plane to communicate, which depends on some addressing and routing. This Autonomic Control Plane should ideally be self-managing and be as independent as possible of configuration. This document defines such a plane and calls it the "Autonomic Control Plane", with the primary use as a control plane for autonomic functions. It also serves as a "virtual out-of-band channel" for Operations, Administration, and Management (OAM) communications over a network that provides automatically configured, hop-by-hop authenticated and encrypted communications via automatically configured IPv6 even when the network is not configured or is misconfigured.
{
"id": "RFC8994",
"number": 8994,
"title_en": "An Autonomic Control Plane (ACP)",
"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": "Autonomic functions need a control plane to communicate, which depends on some addressing and routing. This Autonomic Control Plane should ideally be self-managing and be as independent as possible of configuration. This document defines such a plane and calls it the \"Autonomic Control Plane\", with the primary use as a control plane for autonomic functions. It also serves as a \"virtual out-of-band channel\" for Operations, Administration, and Management (OAM) communications over a network that provides automatically configured, hop-by-hop authenticated and encrypted communications via automatically configured IPv6 even when the network is not configured or is misconfigured.",
"authors": [
"T. Eckert",
"M. Behringer",
"S. Bjarnason"
],
"organizations": [],
"publication_date": "2021-05-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": "anima",
"source_draft": "draft-ietf-anima-autonomic-control-plane-30",
"page_count": 128,
"doi": "10.17487/RFC8994",
"keywords": [
"addressing-scheme",
"ANI",
"autonomic networking",
"autonomous operation",
"BRSKI",
"certificate",
"Data-Plane",
"domain",
"DTLS",
"DULL",
"EST",
"GRASP",
"IDevID",
"inband",
"IPsec",
"IPv6",
"LDevID",
"loopback-interface",
"NOC",
"OAM",
"out-of-band",
"registrar",
"renewal",
"RPL",
"secure",
"self-management",
"ULA",
"VPN",
"VRF"
],
"formats": [
"HTML",
"TXT",
"PDF",
"XML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc8994/",
"html": "https://www.rfc-editor.org/rfc/rfc8994.html",
"txt": "https://www.rfc-editor.org/rfc/rfc8994.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc8994/"
}
}