RFC 8158: IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events

Network operators require NAT devices to log events like creation and deletion of translations and information about the resources that the NAT device is…

Read RFC 8158 on the RFC Editor

Outgoing relationships (15 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 4787: Network Address Translation (NAT) Behavioral Requirements for Unicast UDP
Normative reference — RFC 6146: Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
Normative reference — RFC 7011: Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information
Normative reference — RFC 5382: NAT Behavioral Requirements for TCP
Normative reference — RFC 6888: Common Requirements for Carrier-Grade NATs (CGNs)
Normative reference — RFC 6302: Logging Recommendations for Internet-Facing Servers
Normative reference — RFC 7659: Definitions of Managed Objects for Network Address Translators (NATs)
Informative reference — RFC 8126: Guidelines for Writing an IANA Considerations Section in RFCs
Informative reference — RFC 791: Internet Protocol
Informative reference — RFC 3022: Traditional IP Network Address Translator (Traditional NAT)
Informative reference — RFC 2663: IP Network Address Translator (NAT) Terminology and Considerations
Informative reference — RFC 5424: The Syslog Protocol
Informative reference — RFC 3234: Middleboxes: Taxonomy and Issues

Incoming relationships (1 related RFC)

Informatively referenced by — RFC 9710: Simple Fixes to the IP Flow Information Export (IPFIX) Entities IANA Registry