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

IETF · RFC · RFC7648

RFC7648 · Port Control Protocol (PCP) Proxy Function

Port Control Protocol (PCP) Proxy Function

This document specifies a new Port Control Protocol (PCP) functional element: the PCP proxy. The PCP proxy relays PCP requests received from PCP clients to upstream PCP server(s). A typical deployment usage of this function is to help establish successful PCP communications for PCP clients that cannot be configured with the address of a PCP server located more than one hop away.

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

This document specifies a new Port Control Protocol (PCP) functional element: the PCP proxy. The PCP proxy relays PCP requests received from PCP clients to upstream PCP server(s). A typical deployment usage of this function is to help establish successful PCP communications for PCP clients that cannot be configured with the address of a PCP server located more than one hop away.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC7648",
  "number": 7648,
  "title_en": "Port Control Protocol (PCP) Proxy Function",
  "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 document specifies a new Port Control Protocol (PCP) functional element: the PCP proxy. The PCP proxy relays PCP requests received from PCP clients to upstream PCP server(s). A typical deployment usage of this function is to help establish successful PCP communications for PCP clients that cannot be configured with the address of a PCP server located more than one hop away.",
  "authors": [
    "S. Perreault",
    "M. Boucadair",
    "R. Penno",
    "D. Wing",
    "S. Cheshire"
  ],
  "organizations": [],
  "publication_date": "2015-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": "int",
  "area_ru": "Интернет",
  "working_group": "pcp",
  "source_draft": "draft-ietf-pcp-proxy-09",
  "page_count": 14,
  "doi": "10.17487/RFC7648",
  "keywords": [
    "NAT",
    "firewall",
    "CGN",
    "AFTR",
    "NAT64",
    "port forwarding",
    "pinholing",
    "port mapping",
    "external IP address",
    "discover port number",
    "running a server behind NAT",
    "NAT control",
    "NAT cascading",
    "DS-Lite",
    "incoming connection",
    "control outbound connection",
    "referral",
    "address referral",
    "ALG offload",
    "PCP client",
    "PCP server"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc7648/",
    "html": "https://www.rfc-editor.org/rfc/rfc7648.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc7648.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7648/"
  }
}