<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-pcp-proxy" target="https://datatracker.ietf.org/doc/html/draft-ietf-pcp-proxy-09">
   <front>
      <title>Port Control Protocol (PCP) Proxy Function</title>
      <author initials="S." surname="Perreault" fullname="Simon Perreault">
         <organization>Jive Communications</organization>
      </author>
      <author initials="M." surname="Boucadair" fullname="Mohamed Boucadair">
         <organization>France Telecom</organization>
      </author>
      <author initials="R." surname="Penno" fullname="Reinaldo Penno">
         <organization>Cisco</organization>
      </author>
      <author initials="D." surname="Wing" fullname="Dan Wing">
         <organization>Cisco</organization>
      </author>
      <author initials="S." surname="Cheshire" fullname="Stuart Cheshire">
         <organization>Apple</organization>
      </author>
      <date month="July" day="16" year="2015" />
      <abstract>
	 <t>This document specifies a new Port Control Protocol (PCP) functional element: the PCP proxy.  The PCP proxy relays PCP requests received from PCP clients to upstream PCP server(s).  A typical deployment usage of this function is to help establish successful PCP communications for PCP clients that cannot be configured with the address of a PCP server located more than one hop away.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-pcp-proxy-09" />
   
</reference>
