RFC3620 · The TUNNEL Profile

{
  "id": "RFC3620",
  "number": 3620,
  "title_en": "The TUNNEL Profile",
  "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 describes a Blocks Extensible Exchange Protocol (BEEP) profile that allows a BEEP peer to serve as an application-layer proxy. It allows authorized users to access services through a firewall.",
  "authors": [
    "D. New"
  ],
  "organizations": [],
  "publication_date": "2003-10-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": "sec",
  "area_ru": "Безопасность",
  "working_group": "idwg",
  "source_draft": "draft-ietf-idwg-beep-tunnel-05",
  "page_count": 18,
  "doi": "10.17487/RFC3620",
  "keywords": [
    "TUNNEL",
    "beep",
    "blocks extensible exchange protocol",
    "firewall",
    "application layer"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC8553"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3620/",
    "html": "https://www.rfc-editor.org/rfc/rfc3620.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3620.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3620/"
  }
}