Re: [pcp] Fw:I-D Action: New Version Notification for draft-tsou-pcp-natcoord-08.txt

> -----Original Message-----
> From: Qiong [mailto:bingxuere@gmail.com]
> Sent: Thursday, November 01, 2012 5:11 PM
> To: Dan Wing
> Cc: Simon Perreault; pcp@ietf.org
> Subject: Re: [pcp] Fw:I-D Action: New Version Notification for draft-
> tsou-pcp-natcoord-08.txt
> 
> Dear Dan,
> 
> The learned port-set is only for restricted NAT on IPv4 packet.
> MAP_PORT_SET is sent using native IPv6, and so there is no restriction
> on the port-range.

Oh.

The draft doesn't say the PCP messages are always sent over IPv6.  Or,
I can't find that sentence.

-d

> As Simon said, it can use any UDP port on the
> internal address it already has.
> 
> Thanks for your comments :)
> 
> Best wishes
> Qiong
> 
> 
> 
> On Fri, Nov 2, 2012 at 6:40 AM, Dan Wing <dwing@cisco.com> wrote:
> 
> 
> 	> -----Original Message-----
> 	> From: Simon Perreault [mailto:simon.perreault@viagenie.ca]
> 	> Sent: Thursday, November 01, 2012 2:05 PM
> 	> To: Dan Wing
> 	> Cc: pcp@ietf.org
> 	> Subject: Re: [pcp] Fw:I-D Action: New Version Notification for
> draft-
> 	> tsou-pcp-natcoord-08.txt
> 	>
> 
> 	> Le 2012-11-01 21:53, Dan Wing a écrit :
> 	> >> Le 2012-11-01 15:49, Dan Wing a écrit :
> 	> >>> Ok.  Which UDP port does the CPE send that PCP request, if it
> does
> 	> >>> not yet already know the port range assigned to the CPE?
> 	> >>
> 	> >> Uh?
> 	> >
> 	> > Sorry, I meant to ask:
> 	> >
> 	> >    *from* which UDP port does the CPE send that PCP request.
> 	> >
> 	> > or can it use any source UDP port for its PCP request, or does
> it have
> 	> > to be one of its assigned UDP ports (which aren't yet assigned
> until
> 	> > PCP exchange)?
> 	>
> 	> That's what I understood. And the answer is still the same:
> 	>
> 	> Q: From which UDP port does the CPE send a MAP request?
> 	> A: From any UDP port on the internal address it already has.
> 	>
> 	> Q: From which UDP port does the CPE send a MAP_PORT_SET request?
> 	> A: From any UDP port on the internal address it already has.
> 	>
> 	> There must be something else I'm not getting...
> 
> 
> 	If it doesn't get (learn) that UDP port via PCP, how does it
> 	learn it?
> 
> 	-d
> 
> 
> 
> 	> Simon
> 	>
> 	> >> MAP gives one port.
> 	> >> MAP_PORT_SET gives a set of ports.
> 	> >>
> 	> >> MAP and MAP_PORT_SET have the same answer to your question.
> 	> >>
> 	> >> Simon
> 	> >> --
> 	> >> DTN made easy, lean, and smart -->
> http://postellation.viagenie.ca
> 	> >> NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
> 	> >> STUN/TURN server               --> http://numb.viagenie.ca
> 	> >> _______________________________________________
> 	> >> pcp mailing list
> 	> >> pcp@ietf.org
> 	> >> https://www.ietf.org/mailman/listinfo/pcp
> 	> >
> 	>
> 	>
> 	> --
> 	> DTN made easy, lean, and smart -->
> http://postellation.viagenie.ca
> 	> NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
> 	> STUN/TURN server               --> http://numb.viagenie.ca
> 
> 	_______________________________________________
> 	pcp mailing list
> 	pcp@ietf.org
> 	https://www.ietf.org/mailman/listinfo/pcp
> 
> 
> 
> 
> 
> --
> ==============================================
> Qiong Sun
> China Telecom Beijing Research Institude
> 
> 
> Open source code:
> lightweight 4over6: http://sourceforge.net/projects/laft6/
> PCP-natcoord: http://sourceforge.net/projects/pcpportsetdemo/
> ===============================================
> 
> 