RFC 8158: IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events
In plain English — editorial summary, not part of the RFC
Network operators require NAT devices to log events like creation and deletion of translations and information about the resources that the NAT device is managing. In many cases, the logs are essential to identify an attacker or a host that was used to launch malicious attacks and for various other purposes of accounting. Since there is no standard way of logging this information, different NAT devices use proprietary formats; hence, it is difficult to expect consistent behavior. This lack of standardization makes it difficult to write the Collector applications that would receive this data and process it to present useful information. This document describes the formats for logging NAT events.
Document record
- Document ID
- RFC8158
- Published
- December 2017
- Authors
- S. Sivakumar; R. Penno
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 34
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7961Transparent Interconnection of Lots of Links (TRILL): Interface Addresses APPsub-TLVCurrent
August 2016
- RFC 6570URI TemplateCurrent
March 2012
- RFC 5697Other Certificates ExtensionCurrent
November 2009
- RFC 5249Templates for Internet-Drafts Containing MIB ModulesCurrent
July 2008
- RFC 7703Experience with Testing of Mapping of Address and Port Using Translation (MAP-T)Current
November 2015
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?