Browse Prior Art Database

Port Control Protocol (PCP) Anycast Addresses (RFC7723) Disclosure Number: IPCOM000245076D
Original Publication Date: 2016-Jan-01
Included in the Prior Art Database: 2016-Feb-08
Document File: 18 page(s) / 21K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Kiesel: AUTHOR [+2]


The Port Control Protocol (PCP) [RFC6887] provides a mechanism to control how incoming packets are forwarded by upstream devices such as Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers (NAT64), Network Address Translation from IPv4 to IPv4 (NAT44), and IPv6 and IPv4 firewall devices. Furthermore, it provides a mechanism to reduce application keepalive traffic [PCP-OPTIMIZE]. The PCP base protocol document [RFC6887] specifies the message formats used, but the address to which a client sends its request is either assumed to be the default router (which is appropriate in a typical single-link residential network) or has to be configured otherwise via some external mechanism, such as a configuration file or a DHCP option [RFC7291].

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

Internet Engineering Task Force (IETF)                         S. Kiesel Request for Comments: 7723                       University of Stuttgart Category: Standards Track                                       R. Penno ISSN: 2070-1721                                      Cisco Systems, Inc.                                                             January 2016

              Port Control Protocol (PCP) Anycast Addresses


   The Port Control Protocol (PCP) anycast addresses enable PCP clients    to transmit signaling messages to their closest PCP-aware on-path    NAT, firewall, or other middlebox without having to learn the IP    address of that middlebox via some external channel.  This document    establishes one well-known IPv4 address and one well-known IPv6    address to be used as PCP anycast addresses.

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

Copyright Notice

   Copyright (c) 2016 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 with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Kiesel & Penno               Standards Track                    [Page 1]
 RFC 7723                  PCP Anycast Addresses             January 2016

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

   2.  PCP Server Discovery Based on Well-Known IP Address . . . . .   3

     2.1.  PCP Discovery Client Behavior . . . . . . . . . . . . . .   3

     2.2.  PCP Discovery Server Behavior . . . . . . . . . . . . . .   3

   3.  Deployment Considerations . . . . . . . . . . . . . . . . . .  ...