Subject: Re: [pcp] draft-ietf-pcp-proxy-01

From: "Zhouqian (Cathy)" <[email-masked]>
Date: Thu, 20 Dec 2012 08:27:44 +0000

Dear Med and all,
When looking over section 10 of this document, there is one more advanced feature in my mind that may be added for PCP proxy. 
In [I-D.ietf-pcp-base], the PCP server could send the ANNOUNCE response to both multicast and unicast addresses. For multicast address case, it only applies when the network is layer2 network and there is a multicast link between PCP client and PCP server. If there is no multicast link between PCP client and PCP server, one access router (e.g., PCP proxy) may perform the multicast address/unicast address conversion function. When the PCP proxy receives the ANNOUNCE message from the PCP server, it replaces the unicast address of itself with the PCP client's multicast address and sends ANNOUNCE message to the multicast address. It is required that the network between the PCP proxy and the PCP client is layer2. 
Any comments?

Best Regards,
Cathy

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]] On Behalf Of
> [email-masked]
> Sent: Friday, August 17, 2012 5:33 PM
> To: [email-masked]
> Subject: [pcp] draft-ietf-pcp-proxy-01
> 
> Dear all,
> 
> A new version is now available online:
> http://tools.ietf.org/html/draft-ietf-pcp-proxy-01
> 
> The main changes in -01 are as follows:
> 
> * The reference architecture is updated: the PCP proxy is not restricted to
> the CP router deployment case.
> * Add a new section to specify the behaviour when the PCP Proxy is not
> co-located with a NAT function
> * Add a new section for mappings repair
> * More discussion for the multiple PCP Servers scenario
> * Text is cleanup
> 
> A detailed diff is available here:
> 
>  http://www.ietf.org/rfcdiff?url2=draft-ietf-pcp-proxy-01
> 
> Please review this new version and provide input.
> 
> Cheers,
> Med
> _______________________________________________
> pcp mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/pcp