IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events
RFC 8158
Document | Type |
RFC - Proposed Standard
(December 2017; No errata)
Was draft-ietf-behave-ipfix-nat-logging (individual)
|
|
---|---|---|---|
Authors | Senthil Sivakumar , Reinaldo Penno | ||
Last updated | 2017-12-20 | ||
Replaces | draft-sivakumar-behave-nat-logging | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | Spencer Dawkins | ||
Shepherd write-up | Show (last changed 2016-10-10) | ||
IESG | IESG state | RFC 8158 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Spencer Dawkins | ||
Send notices to | "Spencer Dawkins" <spencerdawkins.ietf@gmail.com> | ||
IANA | IANA review state | IANA OK - Actions Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) S. Sivakumar Request for Comments: 8158 R. Penno Category: Standards Track Cisco Systems ISSN: 2070-1721 December 2017 IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events Abstract 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. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8158. Sivakumar & Penno Standards Track [Page 1] RFC 8158 IPFIX IEs for NAT Logging December 2017 Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 5 2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Deployment . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Event-Based Logging . . . . . . . . . . . . . . . . . . . . . 6 4.1. Logging Destination Information . . . . . . . . . . . . . 6 4.2. Information Elements . . . . . . . . . . . . . . . . . . 7 4.3. Definition of NAT Events . . . . . . . . . . . . . . . . 11 4.4. Quota Exceeded Event Types . . . . . . . . . . . . . . . 12 4.5. Threshold Reached Event Types . . . . . . . . . . . . . . 13 4.6. Templates for NAT Events . . . . . . . . . . . . . . . . 14 4.6.1. NAT44 Session Create and Delete Events . . . . . . . 14 4.6.2. NAT64 Session Create and Delete Events . . . . . . . 15 4.6.3. NAT44 BIB Create and Delete Events . . . . . . . . . 16 4.6.4. NAT64 BIB Create and Delete Events . . . . . . . . . 16 4.6.5. Addresses Exhausted Event . . . . . . . . . . . . . . 17 4.6.6. Ports Exhausted Event . . . . . . . . . . . . . . . . 17 4.6.7. Quota Exceeded Events . . . . . . . . . . . . . . . . 18 4.6.7.1. Maximum Session Entries Exceeded . . . . . . . . 18 4.6.7.2. Maximum BIB Entries Exceeded . . . . . . . . . . 18 4.6.7.3. Maximum Entries per User Exceeded . . . . . . . . 19 4.6.7.4. Maximum Active Hosts or Subscribers Exceeded . . 19 4.6.7.5. Maximum Fragments Pending Reassembly Exceeded . . 19 4.6.8. Threshold Reached Events . . . . . . . . . . . . . . 20 4.6.8.1. Address Pool High or Low Threshold Reached . . . 20 4.6.8.2. Address and Port Mapping High Threshold Reached . 21 4.6.8.3. Address and Port Mapping per User High Threshold Reached . . . . . . . . . . . . . . . . . . . . . 21 4.6.8.4. Global Address Mapping High Threshold Reached . . 22 4.6.9. Address Binding Create and Delete Events . . . . . . 22 Sivakumar & Penno Standards Track [Page 2] RFC 8158 IPFIX IEs for NAT Logging December 2017Show full document text