RFC9834 · YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)
YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)
Delivery of network services assumes that appropriate setup is provisioned over the links that connect customer termination points and a provider network. The required setup to allow successful data exchange over these links is referred to as an attachment circuit (AC), while the underlying link is referred to as a "bearer". This document specifies a YANG service data model for ACs. This model can be used for the provisioning of ACs before or during service provisioning (e.g., RFC 9543 Network Slice Service). The document also specifies a YANG service data model for managing bearers over which ACs are established.
IETF · RFCОфициальная английская аннотация
Delivery of network services assumes that appropriate setup is provisioned over the links that connect customer termination points and a provider network. The required setup to allow successful data exchange over these links is referred to as an attachment circuit (AC), while the underlying link is referred to as a "bearer". This document specifies a YANG service data model for ACs. This model can be used for the provisioning of ACs before or during service provisioning (e.g., RFC 9543 Network Slice Service). The document also specifies a YANG service data model for managing bearers over which ACs are established.
{
"id": "RFC9834",
"number": 9834,
"title_en": "YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)",
"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": "Delivery of network services assumes that appropriate setup is provisioned over the links that connect customer termination points and a provider network. The required setup to allow successful data exchange over these links is referred to as an attachment circuit (AC), while the underlying link is referred to as a \"bearer\". This document specifies a YANG service data model for ACs. This model can be used for the provisioning of ACs before or during service provisioning (e.g., RFC 9543 Network Slice Service). The document also specifies a YANG service data model for managing bearers over which ACs are established.",
"authors": [
"M. Boucadair",
"R. Roberts",
"O. Gonzalez de Dios",
"S. Barguil",
"B. Wu"
],
"organizations": [],
"publication_date": "2025-09-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": "opsawg",
"source_draft": "draft-ietf-opsawg-teas-attachment-circuit-20",
"page_count": 150,
"doi": "10.17487/RFC9834",
"keywords": [
"Slice Service",
"L3VPN",
"L2VPN",
"Automation",
"Network Automation",
"Orchestration",
"service delivery",
"Service provisioning",
"service segmentation",
"service flexibility",
"service simplification",
"Network Service",
"3GPP",
"Network Slicing"
],
"formats": [
"HTML",
"TXT",
"PDF",
"XML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc9834/",
"html": "https://www.rfc-editor.org/rfc/rfc9834.html",
"txt": "https://www.rfc-editor.org/rfc/rfc9834.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc9834/"
}
}