Browse Prior Art Database

Port Control Protocol (PCP) Authentication Mechanism (RFC7652) Disclosure Number: IPCOM000244993D
Original Publication Date: 2015-Sep-01
Included in the Prior Art Database: 2016-Feb-05
Document File: 68 page(s) / 78K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Cullen: AUTHOR [+4]


Using the Port Control Protocol (PCP) [RFC6887], an application can flexibly manage the IP address-mapping information on its network address translators (NATs) and firewalls and can control their policies in processing incoming and outgoing IP packets. Because NATs and firewalls both play important roles in network security architectures, there are many situations in which authentication and access control are required to prevent unauthorized users from accessing such devices. This document defines a PCP security extension that enables PCP servers to authenticate their clients with the Extensible Authentication Protocol (EAP). The EAP messages are encapsulated within PCP messages during transmission.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 3% of the total text.

Internet Engineering Task Force (IETF)                         M. Cullen Request for Comments: 7652                                    S. Hartman Updates: 6887                                          Painless Security Category: Standards Track                                       D. Zhang ISSN: 2070-1721                                                                 T. Reddy                                                                    Cisco                                                           September 2015

           Port Control Protocol (PCP) Authentication Mechanism


   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

 Cullen, et al.               Standards Track                    [Page 1]
 RFC 7652                   PCP Authentication             September 2015

 Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    ( in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions...