%% You should probably cite rfc7652 instead of this I-D. @techreport{ietf-pcp-authentication-05, number = {draft-ietf-pcp-authentication-05}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-pcp-authentication/05/}, author = {Margaret Cullen and Sam Hartman and Dacheng Zhang}, title = {{Port Control Protocol (PCP) Authentication Mechanism}}, pagetotal = 26, year = 2014, month = aug, day = 23, abstract = {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.}, }