RFC 8158 on IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events
rfc-editor@rfc-editor.org Wed, 20 December 2017 22:08 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76EF41205D3 for <ietf-announce@ietfa.amsl.com>; Wed, 20 Dec 2017 14:08:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3-ZrqMI__0Jf for <ietf-announce@ietfa.amsl.com>; Wed, 20 Dec 2017 14:08:41 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7323E1201F2 for <ietf-announce@ietf.org>; Wed, 20 Dec 2017 14:08:41 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4CA65B81433; Wed, 20 Dec 2017 14:08:39 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8158 on IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20171220220839.4CA65B81433@rfc-editor.org>
Date: Wed, 20 Dec 2017 14:08:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/RzSU5LnJCrJhX3rT4IwLVlrB3Kg>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Dec 2017 22:08:43 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8158
Title: IP Flow Information Export (IPFIX)
Information Elements for Logging NAT Events
Author: S. Sivakumar,
R. Penno
Status: Standards Track
Stream: IETF
Date: December 2017
Mailbox: ssenthil@cisco.com,
repenno@cisco.com
Pages: 34
Characters: 78399
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-behave-ipfix-nat-logging-13.txt
URL: https://www.rfc-editor.org/info/rfc8158
DOI: 10.17487/RFC8158
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.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC