Technical Summary
This document extends Port Control Protocol (PCP) with the ability to
associate a description with a PCP-instantiated mapping. It does so
by defining a new DESCRIPTION option.
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?
Nothing controversial.
Document Quality
It is expected that any implementation of RFC 6970 (PCP/UPnP-IGD
interop) would want this extension. One known implementation is
reported in http://tools.ietf.org/html/draft-boucadair-pcp-nat64-experiments-00#section-2.1.
Other than the document editor, the following people reviewed the document
during WGLC and all concluded the document had no substantive issues:
1) Dave Thaler (document shepherd, WG co-chair)
2) Tiru Reddy
3) Simon Perreault
4) Paul Selkirk
5) Reinaldo Penno (WG co-chair, co-author)
Personnel
Document Shepherd: Dave Thaler <dthaler@microsoft.com>
Responsible Area Director: Ted Lemon <ted.lemon@nominum.com>
RFC Editor Note:
Please replace paragraphs 4 and 5 of section three with the following new text.
OLD (in -05):
Because of the UDP payload limit of 1100 octets [RFC6887], the
configured maximum length MUST NOT exceed 1016 octets. The suggested
maximum length is 128 octets. If a PCP client includes a DESCRIPTION
option with a length exceeding the maximum length supported by the
PCP server, only the portion of the Description field fitting that
maximum length is stored by the PCP server and returned to the PCP
client in the response.
If the PCP server receives a DESCRIPTION option having a length which
does not exceed the maximum value configured, the PCP server MUST
record the complete sequence of the description text and MUST send
back to the PCP client the same DESCRIPTION option as the one
included in the request.
NEW:
A PCP server SHOULD be able to store at least 128 bytes for a description.
When the PCP server receives a DESCRIPTION option, it first stores
the value of the received Description field, truncating it if it cannot store
the entire value. The server MUST then send the stored value back to
the PCP client in the DESCRIPTION option in the response.