[BEHAVE] Fwd: RFC 8158 on IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events and Next Steps on management
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 21 December 2017 14:34 UTC
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBE8E120724; Thu, 21 Dec 2017 06:34:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 bR7cQj_0bgQz; Thu, 21 Dec 2017 06:34:50 -0800 (PST)
Received: from mail-yb0-x22d.google.com (mail-yb0-x22d.google.com [IPv6:2607:f8b0:4002:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46960124D68; Thu, 21 Dec 2017 06:34:50 -0800 (PST)
Received: by mail-yb0-x22d.google.com with SMTP id 129so7620978ybe.5; Thu, 21 Dec 2017 06:34:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=2s8lI/g4ghKRqkHKfpnxsT9Z0M258WCIcO8SfaPnn8k=; b=ANlgJCrMobGSV9HgNbejhLGiIDQ/jNa/fkofUyMZIokW88wmlNHA55ip18CMjf36zH g/ErXz2f5JzX6HFFsSIRaAB6Z8j+d0W++HczZG9Z+85iYH3IK7x8RGrcWaiPaRI9GH5m CBBtAoHxl/KtPSAu1R/XqgSTyoiyw16qR9VbsBCwjCHkyER+P+dVW9GR1kYNgtwD8m+R /r9Bw06WpLl8ijSduEEQaTnrqtXHxjkzP40PzpoF5T4P1N9GFXnoJkcrJvlAFxwB42EN 1qolLhlXY6BlnNDRajbv2ijaFVY/lgqe8aZRNlypq624k3/KACGsSPBy7GmSVhInBttm ZTxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=2s8lI/g4ghKRqkHKfpnxsT9Z0M258WCIcO8SfaPnn8k=; b=tIRO/Tzt7VZCOXc84++1E8NHZvQbMTnlguFncvzSgRWluxz8tVlPZ+CKYJJ2NL8CPi v7ZAlAHuAfT/tS9xadk27UaXcA/JuIa5EHqGi0/50AqfCWNcabWGKQCK9AI/NduneD+W MpYvCC1k033xQ/N+OwVYkIfyDbqQrH6DmcOn9BBSPpy/RuVvKuiFxfaynHVe2hGEpeTR xEixlCWGJQiSkWI9nSTwmp/gIo0M19xEBler51owhS7u5updI4A3wGumyrgtHxFg+OUg IK01/F914CplgjOCj3LvrlIloqfJ0mg4Ovk6z3sqCXc6ahZmqG4FNqSUiPOBgPXxmSMc BxqA==
X-Gm-Message-State: AKGB3mJZNyBYsmBHVtMG1jFVUzZ6oFinVhYfSacuDR9Y3iBgIfaTB8/w yuPfj1Zx+6Ueopfotpg1YI6tvMHnLArAhZleKD4HNQ==
X-Google-Smtp-Source: ACJfBouq9GFub1h6bNqZA2Jt3ZHPTxqOGsTR5u9TCLhnBJjmHU2uAVbH5YtcZgWIQ4cFCwHig8yJG0XmQqhghnwFjE0=
X-Received: by 10.37.45.71 with SMTP id s7mr7945340ybe.354.1513866889103; Thu, 21 Dec 2017 06:34:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.175.74 with HTTP; Thu, 21 Dec 2017 06:34:48 -0800 (PST)
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 21 Dec 2017 08:34:48 -0600
Message-ID: <CAKKJt-eLnVT+2t5efgGKSO61rnLmad1S-5TczEgJahihbOvgnQ@mail.gmail.com>
To: behave@ietf.org
Cc: draft-ietf-behave-syslog-nat-logging@ietf.org
Content-Type: multipart/alternative; boundary="f4030435ce9c298db90560da9ace"
Archived-At: <https://mailarchive.ietf.org/arch/msg/behave/vPK9SO-3voYrONf7jYuZFYdOya4>
Subject: [BEHAVE] Fwd: RFC 8158 on IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events and Next Steps on management
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/behave/>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Dec 2017 14:34:53 -0000
I forward this to celebrate the removal of the longest delay in AUTH-48 from the list the RFC Editor sends to the IESG on a regular basis, and to thank Senthil and Reinaldo for bravery above and beyond the call of duty in getting this one out. Thanks to all who contributed. I have one more AD-sponsored BEHAVE leftover in my queue - https://datatracker.ietf.org/doc/draft-ietf-behave-syslog-nat-logging/. Are we ready to do this one? It couldn't possibly take longer ... Thanks for your thoughts. Spencer, as perhaps the worst AD on the current IESG (and if some of your thoughts include "it's time to re-read https://tools.ietf.org/html/rfc7437#section-7", I wouldn't be a bit surprised) ---------- Forwarded message ---------- From: <rfc-editor@rfc-editor.org> Date: Wed, Dec 20, 2017 at 4:08 PM Subject: RFC 8158 on IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org 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
- [BEHAVE] Fwd: RFC 8158 on IP Flow Information Exp… Spencer Dawkins at IETF
- Re: [BEHAVE] Fwd: RFC 8158 on IP Flow Information… Senthil Sivakumar (ssenthil)