Re: [v6ops] management and ipv6

Jeroen Massar <jeroen@unfix.org> Fri, 17 December 2010 19:30 UTC

Return-Path: <jeroen@unfix.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C70DC3A6992 for <v6ops@core3.amsl.com>; Fri, 17 Dec 2010 11:30:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iy86urxUfhof for <v6ops@core3.amsl.com>; Fri, 17 Dec 2010 11:30:31 -0800 (PST)
Received: from abaddon.unfix.org (abaddon.unfix.org [62.220.146.203]) by core3.amsl.com (Postfix) with ESMTP id A66A23A6957 for <v6ops@ietf.org>; Fri, 17 Dec 2010 11:30:31 -0800 (PST)
Received: from [IPv6:2001:41e0:ff42:99:222:cfff:fe31:ce41] (spaghetti.ch.unfix.org [IPv6:2001:41e0:ff42:99:222:cfff:fe31:ce41]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by abaddon.unfix.org (Postfix) with ESMTPSA id AC0B321476; Fri, 17 Dec 2010 20:31:55 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unfix.org; s=DKIM2009; t=1292614336; bh=5OfXb8+noz+p7sVPGy5J5mofLs8rdBzv4E9I4K9jV98=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=bLdSCuMtu9MNcVwT5IGB3jVNSt4pMiTBluMsY7Hg3lSTc5Oe1YGOkARvy3BTNpww3 exiPDKR9aYGrX0TC3bdrMvMY56KuvTnFl4MfLK4BolxwjeNTnU2SuzmvlHsZETl8A0 uP11e5gXbChRDT5jwPj3q2rQFh5jCBhxK1Kb/+qjtvY78x8+HYun3LuFoznUCqJhCn Hkb6LLjLuGm5jRMgi8leuEyIgiWKBxuy6H7YGQ8YnnK8uLn8BhBLxlWg7RFoygFPKr pQ/M+2eaNqqPqfXLzA3G3/cSwSaJ79jrIDILrRHIoDAxsuz579yDaayKb7K8fAsgUb 3NoSpYaiG8QuA==
Message-ID: <4D0BBAB5.9050706@unfix.org>
Date: Fri, 17 Dec 2010 20:32:05 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4D0A5F29.1050502@piuha.net> <4D0AF5BC.2050808@bogus.com> <4D0BB9AD.4050209@gmail.com>
In-Reply-To: <4D0BB9AD.4050209@gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, 'IPv6 Operations' <v6ops@ietf.org>
Subject: Re: [v6ops] management and ipv6
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Dec 2010 19:30:32 -0000

On 2010-12-17 20:27, Brian E Carpenter wrote:
> On 2010-12-17 18:31, Joel Jaeggli wrote:
>> On 12/16/10 10:49 AM, Jari Arkko wrote:
>>> In the course of discussing draft-arkko-ipv6-transition-guidelines in
>>> the IESG, Dan and other IESG members brought up the need to talk about
>>> management in IPv6 networks. For instance, in IPv6-only networks all
>>> your management tools have to be capable of IPv6, both in dual stack and
>>> IPv6-only you want your data models to support IPv6, in dual stack you
>>> need to monitor reachability and errors not just in IPv4 but also in
>>> IPv6, and so on.
>>
>> what version of netflow you use is also germain for example.
> 
> I think you might mean ipfix, in the IETF context. Making sure that
> ipfix is 100% ipv6-safe is important.

NetFlow v9 does IPv6, and IPFIX (NetFlow v10) does it in exactly the
same way, there is just a minor header difference in the packets.

That is the protocol though, if the tools actually understand it is a
different question, but by now I think most major tools have support for
IPv6 for both transport of IPFIX/NFv9 and the fields transported by it.

Now, getting physical gear that sends the exports transporting it using
IPv6 might be another thing though ;)

Greets,
 Jeroen