Re: [BEHAVE] New Version Notification for draft-sivakumar-behave-nat-logging-04.txt

Simon Perreault <simon.perreault@viagenie.ca> Mon, 18 June 2012 20:35 UTC

Return-Path: <simon.perreault@viagenie.ca>
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 F0E1C11E80A3 for <behave@ietfa.amsl.com>; Mon, 18 Jun 2012 13:35:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZpgbwpVTEYNN for <behave@ietfa.amsl.com>; Mon, 18 Jun 2012 13:35:07 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 0A7E011E8095 for <behave@ietf.org>; Mon, 18 Jun 2012 13:35:07 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c064:ec6c:4066:6efd:d9f4]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 64CEA400AB for <behave@ietf.org>; Mon, 18 Jun 2012 16:35:06 -0400 (EDT)
Message-ID: <4FDF90F9.3010704@viagenie.ca>
Date: Mon, 18 Jun 2012 16:35:05 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1
MIME-Version: 1.0
To: behave@ietf.org
References: <CBFF8018.21370%ssenthil@cisco.com>
In-Reply-To: <CBFF8018.21370%ssenthil@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [BEHAVE] New Version Notification for draft-sivakumar-behave-nat-logging-04.txt
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 18 Jun 2012 20:35:08 -0000

On 2012-06-15 14:52, Senthil Sivakumar wrote:
> A new version of the logging draft is posted that is focused towards using
> IPFIX Information
> Elements for NAT logging. Please review and provide feedback.

Looks good!

Question: why did you unite vlan ID and VRF ID? Aren't they orthogonal 
things?

Observation: the term BIB is defined in RFC6146 but only in the context 
of NAT64. Yet this draft uses it in the context of NAT44. I foresee 
problems. For example, it is not clear how a fully symmetric NAT (which 
has no BIB) would use this. Would it only log session events and never 
BIB events? Also, what about NATs that don't track sessions? Would they 
just log BIB events and never session events?

What about NAT46 and NAT66? Are they supported?

Lastly, I see feature overlap between this draft and the MIB draft for 
the addresses exhausted, ports exhausted, and quota exceeded event. Do 
we really want to provide two ways of doing the same thing?

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca