Technical Summary
This document describes the framework, messages, and procedures for
the Diameter Network address and port translation Control
Application. This Diameter application allows per endpoint control
of Network Address Translators and Network Address and Port
Translators, which are added to networks to cope with IPv4-address
space completion. This Diameter application allows external devices
to configure and manage a Network Address Translator device -
expanding the existing Diameter-based AAA and policy control
capabilities with a Network Address Translators and Network Address
and Port Translators control component. These external devices can
be network elements in the data plane such as a Network Access
Server, or can be more centralized control plane devices such as AAA-
servers. This Diameter application establishes a context to commonly
identify and manage endpoints on a gateway or server, and a Network
Address Translator and Network Address and Port Translator device.
This includes, for example, the control of the total number of
Network Address Translator bindings allowed or the allocation of a
specific Network Address Translator binding for a particular
endpoint. In addition, it allows Network Address Translator devices
to provide information relevant to accounting purposes.
Working Group Summary
The document spent well over a year in the WG and has had an intensive
review in the WG. However, the authors
actively kept the document progressing and improving. The document
is a result of collaborative WG work.
Document Quality
There is currently no publicly announced implementations of the
protocol. The document itself is solid, well written and in places
goes into level of details not often seen in Diameter Application
describing documents.
Personnel
Jouni Korhonen is the Document Shepherd for this document.
Dan Romascanu was the first responsible Area Director.
Benoit Claise is the current responsible Area Director.
RFC Editor Notes
After discussing with some of the authors, this document should
reference RFC3588bis and not RFC3588. Therefore, this document
should be considered part of the cluster 133.