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

IETF · RFC · RFC9833

RFC9833 · A Common YANG Data Model for Attachment Circuits

A Common YANG Data Model for Attachment Circuits

The document specifies a common attachment circuits (ACs) YANG data model, which is designed to be reusable by other models. This design is meant to ensure consistent AC structures among models that manipulate ACs. For example, this common model can be reused by service models to expose ACs as a service, service models that require binding a service to a set of ACs, network and device models to provision ACs, etc.

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

The document specifies a common attachment circuits (ACs) YANG data model, which is designed to be reusable by other models. This design is meant to ensure consistent AC structures among models that manipulate ACs. For example, this common model can be reused by service models to expose ACs as a service, service models that require binding a service to a set of ACs, network and device models to provision ACs, etc.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC9833",
  "number": 9833,
  "title_en": "A Common YANG Data Model for Attachment Circuits",
  "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": "The document specifies a common attachment circuits (ACs) YANG data model, which is designed to be reusable by other models. This design is meant to ensure consistent AC structures among models that manipulate ACs. For example, this common model can be reused by service models to expose ACs as a service, service models that require binding a service to a set of ACs, network and device models to provision ACs, etc.",
  "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-common-ac-15",
  "page_count": 56,
  "doi": "10.17487/RFC9833",
  "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/rfc9833/",
    "html": "https://www.rfc-editor.org/rfc/rfc9833.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc9833.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc9833/"
  }
}