IETF Logo Mail Archive

Re: [v6ops] management and ipv6

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 17 December 2010 19:26 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 C91C03A6992 for <v6ops@core3.amsl.com>; Fri, 17 Dec 2010 11:26:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.346
X-Spam-Level:
X-Spam-Status: No, score=-103.346 tagged_above=-999 required=5 tests=[AWL=0.253, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 I3DAvreIkQRA for <v6ops@core3.amsl.com>; Fri, 17 Dec 2010 11:26:02 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 0B3FD3A6957 for <v6ops@ietf.org>; Fri, 17 Dec 2010 11:26:01 -0800 (PST)
Received: by vws7 with SMTP id 7so363611vws.31 for <v6ops@ietf.org>; Fri, 17 Dec 2010 11:27:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=C28NE3TzglfWKhicSyN8fqb4K4XNGLxAvGTTg3PcBoo=; b=fpZycvcqiI4aPTZaBvfMxHDC+RuRGWUigbfBwYqMuzkgskNd00Nx4raxjPfOPu6XwB BeWeps9ZV9Ul2t1HUHK2XGPbXhFXFUWhmCb4QYXTIB5Hh9Ob8m8qa0ezxtm3B1wmuubP D14nlrT6g6CM5PlFPUUJSsTrDpaB4/D77j8C0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=bwyxgRm9Gj8kq+K3mQOtC/bbI2iC1IsSEnirK5tDnRxJmlPoYEYdUaxlHV1yHaMgXu kpCXli84kGQuosHO2Trm8hqV5jjSL5IcwazFEjtiGQexlyetxhjx4FJPZ2u0HNB2tbWM zu/H1A3HVuQ1qJLVG4YIaZFBYkZuxsp9245bU=
Received: by 10.220.180.66 with SMTP id bt2mr372059vcb.134.1292614068141; Fri, 17 Dec 2010 11:27:48 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id r11sm248144vbx.11.2010.12.17.11.27.45 (version=SSLv3 cipher=RC4-MD5); Fri, 17 Dec 2010 11:27:47 -0800 (PST)
Message-ID: <4D0BB9AD.4050209@gmail.com>
Date: Sat, 18 Dec 2010 08:27:41 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Joel Jaeggli <joelja@bogus.com>
References: <4D0A5F29.1050502@piuha.net> <4D0AF5BC.2050808@bogus.com>
In-Reply-To: <4D0AF5BC.2050808@bogus.com>
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:26:02 -0000

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.

    Brian

v2.23.0 | Report a Bug | By Email