RFC 6736: Diameter Network Address and Port Translation Control Application
In plain English — editorial summary, not part of the RFC
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 depletion. This Diameter application allows external devices to configure and manage a Network Address Translator device -- expanding the existing Diameter-based Authentication, Authorization, and Accounting (AAA) and policy control capabilities with a Network Address Translator and Network Address and Port Translator 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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6736
- Published
- October 2012
- Authors
- F. Brockners; S. Bhandari; V. Singh; V. Fajardo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 58
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7648Port Control Protocol (PCP) Proxy FunctionCurrent
September 2015
- RFC 6598IANA-Reserved IPv4 Prefix for Shared Address SpaceCurrent
April 2012
- RFC 6888Common Requirements for Carrier-Grade NATs (CGNs)Current
April 2013
- RFC 6970Universal Plug and Play (UPnP) Internet Gateway Device - Port Control Protocol Interworking Function (IGD-PCP IWF)Current
July 2013
- RFC 7659Definitions of Managed Objects for Network Address Translators (NATs)Current
October 2015
- RFC 7723Port Control Protocol (PCP) Anycast AddressesCurrent
January 2016
- RFC 7857Updates to Network Address Translation (NAT) Behavioral RequirementsCurrent
April 2016
- RFC 8045RADIUS Extensions for IP Port Configuration and ReportingCurrent
January 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?