Re: [pcp] WGLC: draft-ietf-pcp-proxy-06 comments due by FEB 19

I am doing the document shepherd proto writeup for this doc and have a few
comments.

Section 1.1:
> likely to be more than on NAT on the path between client machines and

s/more than on/more than one/

Section 1.2:
Is it worth noting that the pcp-anycast draft is an alternate solution to this
same use case?

Section 3.2:
This section's wording is a bit confusing.   Section 1 explained the reference
model of back-to-back client and server.  So termination would occur when
either
a) the request gets to a server that does not have the PCP proxy functional element,
or
b) it gets to a PCP proxy whose PCP client has no PCP servers reachable 
(e.g. none configured and no default routers that respond to PCP)
and thus has nothing to forward to.
No?

The two examples currently in 3.2 are merely ways a NAT gateway (but
a PCP proxy could be a firewall or something other than a NAT...) could
choose to enable or disable a PCP proxy functional element and hence
toggle between a and b above.   But the PCP speaker might not be a NAT
gateway, or it might not implement a PCP proxy at all, or it might implement one
but not be "configured to know it's the outermost" but rather use rule b above.
So I think section 3.2 needs further elaboration as noted above.

Section 3.6:
I think the reference to Zone ID [I-D.penno-pcp-zones] should probably
reference the Third Party ID Option [I-D.ietf-pcp-third-party-id-option].

Section 5:
> Section 3.3 specifies the cases where a THIRD_PARTY option is
> inserted the PCP Proxy.  In those cases, means to prevent a malicious

s/inserted/inserted by/

> THIRD_PARTY option MUST NOT be enabled unless the network on which

Grammar: s/option/options/

>   dropped (or in the case of an unknown Option which is not mandatory-
>   to-process the Option be removed) if it is not compatible with

s/Option be/Option SHOULD be/

Dave

> -----Original Message-----
> From: pcp [mailto:pcp-bounces@ietf.org] On Behalf Of Dave Thaler
> Sent: Thursday, February 5, 2015 12:24 PM
> To: pcp@ietf.org
> Subject: [pcp] WGLC: draft-ietf-pcp-proxy-06 comments due by FEB 19
> 
> This email initiates a Working Group Last Call on it to conclude on Thursday,
> February 19th.
> Please send comments to the list.
> 
> As a reminder, when responding to a WGLC, what we chairs are looking for is
> a statement about document quality (not really about whether the
> mechanism should move forward).
> That is, state whether you think the document is ready as is, or if not, what
> issues you see.
> 
> Thanks,
> Dave
> 
> -----Original Message-----
> From: pcp [mailto:pcp-bounces@ietf.org] On Behalf Of internet-
> drafts@ietf.org
> Sent: Wednesday, December 17, 2014 12:53 AM
> To: i-d-announce@ietf.org
> Cc: pcp@ietf.org
> Subject: [pcp] I-D Action: draft-ietf-pcp-proxy-06.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Port Control Protocol Working Group of the
> IETF.
> 
>         Title           : Port Control Protocol (PCP) Proxy Function
>         Authors         : Simon Perreault
>                           Mohamed Boucadair
>                           Reinaldo Penno
>                           Dan Wing
>                           Stuart Cheshire
> 	Filename        : draft-ietf-pcp-proxy-06.txt
> 	Pages           : 12
> 	Date            : 2014-12-17
> 
> Abstract:
>    This document specifies a new PCP functional element denoted as a 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 can not be configured with the address of a PCP server
>    located more than one hop away.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-pcp-proxy/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-pcp-proxy-06
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-pcp-proxy-06
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> 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