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

"Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com> Mon, 15 February 2016 16:41 UTC

Return-Path: <ssenthil@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53A461A0049; Mon, 15 Feb 2016 08:41:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.506
X-Spam-Level:
X-Spam-Status: No, score=-14.506 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.006, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 hm3yI4vcBnLG; Mon, 15 Feb 2016 08:41:00 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBB971A87DE; Mon, 15 Feb 2016 08:40:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=41694; q=dns/txt; s=iport; t=1455554459; x=1456764059; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=tJAImbhee+ckeL04X2ne1nAFIYpz2jWicgoY/fMY2ro=; b=eOXg/AHlvkGA4pW80YBhj3e2colByHgc1wHurnA59icB9g5gh1VMhG3e 3nZnqwIk/1Nheit+T+fPC/wRPZEyA1buQzHiyNuNjBHYPy0EGozw8/3Gk R1v1JNiCh+a6Ai2ld03FltKalwFn9H4uaJ5aeuaxjJuAWUXBdB8mWmbLy o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D9AQAH/8FW/4gNJK1UCoJuTFJtBrgEg?= =?us-ascii?q?hMBDYFnIIVtAoE1OBQBAQEBAQEBgQqEQQEBAQQaUQ4QAgEIDgMDAQIhAQIEBzI?= =?us-ascii?q?UCQgCBAENBYgaDrwyAQEBAQEBAQEBAQEBAQEBAQEBAQEBEQSKRoQAAQIFBQo7F?= =?us-ascii?q?oQEBYVNh1qFNIQeAYVOgm2CZII1gVyEQ4QdhDiOPQEeAQFCgX0FGRSBNGoBAQG?= =?us-ascii?q?HPAEfHXwBAQE?=
X-IronPort-AV: E=Sophos; i="5.22,451,1449532800"; d="scan'208,217"; a="76285823"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 Feb 2016 16:40:58 +0000
Received: from XCH-ALN-009.cisco.com (xch-aln-009.cisco.com [173.36.7.19]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u1FGewTD030797 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 15 Feb 2016 16:40:58 GMT
Received: from xch-aln-007.cisco.com (173.36.7.17) by XCH-ALN-009.cisco.com (173.36.7.19) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 15 Feb 2016 10:40:57 -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.1104.009; Mon, 15 Feb 2016 10:40:57 -0600
From: "Senthil Sivakumar (ssenthil)" <ssenthil@cisco.com>
To: Paul Aitken <paitken@brocade.com>, "draft-ietf-behave-ipfix-nat-logging@ietf.org" <draft-ietf-behave-ipfix-nat-logging@ietf.org>
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: AQHRZNm5lzhUvHrQNUCIztsT3jxre58pJQsAgAEeHwCAAyMtgA==
Date: Mon, 15 Feb 2016 16:40:57 +0000
Message-ID: <D2E764D8.168A91%ssenthil@cisco.com>
References: <56BC9C63.3080404@brocade.com> <D2E3BF4A.168243%ssenthil@cisco.com> <56BF1786.5090607@brocade.com>
In-Reply-To: <56BF1786.5090607@brocade.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.0.151221
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.211.251]
Content-Type: multipart/alternative; boundary="_000_D2E764D8168A91ssenthilciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/iVzKFSTJ3mXGBIk2Mrq1bwxXC3A>
X-Mailman-Approved-At: Tue, 16 Feb 2016 08:13:38 -0800
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2016 16:41:05 -0000

Hi Paul,
Please look for [Senthil2].

From: Paul Aitken <paitken@brocade.com<mailto:paitken@brocade.com>>
Date: Saturday, February 13, 2016 at 6:46 AM
To: Senthil Sivakumar <ssenthil@cisco.com<mailto:ssenthil@cisco.com>>, "draft-ietf-behave-ipfix-nat-logging@ietf.org<mailto:draft-ietf-behave-ipfix-nat-logging@ietf.org>" <draft-ietf-behave-ipfix-nat-logging@ietf.org<mailto:draft-ietf-behave-ipfix-nat-logging@ietf.org>>
Cc: "ietf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf.org<mailto:ietf@ietf.org>>
Subject: Re: Last Call: <draft-ietf-behave-ipfix-nat-logging-06.txt> (IPFIX Information Elements for logging NAT Events)

Senthil,

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.

Replies inline @@PJ2.


From: Paul Aitken <<mailto:paitken@brocade.com>paitken@brocade.com<mailto:paitken@brocade.com>>
Date: Thursday, February 11, 2016 at 9:36 AM
To: "<mailto:draft-ietf-behave-ipfix-nat-logging@ietf.org>draft-ietf-behave-ipfix-nat-logging@ietf.org<mailto:draft-ietf-behave-ipfix-nat-logging@ietf.org>" <draft-ietf-behave-ipfix-nat-logging@ietf.org<mailto:draft-ietf-behave-ipfix-nat-logging@ietf.org>>
Cc: "<mailto:ietf@ietf.org>ietf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf.org<mailto:ietf@ietf.org>>
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<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc4787&d=CwMF-g&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=aFOj9PLeooXMHRXima8gIP54ipb4rlFwPk4XSgkDnFs&s=fPl32NCjRXlcp_YL261dUPyU67jiIq7tyzzfC7tKpvw&e=>] and [RFC5382<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc5382&d=CwMF-g&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=aFOj9PLeooXMHRXima8gIP54ipb4rlFwPk4XSgkDnFs&s=16Ab6VcDIcMdMKTX968UOAJXu7V-HfXqiwrnDfs0EAk&e=>]7V-HfXqiwrnDfs0EAk&e=>].

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<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc4787&d=CwMF-g&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=aFOj9PLeooXMHRXima8gIP54ipb4rlFwPk4XSgkDnFs&s=fPl32NCjRXlcp_YL261dUPyU67jiIq7tyzzfC7tKpvw&e=>] and [RFC5382<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc5382&d=CwMF-g&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=aFOj9PLeooXMHRXima8gIP54ipb4rlFwPk4XSgkDnFs&s=16Ab6VcDIcMdMKTX968UOAJXu7V-HfXqiwrnDfs0EAk&e=>]7V-HfXqiwrnDfs0EAk&e=>].

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.

@@PJ2 The MUST was good since this is a standards track document. Whereas SHOULD gives wiggle room for RFC-compliant but non-interoperable implementations.

How about this:

   This document details
   the IPFIX Information Elements(IEs) that MUST be logged by a NAT
   device that supports NAT logging using IPFIX,   and all the optional fields.  The fields specified in this
   document are gleaned from [RFC4787<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc4787&d=CwMF-g&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=aFOj9PLeooXMHRXima8gIP54ipb4rlFwPk4XSgkDnFs&s=fPl32NCjRXlcp_YL261dUPyU67jiIq7tyzzfC7tKpvw&e=>] and [RFC5382<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc5382&d=CwMF-g&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=aFOj9PLeooXMHRXima8gIP54ipb4rlFwPk4XSgkDnFs&s=16Ab6VcDIcMdMKTX968UOAJXu7V-HfXqiwrnDfs0EAk&e=>]7V-HfXqiwrnDfs0EAk&e=>].



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
   freed.

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<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Dbehave-2Dipfix-2Dnat-2Dlogging-2D06-23section-2D4.1&d=CwMF-g&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=aFOj9PLeooXMHRXima8gIP54ipb4rlFwPk4XSgkDnFs&s=wWv4DJ-C66KkaISni6E6o7kuLUdi-NXOQiPBAl6ITcI&e=>LUdi-NXOQiPBAl6ITcI&e=>.

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?

@@PJ2: It could be removed, or clarity the issue for readers who may not be familiar with IPFIX, eg:


   A collector may receive NAT events from multiple CGN devices. The collector
   distinguishes between the devices using the source IP address, source port,
   and Observation Domain ID in the IPFIX header.


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?

@@PJ Consider adding an xref to section 8.4 of RFC 7011 which specifically mentions template refresh for UDP.



Section 5, third paragraph:

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

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?

@@PJ2: If this is to be a standard table that everyone can use and anyone can potentially define new values, then we need to know who controls the allocation of new entries and how those are requested. Where/how are the new values defined, and who reviews / approves the allocation?

See section 4.1 of RFC5226.

eg, new IPFIX fields are requested through IANA, who asks a designated group of experts to review and approve them. It could make sense to define the table in an IANA registry with a designated expert, possibly even as a sub-table in IANA's IPFIX registry.

[Senthil2] There is already an entry in IPFIX IANA registry for natEvent. There are 3 events (create/delete/pool exhausted) defined there. So I will add text to point to IPFIX IANA registry.
I assume I have to add the additional events to the IANA considerations section of this draft to have IANA assign these. However, I am not clear how do I request these new values for
natEvent.  Is the following the right format to ask for the new values?

Name : natEvent

   Description: This Information Element identifies an Instance of the
   NAT that runs on a NAT middlebox function after the packet passed the
   Observation Point.

   Abstract Data Type: unsigned8

   Data Type Semantics: identifier

   Element ID : 230

   New values requested : The values 4-16 are requested as described in Table 2.

   Reference:

   See RFC 3022 [RFC3022] for the definition of NAT.  See RFC
   3234 [RFC3234] for the definition of middleboxes.

Thanks
Senthil


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?

@@PJ2: It isn't clear whether this table defines new values for the natEvent IE. If so then it needs to be discussed in the IANA section of the draft because the new values must be requested through IANA.

[Senthil2]. Yes, it does. I will add this to the IANA section.

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.

@@PJ2: See section 6 of RFC7012



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
   reached.

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.

@@PJ2: see the discussion above.


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.

@@PJ2: OK.


P.


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 5.6.7.1 and 5.6.7.2:

   The maximum ... is generated when

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



Section 5.6.7.1:

   when the administratively configured limit is reached.

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



Section 5.6.7.2:

   when the administratively configured limit is reached.

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



Section 5.6.7.3:

   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.



Section 5.6.8.4

   This event is generated when the high is reached

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



Section 5.6.8.4

   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:

s/Trammel/Trammell/



Section 9:

   Some management considerations is covered

s/is/are/



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.
P.