Re: [BEHAVE] Fwd: RFC 8158 on IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events and Next Steps on management

"Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com> Tue, 02 January 2018 15:05 UTC

Return-Path: <ssenthil@cisco.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 AACF3126CD8; Tue, 2 Jan 2018 07:05:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 vJ7zENjhHICL; Tue, 2 Jan 2018 07:05:41 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22793124BAC; Tue, 2 Jan 2018 07:05:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19596; q=dns/txt; s=iport; t=1514905541; x=1516115141; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=PTxAsyPnB6X7iO0Oj5tji2E+QKVSxCTZ6m5+hHgpq/8=; b=dL1nVNmPrDLZKBdjguZxzgodQthUf3Zba6cAsSh+FhKl28WGplPOEOMo eMtEFc+bDm10FxHFg80zv2Jez2+dOhZqgWGpw4UTSMimzcIe1KjCb11JT RO1zH4kEuNhujJ0R+aOjypIUwjsdaJTjBnuKxz10+p+x3TZM9gS+k11L/ M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DsAADDnkta/4QNJK1TChkBAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGCSnRmdCcHhACKJI8YggGJCIhRhVGCFQoYAQqFGAIahBY/GAE?= =?us-ascii?q?BAQEBAQEBAWsohSMBAQEBAwEBISsrEAIBCBEDAQINFwQDAgICHwYKARQJCAIEA?= =?us-ascii?q?Q0FFAcCBIkpTAMVELIGgicmhw8NgnABAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYQ?= =?us-ascii?q?MghKDPymDBYFJFIEORAEBgTYMCUIWgmExgjQFik8cjnaJLj0ChnyBBYg0hH6CF?= =?us-ascii?q?4YWhBCHQIpUglA+iHQCERkBgTsBHzmBT28VGSQqAYF+gmApgU54hjUPGIENgRY?= =?us-ascii?q?BAQE?=
X-IronPort-AV: E=Sophos; i="5.45,497,1508803200"; d="scan'208,217"; a="50783764"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jan 2018 15:05:40 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id w02F5d2p009300 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 2 Jan 2018 15:05:39 GMT
Received: from xch-aln-007.cisco.com (173.36.7.17) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 2 Jan 2018 09:05:39 -0600
Received: from xch-aln-007.cisco.com ([173.36.7.17]) by XCH-ALN-007.cisco.com ([173.36.7.17]) with mapi id 15.00.1320.000; Tue, 2 Jan 2018 09:05:39 -0600
From: "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, "behave@ietf.org" <behave@ietf.org>
CC: "draft-ietf-behave-syslog-nat-logging@ietf.org" <draft-ietf-behave-syslog-nat-logging@ietf.org>
Thread-Topic: [BEHAVE] Fwd: RFC 8158 on IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events and Next Steps on management
Thread-Index: AQHTemjnzRw9gfJ3tU2xANEarWarwaNg0kOA
Date: Tue, 2 Jan 2018 15:05:39 +0000
Message-ID: <09E1CA28-EF33-4C14-A5F7-780706DA6352@cisco.com>
References: <CAKKJt-eLnVT+2t5efgGKSO61rnLmad1S-5TczEgJahihbOvgnQ@mail.gmail.com>
In-Reply-To: <CAKKJt-eLnVT+2t5efgGKSO61rnLmad1S-5TczEgJahihbOvgnQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1d.0.161209
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.150.25.83]
Content-Type: multipart/alternative; boundary="_000_09E1CA28EF334C14A5F7780706DA6352ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/behave/JBP4qc8Zf1gRkpZ4PV3OpdgVku4>
Subject: Re: [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: Tue, 02 Jan 2018 15:05:44 -0000

Hi Spencer,
First of all, special thanks to you on ensuring that this draft sees the daylight!

I am personally interested in making sure that the syslog draft gets published so that the entire portfolio is complete, so I am willing to work on this.

Thanks
Senthil

From: Behave <behave-bounces@ietf.org>; on behalf of Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>;
Date: Thursday, December 21, 2017 at 9:34 AM
To: "behave@ietf.org"; <behave@ietf.org>;
Cc: "draft-ietf-behave-syslog-nat-logging@ietf.org"; <draft-ietf-behave-syslog-nat-logging@ietf.org>;
Subject: [BEHAVE] Fwd: RFC 8158 on IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events and Next Steps on management

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<mailto: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<mailto:ietf-announce@ietf.org>, rfc-dist@rfc-editor.org<mailto:rfc-dist@rfc-editor.org>
Cc: drafts-update-ref@iana.org<mailto:drafts-update-ref@iana.org>, rfc-editor@rfc-editor.org<mailto: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<mailto:ssenthil@cisco.com>,
                    repenno@cisco.com<mailto: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<mailto: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