Re: [pcp] WG Call for Adoption: draft-tsou-pcp-natcoord-09

Dear Dan,

Let me explain the deployment senario of NATCOORD here.

The major functionality of NATCOORD is to get the External Port-Set and
External public address for the PCP client. It is applied to the senario
where NAT is offloaded to the home gateway and the PCP-controlled device
does not run NAT(or port-mapping). The home gateway will restrict the
source port into the external port-set, and therefore the PCP-controlled
device does not need to do port-mapping anymore. Currently, there are
several candidate solutions can work with it, including lightweight 4over6,
PRR, and SLNAT44.

NATCOORD does not work with ordinary CGN because there is no need for the
home gateway to get a range of ports if it does not do port restriction.

We will clarify it in the document. Thanks a lot for your consideration !

Best wishes
Qiong

On Sat, Jan 5, 2013 at 10:09 AM, Dan Wing <dwing@cisco.com> wrote:

> > -----Original Message-----
> > From: Qiong [mailto:bingxuere@gmail.com]
> > Sent: Friday, January 04, 2013 1:55 AM
> > To: Dan Wing
> > Cc: Reinaldo Penno (repenno); pcp@ietf.org
> > Subject: Re: [pcp] WG Call for Adoption: draft-tsou-pcp-natcoord-09
> >
> > Dear Dan,
> >
> >
> > Thanks for your comments. Please see inline ~~
> >
> >
> >
> > On Thu, Jan 3, 2013 at 9:39 AM, Dan Wing <dwing@cisco.com> wrote:
> >
> >
> >       > -----Original Message-----
> >       > From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On
> > Behalf Of
> >       > Reinaldo Penno (repenno)
> >       > Sent: Wednesday, January 02, 2013 3:35 PM
> >       > To: pcp@ietf.org
> >       > Subject: [pcp] WG Call for Adoption: draft-tsou-pcp-natcoord-09
> >       >
> >
> >
> > [Qiong] Thanks for your suggestion. We will clarify it more clearly.
> > PCP_NATCOORD can not only work with draft-cui-softwire-b4-translated-ds-
> > lite, but can also work with PRR (either using internal IPv4 address, or
> > IPv6 address).
>
> Can it work with a CGN?
>

>
> > In the current draft, "the PCP server for MAP_PORT_SET
> > will not run NAT" because the home gateway will run NAT instead of PCP
> > server, but it would be easy to modify the draft to address the use
> > cases which Reinaldo has pointed out in http://www.ietf.org/mail-
> > archive/web/pcp/current/msg02664.html. The WG can decide which
> > applicabilities should go in it when we agree that we should start work
> > on this port-set Opcode.
>
> With the current document text, I cannot understand what sort of
> deployments where NATCOORD can or cannot be used.  Until I understand
> that, I can't decide if this document is a good idea or a bad idea.
>
> > For the title and content in section 1 and 2, we will take reconsider it
> > once the applicability of MAP_PORT_SET has been determined by the WG.
> >
> >
> >
> >       Nit: Figure 2 shows a 24 bit Reserved field, but the description
> >       says it is 16 bits.  Also, Figure 2 has a cut/paste mistake
> >       with Suggested Port Set Index (should be Assigned Port Set Index).
> >
> >
> > [Qiong] Thanks ! We will fix it.
> >
> >
> >
> >       What is the status of draft-cui-softwire-b4-translated-ds-lite in
> >       SOFTWIRE?
> >
> >
> > [Qiong] As far as I know, the concensus from the Atlanta meeting is that
> > draft-cui-softwire-b4-translated-ds-lite would be moved forward after
> > the softwire WG has a unified CPE draft covering both lightweight 4over6
> > and MAP.
>
> -d
>
> >
> >
> > Hope it clarifies. Thanks !
> >
> >
> > Best wishes
> > Qiong
> >
> >
> >
> >       -d
> >
> >
> >
> >       > The call for adoption ends 16th January 2013.
> >       >
> >       > Thanks,
> >       >
> >       >
> >       >
> >       >
> >       >
> >       >
> >       >
> >       > _______________________________________________
> >       > pcp mailing list
> >       > pcp@ietf.org
> >       > https://www.ietf.org/mailman/listinfo/pcp
> >
> >       _______________________________________________
> >       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/
> > ===============================================
> >
>
>
>

-- 
==============================================
Qiong Sun
China Telecom Beijing Research Institude

Open source code:
lightweight 4over6: *http://sourceforge.net/projects/laft6/*
PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/ *
===============================================