Skip to main content

Port Control Protocol (PCP) Extension for Port-Set Allocation
draft-ietf-pcp-port-set-13

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: brian@innovationslab.net, rfc-editor@rfc-editor.org, "The IESG" <iesg@ietf.org>, draft-ietf-pcp-port-set@ietf.org, pcp@ietf.org, rapenno@yahoo.com, pcp-chairs@ietf.org
Subject: Protocol Action: 'Port Control Protocol (PCP) Extension for Port Set Allocation' to Proposed Standard (draft-ietf-pcp-port-set-13.txt)

The IESG has approved the following document:
- 'Port Control Protocol (PCP) Extension for Port Set Allocation'
  (draft-ietf-pcp-port-set-13.txt) as Proposed Standard

This document is the product of the Port Control Protocol Working Group.

The IESG contact persons are Brian Haberman and Terry Manderson.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pcp-port-set/


Ballot Text

Technical Summary

   This document defines an extension to the Port Control Protocol (PCP)
   allowing clients to manipulate sets of ports as a whole.  This is
   accomplished by a new MAP option: PORT_SET.

Working Group Summary

  Was there anything in WG process that is worth noting? For 
  example, was there controversy about particular points or 
  were there decisions where the consensus was particularly 
  rough?

No

Document Quality

  Are there existing implementations of the protocol? 

Yes, two implementations. 

Have a significant number of vendors indicated their plan to 
implement the specification? 

None besides the two implementations discussed during review.

Are there any reviewers that  merit special mention as having
done a thorough review,   e.g., one that resulted in important
changes or a  conclusion that the document had no substantive issues? 

Dan Wing and Dave Thaler did a thorough review

Personnel

  Who is the Document Shepherd? 

Reinaldo Penno

Who is the Responsible Area Director?

Brian Haberman <brian@innovationslab.net>

RFC Editor Note