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

IETF · RFC · RFC3201

RFC3201 · Definitions of Managed Objects for Circuit to Interface Translation

Definitions of Managed Objects for Circuit to Interface Translation

This memo defines an extension of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the insertion of interesting Circuit Interfaces into the ifTable. This is important for circuits that must be used within other MIB modules which require an ifEntry. It allows for integrated monitoring of circuits as well as routing to circuits using unaltered, pre-existing MIB modules. [STANDARDS-TRACK]

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

This memo defines an extension of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the insertion of interesting Circuit Interfaces into the ifTable. This is important for circuits that must be used within other MIB modules which require an ifEntry. It allows for integrated monitoring of circuits as well as routing to circuits using unaltered, pre-existing MIB modules. [STANDARDS-TRACK]

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

updated_by: RFC9141

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

Полные импортированные сведения карточки
{
  "id": "RFC3201",
  "number": 3201,
  "title_en": "Definitions of Managed Objects for Circuit to Interface Translation",
  "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 defines an extension of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the insertion of interesting Circuit Interfaces into the ifTable. This is important for circuits that must be used within other MIB modules which require an ifEntry. It allows for integrated monitoring of circuits as well as routing to circuits using unaltered, pre-existing MIB modules. [STANDARDS-TRACK]",
  "authors": [
    "R. Steinberger",
    "O. Nicklass"
  ],
  "organizations": [],
  "publication_date": "2002-01-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": "int",
  "area_ru": "Интернет",
  "working_group": "frnetmib",
  "source_draft": "draft-ietf-frnetmib-frsi-04",
  "page_count": 23,
  "doi": "10.17487/RFC3201",
  "keywords": [
    "mib",
    "management information base"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC9141"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3201/",
    "html": "https://www.rfc-editor.org/rfc/rfc3201.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3201.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3201/"
  }
}