Re: Last Call: <draft-ietf-behave-ipfix-nat-logging-06.txt> (IPFIX Information Elements for logging NAT Events)

"Senthil Sivakumar (ssenthil)" <> Fri, 12 February 2016 23:42 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 63C541ACD24; Fri, 12 Feb 2016 15:42:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Status: No, score=-14.501 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id R_Z5a7w8oWAc; Fri, 12 Feb 2016 15:42:23 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 553DA1ACD1F; Fri, 12 Feb 2016 15:42:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=27004; q=dns/txt; s=iport; t=1455320543; x=1456530143; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=KP4oChXnHasHQRZYrAAs7gLP43eINk3+pa49M9HHCxo=; b=MhYbsKH+i98NNsXmAegEvdXjfMBdeG4MvxGtGQmSk1tPyWmULjE0pZrm guZNbjPPzp6+oBJ+UZpPU2keV25WoPmxiDCPOpOSNx+GfhaYDGTTwijL8 WvgD3twk25sjZfi74VnzD1QKqvXGFQztDvlyYN9chv5csVqwFfhVuj6tR 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.22,437,1449532800"; d="scan'208,217";a="237323320"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 12 Feb 2016 23:42:14 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id u1CNgEGe004302 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 12 Feb 2016 23:42:14 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 12 Feb 2016 17:42:13 -0600
Received: from ([]) by ([]) with mapi id 15.00.1104.009; Fri, 12 Feb 2016 17:42:13 -0600
From: "Senthil Sivakumar (ssenthil)" <>
To: Paul Aitken <>, "" <>
Subject: Re: Last Call: <draft-ietf-behave-ipfix-nat-logging-06.txt> (IPFIX Information Elements for logging NAT Events)
Thread-Topic: Last Call: <draft-ietf-behave-ipfix-nat-logging-06.txt> (IPFIX Information Elements for logging NAT Events)
Thread-Index: AQHRZNm5lzhUvHrQNUCIztsT3jxre58pJQsA
Date: Fri, 12 Feb 2016 23:42:13 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_D2E3BF4A168243ssenthilciscocom_"
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Approved-At: Tue, 16 Feb 2016 08:13:24 -0800
Cc: "" <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 12 Feb 2016 23:42:27 -0000

Hi Paul,
Thanks for taking the time to do a detailed review. Please see inline for [Senthil]. I have incorporated most of your comments,
I have a few questions embedded inline.


From: Paul Aitken <<>>
Date: Thursday, February 11, 2016 at 9:36 AM
To: "<>" <<>>
Cc: "<>" <<>>
Subject: Re: Last Call: <draft-ietf-behave-ipfix-nat-logging-06.txt> (IPFIX Information Elements for logging NAT Events)

Section 1, second paragraph:

   The IPFIX Information elements that are NAT specific are created with
   NAT terminology.  In order to avoid creating duplicate IE's, IE's
   that are reused if they convey the same meaning.

Capitalise "Elements" and remove the redundant "that" in "that are reused".

The plural of "IE" is "IEs". See section 5 of RFC 7012. Please s/IE's/IE/ throughout the draft.

The draft defines "Information Element (IE)" in section 1 and "Information Elements (IEs)" in section 2. There's no need to repeat (IEs) in sections 2 and 5.2.

[Senthil] Ok, done.

Section 2, first paragraph:

   This document details
   the IPFIX Information Elements(IEs) that MUST be logged by a NAT
   device that supports NAT logging using IPFIX.  The document will
   specify the format of the IE's that SHOULD be logged by the NAT
   device and all the optional fields.  The fields specified in this
   document are gleaned from [RFC4787<>] and [RFC5382<>].

I can't reconcile the "MUST" with the "SHOULD" and the "optional".

[Senthil] How about

   The document will specify the format of the IE's that SHOULD be logged by the NAT
   device and all the optional fields.  The fields specified in this
   document are gleaned from [RFC4787<>] and [RFC5382<>].

The optional fields are described in the specific events. For example Table 5, describes a nat session create event,
There are a few mandatory fields and a few optional fields.

Section 5, first paragraph:

   The creation and
   deletion of NAT sessions and bindings are examples of events as it
   results in the resources (addresses and ports) being allocated or

s/as it results in the resources/as they result in resources/

[Senthil] Done.

Section 5, first paragraph:

   The events can happen either through the processing of data
   packets flowing through the NAT device or through an external entity
   installing policies on the NAT router or as a result of an
   asynchronous event like a timer.

Since this is either/or/or, simply remove the "either".
[Senthil] Yes. Done.

Section 5, first paragraph:

   The list of events are provided in Section 4.1<>.

There is no section 4.1.
[Senthil] Fixed by pointing to the table that lists the events.

Section 5, second paragraph:

   A collector may receive NAT events from multiple CGN devices and MUST
   be able to distinguish between the devices.  Each CGN device should
   have a unique source ID to identify themselves.  The source ID is
   part of the IPFIX template and data exchange.

No; this requires ID synchronisation across devices which is not required for IPFIX. IPFIX uniqueness is guaranteed by the combination of source address, source port, and source ID. The source address provides uniqueness across devices. The source port provides uniqueness when there are multiple exporters within a device (ie, the source addresses are identical). The source ID provides uniqueness when an exporter exports information from multiple unique sources (ie, the source address and source port are identical).

In IPFIX, the source ID is called the Observation Domain ID. See section 3.1 of RFC 7011.

[Senthil] Ok, the paragraph can be safely removed, as I understand?

Section 5, third paragraph:

   The templates can be
   exchanged as frequently as required given the reliability of the
   connection.  There SHOULD be a configurable timer for controlling the
   template refresh.

It's not just about the reliability of the connection. eg the collecting process could restart with no knowledge of the previously exported templates.

[Senthil] True, in the case of the restart all the exported data will be thrown away by the collector until the template refresh timer kicks in.
Are you suggesting any changes to what should/shouldn’t be said?

Section 5, third paragraph:

   NAT device SHOULD combine as many events as
   possible in a single packet to effectively utilize the network

Say "The NAT device ...".

[Senthil] Ok done.

Section 5.2, table 1:

   |        sourceIPv6Address         |     27 |   128 |  Source IPv6  |
   |                                  |        |       |    address    |

Most IPv6 addresses have more than 27 bits. The size and ID values appear to be swapped.

[Senthil] :-), Good catch, fixed now.

Section 5.3:

        The list can be expanded in the future as necessary.

Define the process for expanding the table, eg Expert Review. Consider putting the table under IANA control to avoid implementers having to refer to a chain of RFCs for the complete definition.

[Senthil] Is the process explained somewhere that I can just point to? Also, I am not clear on what you mean by “putting the table under IANA control”. Can you please elaborate?

Section 5.3, Table 2: NAT Event ID table

When / where is this table used? It seems to be an extension of the existing natEvent IE, though no mention of this is made in the IANA section and the proposed values constrain the existing "create" and "delete" events to be NAT44 specific.
[Senthil] The value of the natEvent IE uniquely identifies the event that is being reported. Do we need IANA to assign all the possible valid values that natEvent can have?

Section 5.4:

   The Quota exceeded events are generated when the hard limits set by
   the administrator has reached or exceeded.

Say "has been reached or exceeded."

The text should mention that the values are used for the natLimitEvent element in section 8.

[Senthil] Ok. Is there an example of how the values are to be specified for IANA? Thanks.

Section 5.4:

   The events that can be reported are the Maximum session entries limit
   reached, Maximum BIB entries limit reached, Maximum session/BIB
   entries per user limit reached and maximum subscribers or hosts limit

Capitalise "maximum subscribers". The "Maximum fragments pending reassembly" event isn't mentioned.

[Senthil] Done.

However there's really no reason to duplicate the information from the table in the preceding description.

Section 5.5:

The text doesn't describe the "Global Address mapping high threshold event" in Table 4.

The text should mention that the values are used for the natThresholdEvent element in section 8.

[Senthil] Ok.

Section 5.6:

   The following is the template of events that will be logged.  The
   events below are identified at the time of this writing but the set
   of events is extensible.

Describe the process for extending the list of events, eg Expert Review.

Tables 5 - 21:

There's no need to describe the size of each field since that information has already been given in Table 1.
It draws unnecessary attention to the field sizes which should be invariant.

[Senthil] I find it useful to quickly refer to it and say the size of the record. I am inclined to leave it there.

Section 5.6.5:

   The following is a template of the event.  Note that either the NAT
   pool name or the nat pool identifier SHOULD be logged, but not both.

No mention is made of how the NAT pool name could/should be logged (IPFIX IE #284). natPoolID is mandatory in Table 9 which suggests that mention of the NAT pool name should be removed from the text.
[Senthil] Right, probably a spill over from a revision that I didn’t clean up the pool name.

Sections and

   The maximum ... is generated when

Say "The maximum ... event is generated when" or "This event is generated when".


   when the administratively configured limit is reached.

Define what the limit is, eg "when the administratively configured NAT session limit is reached."


   when the administratively configured limit is reached.

Define what the limit is, eg "when the administratively configured BIB entries limit is reached."


   when a single user reaches the administratively configured limit.

Define what the limit is, eg "when a single user reaches the administratively configured IPv4 or IPv6 address limit."

[Senthil]  The limit is the number of NAT translations per user. Point taken though.

Section 5.6.8

   This event will be generated

Say, "These events will be generated"

Section 5.6.8

   The threshold reached events are described in the section above.

Please add an xref to the relevant section.


   This event is generated when the high is reached

Say, "This event is generated when the high threshold is reached"


   This is generated only by NAT devices that use a address pooling behavior of paired.

Would it be clearer to say, "... that use a paired address pooling behavior." ?

[Senthil] Ok.

Section 5.6.9

   This binding event happens when the first packet of the first flow
   from a host in the private realm.

Say, "These binding events happen when". The remainder of the sentence seems incomplete?

Section 7:


Section 9:

   Some management considerations is covered


Section 9.1:

   An IPFIX collector MUST be able to collect events from multiple NAT
   devices and be able to decipher events based on the sourceID in the
   IPFIX header.

s/sourceID/Observation Domain ID/ per RFC 7011, section 3.1.

Section 11.2:

The References to [RFC5101bis] and [RFC5102bis] should be updated to RFC7011 and RFC7012 respectively.

[Senthil] Done for the above items.