metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 7652: Port Control Protocol (PCP) Authentication Mechanism

In plain English — editorial summary, not part of the RFC

An IPv4 or IPv6 host can use the Port Control Protocol (PCP) to flexibly manage the IP address-mapping and port-mapping information on Network Address Translators (NATs) or firewalls to facilitate communication with remote hosts. However, the uncontrolled generation or deletion of IP address mappings on such network devices may cause security risks and should be avoided. In some cases, the client may need to prove that it is authorized to modify, create, or delete PCP mappings. This document describes an in-band authentication mechanism for PCP that can be used in those cases. The Extensible Authentication Protocol (EAP) is used to perform authentication between PCP devices. This document updates RFC 6887.

Document record

Document ID
RFC7652
Published
September 2015
Authors
M. Cullen; S. Hartman; D. Zhang; T. Reddy
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
34
Also known as
—
Updates:
RFC 6887

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/7652-port-control-protocol-pcp-authentication-mechanism