Sign in
Version 5.13.0, 2015-03-25
Report a bug

Port Control Protocol (PCP) Authentication Mechanism

Document type: Replaced Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2012-09-12 (latest revision 2012-03-11)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Replaced by draft-ietf-pcp-authentication
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:


An IPv4 or IPv6 host can use the Port Control Protocol (PCP) to flexibly manage the IP address and port mapping information on Network Address Translators (NATs) or firewalls, to facilitate communications with remote hosts. However, the un-controlled 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 proposes 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.


Margaret Wasserman <>
Sam Hartman <>
Dacheng Zhang <>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)