Last Call Review of draft-ietf-pcp-proxy-08

Request Review of draft-ietf-pcp-proxy
Requested rev. no specific revision (document currently at 09)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2015-07-07
Requested 2015-06-23
Authors Simon Perreault, Mohamed Boucadair, Reinaldo Penno, Dan Wing, Stuart Cheshire
Draft last updated 2015-07-13
Completed reviews Genart Last Call review of -08 by Joel Halpern (diff)
Secdir Last Call review of -08 by Samuel Weiler (diff)
Opsdir Last Call review of -08 by Mehmet Ersue (diff)
Assignment Reviewer Mehmet Ersue 
State Completed
Review review-ietf-pcp-proxy-08-opsdir-lc-ersue-2015-07-13
Reviewed rev. 08 (document currently at 09)
Review result Ready
Review completed: 2015-07-13


I reviewed the document "Port Control Protocol (PCP) Proxy Function" (draft-ietf-pcp-proxy-08.txt) as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were
written primarily for the benefit of the operational area directors.  Document editors and WG chairs should treat these comments just like any other last call comments.


Intended status: Standards Track

Current IESG state: IESG Evaluation 

IANA Review State: IANA OK - No Actions Needed 


Summary: The 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).  


There are no nits in the draft.


I don't see any issues from the operations and management pov.


Not being an insider I just wonder which MIB or YANG module is used to configure such a PCP proxy?

Are we prepared for this?