IPFIX Information Elements for logging NAT Events
draft-ietf-behave-ipfix-nat-logging-13

Document Type Active Internet-Draft (individual)
Last updated 2017-04-26 (latest revision 2017-01-09)
Replaces draft-sivakumar-behave-nat-logging
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd Spencer Dawkins
Shepherd write-up Show (last changed 2016-10-10)
IESG IESG state RFC Ed Queue
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
RFC Editor RFC Editor state AUTH48
Behave                                                      S. Sivakumar
Internet-Draft                                                  R. Penno
Intended status: Standards Track                           Cisco Systems
Expires: July 13, 2017                                   January 9, 2017

           IPFIX Information Elements for logging NAT Events
                 draft-ietf-behave-ipfix-nat-logging-13

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.  The logs are essential in many cases 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
   log the information using proprietary formats and hence it is
   difficult to expect a consistent behavior.  The lack of a consistent
   way to log the data 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
   of NAT events.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 13, 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

Sivakumar & Penno         Expires July 13, 2017                 [Page 1]
Internet-Draft          IPFIX IEs for NAT logging           January 2017

   (http://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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Deployment  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Event based logging . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Logging of destination information  . . . . . . . . . . .   6
     4.2.  Information Elements  . . . . . . . . . . . . . . . . . .   6
     4.3.  Definition of NAT Events  . . . . . . . . . . . . . . . .   8
     4.4.  Quota exceeded Event types  . . . . . . . . . . . . . . .   9
     4.5.  Threshold reached Event types . . . . . . . . . . . . . .  10
     4.6.  Templates for NAT Events  . . . . . . . . . . . . . . . .  11
       4.6.1.  NAT44 create and delete session events  . . . . . . .  11
       4.6.2.  NAT64 create and delete session events  . . . . . . .  12
       4.6.3.  NAT44 BIB create and delete events  . . . . . . . . .  13
       4.6.4.  NAT64 BIB create and delete events  . . . . . . . . .  13
       4.6.5.  Addresses Exhausted event . . . . . . . . . . . . . .  14
       4.6.6.  Ports Exhausted event . . . . . . . . . . . . . . . .  14
       4.6.7.  Quota exceeded events . . . . . . . . . . . . . . . .  15
         4.6.7.1.  Maximum session entries exceeded  . . . . . . . .  15
         4.6.7.2.  Maximum BIB entries exceeded  . . . . . . . . . .  15
         4.6.7.3.  Maximum entries per user exceeded . . . . . . . .  15
         4.6.7.4.  Maximum active host or subscribers exceeded . . .  16
         4.6.7.5.  Maximum fragments pending reassembly exceeded . .  16
       4.6.8.  Threshold reached events  . . . . . . . . . . . . . .  17
         4.6.8.1.  Address pool high or low threshold reached  . . .  17
         4.6.8.2.  Address and port high threshold reached . . . . .  17
         4.6.8.3.  Per-user Address and port high threshold reached   18
Show full document text